Vibrant Drivers
6 messages in this thread
Noah, I know of at least 4 people using the 3DS/PCI/Viper/latest Vibrant
drivers (including myself) with absolutely no problems, So we at least know
they work pretty good most of the time <g>. I'm using the latest ones off the
forum, here. Have you tried excluding a memory segment (if you are using a
memory manager like QEMM)? Actually, I do not know if this is an issue with the
PCI version like it was with the VLB.
If you keep having problems, let me know and if you wish, I'll Email you my
phone # and I'll try to talk you through a set-up using my system as an
example…
-Alan
PS –Just saw your latest. Please disregard and I'm happy you are up and
running!
Alan-
Thanks for the tip. My attitude is it's working (apparently with the same set
you and the others are using) and I'm just not intellectually curious enough to
delve into it more.
I'm assuming for now that that later driver is a problem….
–Noah
If it IS a later driver that is actually trashed for the Viper, Noah, I sure
hope the folks at Vibrant know about it!
-Alan
You know, I told Diamond but I'm not sure I told Vibrant. Isn't there a
Vibrant guy who hangs out here? Do you know his name/addr?
–Noah
I can't seem to the find the original description of the problem… Can someone
give me the run down of the problem and the attempted fixes to this point?
Chuck Walbourn – Vibrant Graphics
Chuck-
I'm fuzzy on it now, but it seems that when I used your 4/8/94 version it kept
telling me the MemAddr in my .ini file was incorrect. It said that a Viper
should be @ 2000, 8000, or A000, while my .ini file said B800. I tried
changing to each of the suggested values, and it reported (surprise) that it
couldn't find my card. As you probably picked up, the version on this forum
lib worked.
I'm sorry that I can't look into it deeper, but I'm burning under a deadline.
Someone else reported a similar problem.
–Noah