Hey BRUCE,

18 Jun 04 23:55, you wrote to me:

 BC> -=> Quoting Dan Egli to Bruce Clark <=-

 DE>>> 90% of them will be fine as long as they used nothing but the
 DE>>> standard Win16 API. It's the funky ones that used extensions
 DE>>> like WinG that will give issues now.

 BC>> What is WinG?
 BC>> And is there an easy way to tell if an old windows program uses
 BC>> it?

 DE>> WinG was an attempt at 3D graphics (or REAL high res graphics,
 DE>> for those days) under 3.1. If you are running under 3.x you will
 DE>> recognise WinG by the funky startup test it does on first load
 DE>> and on the first load after changing any display settings. Whole
 DE>> bunch of lines that sometimes form sinuous lines, sometimes form
 DE>> circles, etc.. and blocks change here and there.

 BC> Considering that my normal graphics are greyscale LCD 640x480 VGA,
 BC> with 256 color an option if I plug in the VGA PC card for an external
 BC> monitor, I probably don't have to worry about that.


 BC> I'm just hoping that the:
 BC> "Hyper-Threading" Mobile Intel Pentium 4 Processor
 BC> won't have any problems running 16bit Win3.1 programs like one tech
 BC> support person said.

It's possible. But I doubt it. Hyper-threading could only cause problems if
it expects responses from the CPU in an absolute fixed format. Most
programs are not that strict.

-- Dan

--- FMail/Win32 1.60