#R3/Win 3.1/Vibrant fails
2 messages in this thread
I have also had problems running with the Vibrant drivers under
windows. If you use a simple generic VGA or use the VESA driver it
seems to run. You can make two seperate set files and use the "set="
command line switch. You can edit the display setup of the other set
file by typing the following:
3ds set=windows.set vibcfg
I still haven't really enjoyed running 3DS under windows. I get much please
from using the vibrant drivers under DOS. 3DS is so much slower without them it
is not worth running under windows.
Thanks for your suggestions, Robert. I have tried using the generic VGA
driver, and that _did_ allow me to enter 3DS under Windows, initiate a
rendering, and then switch over to other Win apps (Whee! Look, Honey, you can
use WordPerfect this week, while I'm rennnnndering!). But, when I tried to
_return_ to 3DS, Windows said 3DS had violated all that was good and holy and
crapped out.
I spoke to "Paul" at Vibrant Tech Support, Friday. He said that the driver
code licensed to Autodesk for R3 was NOT WARRANTED to run under Windows, and
was NEVER EVEN TESTED by Vibrant for that purpose! So mebbe this feeeture is
just Autodesk wishful thinking?! <Nik Grant, you there?!>