#Cirrus Logic 5426
8 messages in this thread
You mentioned that you couldn't get the Vibrant 3DS drivers to work, but I'm
pretty sure the Cirrus board should have VESA VBE support in its BIOS,
therefore, instead of VIBRANT or RCPADI for the display type in VIBCFG, you
could choose VESA.
-Chris
Panacea
Thanks for the reply. I have several projects ongoing with Cirrus L. boards.
One board, a generic, would not function above 640x480x16 color. Upon close
examination I discovered that half the ram was 70 ns. and the other half was 80
ns. When we installed matching ram everything worked. It was a screwup at the
mfg. Another project involves testing of 3DSr3 with an RCPADI type driver. I
have not been successful with getting your RCTURBOD.exp to work. I may not
have the 3DS.set file configured properly but on first try I was just booted
back to the dos prompt when attempting to select the card from your menu
screen. I need to check out the 3ds.set parameters next. Any suggestions would
be appreciated.
More info on using the RCTURBOD.exp. I played around with it again
this evening and here is a message that pops up just prior to
aborting to the dos prompt. — CS:EIP=0057h:0008611Fh
Maybe this will give you a clue. I also checked the installation manual and I
had the 3DS.set file correct. I also went back to the Panacea Install and this
time got all the way to loading the main display in 3DS before the program
aborted. Moving the mouse around also triggered the abort.
Don,
This CS:EIP error indicates a memory corruption above one meg. What's your
memory (config.sys) setup? You might experiment there and try a plain boot, or
watch which devices you have in the machine.
Nik
Thanks for the lead pointing me in the memory direction. I found the cirrus
board didn't get along well with Stealth on QEMM. Removing ST:M solved the
problem with the RCPADI as well as windows drivers.
Thanks.
Don,
Thanks for letting us know what happened with this CS:EIP error. There are
some errors that can be created by a variety of conditions, so it's nice to get
a case history for something specific like this.
Nik
What version of RCTURBOD.EXP is this? (Check the disk.)
If you are using a version of TurboDLD before version 1.02J, there isn't
anything you can do to get it to work with 3DS 3.0, you have to get a newer
version from an OEM or from us.
-Chris
Thanks Chris, But I got it working. Seems I had Stealth:M (QEMM) and the
particular Video card didn't like it when loading RCPADI in r3. Wierd combo
but just removing Stealth and everything works now.