CompuServe Messages

Well hello Chris, I sent you some email last week. Sounds like you didn't get it. Here's what's happening. I've got 3dsr2 running on a Diamond m/b (with the most current bios) and the 2 meg Viper VLB. I cannot get 3ds to run with anything higher than 256 colors at 640×480. I have not tried any other resolutions, because I want to stay close to what is television. I re-installed all the software today, thinking that something might have gone wrong with the original installation. That didn't help. If I try to use 65k colors, the screen on 3ds bootup goes wacky. By that I mean that the normal area that you would see, is compressed to the left side of the raster. It's been compressed down to approx. 40% of the total screen area. The remaining 60% is columns of scraggly lines in a gawd awful pink color. 3ds runs normally, meaning I have control over the program, but the display is totally wrong. If I try to create a light, and I move the bars to select the color, the sample box stays stuck on white. note: this was with the Turbodld lite driver that I downloaded last week. [rcturbol.exp] With rcturbod.exp, I get the aforementioned compression of the viewing area, and I don't go any farther. At this point, let me ask you this. Instead of running the batch files, I have incorporated the set statements into an environment file that loads everytime I boot under my [Autodesk] configuration w/DOS 6. (I've also tried using the batch files "as is" with the same results.) Is there any problem in doing that? Command.com is not capable of doing this, but Ndos is. And that is the command processor that I am using. Have your drivers been tested with alternate command processors? Are they compatible? Maybe I need to use plain old command.com??? Got any ideas? I'm worn out. md