#mach32 card and Vibrant
7 messages in this thread
To All,
My new Pentium 90 just arrived and I'm having trouble configuring 3ds to use
the Mach32 graphics card that it has in it. When I run "3ds vibcfg" and try to
choose the ATI MACH 32 IT isn't listed. Why is that? Is the MACH 32 not
supported?
any ideas?
Jim Beyer
>>ATI MACH & Vibrant…
Jim, I've got the same card in one of my machines. It is rendering
now so I can't run vibcfg to verify, but looking across the net at my
3DS.SET file I see:
MAIN-DISPLAY = VIBRANT
VIBRANT-MAIN = 1707 ; 5163528 ATI Ultra XLR 1024×768 256 colors
VIBRANT-MAIN-FONT = "VIBRANT14"
MATERIAL-DISPLAY = VIBRANT
VIBRANT-MATERIAL = 1711 ; 5163533 ATI Ultra XLR 640×480 16777216
colors
VIBRANT-MATERIAL-FONT = "VIBRANT14"
Is the Ultra XLR still on the vib menu?
BTW, the card works well with 3DS in all modes, except that when (in a
weak moment) I tried to run 3DS under Windows, it trashed the Windows
screen. I never bothered to try to get that working.
JKJ
John,
Thanks for the help, I'll give it a whirl.
Are you in Omaha? I thought I saw that in a thread some time ago. I'm located
in Des Moines.
Jimbo
Omaha? No, I'm in Oak Ridge, Tennessee. That must have been some other
scoundral.
JKJ
Jim, the Mach32 and 64 are listed in the Vibrant driver selections.
You have to scroll back a bit to find them. I run the MAch 32 and all
runs well with the exception of one minor glitch. I have to clear my
card by rendering a blank screen at 320×200 so as not to get
scrambled screens from other Graphics Apps once leaving 3-DS. Jonas
and Nik were advised of this in detail many times… dating back to
the first roll-out of R3. The bug continues. A friends, running
identical system has a similar problem, but his work around is simply
going to windows and back out to DOS and that clears his drivers.
That does not work for me. Now I notice that someone else replying to
you is using the Ultra XLR driver choice. If he is also using a
Mach32, I might try that driver set to see what happens.
Jeffrey,
Thanks for the info, I'll try both suggestions and see which works best!
Jimbo
FYI, I tried the other driver and it ran my card fine. However, the quirky bug
continues and my workaround is now just routine.