@Gary,
You can create one using the format from V4 4500 on the device.ini and modify it with ID VENDOR showed on V-Control for rampage card.

It will have same features as a V4 on V-Control.

Regards,
Oscar.

I got it back!

I don't trust the reported chip speed or indicated 16mb ram, we know the boards have 32 mb.

Gamma correction tools work though!! 

Now I need to get things stable, going to have to figure out a whole bunch of tweaking settings to keep stuff from crashing.

G1nX wrote on 15.06.13 at 13:07:16:


I have not tried it yet, just getting the beast to run this far has been chore enough without opening a fresh can of worms.

You are looking at several nights worth of effort with driver swapping, inf file hacking, BIOS poking, card swapping, several versions of directx installing/de-installing, bootlogging to find out what is crashing on start up, pulling hardware that may or may not be conflicting all the while staring at monitors that looks like faded ass when in DOS and smeared with grease when in windows at 1024 x 768 (the only way to get at some control tabs/panels)

(And please, no slight is intended nor implied toward Loeschzwerg who has his work cut out for him with no direct access to the hardware nor hi-res photos of the original and I have had very little feedback from the current original dongle owner as to picture quality)

Loeschzwerg has done a fantastic job and things would not have progressed to this point without his help, the dongle has been the least of my problems! Were both doing our best with the tools at hand, things will progress one step at a time.

In case you wanted to know what things looked like without the dongle, a simple solution is to not use it when I need a DOS window. In the case doing a hardware dump with v_control.

Is Koolsmoky still tinkering with the program? Here is the hardware dump that I got. Adding the proper ID string to the SYSTEM.INI file lets the program "properly" ID the board but no options are present even with a modified 4500/rampage INI file.

[Device 5]
device_name    = \\.\Display1
device_key     = System\CurrentControlSet\Services\Class\DISPLAY\0002
bus            = 1
dev            = 0
func           = 0
vendor         = 121a
device         = 10
subvendor      = 121a
subsystem      = 3
revision       = 1
command        = 3
status         = 230
class          = 3
sub_class      = 0
prog_interface = 0
agp_capability = 206002
agp_status     = 1f000237
agp_command    = 1f000301
pci_command    = 3
pci_status     = 230
base_address_0 = e0000000
base_address_1 = d0000008
base_address_2 = 9001
base_address_3 = 0
base_address_4 = 0
base_address_5 = 0

Had one crash too many I think, Win98 install is hosed. I can't get back onto a desktop with any hardware acceleration active. Time to call it a day and relax.

C++   i used but long time ago....
What do you want to know?

@Gary,
Possibly some info is got from voodoox.inf- Did you try to use the inf from Rashly driver and check what info you get on 3Dfx Tool?

- Oscar.

Excellent new!!! Now times to check if your system is enough stable for testing D3D games without BSOD.

- Oscar.