CompuServe Messages

3DS running in the foreground under OS/2 is no fluke because the DPMI problem had been brought to the Yost Group's attention many times by you and others. The problem is that 3DS does graphics output even in batch or slave modes. I see no reason why there shouldn't be a switch to make these things run blind. Maybe someone could write a null RCPADI driver? It would be even better if there were a switch to make 3DS do NO graphics output at all while rendering (output only to RDPADI and files). OS/2 doesn't care if a process using a display mode that is not supported for background execution runs in the background as long as it does no graphics output while it is in the background. This way, you could use whatever display driver/mode you wanted and use 3DS in the foreground and then switch to something else while it is rendering a test image. I am just glad that with my setup, I can use the Vibrant S3 drivers in the foreground and the VESA driver in the background. I wonder if 3DS can be run in the background under NT (not that I'm interested in running NT myself)?