*************** WinBatch+Comiler 2021D release ***************

[td]

WinBatch, WebBatch, and WinBatch+Compiler 2021D are now available for download.

Customers with a current license may download the latest version of the software from the download page.

https://www.winbatch.com/download.html - use the "Click here to download WinBatch+Compiler" link.

If you do not have a current license and are interested in this and future releases, please visit our software purchase page. You can easily order online.

https://commerce.winbatch.com


Release notes:


WB 2021D Oct 22, 2021   

DLL 6.21dud First appearing in WB 2021D

   Add the JSON extender to the Consolidated WIL Help system, the WIL Syntax Analyzer, and
   WinBatch Studio menu and syntax colorizing systems.

   Corrected 8-bit characters in WIL Map key names causing a memory exception when the key name
   is added to a WIL Map.

   Address problem in the ObjectClrNew function that caused 64-bit integers class constructor
   parameters to be truncated to 32-bits.

   WinBatch Studio
    Increased limit on the size of strings representation of values in map key/value pairs when
    they are displayed in the "Array View" window. This change also addresses a problem with
    corrupted display data caused by long string values.

[jmburton2001]

Release notes:

WB 2021D Oct 22, 2021   

   Corrected 8-bit characters in WIL Map key names causing a memory exception when the key name
   is added to a WIL Map.

Hi Tony,

I've been anxiously awaiting a release for this issue (because I'm lazy) --> https://forum.winbatch.com/index.php?topic=2681.0

Is this the release I've been waiting yearning for? If so, have you tested it against the script and raw data from the above referenced post?  :)

[td]

This release has not been tested against your script. Instead, the release was tested using ILC's regular testing procedures that target all code modifications. It was also tested using the regression test suite. Regression testing involves test cases that attempt to recreate defects that are supposedly fixed by the current and previous releases. 

I think you will find your Map problem has been corrected although your script may still have some problems not related to WinBatch defects.

And sorry it took so long. This update patch was targeted for a late August or early September release date but a lot of stuff happened...

[jmburton2001]

...although your script may still have some problems not related to WinBatch defects.

That's an understatement. Best case scenario I'm a kludgy hobbyist/tinkerer. Worst case? I "sometimes" know how to open Notepad!  ;)

Thanks for this update! I'm hoping to try it out before the end of the year.

[td]

FWIW. Managed to test your script. The WIL map functions work with your data now.

[jmburton2001]

FWIF. Managed to test your script.

You didn't have to do that but you did soooo, it's priceless!

Thank you Tony! You're awesome!  8)

[jmburton2001]

FWIW. Managed to test your script. The WIL map functions work with your data now.

Hi Tony!

I purchased and installed Winbatch 2021D and the strangest thing happened. I changed the extender at the beginning of the script (as follows) in order to compile a 64 bit version.

I had previously compiled that same script with the Winbatch 2019A 32 bit compiler with no ill effects.

Code (winbatch) Select Expand

IntControl (49, 1, 0, 0, 0)
;AddExtender("wwsop34i.DLL")
AddExtender('WWSOP64I.DLL')

HomeLoc = DirScript()
DirChange (HomeLoc)
LogViewRaw = "RawRecordings.txt"


Windows Defender obliterated (well, it's actually quarantined) the executable from my system with the following warning.



The only changes between the script you tested and this compiled version are:

• Changing the Shell Ops extender to 64 bit.
• Appended "64" to the executable name.

Do you have any insights or pointers?

EDIT Additional observations - I scanned every "expanded" component extracted from the executable (Nirsoft's FullEventLogView.exe, WBDUD64I.DLL, and wwsop64i.dll plus a cfg file) and they all came back clean.

I also changed the Shell Ops back to "wwsop34i.DLL" and then compiled it with the 32 bit compiler. That came back clean when scanned.

[td]

False positives are an all too common problem with so-called "antimalware" products. You will need to white list your executable.

[td]

Other steps to take include performing a proper install of your compiled scripts. That means placing them in a secure folder. Codesigning also helps but it has the cost of a certificate associated with it.  There are Websites that offer free code signing but I can't recommend them.

[td]

Just to clarify, MSFT calls secured folders "protected" folders which means that only "admins", "trusted installer", and "system" can write to the folder. The "Program Files" folder is a commonly referred to example.

[jmburton2001]

Thanks Tony!

It appears that the days of the "portable app" tinkerer/hobbyist is over. The two (maybe three+) people on the planet that use the utilities I write will either have to whitelist them or simply not use them. I'm not industrious enough to mess around with code signing or creating a trusted installer for them. I've created trusted installers in the past but the things I do now just aren't worth the extra effort.

Now I'm from the "drop the executable in a random folder and double-click to run" community.

I'll never stop using Winbatch though. It's just too flexible, comprehensive, and easy to use. I've been a user (and a fan) since the mid 1990s and will remain so for life!

Thank you for everything!  ;)

[stanl]

Now I'm from the "drop the executable in a random folder and double-click to run" community.

I'm a member. I used to rename .exe => .zip and have users rename after extracting if sent by email, or if from a dropbox account I had them set up and give me full access. If I do a WB update at home the .exe's get flagged by Avast.... get the pop-up with "we are sending to our lab for checking"... which I don't really believe but it settles after 5-10 seconds. At work, McAfee will let an .exe run, but internal IT security will flag the user if they run it from their hard drive [both WB and compiled Powershell].


There is always something, but security is always assumed with best intentions :-\

[td]

Thanks Tony!

It appears that the days of the "portable app" tinkerer/hobbyist is over. The two (maybe three+) people on the planet that use the utilities I write will either have to whitelist them or simply not use them. I'm not industrious enough to mess around with code signing or creating a trusted installer for them. I've created trusted installers in the past but the things I do now just aren't worth the extra effort.

Now I'm from the "drop the executable in a random folder and double-click to run" community.

I'll never stop using Winbatch though. It's just too flexible, comprehensive, and easy to use. I've been a user (and a fan) since the mid 1990s and will remain so for life!

Thank you for everything!  ;)

There are not any guarantees that placing an executable in a folder under "Program Files" prevents that attack of the antimalware malware but it is known to work. All you need to do is create a folder under "Program Files" or "Program Files X86" and copy the exe to it. Of course, you need to perform the creation and copy from an admin account. You may need to compile using the small exe and include any extenders and the WIL DLL as separate files. This is because the exe will not be able to extract files unless it is executed the first time by an admin and you use the UAC "highestAvailable" setting.

[jmburton2001]

My love affair with computers started when I watched the original premiere episode of Star Trek when I was a wee lad and years later when I wrote my first program in FORTRAN on a teletype machine. Having gone through the phases of needing to be bleeding edge, cutting edge, current edge, (and spending tens of thousands, probably more) I'm now in the "old codger" phase of my life.

I'll continue to write custom utilities that make MY life easier, but I'm just not interested in writing them for others.

As mentioned previously... I'll "ride or die" with Winbatch for whatever time I have left. It has been a constant (and a lifesaver) for decades. Thank you for taking up the mantle and keeping Winbatch alive!  ;D

PS -> One of my proudest moments was when one of my scripts was memorialized in the Tech Database.

[kdmoyers]

One of my proudest moments...

My proudest moment was the time Marty called me an "unreconstructed hacker."  Not entirely sure what he meant, but I beamed for a week.
-Kirby

[td]

My love affair with computers started when I watched the original premiere episode of Star Trek when I was a wee lad and years later when I wrote my first program in FORTRAN on a teletype machine. Having gone through the phases of needing to be bleeding edge, cutting edge, current edge, (and spending tens of thousands, probably more) I'm now in the "old codger" phase of my life.

I'll continue to write custom utilities that make MY life easier, but I'm just not interested in writing them for others.

I guess I mentioned the protected folder business for the lurking followers of this thread but as Captain Burnham says, "Let's go."