CompuServe Messages

3DS r3 (Rev 2), eh? New one on me. The best way to figure out what the heck is happening, Mike, is to *completely* simplify your system (NO TSRs, nothing loaded high, no network, simple-as-possible memory manager set-up (or none at all to start), and no video driver loaded or configured (render to NULL and look at the pic in another program). Remove all adapter boards except the basic VGA and controller/ I/O stuff that is critical to the basic operation of 3DS in the system. If 3DS renders OK at this point, install the video-related drivers and see how this works for you. Only after 3DS renders fine on *all* your machines in their simplest possible configurations, should you attempt to "fine-tune" each one and get things working together and at their best. Now add peripheral boards to the system. Chances are, while adding things to the system, test-rendering as you go, you'll run into the culprit(s) and deal with them on a by-problem basis, using say, QEMM to arrange memory-related problems for you. Tedious and time-consuming, yes, but often the best way of setting up a rather complicated system. If 3DS fails on a simplified system, the basic hardware/software/BIOS is suspect. The above system, however, has worked for me every time. Good luck, -Alan Iglesias