CompuServe Thread

#VIB 1.0.5 driver prob

7 messages in this thread
#129710From: Oct 18, 1994 2:50 PM
>Well, unfortunately, the VIBRANT 1.0.5 drivers still locks up in *.FL? >playback inside 3DS (v 3) on my S3 805 chip! If I use a (any other) non-3DS >program to play them, all works just fine… My specific card is an Orchid >Fahrenheit VA/VLB w/2MB memory. I never had any problem(s) prior to 1.0.4, >either. Take a look at the read.me with the 1.0.5 update… Chuck Walbourn – Vibrant Graphics
#129788From: Mike RatledgeOct 18, 1994 9:26 PM
I have, Chuck – unfortunately, none of the *.FLC files were created with the 1.0.4 version, so I don't find anything that applied to me – did I miss it? (I'll read it again, just to be sure…) I immediately had to go backwards to the 1.0.3 version becuase of problems with the S3 support. I read the part about "recreating anything you made (if it was a *.FL?) using 1.0.4… This locks up on *any* Flic file (almost – I've found one or two very small (120×120) ones with only a few frames that play).
#129884From: Oct 19, 1994 11:24 AM
>I have, Chuck – unfortunately, none of the *.FLC files were created with the >1.0.4 version, so I don't find anything that applied to me – did I miss it? >(I'll read it again, just to be sure…) I immediately had to go backwards to >the 1.0.3 version becuase of problems with the S3 support. I read the part >about "recreating anything you made (if it was a *.FL?) using 1.0.4… This >locks up on *any* Flic file (almost – I've found one or two very small >(120×120) ones with only a few frames that play). Hmm.. Ok. Can you e-mail me your 3DS.SET file and a smallish flic that hangs (ZIP them would be best). Thanks! Chuck Walbourn – Vibrant Graphics
#130450From: DONALD NEWLANDSOct 21, 1994 2:57 PM
Chuck, This question has probably circulated a hundred times on this fourm, but…we just bought a Matrox MGA Utlima Plus for a P90 (Intel?) PCI and the Vibrant Inline driver sez "No MGA"…. meanwhile, the board works fine in all other apps. Help! Thanks, Donald Newlands
#130482From: John TissavaryOct 21, 1994 5:24 PM
The only time the vibrant drivers couldn't find the MGA on my computer was when I had an OPTI chipset based motherboard installed, which used a flavor of PCI designed for multi-processor boards (confirmed by OPTI). As soon as I switched to an Intel Neptune based MB I was back in buisness. I can only suggest that you make sure your MGA is being recognized properly in all other applications (Windoze, for instance). If this is the case, then maybe there's a hardware problem. If not, you might want to check into memory managment or PCI cmos values (don't ask me about those <g>). John Tissavary | LUNA cie, inc
#130852From: DONALD NEWLANDSOct 24, 1994 3:29 AM
John, The board is a joy in Windows and works fine in ACAD (tho I wish they had implemented their neato 3D stuff on the Ultima). PCI CMOs values?! Huh, I thought that PCI was supposed to be "friendly". Memory management?! — the only driver I use is Himem.sys… Thanks for your help, Donald
#131017From: John TissavaryOct 24, 1994 9:12 PM
Himem sys could be your problem… but with PCI I'm not really sure. You might want to try QEMM? John Tissavary | LUNA cie, inc