CompuServe Thread

'we did run 3ds under NT'. I never thought one remark could mean so much. I made it in a different forum and a different context, but it spread to this forum and draw more attention than I expected. I didn't realize it was such a hot item, otherwise I would have made a more prudent statement. We did run 3ds under NT for the single purpose of TESTING NT; we didn't expect it to be productive, fast or fun (and it wasn't). Based on our experience there is no sense in using 3ds under NT for any SERIOUS work. We were just curious about the possibilities of NT. Having this stated I'll try to answer some specific questions: – yes, we did run 3ds under NT 3.1 (no, not plain windows or daytona). – no, the vibrant drivers won't work: we used vesa drivers on a ET4000. – yes, you have to disable the hardware lock checks (NT won't allow them) – no, I'm not gonna tell you how to disable locks: we are an authorized 3DS dealer and don't want to ruin sales of a worthy product. – yes, the Pharlap settings must be changed: you have to set 'realbreak' to zero. If you do all of the above 3DSr3 will run, but disk access is slow, you need lots of memory to prevent (extreme slow) swapping and you are limited to vesa drivers. Rendering speed seemed not dramatically low and you can switch between apps, but being a dos app it won't render in the background. Conclusion: anyone in his right mind should stay away from this 'solution'. Hope this explanation helps. Fremer Huijgen (Studio PC) P.S. Let's push the Yost group and A'desk to produce a real NT / Daytona version. The benefits would be enormous (and I can finally use my new dual Pentium system for some real work!).