OS/2 w/ 3DS 3
<<What I would do is create two batch files for launching 3DS. >>
Actually, I don't really need my main display to be VIBRANT driven. I think, at
the moment. I'm happy with regular VGA. I'm not sure if this affects screen
redraws or object colors but I'm going to play with it.
Anyway, to update you: nobody at Diamond, but I took the liberty of
logging onto their BBS. I found the OS/2 2.1 drivers. Downloaded and
installed and it looks great (a little small)… This solved the
problem of switching from 3DS to the desktop, but now when I switched
back, no display. Okay, so I set MAIN-DISPLAY for VGA with the
VIBCFG. Now I can switch back and forth from the main-display, no
prob – just not from the MATERIAL or RENDER – both still using the
Vibrant Viper driver…
So that's all right, as far as I'm concerned. I'll have to see what I
compromize… Yeah, I just loaded in one of my workfiles – it's a _little_
slower in screen redraw and no colors are available. I guess I lock myself out
of getting Liquid Speed… Oh, and in Keyframer, the playback is some slower.
Now the other problem I've discovered is that, once I start a rendering and the
switch back to the desktop, 3DS stops rendering. Switch back and it continues
where it left off. I have set the DOS_BACKGROUND switch to on for the session,
so I'm not sure what's happening.
Anyway, that's 3DS. Sorry if I'm blabbering on but I'm assuming you're
interested.
Next was Photostyler, which seems to run fabulously… Yeah, I've just loaded
it up in a WIN-OS/2 window and it's okay. The mouse is a little jerky, but
nothing worth whining about. But it looks fab!
I think that's it for now (unless you want to talk about my SCSI board that
freezes my system, but that is a whole nother story)
Thanks for your help and interest Bailey!
James