Author Topic: Bcx EDitor (BED)  (Read 509 times)

MrBcx

  • Administrator
  • Hero Member
  • *****
  • Posts: 749
    • View Profile
Bcx EDitor (BED)
« on: December 14, 2020, 07:46:53 PM »
This is BED ... short for Bcx EDitor


It is a modified version of BCXIDE (2005) by Mike Henning.

I don't consider BED to be an IDE - it is a code editor tailored for BCX users.


It's notable features include:

It uses a dark theme that I have devised.

Most ( all? ) BCX keywords are syntax highlited in BLUE

Many Win32 functions and constants are highlited in RED

Normal text is highlited in GREEN

The syntax files are in \Bed\Syntax\

Hi-Light-Other.Txt can contain words of your choosing ( currently empty ).

Colors can be changed via  Tools | Configure on the main menu

Macros have been added to the main menu (You can add more but requires a recompile).

Search and Replace text is now preserved between sessions via the Bed.ini file.

Several BCX related tools are included under the tool menu

The latest BCX and Win32 help CHM's are included.



Simply unzip into the root of your C drive and you'll be off to the races.

If you install anywhere besides C:\Bed, you will need to edit the Bed.ini file.

If you want to recompile Bed.exe, I recommend using Pelles C v10.

The included compiler manager has not changed since 2005 and I don't personally use it.

I consider BED a work-in-progress but I have been using it in various stages of development
for many years.  It has never crashed or caused problems for me -- YMMV.

If you want to change the fonts or font size in the editor or in the SUB/FUNCTION Navigator, you can
change the following constants in BED.BAS and recompile.  The fonts and sizes that I've chosen work
well for me -- YMMV

« Last Edit: December 14, 2020, 07:49:39 PM by MrBcx »

dgarner

  • Newbie
  • *
  • Posts: 33
    • View Profile
Re: Bcx EDitor (BED)
« Reply #1 on: December 14, 2020, 10:00:52 PM »
Thanks, MrBcx, for sharing BED.

I downloaded the .zip file and saved it to my BCX folder.  I then double clicked the .zip file in Windows Explorer and copied the Bed folder into c:\ .  I double clicked the Bed.exe and the editor window launched.  I dragged it from my 4K monitor to the standard 1K? monitor.  That makes things larger (easier to see).

I then decided to click the Help menu option.  Clicked on About and glanced at it and closed it.  Then clicked on the BCX Help option at the top of the Help menu popup.  The help file launched.  Clicked on Contents in the Help file. ...

Short story longer, I had to right click each help file under the Tools folder and under the properties option, toward the bottom, right hand side of the dialog, click and apply the Unblock checkbox.  I think I needed to close the Help and BCX Editor and launch them again to see the contents in the right hand window of the help file interface.  All four files under Tools/Help/ had an Unblock checkbox option.

I suspect this is not news to many of us who have been here for a while, but might be news to someone.  Thanks Robert, for cluing me in  10 or 15 years ago.


MrBcx

  • Administrator
  • Hero Member
  • *****
  • Posts: 749
    • View Profile
Re: Bcx EDitor (BED)
« Reply #2 on: December 15, 2020, 12:35:24 AM »
David -- Thanks for posting the unblocking tips.

dgarner

  • Newbie
  • *
  • Posts: 33
    • View Profile
Re: Bcx EDitor (BED)
« Reply #3 on: December 15, 2020, 07:40:25 AM »
I woke up this morning thinking, that I did not mention, the attempt that Windows made, to protect me from the Bcx Editor.  Evidently, Windows does not know how popular Bcx EDitor is.  It popped up a blue screen warning me that I was entering into mirky territory if I continued to execute it.

I instinctively clicked the links and buttons to tell Clippy to get out of the way.

This reminds me of the news article that I saw recently, about Microsoft 365 being the conduit for security breaches at some major organizations.  I would not be surprised to learn that Clippy was behind those events too.

On another note, how would one avoid the security warnings, and almost silent access blocking of help files, if one were to use BCX to create a program for the general masses?  Does it involve paying a Microsoft tax for some kind of certificate, or is there some manifest file that could be created, to circumvent the spurious warnings?

Anyone know the right way to address such issues?


MrBcx

  • Administrator
  • Hero Member
  • *****
  • Posts: 749
    • View Profile
Re: Bcx EDitor (BED)
« Reply #4 on: December 15, 2020, 08:16:46 AM »
BED.exe was linked with BED.res which contains the following manifest. 

The <!-- Trustinfo section --> has long been one piece of the Windows Security "STFU" puzzle. 
On my PC's, I keep automatic updates and daily scans enabled. 

Code: [Select]
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
   <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

      <assemblyIdentity version="1.0.0.0"
         processorArchitecture="X86"
         name="ApplicationName"
         type="win32"/>
      <description>Optional description of your application</description>


  <windowsSettings>
  <dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2</dpiAwareness>
  <dpiAware>true</dpiAware>
  </windowsSettings>

      <!-- Compatibility section -->
      <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
         <application>
            <!--The ID below indicates application support for Windows Vista -->
            <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
            <!--The ID below indicates application support for Windows 7 -->
            <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
            <!--This Id value indicates the application supports Windows 8 functionality-->
            <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
            <!--This Id value indicates the application supports Windows 8.1 functionality-->
            <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
            <!-- This Id value indicates the application supports Windows 10 functionality-->
            <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>           
         </application>
       </compatibility>

      <!-- Trustinfo section -->
      <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
         <security>
            <requestedPrivileges>
               <requestedExecutionLevel
                  level="asInvoker"
                  uiAccess="false"/>
               </requestedPrivileges>
         </security>
      </trustInfo>

      <dependency>
         <dependentAssembly>
            <assemblyIdentity
               type="win32"
               name="Microsoft.Windows.Common-Controls"
               version="6.0.0.0"
               processorArchitecture="X86"
               publicKeyToken="6595b64144ccf1df"
               language="*" />
         </dependentAssembly>
      </dependency>

   </assembly>

Robert

  • Hero Member
  • *****
  • Posts: 580
    • View Profile
Re: Bcx EDitor (BED)
« Reply #5 on: December 15, 2020, 02:01:07 PM »
I woke up this morning thinking, that I did not mention, the attempt that Windows made, to protect me from the Bcx Editor.  Evidently, Windows does not know how popular Bcx EDitor is.  It popped up a blue screen warning me that I was entering into mirky territory if I continued to execute it.

I instinctively clicked the links and buttons to tell Clippy to get out of the way.

This reminds me of the news article that I saw recently, about Microsoft 365 being the conduit for security breaches at some major organizations.  I would not be surprised to learn that Clippy was behind those events too.

On another note, how would one avoid the security warnings, and almost silent access blocking of help files, if one were to use BCX to create a program for the general masses?  Does it involve paying a Microsoft tax for some kind of certificate, or is there some manifest file that could be created, to circumvent the spurious warnings?

Anyone know the right way to address such issues?

Several engines of VirusTotal and Jotti, flag BED.zip as a poxy piece of work including ESet and Sophos.

MrBcx

  • Administrator
  • Hero Member
  • *****
  • Posts: 749
    • View Profile
Re: Bcx EDitor (BED)
« Reply #6 on: December 15, 2020, 02:33:58 PM »
Below are 38 AV engines that did not detect problems. 
Windows Defender offline scanner also found no problems. 
I suppose one can unzip Bed.zip and do independent scans of the .exe and .chm files
If anyone is uncomfortable unzipping Bed.zip, it's probably best to delete it and move on.

Ad-Aware
AegisLab
Alibaba
Antiy-AVL
Avast-Mobile
Avira (no cloud)
BitDefenderTheta
CAT-QuickHeal
CMC
Comodo
Cynet
Elastic
eScan
ESET-NOD32
F-Secure
Fortinet
Gridinsoft
Ikarus
Jiangmin
K7AntiVirus
K7GW
Kaspersky
Malwarebytes
NANO-Antivirus
Panda
Qihoo-360
Rising
SentinelOne (Static ML)
SUPERAntiSpyware
Symantec
TACHYON
Tencent
TrendMicro
TrendMicro-HouseCall
VBA32
VIPRE
ViRobot
ZoneAlarm by Check Point

dgarner

  • Newbie
  • *
  • Posts: 33
    • View Profile
Re: Bcx EDitor (BED)
« Reply #7 on: December 15, 2020, 10:12:15 PM »
I don't think there is any issue with malware/antivirus in this case.

Windows evidently keeps track of which programs it sees frequently? or has verified before?  Or maybe it's based on ?  Could be anything they want I guess.




MrBcx

  • Administrator
  • Hero Member
  • *****
  • Posts: 749
    • View Profile
Re: Bcx EDitor (BED)
« Reply #8 on: December 16, 2020, 08:51:52 AM »
The ever-increasing number of companies offering AV software clearly indicates the presence of "profit motive".

The more companies that participate in that business, the more false positives will be detected.

I figured that out a long time ago.  The following article is worth a read.

https://www.pcworld.com/article/3434097/why-you-can-stop-paying-for-antivirus-software.html



iancasey

  • Newbie
  • *
  • Posts: 45
    • View Profile
Re: Bcx EDitor (BED)
« Reply #9 on: December 16, 2020, 10:13:34 AM »
I was giving this a try :-) but when compiling a console file with PellesC I get
'pc32' is not recognized as an internal or external command,
Is this file missing from the download?


MrBcx

  • Administrator
  • Hero Member
  • *****
  • Posts: 749
    • View Profile
Re: Bcx EDitor (BED)
« Reply #10 on: December 16, 2020, 11:52:38 AM »
Ian,

Looks like the Compiler Manager is not completely original, as the PELLES section uses my 3 Pelles batch files. 

Sorry about that ...

See attached:

iancasey

  • Newbie
  • *
  • Posts: 45
    • View Profile
Re: Bcx EDitor (BED)
« Reply #11 on: December 16, 2020, 03:22:12 PM »
Thanks Kevin,
that worked

Ian

GSAC3

  • Newbie
  • *
  • Posts: 16
    • View Profile
Re: Bcx EDitor (BED)
« Reply #12 on: February 04, 2021, 05:05:23 PM »
Kevin:

Downloaded BED and properly installed in C root.  When I tried to run BED, it did not respond at all.  I then tried to rebuild the source using BCX 731 with PellesC 10.  The C code generated with BCX 732 would not compile with either PellesC 8 or 10. But after rebuilding again with BCX 761 the C code built properly with both PellesC 8 and 10.  BED works fine now and is a great BCX editot.  Thanks.
Don

MrBcx

  • Administrator
  • Hero Member
  • *****
  • Posts: 749
    • View Profile
Re: Bcx EDitor (BED)
« Reply #13 on: February 04, 2021, 05:47:53 PM »
Hi Don,

Recompiling BED.exe using BCX versions 761 (and newer) plus Pelles C v10 should always get the job done.

Glad you like it ... I like it too  ;D