#viperpci/viberant
13 messages in this thread
hi everybody:
i am experiancing a RANDOM problem when the renderer switches video modes to
show the image. i get a red screen saying
"unknow fatal errer#"
"this error should not happen"
"contact supplier"
"cant switch to vga 320×200"
i am using a pemtium pci/viper pci/r3/viberant driver(latest)
the viberant is set to display=800×600 256
renderer=800×600 16M
i am not even using vga 320×200??? and the error says it cant switch to it.
has anyone had this problem? do you know whats going wrong.
thanks in advance
ara
Ara, I have gotten that message (ERROR 18) a number of times using my Viper
VLB. I have documented it a number of times to Vibrant, but to no avail. It
always happens (with me) on the first entry into Medit when certain axp's have
been applied in the Ed/KF. I wish they could figure it out, too. I've
documented everything possible regarding this. Please let me know if you find a
solution. If I hit <ESC>, it'll return and the next time it'll go away, FWIW.
Did you by any chance have axp's applied to anything ?
BILL
bill:
esc also solves my problem.
i will keep an eye on the axp issue and let you know.
so far it has seamed random!
thanks
ara
The axp thing is only my opinion…it could be a coincidence, or just one of
several things that trigger it. I'm just curious, does your upper left viewport
frequently not redraw with the others, as in returning from a render screen ?
That's the only other annoying problem I've always had with this
display/driver.
BILL
no, i have not had that happen to me yet.
the only other problem which is no bigee is that sometimes it takes a good
2-3secs to switch from 3d edit or the other modules to material editor. going
back from mat editor to the other modules is fast.
ara
Bill
>>.. does your upper left viewport frequently not redraw with the others, as in
returning from a render screen?
Yup. Only on the Viper VLB's not on the Viper PCI.
JB
Bizarre. I'm using a Pentium DEC PCI-based machine with a Viper PCI card as
well, and have never had any problems with it. (I'm also using the latest
Vibrant drivers.) Those aren't 3DS error messages, so it sounds like the bios
is having a spas attack. Yeesh. When did this start happening?
– G
gary:
my computer is a micron p60 pci with a viper pci card.
i have had this problem on and off since i have owned this computer, even with
the older viberant drivers.
yesterday i installed a dps-par unit in my computer and since then the problem
is happenning more often but still randomly.
i will try to find a pattern.
thanks
ara
>> does your upper left viewport frequently not redraw with the others, as in
returning from a render screen?<<
Hi Greg, We have the "no-redraw top left viewport " problem as described
earlier. We are running 3DS3 on Gateway2000 4DX2-66Vs with a min. of 32MB RAM.
One machine has a ATI Ultra Pro/NEC Multisync 5FGe and the others have Diamond
Speedstar Pro\CrystalScan 1024 N1. This has happened periodically since I can
remember (year and a half or so). I will start documenting when this happens.
Using "Redraw All" in The Views pull down brings the mesh back into view in the
top left viewport. I have all the latest VIB drivers. I guess we have gotten
used to this and don't really pay attention to it any more.
Thanks, Randy
I'm using the Viper on serveral machines. I've notice different problems with
different viper cards with different bios. I would recomend looking into BIOS
updates for the Viper (ver 3.02 or better) and get the latest Vibrant drivers.
I have not experienced these problems. Of course the Vibrant drivers shipped w/
3DS don't work at all.
good idea i will get the upgrade
ara
FWIW, I've got the latest Viper (VLB) BIOS, and still have the problems.
BILL
i belieave this problem is somehow related to the par driver when its loaded
throught the pxp and the viberant driver. the error message is a viberant
message.
but somehow the error only gets trigered the first time the pxp is loaded. when
i get the error i can get rid of it by pressing esc a few times and the problem
is gone until i access the pxp again. everytime the pxp is loaded(par driver)
it does something to viberant that trigers the peoblem. i cant tell what.
maybee the viberant people can figure this out?!
any way it is not a bigy since pressing esc solves the problem.
thanks
ara