Path: utzoo!attcan!uunet!microsoft!michaelt
From: michaelt@microsoft.UUCP (Michael THURLKILL)
Newsgroups: comp.windows.ms
Subject: Re: Win3, Questions to answer
Message-ID: <55205@microsoft.UUCP>
Date: 13 Jun 90 17:54:54 GMT
References: <9774@rouge.usl.edu>
Reply-To: michaelt@microsoft.UUCP (Michael THURLKILL)
Organization: Microsoft Corp., Redmond WA
Lines: 40

In article <9774@rouge.usl.edu> pcb@gator.cacs.usl.edu (Peter C. Bahrs) writes:
>
>2) In our 30000 line application, what do I have to do to make it 
>   run without the initial warning under win 3?  Do I just
>   recompile?  or recode?
>
You technically only have to run the program through MARK.EXE that
is included with the 3.0 SDK. I know, you don't have it yet. Nothing
I can say except maybe "wait for the SDK". You could possibly use
one of the PD mark apps that have been mentioned in this forum.
In general, apps that work under 2.x and "follow the rules" should
work under 3.0. The biggest thing you'll encounter when running
under 3.0 is protect mode. This gives you more memory to play with,
but it also imposes some new restrictions. In general the 
restrictions aren't bad, they simply force you to remove some things
that were bugs or "not good practice". Here are some guidelines:
Do not assume the priviledge level in which your app is running.
Do not load a segment register with a value other than one
provided by Windows or DOS.
Do not perform segment arithmetic.
Do not compare segment addresses.
Do not read or write past the ends of memory objects.
Do not use code segment variables.
When increasing the size of a memory object across a 64k boundary,
do not assume that the GlobalRealloc function returns the same
handle it was passed.
Do not rely on GlobalFlags to indicate how many times your app 
has called GlobalLock if your app is running in standard or
enhanced mode. Your application should not rely on GlobalFlags to 
determine the usage count of a globally allocated object. Instead,
your app should maintain it's own reference count for the object.

Also, Win3 uses a proportional system font in 3.0 apps. You 
should make sure your dialogs all look right with the proportional
font.

Mike Thurlkill

Disclaimer: These are my opinions. They should in no way be
miscontrued as being correct or in any way related to my employer.