#3DS3 Window NT
5 messages in this thread
Has anyone tested 3DS with Windows NT 3.5 (codename "Daytona")? Is it
possible that this has fixed the problem?
Tim,
I just ordered NT 3.5 because I need some of it's benefits for my graphic
design work in Photoshop/Pagemaker. I was thinking of running 3DS under it but
hadn't heard of the "problem", what is the conflict if you don't mind telling
me?
Paul
3DS doesn't run under WinNT 3.5, either – same as WinNT 3.1, it doesn't support
DMPI. Now, I'd love to hear why DMPI can't be emulated under WinNT… I'm
sure there's a reason. 🙂
The 32-bit Windows platforms don't support DPMI *at all*!? I heard they
did, but that the implementation thereof sucks dead bunnies through a straw.
Windows 3.1 supports DPMI, albeit imperfectly. To prove this, run PKZIP or
PKUNZIP 2.04g (the latest version) both outside Windows and inside a Windows
DOS Prompt. Assuming your memory manager doesn't itself provide DPMI Server
functions (the only one that does directly that I know of is 386-to-the-Max —
QEMM has QDPMI.SYS but you have to load that separately, and frankly I don't
recommend that at all), you will see the line "DPMI Version 0.91 detected."
when PKstuff starts up under Windows DOS Prompt but not when it starts up
straight from DOS (it appears in the same group of messages about "EMS Version
… detected" and "XMS Version … detected," etc.).
I suppose one could run PKstuff from a Windows NT or Windows95 DOS emulator
box to see if they attempt to support DPMI at all. Could someone who has them
do this and report back to the rest of us?
In the meantime, OS/2 remains the ONLY 32-bit OS for Intel CPUs that
supports DPMI well enough to handle 3DS, and it does it pretty darn well, too!