New
#1
Avoiding '<application name> is not a valid Win32 application' error.
OK, this is admittedly a strange one...
I have used an old (probably a 16-bit) application as my time synchronizer this I've used for quite some time. Its name is TimeRC, and is a great synchronizer as it tracks moon phases along with the time (from selectable, multiple potential time servers). After a fatal software crash a couple of weeks ago, I'm in the process of recovery. Attempts to manually launch the EXE, result in a launch-time error stating that the ap is not compatible with my Windows 7 Pro (SP1). Note that I'm running on the same level of Windows that I was using prior to the crash/re-install. I have inhibited compatibility checking (Group Policy adjustment) only to incur the Win32 error.
I've been through the litany of utilities (registry) to correct this situation, and I KNOW that this ap runs just fine on Windows 7 (from pre-crash days). I am at my wits end trying to avoid this situation. I suspect that there is a registry setting difference (now versus pre-crash) about which I'm ignorant, so I'm open to any, and all suggestions.
To use an alternative time synchronizer is not an option...I'm anal about how my system looks, feels, and performs!! I've even tried running in XP mode (virtual machine) to no palatable result. Note that I don't have access to the program's source code, otherwise I could recompile!
There's got to be something that I'm missing.
Color me frustrated,
Randy Reist (Lairbear)