This is an archive of CompuServe forum messages from 1985 to 1995, as saved in transcripts by John Foust.
Search Results (187 messages)
Nik – The Windows problem is fairly hairy. The main problem technically is that the Windows' driver takes control away from us at strange points, which leaves the system in an unstable state which could crash, or at least, trash the display. The only time we have run our DOS…
We'll, we are trying to get one in house. Which version of the inline driver are you using ? Chuck Walbourn – Vibrant Graphics
Can you describe the problem? Is it not syncing? Are the colors wrong? Any information would help. We do not have an STB LightSpeed in house, so we'll try to get one to resolve the problem. The problem is probably that their BIOS is not properly setting up the RAMDAC…
#93147-
VIBCFG Problem
Message #93995
The 1.0.1 version has a listing for Cirrus 5428 in the second half of the cardlist (keep pressing C in the cardlist until you get to the Cirrus entries). This should work. Chuck Walbourn – Vibrant Graphics
We are working on getting the card in house. Once we have it, it should be in the next inline driver. Once we get once, we should be able to tell you which generic setting to use. We think it is based on a Cirrus Logic 5428, try the generic…
This is for the Compaq AG-1024. The Compaq AG-1024 used it's own version of TIGA 1.1, so you can use the VIB-AG1.EXE support program (I sent it to David Ang, but I don't know where it is for the public) to run the Compaq with their system, which is fairly…
So none of the Compaq QVision modes worked? Can you send me a list of the modes that your card should have (maybe in docs somewhere). Chuck Walbourn – Vibrant Graphics
The inner workings of hardware locks are pretty much secrets of the manufacturer, but it basically invovles giving the hardware lock a password and seed value(s), it then returns recongition values that are checked by the program.. if they match, away you go. Considering that a hardware lock is sitting…
The 1.0.1 inline driver update (in the download area… look for VIB3DS.ZIP) should have compaq support for some of the modes listed as Compaq QVision. If it doesn't work for you, please send me e-mail and I'll try to get information to our TQM guys about getting us the board.…
Can you send me your 3DS.SET file again, along with your CONFIG.SYS and your AUTOEXEC.BAT (zip them up and e-mail them). I'll see if that will help any. Are you using VIBRANT in VESA mode, or are you using the VESA driver? Chuck Walbourn – Vibrant Graphics
Mach32's using rev 6 silicon added the 'memory-mapped' system. This basically means faster access to the board using memory-mapped i/o as opposed to the io channel instructions. The new Mach64 uses all memory-mapped modes, but the Mach32 needed to keep the non-memory-mapped versions for compatability.
We are trying to get the Classic and Plus versions of TARGA going first. After that, we'll implement the others as we can get the boards in house.
Good idea anyway!
Thanks. We have been looking for this kind of information, but it isn't exactly easy to find! This won't address all of the problems however. One of the biggest problems is the 1sec requirement for the operations. Saving a screen from a TIGA could take more than 4-5 seconds… Also,…
Still looking into it. We have found a few small bugs in the P9000 code which could cause problems on some systems, but still should not have resulted in an Error #18. We still think it has to due with either the .INI file or possible the FILES lines in…
For the TARGA card, you need the TARGA ADI driver. You'll need the RDPADI environment vairable to point to the driver–check out the 3DS R3 manual installation guide for details. We are working on TARGA support, so hopefully in the near future, you can just select TARGA from our configuration!…
I have no idea. Has it ever happened again? Chuck Walbourn – Vibrant Graphics
I don't remember getting a message about Windows handling code. I'll be on the lookout… Chuck Walbourn – Vibrant Graphics
Ok. Again, I assume that you are using a #9 GXE and you are using the 'Number Nine GXE S3' selections on the configuration. Right? Try testing each mode and turn and let me know which ones don't work. I'll check with our draw-code guy and see if we can…
Firstly, I assume that you using the 1.0.1 Inline drivers. Did this happen entering 3D Studio or while running the configuration's test? This shouldn't have corrupted anything that I am aware off, unless you had some other problem earlier (crashing or something). Error #1806 is P9000 not found in system.…
What card are you running? Make sure that you don't have more than one .VLM file in your directory and try to 'test' the video mode from the configuration. Chuck Walbourn – Vibrant Graphics
I assume that you are talking about the #9 GXE PCI card. We have had some problems with the #9 PCIs here and have found some small BIOS problems that we are working around now. At least some of the modes should have worked. Please send me a list of…
I believe it is another flavor of Mach32… Try the ATI Ultra Pro XLR settings… Chuck Walbourn – Vibrant Graphics
Any description of the brand of video card? The most common problem with supporting cards like another S3 is BIOS changes that are specific to the vendor. The S3 code generally works the same, but some cards need slightly different code. If we can find out what vendor made your…
Are you using the 1.0.1 Inline update? It should have fixed all of the problems with the Diamond Viper PCI. In general, PCI boards require special setup, so 'faking' it won't work anyway. There were several problems with the Diamond Viper, all of which have been resolved to my knowledge…
> How can an ADI 4.2 driver work with 3D Studio R3 when the 4.2 spec won't work > with the software? ADI drivers _should_ work with 3D Studio R3. I don't know how much testing was done by Autodesk for this, but it is still available. ADI drivers DO…
#91100-
#3ds in windows
Message #91173
> will go into 3DS, then [Alt]+[Tab] back to Windows, then back to 3DS, without > either the 3DS or the Windows screen or both being TOTALLY DESTROYED, and/or > the system locking up entirely. And this isn't even with trying to have 3DS > actually _run_ in the Background!…
#91154-
#3ds in windows
Message #91172
> (Alt-Tab) the screen doesn't get repainted (this is a Vibrant problem and > could be fixed by a simple hook into Windows when it goes up). To fix that, I What do you mean by 'simple hook'? I remember our draw-code guy was looking for some way to tell…
I will keep you posted. I am having a look through the P9000 draw-code to see exactly where the error might have been generated… Chuck Walbourn – Vibrant Graphics
Well, we have never seen error #18 here… We don't even have an error description for it (hence the "This should not happen" message). I'll try to dig around the DOS manual a while and see if I can figure out where exactly an error #18 is coming from… Chuck…
Excuse me. The Weitek P9000 CHIP is correct. It is used by the Diamond Viper, an Orchid card, a Cardinal card, one of the Photon Torpedos, and a few other cards including the MaxVision… I didn't think the chipset police were about 🙂 Chuck Walbourn – Vibrant Graphics PS: Besides……
Vibrant Drivers
Message #89487
For those that have downloaded the updated drivers… make sure that you do not rename the old drivers to something with an extender of VLM. All VLM files in the 3D Studio directory are loaded, so this might cause problems. The READ.ME suggests VIB3DS.OLD and VIBRANT.OLD, and these will work…
Nik – We actually have a Gateway ROCKET in house… it arrived recently. We will be putting it into the next Inline driver (1.0.2) which will probably be out in a few weeks). Chuck Walbourn – Vibrant Graphics
I just got a small hint from the guy that wrote the P9000 draw-code. Error #18 could be an extended DOS error returned when we try to read the VIPER.INI file. Error #18 again makes little sense (No more files), but it might mean that you have some kind of…
I'll take a look at it. Error #18 is VERY strange, so I'll keep you posted… PS: You 3DS.SET looked fine… Chuck Walbourn – Vibrant Graphics
Well, we can't really talk much about which boards to buy, since we support the Graphite and we are almost done with support for the MGA, as well as the Diamond Viper. Let me just say that the Weitek P9000 is probably the fastest chip around for 256 color. We…
John – If you are using 3D Studio R3, then the Diamond Viper support is free! It is included in the Inline driver. You should get the 1.0.1 updated driver, which fixes some minor problems with the Diamond Viper as well as PCI support. If you are using 3D Studio…
Page 4 of 4