06/02/2016
Topic:
Autorun 32 or 64 bit version of app
ZeDingo
|
IsOS_64bit() {
; Returns TRUE for 64bit OS
Return (FileExist("C:\Program Files (x86)")) ? 1 : 0
}
Not everyone has Windows installed on C:. You should use "%SYSTEMDRIVE%\Program Files (x86)", or check either PROCESSOR_ARCHITECTURE or PROCESSOR_ARCHITEW6432 is AMD64 or IA64.
PROCESSOR_ARCHITEW6432 will be AMD64 or IA64 when running via WOW64.
PROCESSOR_ARCHITECTURE will be AMD64 or IA64 when running 64-bit native.
And just in case everything's running in 32-bit mode on a 64-bit machine, launch the 64-bit app with %SYSTEMROOT%\sysnative\cmd.exe /c
HOWTO: Detect Process Bitness
EM64T is another possible value of PROCESSOR_ARCHITECTURE, but quite rare.
Possible values of %PROCESSOR_ARCHITECTURE% |
25/02/2016
Topic:
Small bug in SPS Builder v1.1.2 when form is blank
ZeDingo
|
Every "Insert multiline text" button, every "Insert list" button, "Validate" button, and "Save" button throw an exception when all fields are empty:
************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'System.Query, Version=1.0.2319.19041, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'System.Query, Version=1.0.2319.19041, Culture=neutral, PublicKeyToken=null'
at SPSBuilder.formMain.TextboxAndButton_ClickButton(Object sender, EventArgs e)
at SPSBuilder.Controls.TextboxAndButton.btnOpenDetail_Click(Object sender, EventArgs e)
I'm aware that it's a situation like "Doctor, it hurts when I poke myself in the eye!" but an uncaught exception is always worth a report. |
26/02/2016
Topic:
Small bug in SPS Builder v1.1.2 when form is blank
ZeDingo
|
Sure enough, that's what it was. I must have ran the exe straight out of the zip from PowerArchiver. The beer probably didn't help, either. |
28/02/2016
Topic:
Autorun 32 or 64 bit version of app
ZeDingo
|
Here it is as a CMD script. It doesn't pass parameters because Windows is absolutely terrible at handling parameters in batch files. I'm writing a Win32 utility that will handle this whole mess correctly.
Edit: In a batch script, the fastest/easiest way to check for 64 bit arch is the environment variables. Inside a program, Microsoft recommends using GetProcAddress on kernel32.dll to make sure the call to GetNativeSystemInfo is safe, then GetNativeSystemInfo into a SYSTEM_INFO struct blah blah heavy crap we probably don't need.
I pulled out my Windows 7 ISOs (will need to check on XP/Vista) and opened up the install.wim files. WiaExtensionHost64.dll, ntvdm64.dll, and wowreg32.exe do not exist in 32-bit System32, but do exist in both SysWOW64 and 64-bit System32. This edit is a reminder to myself to try and use the faster(?) method of checking for a file's existence rather than wading through unnecessary WINAPI calls.
edited by ZeDingo on 29/02/2016 |
09/03/2016
Topic:
SyMenu v5.01.5911 Update
ZeDingo
|
Gianluca wrote:
- The SPS programs can be installed inside a container named as their own category. So you can install in one time all the suite programs without crowding your context menu at its root.
- Multiselect is allowed for the SPS using the SHIFT button modifier and the mouse click.
Thanks, Obama. While not perfect fixes, they at least address my two biggest complaints about SyMenu. |
13/03/2016
Topic:
SyMenu v5.01.5911 Update
ZeDingo
|
It means it's not included in this version of SyMenu, and I assume it won't be included in future versions either. If you so choose, simply delete the folder SyMenu\Plugin\SyMenu.Plugin.PAF |
29/07/2016
Topic:
Very minor bug when exiting
ZeDingo
|
I had open both "Configuration" and "Get New Apps", I right clicked on the SyMenu icon in the system tray and clicked Exit, which caused "SyMenu has stopped working" to pop up. Seems like it's just an rare case uncaught exception.
Exception message from clicking "Debug program" and attaching VS2013 Pro.
System.InvalidOperationException was unhandled
Message: An unhandled exception of type 'System.InvalidOperationException' occurred in System.Windows.Forms.dll
Additional information: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.
SyMenu 5.03.6054, Win7 HomePrem x64 |
30/07/2016
Topic:
Very minor bug when exiting
ZeDingo
|
I recorded my reproduction of the bug and uploaded (unlisted) to Youtube. https://www.youtube.com/watch?v=ZnWOoGJb-60 |