CompuServe Messages

Hi ! I had this problem, the best fix I found was to make a special 3DS.set file that I named 3DWIN.SET. In the 3DS.PIF in Windows on the line optional parameters I put SET=3DWIN.SET. At the first start the program configure itself as plain Vesa driven. Now I can go in 3DS thru Win 3.1 without bugs. The problem is that you loose RAM in that operation. Autodesk doesn't recommand rendering in that configuration, but it can be handy just to make check with files made with graphic software under Windows. Now,I'm wandering how the thing will work with Chicago (Windows 4.0) next fall. But that's another problem and we don't have to much hint on that. It's a top secret matter! Just to leave our imagination dreaming about 32 bits access. Hope this will help, from an intermediate beginners ! Pierre Menard Montreal