munson@matt.ksu.ksu.edu (Jeff S Pihl) (05/29/90)
I seem to have found a way to let older windows aplications run in standard mode win3.0 without being prompted with the annoying 'use win/r' notice. I assume that this procedure will work for enhansed mode as well. First lets examine the makeup of a 'generic' windows application first | MZ [then a few characters] | [blank section] next | This program requires .... [printed string for dos line execution] | [blank section] then | N [then many characters] It is this 'then' section that you will need to modify. It always starts with an N (I have not seen otherwise), and is usually at file ofset 400H. You will need to change the character (byte) that is 37H after the N eg, 437H. 436H is usually <02>. you will nedd to change 437H from <00> to <04>. If you hack around a bit, you will notice that the win3.0 applications contaion a <08> at this offset, but all of the older apps that I've changed did not work with <08> in that offset. To make the modification, you can use The Norton Utility hex editor, FM.COM a PD hex editor, or you can use debug, or any other hex editor. BUT, whatever you use, MAKE A BACKUP OF THE .EXE BEFORE YOU MESS WITH IT!! Note: This modification does not correct any possible compatibility problems, It only eliminates the 'old application' notice. Please, make extensive tests on your applications before giving them the OK. -jeff P.S. .DLL's are .EXE's in disguise, this modification should work on them as well. enjoy.
philba@microsoft.UUCP (Phil BARRETT) (06/05/90)
Its important for people to realize that marking their applications as 3.0 compatible may cause them more grief in the long-run. The `use win/r' dialog that comes up when you run a pre-3.0 app is there for your benefit. Any app can be marked but since it hasn't been tested, there may be lurking protection faults. A user that marks an app as win 3.0 compatible which then crashes after he enters a bunch of data will be pissed. I'm not saying don't do it but if you must mark your apps, caveat emptor. Phil Of course, the above opinions are mine and do not necessarily represent those of Microsoft.