Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!iuvax!rutgers!deimos.cis.ksu.edu!maverick.ksu.ksu.edu!matt.ksu.ksu.edu!munson
From: munson@matt.ksu.ksu.edu (Jeff S Pihl)
Newsgroups: comp.windows.ms
Subject: marking 2.x apps OK for win3.0
Message-ID: <1990May28.201449.22218@maverick.ksu.ksu.edu>
Date: 28 May 90 20:14:49 GMT
Sender: news@maverick.ksu.ksu.edu (The News Guru)
Distribution: usa
Organization: Kansas State University
Lines: 36


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.