3dfxzone.it WorldWide Community

3dfx Hardware & Software => Voodoo2 Setup and tweaking => Topic started by: Avenger on 07 January 2004, 18:25:18

Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 07 January 2004, 18:25:18
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.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Obi-Wan Kenobi on 07 January 2004, 18:55:12
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


Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 08 January 2004, 00:03:22
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.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Glide on 08 January 2004, 00:13:56
QuoteI 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...

QuoteI 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.

QuoteFurther both V2 get installed, but the V2 CP doesn't detect SLI.
This is a known and general (and minor) issue.


Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 08 January 2004, 10:55:23
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.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 10 January 2004, 20:53:45
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....
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 11 January 2004, 13:26:53
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
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 11 January 2004, 17:23:29
Done ! And thanks for looking into it :)

Download Attachment: (https://www.3dfxzone.it/enboard/images/icon_paperclip.gif) hardinfo.zip (https://www.3dfxzone.it/enboard/../public/uploaded/Avenger/2004111172135_hardinfo.zip)
1.68 KB
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 12 January 2004, 02:18:50
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
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 12 January 2004, 09:03:14
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.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 12 January 2004, 11:28:45
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
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 12 January 2004, 11:31:26
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: (https://www.3dfxzone.it/enboard/images/icon_paperclip.gif) hardinfo.zip (https://www.3dfxzone.it/enboard/../public/uploaded/Avenger/200411211546_hardinfo.zip)
1.81 KB
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 12 January 2004, 12:50:54
Fantastic. I'll see what I can do. One more question, what memory range does the Device Manager report for the Radeon?

KoolSmoky
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 12 January 2004, 13:04:29
Ok, all the ranges for the Radeon as follows:

000A0000-000BFFFF primary
B0000000-BFFFFFFF primary
C0000000-CFFFFFFF secondary
D5000000-D500FFFF primary
D5010000-D501FFFF secondary
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 13 January 2004, 00:50:35
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.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 14 January 2004, 18:00:35
It looks like there's nothing wrong with the Obsidian's and Radeon's memory addresses. Could you tell me the exact error message? BTW, I see you're using the 5th PCI slot. Is it a master?

KoolSmoky
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 14 January 2004, 20:58:06
"mapmem returned an error trying to map memory", that's all. And then the Glide app exits and my desktop is screwed up. Icons in black and general display errors. I have to reboot to fix that. How could my 2D get messed up if there is no conflict ? I don't know about the PCI slot, I'm afraid that's beyond my technical knowledge. How do I find out if it is a master ?
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 15 January 2004, 10:21:17
QuoteHow could my 2D get messed up if there is no conflict ?
The memory address/space looks ok. At least Windows think so.

Perhaps the V2 or the Radeon is using unlisted resources without claiming them from the system or has failed to check if they are free to use.

BTW, has your setup worked with Windows 98?
QuoteHow do I find out if it is a master ?
Have you tried the VP6 manual? AFAIK, the V2 needs to be installed in a non-shared master slot.

Shoot me an email.

KoolSmoky
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 15 January 2004, 11:29:18
I've never tried it on Win98. My machine has one big NTFS partition, no dual-boot.

My VP6 manual says nothing about master or not, but it does list the shares. According to that, slot 5 is shared with the HPT RAID, slot 4 is shared with the USB and slot 1 is shared with the AGP as on every board I know. Guess I'll have some card shuffling to do, though I'd rather not have the Obsidian anywhere else than in the lowest slot.

Edit: It's impossible to move the card. In PCI slots 2-4 it would collide with either the floppy or the IDE connector. Slot 5 is the only possibility. I'd really like to try and change the resources for the Obsidian into the F range, but Windows won't let me...
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 16 January 2004, 07:57:23
QuoteI'd really like to try and change the resources for the Obsidian into the F range, but Windows won't let me...
You would have to remap the DEC PCI-to-PCI bridge first but if the Obsidian2 is a PnP device, Win2K has already mapped it into a valid open address space. I need your help to test a few things so drop me a line <koolsmoky at 3dfxzone dot it>.

KoolSmoky
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 16 January 2004, 11:53:20
You have mail :)
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Glide on 16 January 2004, 22:49:20
Good work guys ;)
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 16 January 2004, 22:54:31
Thanks :)
No positive result yet though.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Glide on 16 January 2004, 23:07:15
These will arrive [^]
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 17 January 2004, 00:12:43
I'll believe that :)
You guys have worked wonders already. My Voodoo 5 isn't in my main machine anymore, but it is in the secondary one. And OpenGL runs nicely with the MESAFX. In GLeXcess the V5 dropped under 1 FPS in the final zoom in of the crypt scene, on a P3 930 MHz. With MESA it does that same part at 30 FPS, on a K6-3 600 MHz.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 21 January 2004, 10:30:15
Hm, new Catalyst drivers are out. I'm not installing them yet, because I'm going the Omega driver route with my Radeon. Maybe the new Cats will help with the V2 issue, though I doubt it.

Edit: Right, no change. The 4.1 have made my Radeon more stable, though.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 06 February 2004, 19:20:47
Hm, maybe my dual CPUs are a problem ? They're probably the only thing where my system differs from other P3 machines where V2 work.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 02 April 2004, 21:39:25
To: Avenger
I've made another attempt to fix the mapmem errors. If your can spare some time to test, drop me an email.

- KoolSmoky
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 03 April 2004, 11:22:37
You have mail :)
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Grand Admiral Thrawn on 09 April 2004, 19:19:01
Got the same problem...
http://www.3dfxzone.it/enboard/topic.asp?TOPIC_ID=551
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 01 December 2004, 17:22:24
Mine is fixed, thanks to Koolsmoky. It was a conflict with my network card.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 12 December 2004, 18:45:08
I'm uploading what may help ppl experiencing desktop corruptions and memmap or mapmem errors. The fix is intended for all V2 cards, including Q3D Obsidian2.

The attachment contains bleeding-edge builds of Glide2 and Glide3 drivers from glide.sourceforge.net that Daniel and I have worked on. They should work without desktop corruptions. Also included are my modified windows miniport drivers which attempts to fix memmap or mapmem errors under win2k/xp.

Check out readme.txt before installing the drivers and post your feedbacks here. This is a test release! You have been warned. :D

Cheers,
KoolSmoky

edit: removed attachment
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Nightbird on 12 December 2004, 19:16:34
Yeah...
Thks to you !! :D
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: ps47 on 12 December 2004, 20:08:12
yes indeed,the glide2x fixes the desktop corruption for me (radeon9800pro)! great!
I can see that all reg setting are really ignored.is this permanent or just because the release is "beta"?
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 12 December 2004, 21:38:24
QuoteOriginally posted by ps47

I can see that all reg setting are really ignored.is this permanent or just because the release is "beta"?
The function will be added sometime in the future. ATM you can always set the env vars from the system environment.

-KoolSmoky
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: ps47 on 12 December 2004, 23:46:51
[8D]thanks.
great work!;)
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: dborca on 13 December 2004, 10:06:30
QuoteOriginally posted by ps47

is this permanent or just because the release is "beta"?
there will be a big (all-cards) glide3x release on sourceforge in the near future, so stay tuned. atm, we're working on revived code.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: ps47 on 16 December 2004, 09:26:51
hitman1 works with the new glide3x,but after exiting the game I have a black screen with frozen mouse (the pc however seems to be running,when I press alt+f4+enter it goes to sleep mode as usuall).the old glide3x (667) works,with an error message after exiting the game (some memory error,clicking ok is all I need to to)..
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 16 December 2004, 11:56:06
My PC simply freezes or reboots when I exit Unreal Gold. I can however use ALT TAB and then terminate it with the taskmanager.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Glide on 26 December 2004, 12:53:03
Newer Voodoo2 driver with Memmap fix is now on line: you can read setup info and grab it at this link: https://www.3dfxzone.it/news/reader.php?objid=579

This is an other great KoolSmoky work: I like thanks him here ;)

Good 3dfx gaming to all :)

Bye bye

Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Manuelson on 27 December 2004, 12:09:41
great KoolSmosky!!!! :-)
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: ps47 on 28 December 2004, 15:31:48
@koolsmoky:
that glide2x you made is absolutely great (glide2x,minigl games run without lag and there is no desktop corruption after exiting),but unfortunately,it doesnt work with wickedgl (using your glide2x,wickedgl cannot identify the voodoo2 properly,seems like my voodoo2 gets identified as voodoo3 or banshee[?]).wickedgl works fine with glide2x version 2.56.00.0459 (but corrupts the desktop after exiting[V])..
I hope this helps a bit..
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: duanevw on 05 January 2005, 02:38:51
Hello, I am new here nut not new to the Voodoo cards anyway's I digged my Quantum Obsidian x2 by Quantum 3d out of the closet still in the box even.  Anyway's  I plugged it in the motherboard with my Radeon 9600 pro installed the new memfix drivers.  I can run the donut demo thats it.  No NFL blitz glide, unreal tournament it goes black or freezes?  I know the other voodoo 2 drivers I couldn't get that far it would say window handle error and mem error.  I am running windows XP service pack 2 with a msi and barton XP core.


Thanks

Duane MI
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: PanoramixDruida on 07 January 2005, 17:52:04
Stupid question: how do I install it?. I've done right clic on the .inf file, install, and nothing happens. Thanks.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 07 January 2005, 19:35:27
That already did it. There is no message. Reboot to be sure and all should be go.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 13 January 2005, 22:58:46
OK, time for a new test release. I revised the memmap fix so more feedbacks are appreciated. As always, the glide files are bleeding-edge builds from SF. Both glide2x and glide3x will use 3dnow! or mmx instructions if your cpu supports it. Regtweaks will work and there's support for mismatched sli. Don't forget that you need to set special regtweaks for Q3D Obsidian2 boards. Also problems with WickedGL is fixed. Remember to uninstall any previous V2 driver before using this kit and read readme.txt!

If windows doesn't ask for a driver, open device manager and install the driver from there.

Those who are using win9x can use the new glide2x.dll and glide3x.dll by copying them to c:\windows\system.

If you post feedbacks, don't forget to include descriptions of your pc system, os, app version, if the app uses glide2 or glide3, etc.

Cheers,
KoolSmoky

edit: removed attachment
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: enthomologist on 14 January 2005, 01:48:48
Hi, i've just downloaded this and gave it a shot. Glide 2x works with the mismatched SLI as promised, however, i expected more than 30fps in 1024x768 through watching the Donut demo - i had about 100fps in 800x600 so far, both with vsync ON and OFF and such a drop is kinda problematic to me. Glide 3x doesn't work - it just makes "zzzooooot" sound in the background and the screen turns dark. Any suggestions? Grtz, Ent.
PS. I'll try them out with "Ignore_SLI_check" also.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 14 January 2005, 05:45:51
For starters, it would help to give a description of your pc system, os, app version, what V2 boards you're using, etc. ATM I'm not dealing with mixed driver sets for win2k,xp because it makes it difficult to track down a problem. Besure you've cleaned out all previous V2 files and envvars.

-KoolSmoky
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: enthomologist on 14 January 2005, 13:39:48
Yes, i'm sure my system was "3dfx clean" - i removed the driver from the Device Menager and manually removed infs (because unlike other drivers, 3dfx ones usually leave behind that sort of stuff) and registry entries, too. But ney, it doesn't work properly one way or another. Sometimes demos run both in glide2x and 3x just to fall into black with another round. One question: is fxoem2x.dll no longer needed (there was no such file in the package this time)? My specs are: Athlon XP 2000+, 512MB DDR RAM, Radeon 9550 128MB card as a primary adapter, one Colormax(not sure) 12MB V2 board and one totally unknown (just a sticker with "EON Electronics" on it - a retail brand?)12MB V2 in SLI;the system is Windows XP Pro SP2 with already integrated Directx9.0c. Cats are last 4.12 official. The mainboard is an ECS K7S5A. The SLI was properly detected in Win98SE and works fine for the moment on this platform with FV4.6, but produces a hell of a mess upon exit. From another hand, i couldn't menage to get a stable set of drivers working in SLI with Win2K/XP. No mixed set has been used by me so far, just sometimes put different glide files in game folders to run some problematic titles, but no such tricks this time. Regs, Ent.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 14 January 2005, 17:22:59
fxoem2x.dll isn't required if we're not using the TV out component. I removed the file from the kit so that the test environment would be simple. Just to be on the safe side search and delete all fxoem2x.dll, 3dfxspl2.dll, 3dfxspl3.dll, and ntremap.sys on your system. And be sure you install the test kit from the windows device manager.

So, what apps are you using and which V2 do you have the display connected to? Do you hear the apps running in the back when the screen is blank? Have you checked the SLI cable? Tried changing PCI slots or swapping them? Have you tried running with just single V2 installed?

Set SSTV2_SWAPBOARDS = 1 and see what happens.

-KoolSmoky
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: enthomologist on 14 January 2005, 23:35:14
Thanks for reply, more to follow. Regs, Ent.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: enthomologist on 16 January 2005, 14:02:38
After messing around for a while, i found it working at last. All i had to do was to "underclock" Voodoos - i set them to 90MHz. Voila, both glides work now (good job, KoolSmoky). All that stresses me up for a moment is glide2x performance, twice as low as glide3x - i put a glide2x.dll from the package to the Redguard's directory  and ran Win98, it was horrible, yet better run it via Glidos. Cheerz, Ent.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: koolsmoky on 16 January 2005, 16:38:01
QuoteOriginally posted by enthomologist

After messing around for a while, i found it working at last. All i had to do was to "underclock" Voodoos - i set them to 90MHz. Voila, both glides work now (good job, KoolSmoky). All that stresses me up for a moment is glide2x performance, twice as low as glide3x - i put a glide2x.dll from the package to the Redguard's directory  and ran Win98, it was horrible, yet better run it via Glidos. Cheerz, Ent.
Nice to hear you got your V2 working. Strange you mention underclocking though, the V2 defaults to 90MHz. I'll check if the driver is messing with the clock. Anyway, is Redguard the only app showing low performance? Could you point me to a demo? I'd appreaciate it if you would post some numbers. Does the performance change between win98 and winxp? Also check if the performance changes when you change the refreshrate of Glide. Use SSTV2_REFRESH_640x480 = 60

-KoolSmoky
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: enthomologist on 27 January 2005, 01:02:25
@KoolSmoky, about that glide performance: the newest 2x one (from your beta drivers package) shows average performance in Unreal Tournament v.436 (about 45fps), the best score belongs to FV4.6's win98 Glide (above 50fps, with desktop corruption problem of course) - all measured with vsync off, triple buffer off, glide dithering off, 1024x768@60Hz on highest settings, software sound, WinXP SP2, rest of my config above. In the Donut demo, where i can compare both Glide 2 and Glide 3 performance, there is 30fps (g2) and 60fps (g3), where FV4.0GE set shows, in this order, from ~50 to ~70fps in Win98 (1024x768@60Hz, glide environment as above). I excluded Redguard from comparison because 1 - this is a DOS game (no way to play it on XP); 2 - after toying with glide-switching it refused to launch finally for good.  Anyway, if you haven't played that glide-masterpiece back from '98 so far, i recommend you to get the demo @ http://www.uesp.net/redguard/files/redguarddemo.exe - enjoy.  Best regards, Ent.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: ps47 on 03 February 2005, 22:41:25
..I have tested the new glide2x as well,it runs fine,but only when refresh is set to 60Hz.if I set it higher,the game (unreal tournament) is somewhat jerky.the FPS remain the same,but the game is simply not as fluent.original glide2x doesnt have this problem..anyway it is still way better than desktop corruption or glide2x to 3x wrapper..

(athlonxp3000,radeon9800p,voodoo2 SLI 24MB A-Trend,Winxp)

edit: tested a bit more,and I get the jerkines with the wrapper as well,once I set FX_GLIDE_SWAPINTERVAL=1 (this basically enables v-sync).
any chance that your glide has v-sync enabled internally (I was not able to turn it off,not even envvars in *.bat file help)
to make it short:
60Hz+FX_GLIDE_SWAPINTERVAL=1 ->fine
85Hz+FX_GLIDE_SWAPINTERVAL=1 ->jerky
85Hz+FX_GLIDE_SWAPINTERVAL=0 ->fine
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: ps47 on 07 February 2005, 05:23:58
more stuff.seems like that jerkiness happens only with unreal tournament with refresh set to 75Hz or higher.deus ex runs fine with any refresh.the latest glide2x runs fine with wickedgl (yes!),and seems to be more compatible as well (Incubation finally recognizes the voodoo2 and runs in 3dfx mode.the game was crashing to desktop with the first glide2x you released).I couldnt get soldier of fortune2 working (getting a glide error using wickedgl+glide2x),but this seems to be related to the game (mesafx has problems as well).quake3 and return to castle wolfenstein run very vell (wickedgl+glide2x).counter-strike has some weird texture flicker when choosing the team for the first time,but the game itself is ok.weir thing is,it dissapiers for the second I want to make a screenshot,and the screenshot is ok..and umm,this may be trivial,but the 3dfx splash screen works somewhat weird (appearing too shortly or not at all,and it has the old 3dfx logo for some reason)..
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: ps47 on 08 February 2005, 19:50:23
..reinstalled UT,and the jerkiness is 99% gone.life is weird..
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: ps47 on 09 February 2005, 19:27:13
..ok,to sum it up,it seems like all native glide2x applications work fine (a bit slower though).opengl glide2x apps (using wickedgl or minigl) have some minor texture flicker problems (counter strike 1.5 when selecting team after entering the game,return to castle wolfestein when changing options from the ingame menu).soldier of forune2 doesnt start (babbling something about a glide error).anyway,its great to see my voodoo2 SLI working almost perfectly again.thanks[8D]
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: enthomologist on 09 February 2005, 23:08:46
@PS47: Are you using the "special" glide2x.dll from the "patch" directory for Radeon owners or stick with the regular version installed by default (2.56)?
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: cl1986 on 11 February 2005, 04:26:55
Are u guys serious, your using your 6 year old obsidian 2 sli2 boards or am i mis understanding u??

I am currently trying to install my Obsidian in winxp, dont think it will happen but would like to know what u guys think. Trying to use generic card with this excellerator to play bf1942.

What does this card do to the new cards like your 9600 pro???? Very curious and is it at all better????
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 11 February 2005, 10:00:53
The card allows Glide games to run in hardware. No wrappers, no less well supported (on the early games) alternative video mode. The age does not matter, the games I run on it are equally old. And the modern games are being handled by the Radeon. As long as I have a PCI slot in my PC and as long as I have drivers for my Obsidian, it's going to stay.

Your card should actually work well under XP, with the drivers found in this thread.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: cl1986 on 11 February 2005, 15:10:48
ok, i must be stupid.

I do a search on all forums i go to, and i can never find what im looking for. Please help me out here, im about 90% sure i have a x24. It looks like a sli card with a daughter board piggy back on it on what is like a riser. All it says is obisidian2 sli2 by quantum. Need driver for winxp and maybe instructions, as i have found some drivers that xp wont recongnize and just says driver info not found.

Ive done searches for obsidian2 sli2 and found this topic only, and also x24 driver and found absolutely nothing, well something about a voodoo3 3500, but nothing for me.

Ok i found the fast voodoo2, is this going to do it for me? 4.0 or 4.6??
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Avenger on 11 February 2005, 16:21:12
Well, the link to the drivers is on page 3 in this thread, but I'll repeat it anyway: https://www.3dfxzone.it/news/reader.php?objid=579
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Devildriver on 12 February 2005, 00:52:51
I installed Fast VooDoo GE drivers and fix for memory error, but if i start any game my computer is restarting :(
can some1 help me how to fix this problem?
Barton 2500+
Nforce2Ultra400 EPOX  8rda3i
Asus 9550GE/TD 128mb/128bit
if this bug is not fixed pls give me default voodoo2 win2k drivers or any working.in win98 my voodoo2 SLi work with default drivers, but with fast voodoo give memory error
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: cl1986 on 12 February 2005, 17:30:28
Tried said voodoo2 driver and my computer will lock up or give driver error. X24 board gets hotter than hell, didnt they have heatsinks back then???

I dont think its worth trying to get it to work, most games i have have directx or glide versions.
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: ps47 on 12 February 2005, 17:40:03
QuoteOriginally posted by enthomologist

@PS47: Are you using the "special" glide2x.dll from the "patch" directory for Radeon owners or stick with the regular version installed by default (2.56)?

..I'm using the glide2x from the latest koolsmoky's driver (ver. sourceforge 2.56.0.40404).I must use it because I have desktop corruption with the original glide2x..I'm not using the driver itself though,as I dont have any problems with memmap errors,so I use fastvoodoo2 4.0xp with koolsmoky's glide2x (dont fix something that isnt broken;))

@cl1986:
check here (http://www.inc_exe.szm.sk/hlp/default_fix.htm#SLI) if you want some information about voodoo2,drivers,SLI etc..
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Devildriver on 13 February 2005, 03:54:16
ps47 where can i find 2.56.0.40404 ? i cant find in sourceforge :(
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: ps47 on 13 February 2005, 21:17:00
..its included in the latest koolsmoky's voodoo2 driver,you can get it from here (http://www.vfdownloads.info/3dfx/voodoo2_xp_koolsmoky.zip)

..btw,I have just found out a weird thing.the original glide3x ver.670 actually creates desktop corruptions just like the original glide2x (using a radeon card of course).the strange thing is,the original glide3x ver.667 works perfectly fine.I think I'll check on older original glide2x releases to see if I find something similar..
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Devildriver on 13 February 2005, 22:16:24
when i use koolsmoky's voodoo2 driver, if i try to play games it gives me map memory error [i have r9550ge]
with fv2_fix_2k.exe games work fine, but in resolutions larger than 640X480 the lights [and any other effects] have a pink hue.can some1 help me how to remove this res problems?
i can play only with original driver [nt40v2.exe] but i cant install now [dont ask me why]
i tryed latest glide drivers from koolsmoky's web page, but games say this mode is not supported by ur  video card [like half-life].
i read this in koolsmoky's web page:
currently supports 3dfx Voodoo Banshee, Velocity, Voodoo3, Voodoo4, Voodoo5.
my voodoo2 is not supported?
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: enthomologist on 13 February 2005, 23:52:44
QuoteOriginally posted by Devildriver


with fv2_fix_2k.exe games work fine, but in resolutions larger than 640X480 the lights [and any other effects] have a pink hue.can some1 help me how to remove this res problems?
Try this:
regedit.exe
[hkey_local_machine]
Software\3Dfx Interactive\Voodoo2\Glide
(string) SSTV2_VIDEO_24BPP
value=0
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Devildriver on 14 February 2005, 12:58:30
tnx, it works now :P
only one more question:
Scanline Interleave:Detected!!       

FBI Revision:4      
Frame Buffer Memory:4 MB      
Texture Mapping Unit(s):2      
TMU Revision:4      
Total Texture Memory:8 MB      

My VooDoo2 is 8MB or 12MB? [8+4]
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: ps47 on 15 February 2005, 13:02:20
..ok radeon guys,got a present for ya-you have desktop corruption after exiting a glide2x app? well get the original 3dfx glide2x ver. 2.56.00.0456 (its in the beta directx7 win9x voodoo2 driver,get it here (http://www.inc_exe.szm.sk/glide2x_radeon.zip)),put it in your system32 folder,boom everything works.I almost cant believe the solution was so simple..
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: enthomologist on 16 February 2005, 20:44:18
@DevilDriver: you suspect allright, it's 12MB (8MB is for 2x2TMU and 4MB is for FBI):)
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: Devildriver on 17 February 2005, 18:04:34
ps47 if i install FastVooDoo2 4.0 and after restart install original WinNT Drivers all games work fine, tnx for the help :)
enthomologist tnx for the info ;)
and one more question:
I cant view FPS in games with normal programs like Fraps.What programs i need [i seeen one somewhere but i cant remember the name]
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: max1024 on 06 August 2007, 22:27:17
So question for all and especially for ps47. I'm looking for drivers for Obsidian2 X-24 on Win2K & XP. On the official Quantum3D page there are only drivers for W9X & Nt. I se the signature of ps47 where is written "Obsidian2 X-24,running xp pro" what set of drivers do you use ? I found non official drivers there http://www.geocities.com/shs_3dfx/download/Obsidian2_Win2k-XP.zip may be you use another ?
Title: Q3D Obsidian2 SLI2 X-24 problem, W2K
Post by: ps47 on 13 August 2007, 15:08:14
use koolsmoky's drivers,the obsidian is out of the pc right now but last time it worked fine.. http://www.3dfxzone.it/enboard/topic.asp?TOPIC_ID=1839