CompuServe Messages

I use the PAR under Windows/95 but there are some tweaks that must be done. First of all, it will not be possible to use it "within" Windows as disk access in Win/95 is done in 32 bit mode (unlike Video which still is largely 16 bits). What I've done was to create a pif file for a DOS box. This pif has a setting which "hides" the fact it is running under Windows (the TSR would not, normally, load under Windows). I then created an Autoexec and Config just for that DOS box and that's where I load the PAR drivers. It's also there I run the PAR.EXE (DOS) application and 3D Studio. They all work just fine. Note that not all video drivers support changing modes from a DOS box to Windows and Back. This has nothing to do with Vibrant drivers while running 3D Studio. It's a problem of the Windows driver (written by the Video board manufacturer). My video is a plain jane Viper and the drivers (which are luckily 32 bit) will support switching back and forth just fine. Yep… this is the beginning of the end. From now on, it will be harder and harder to use "old" hardware 'till nothing else will work other than new stuff with proper drivers. Manufacturers can't keep up with drivers for their new stuff, much less to support hardware they no longer sell. The only way to support the PAR under Win/95 (or worse yet, NT) will be if DPS provides low level drivers for it in order to run. It's a heck lot easier to write drivers for Win/95 than for NT. Let's just see where this goes…