Q3D Obsidian2 SLI2 X-24 problem, W2K

[Avenger]

I'm trying to get said card to run with my Radeon 9600 XT under W2K. With the Fastvoodoo 4 GE I get the mapmem error. With the latest hotfix any Glide app simply hangs at 100 % CPU use and the V2 control panel gets removed from the advanced display settings. Further both V2 get installed, but the V2 CP doesn't detect SLI.

System info:
Abit VP6 mainboard, VIA Apollo Pro 133A chipset, latest 4in1 installed
Dual P3 800EB, slightly overclocked to 840 (140 MHz FSB)
512 MB PC-150 RAM
Two Seagate 40 GB ATA 100 at HPT370 RAID in RAID 0, latest RAID drivers and BIOS installed
Pioneer DVD-105 and Plextor PX-W 1210A at primary IDE
AGP: the Radeon, using latest Omega drivers
PCI 1: empty, but blocked by secondary USB slot (cable is too short to install above AGP)
PCI 2: Realtek 8139 based 10/100 NIC
PCI 3: Tekram 315U UWSCSI controller with my scanner
PCI 4: SB Live 5.1
PCI 5: the Obsidian
no further slots
OS: Windows 2000 SP4

It's funny, especially seeing that the hotfix Glide files are actually from Q3D. Still the card won't play nice. Help is appreciated.

[Obi-Wan Kenobi]

Oh man , join the club, I had exactly the same problem, with my Radeon 9700 Pro systems.

sys1:

AMD AthlonXP 2600+
ASUS A7N8X Deluxe2.0
2x 512MB PC-2700 Samsung Original
Hercules 3D Prophet 9700 Pro
WinXP Pro SP1 N.L.
+
Skywell Technologies Magic 3D II PluS 24MB [2x 3Dfx Voodoo2 12MB Sli]

as for this system:

Sys2.

Dual AMD AthlonMP 2200+
ASUS A7M266-D [AMD AM760MPX]
1x 1GB PC-2100 ECC Reg Twin-Moss.
Club-3D Radeon 9700 Pro
Win2K Pro SP4 U.S.A.
+
Skywell Technologies Magic 3D II PluS 24MB [2x 3Dfx Voodoo2 12MB Sli]


On these two systems I get the same "mapmem error"

and on my 3rd system everything went okay, thanks to my good old GeForce 3.

Sys 3:

AMD AthlonXP 2700+
ASUS A7V333-R [VIA KT333]
1x 512MB PC-2700
Gainward GeForce3 Powerpack!!! Golden Sample ViVo 64MB DDR [now V5 5500 AGP, sold GF3;)]
Win98SE Fully Updated
+
Skywell Technologies Magic 3D II PluS 24MB [2x 3Dfx Voodoo2 12MB Sli]

and this went fine, I also tried the other two systems with my GeForce3 and my friend's GeForce4 Ti 4200 and my worries were over

So my conclusion is that when you install a radeon based card, you actually install it twice! so your system sctually sees 2 Radeon based cards for example!  So if you're going to install another 2 Voodoo'2, the system just will not accept it. That counts for WinXP Pro and Win 2K Pro, but for Win98SE I do not know

What you possibly could do is install Win98SE and then install your Radeon 9600 Pro with your Quantum 3D Obsidian X24 Voodoo2 card and see what happens there.

Is it a ATI 3dfx issue that is causing this to occur and is it a must that you need a nVidia card for your Voodoo2 Sli sets?  Well this question still remains to be answered.

I hope that I heped you out a little and I hope that someone can give us a reasonable answer here.

With Cool Regards,

Obi-Wan Kenobi

[Avenger]

Well, FV 4 have improved somewhat over 3.5. With 3.5 I got them mapmem error too, of course, but also I couldn't call up the advanced display properties with the V2 CP installed. That works with 4.0. So maybe 4.5 or 5.0 will finally allow V2 and Radeons to coexist And I don't think the Radeon being installed as two cards is the main problem. After all, the V2 are installed as 3D multimedia devices, not as video cards. Or maybe I'm wrong.

I think V2 drivers should be a priority. The V2 will outlive the V3/4/5 quite a bit. People are switching main cards, but V2 for Glide compatibility will always be in demand.

[Glide]

I think V2 drivers should be a priority. The V2 will outlive the V3/4/5 quite a bit. People are switching main cards, but V2 for Glide compatibility will always be in demand.

I also think Voodoo2 support is important and we are looking to completely solve these problems. Personally, I will continue to do all that I can...

I couldn't call up the advanced display properties with the V2 CP installed

Do thus: remove Radeon files (drivers and control panel) and Voodoo2 files (drivers and oc control panel) then reboot. So install ATI Catalyst packages (and reboot...) and FastVoodoo2 as suggested in release notes (and reboot...).
Let me know if now advanced properties are displayed.

Further both V2 get installed, but the V2 CP doesn't detect SLI.

This is a known and general (and minor) issue.

[Avenger]

Thanks for the reply, but as I said, that issue with the advanced display properties was only in FV 3.5, not in 4.0 GE anymore.

[Avenger]

As a thought, has it been tried to work together with Ati, or more specifically the Catalyst developers, to sort the compatibility issues out ? From reading the Rage3D and driverheaven.net forums it seems that the lead Catalyst programmer is someone who'd be willing to listen and help....

[koolsmoky]

The problem you guys are having are most likely due to a conflict between the memory mapped address space that the 3Dfx Voodoo2 and the ATI Radeon occupy. The cure is to remap the address of one of the two. The Voodoo2 requires 16Mbytes of address space and the default base address is 0xff000000.

It would be very nice if the ATI developers thow in a fix in their Radeon driver. If not, we need to make our own Voodoo2 miniport and to do that I need to at least know the PCI Vendor/DeviceID of the Radeons. If you have V.Control installed, open dos prompt, CD to its directory, and execute "v_ctrl dump". It will create a file named "hardinfo.txt" with the necessary info. Zip it and attach it to this message board.

KoolSmoky

[Avenger]

Done ! And thanks for looking into it

Download Attachment: hardinfo.zip
1.68 KB

[koolsmoky]

TY for the file Avenger. BTW, are you using the V2? According to the hardware info you attached, there's none installed. What memory range does the Windows Device Manager say they occupy?

KoolSmoky

[Avenger]

You're right, it isn't in right now. Little point of having the behemoth take up space and heat up the case as long as it won't work. Besides that, I couldn't get Earth 2150 installed as long as it was inside. The video test of that game tests Glide, and that cannot be skipped. Never got past the test with the Obsidian not working, so I had to remove it. I plan to put it back in and test with the next driver release.

[koolsmoky]

As much as I would like to help, it's impossible to tell anything if the hardware dump isn't taken with *both* the V2 and Radeon installed.

KoolSmoky

[Avenger]

No problem, I'll get to it later today.

Edit: Ok, here it is. Obsidian installed. I wish the Medusa cable was shielded...the 2D image quality loss is noticeable. But if I can get Glide running, I'm willing to accept that.

According to the device manager, number 1 uses D7000000-D7FFFFFF, number 2 uses D8000000-D8FFFFFF, the DEC PCI to PCI bridge on the Obsidian spans the whole range from D7000000-D8FFFFFF.

Download Attachment: hardinfo.zip
1.81 KB

[koolsmoky]

Fantastic. I'll see what I can do. One more question, what memory range does the Device Manager report for the Radeon?

KoolSmoky

[Avenger]

Ok, all the ranges for the Radeon as follows:

000A0000-000BFFFF primary
B0000000-BFFFFFFF primary
C0000000-CFFFFFFF secondary
D5000000-D500FFFF primary
D5010000-D501FFFF secondary

[Avenger]

Tagrineth has a working Obsidian next to a Radeon 9500 Pro under Windows XP. Hers is using F4000000-F4FFFFFF and F5000000-F5FFFFFF. Those ranges are reported free on my machine. So why isn't my card using them ? I can't manually change it either, not even in safe mode.