#ATI Mach 64 Winturbo
5 messages in this thread
I am attempting to get an ATI Mach 64 PCI card working in a P5-100 system using
Intel's Triton chipset. The problem is garbage left on the screen in the
materials editor in 16-bit and 24-bit color modes. The garbage can be cleared
by switching to another module, but when there is a lot of stuff in the editor,
this can take some time.
System config:
DOS 6.22
3d-Studio R4 (using Vibrant drivers downloaded 6/7/95)
Pentium 100 w/ Triton chipset
64Meg RAM
Curious bits:
1) VLB version of the card (using same driver) works O.K. on a 486DX2-66 system
w/ 20Meg RAM
2) ADI drivers supplied with card all fail to display a test pattern in any
mode (black screen w/ blinking cursor)
Workarounds? BTW, 256 colors is not an option with this system. The clips and
such are for (eventual) film and broadcast.
Rick
Thomas Paton and Associates
>>garbage in Materials Editor in 16/24 bit modes<<
Have you tried the plain bootup? Press F5 during the DOS6.22 bootup, and if
you can avoid loading the mouse (tough to get around in 3DS, but worth trying)
start 3DS and F5 (again!) into the Materials Editor. I don't know if you need
to do something to recreate your garbage condition, but a plain boot would be a
good starting point.
I would also try a couple of other things, prior to starting 3DS: CHKDSK /F,
and running MSD.EXE to see if the Video info suggests a different VIBCFG
option. You might try configuring for a chipset or some other ATI options,
just in case this works.
If not, you might wish to give us info requested on the VIBBUG.TXT file here
and reply to me.
Good luck.
>>Have you tried the plain bootup? Press F5 during the DOS6.22 bootup, and if
you can avoid loading the mouse (tough to get around in 3DS, but worth trying)
start 3DS and F5 (again!) into the Materials Editor. I don't know if you need
to do something to recreate your garbage condition, but a plain boot would be a
good starting point.
I would also try a couple of other things, prior to starting 3DS: CHKDSK /F,
and running MSD.EXE to see if the Video info suggests a different VIBCFG
option. You might try configuring for a chipset or some other ATI options,
just in case this works.
If not, you might wish to give us info requested on the VIBBUG.TXT file here
and reply to me.<<
Actually, as I was posting here I was also in touch with ATI, my motherboard
vendor, and a couple of local suppliers. I finnaly got it working, but this is
what I found out along the way:
Windows would not go past the inital hourglass cursor with the ATI driver
installed and the original motherboard – VGA worked fine, though.
ATI's diagnostics for the board (driver disk version 1.44) report "Error 88821
Drawing engine failure" None of the ADI drivers supplied worked at all (locked
up or just didn't display anything when attempting to display the test screen).
An earlier version of the driver disk failed every time it attempted to switch
to a graphical mode (i.e. setting up a custom monitor, diagnostics, ect.). It's
driver's weren't tested.
Some earler Winturbo boards use an ASIC that is incompatable with Intel's
Triton chipset – which I was (of course) using. ATI will replace boards using
the problem ASIC. ATI also recommended a Triton motherboard that should work
with all of their cards – it dosn't, at least not this card. In fact, we tried
a total of 3 Triton-based motherboards and *none* of them worked at all
A motherboard using an ALR (?) chipset worked flawlessly. Cheaper that any of
the others, too – go figure.
Bug report is on the way 🙂
Rick
Thomas Paton and Associates
P.S. Simalar results with the Diamond Stealth 64 VRAM (PCI) and DRAM (VLB), so
look for two of em'
Rick,
Thanks for the details of your hardware adventures. I'm glad to have not been
the one to tell you to try all those things! We'll be on the lookout for your
bug.
Nik
Have you tried the Graphics Pro Turbo config. instead of the generic Mach 64.
This change worked for me.