Ошибка не найден драйвер spooge скачать для warhammer 40000 dawn of war

Ошибки драйвер не найден warhammer 40000

This worked for my retail editions of DoW, DoW: Winter Assault, and DoW: Dark Crusade

1. Go to your DoW file(where you installed your game, usually the «THQ» folder).
2. Open the game folder you currently have (e.g. Winter Assault, Dark Crusade)
3. Open your «Drivers» folder.
4. Open the «spdx9_config» file.
5. Scroll down to your appropriate video card (e.g Nvidia, ati).
6. Find the «allowdevice 0» lines.
7. Change the «0» to «1» on all the «allowdevice 0» lines.
8. Save the file as «spdx9_config». You may have to delete the original to do so.
9. Try running the game.
***Note: Don’t include the apostrophes (» «). Disregard them. I only used them as separators.

Think we are trying to rediscover the weel 🙂

I found this post that worked for me

The poster Spider008 Says :

This is my first post on this site but here is the solution I’ve found and I’ve done it on two different PCs to get Dawn of War and Winter Assault to run on a 64 bit Windows 7 platform:

1. Install Dawn of War and the other chapters if you have them

2. In ‘C:Program Files (x86)THQDawn Of WarDrivers’ there are two files spdx9_config.txt and nvidia.txt, create a new folder say ‘Archive’ in there create two further folders ‘Original’ & ‘Modded’, this can be in the same directory — you need to keep the original files.

3. The protection/permissions stops you altering the txt files but does not stop you copying over files.

4. So on your desktop create two dummy txt files and name them as the above and copy these into the ‘Modded’ folder, they don’t need any content at all, they just need the right file names.

5. Copy your original files into the other folder, Original, as you will need these to add patches later, I believe the software does a volume check on the txt files and recognises it’s changed — unsure but not a problem. Just copy them back when updating the game.

6. Place the dummy files into ‘C:Program Files (x86)THQDawn Of WarDrivers’ and then run the game — it should all work fine now but I’d advise not going for the Window option on configure as I found it buggey on my machine.

One after thought I’ve yet to test but the TXT files make reference to various graphics cards, if you delete reference to the make you have I believe it should work but yet to try it as the current method works fine, I’ve also noticed that the two PCs react differently on the intro, I can exit the movie sequence on my machine but on my son’s he can’t?!

Think we are trying to rediscover the weel 🙂

I found this post that worked for me

The poster Spider008 Says :

This is my first post on this site but here is the solution I’ve found and I’ve done it on two different PCs to get Dawn of War and Winter Assault to run on a 64 bit Windows 7 platform:

1. Install Dawn of War and the other chapters if you have them

2. In ‘C:Program Files (x86)THQDawn Of WarDrivers’ there are two files spdx9_config.txt and nvidia.txt, create a new folder say ‘Archive’ in there create two further folders ‘Original’ & ‘Modded’, this can be in the same directory — you need to keep the original files.

3. The protection/permissions stops you altering the txt files but does not stop you copying over files.

4. So on your desktop create two dummy txt files and name them as the above and copy these into the ‘Modded’ folder, they don’t need any content at all, they just need the right file names.

5. Copy your original files into the other folder, Original, as you will need these to add patches later, I believe the software does a volume check on the txt files and recognises it’s changed — unsure but not a problem. Just copy them back when updating the game.

6. Place the dummy files into ‘C:Program Files (x86)THQDawn Of WarDrivers’ and then run the game — it should all work fine now but I’d advise not going for the Window option on configure as I found it buggey on my machine.

One after thought I’ve yet to test but the TXT files make reference to various graphics cards, if you delete reference to the make you have I believe it should work but yet to try it as the current method works fine, I’ve also noticed that the two PCs react differently on the intro, I can exit the movie sequence on my machine but on my son’s he can’t?!

Источник

Ошибки драйвер не найден warhammer 40000

This worked for my retail editions of DoW, DoW: Winter Assault, and DoW: Dark Crusade

1. Go to your DoW file(where you installed your game, usually the «THQ» folder).
2. Open the game folder you currently have (e.g. Winter Assault, Dark Crusade)
3. Open your «Drivers» folder.
4. Open the «spdx9_config» file.
5. Scroll down to your appropriate video card (e.g Nvidia, ati).
6. Find the «allowdevice 0» lines.
7. Change the «0» to «1» on all the «allowdevice 0» lines.
8. Save the file as «spdx9_config». You may have to delete the original to do so.
9. Try running the game.
***Note: Don’t include the apostrophes (» «). Disregard them. I only used them as separators.

thanks a lot, I was not able to play this game in a long time, but your post did it.

I did it usung notepad, there is a function «exchange» that can be opened by CTRL+H, because there are a lot of entries that need to be changed.

thanks a lot, I was not able to play this game in a long time, but your post did it.

I did it usung notepad, there is a function «exchange» that can be opened by CTRL+H, because there are a lot of entries that need to be changed.

All attempted fixes are appreciated, but this does NOT fix the current problem with getting WH40K Gold and Winter Assault Editions to run since the last STEAM patch.

examining the file noted in the proposed solution above, first the file had not been changed since April 7, 2013 . well over a year ago. Second, the block for my video card (Nvidia) did not have the line mentioned. Those txt blocks were to exclude or include certain very old and now obscure video cards. The original post this fix comes from is dated April 27, 2008 . yes , thats over 6 years ago.

im not saying that this solution didnt help someone (maybe with an old computer system or lapotp), perhaps, but it is not the solution for the issue the rest of us are having.

We look forward to some kind of reply from the STEAM people.

All attempted fixes are appreciated, but this does NOT fix the current problem with getting WH40K Gold and Winter Assault Editions to run since the last STEAM patch.

examining the file noted in the proposed solution above, first the file had not been changed since April 7, 2013 . well over a year ago. Second, the block for my video card (Nvidia) did not have the line mentioned. Those txt blocks were to exclude or include certain very old and now obscure video cards. The original post this fix comes from is dated April 27, 2008 . yes , thats over 6 years ago.

im not saying that this solution didnt help someone (maybe with an old computer system or lapotp), perhaps, but it is not the solution for the issue the rest of us are having.

We look forward to some kind of reply from the STEAM people.

Maybe it only works for Win 7..
And who says the fix can´t work just because it´s 6 years old?

The PC i used back then had an i5 (sandy bridge, I think) and a gtx 560, so it wasn´t THAT old.
I´m pretty sure i have had it running with my current PC as well — which runs Sabertooth Z97, i7-4770K, GTX 780 SuperClocked, win7 64bit, and SSD´s.

But feel free to post it if you find a solution that works for your setup 🙂

WHA? is right. This has nothing to do with the current problem.
The Spooge driver settings which are edited in this file have nothing to do with operating system — only with the graphics card vendor and model.

for most if not all users by now the first line is the one that will be used, and that one is already:
allowdevice 1
on a fresh install of the game.

for example the allowdevice 0 in the 3dfx block will disallow all 3dfx made graphics cards which fail initialization AFTER that general setting in the first line. who still uses those?

in the ati and nvidia blocks (which i assume are the ones relevant today — perhaps some modern intel chips too, but the intel block is very specific about some very old chips used mostly in very old — read 10+ years — notebooks) there is no override of the first line of allowdevice, so you could not set those to 1 either — it’s already 1 from the general setting of the first line.

the rest of the settings are so old by now, they probably aren’t relevant vor most anybody and will be ignored if you don’t use a graphics card of those vendors (or specific models).

so thanks for your input, but this really is not the current problem people have starting the game.

i’d assume the problem is more in the line of an incompatibility with windows 8.1u (at least that’s what i’m running and the game doesn’t start for me — doesn’t write logs either, which it would do if it only did find the wrong graphics setting — i tested this by setting the general allowdevice to 0 — in that case the graphics config utility does not work — with setting to 1 the graphic configuration works, i can test the settings, see the space marine, finish the graphics config and then the game does nothing).

if it’s not windows 8.1u, it probably is an error which got introduced with the last patch. this is the reason why so many people want to hear from relic.

also: i ran dow goty on this specific machine earlier this year. could have been before the windows 8.1 update, definitely was before the windows 8.1u update. but hardware is the same. which further leads to the conclusion it is either windows 8.1u incompatibility — anyone here got the game running on win8.1u with a radeon graphics card? — or a patch problem specific to some of the users setups.

i would guess it’s nothing graphics related at all — after all i can view that space marine test from the graphics config utility. but what the real reason is? beats me.

also, i read somewhere here on the forums that someone had found an error message (i didn’t) saying something about an error with ntdll.dll which is not part of the game but part of windows. so from that info i gathered it might be a compatibility problem. sadly using the «compatibility settings» you can set for any executable in windows does not help me.

WHA? is right. This has nothing to do with the current problem.
The Spooge driver settings which are edited in this file have nothing to do with operating system — only with the graphics card vendor and model.

for most if not all users by now the first line is the one that will be used, and that one is already:
allowdevice 1
on a fresh install of the game.

for example the allowdevice 0 in the 3dfx block will disallow all 3dfx made graphics cards which fail initialization AFTER that general setting in the first line. who still uses those?

in the ati and nvidia blocks (which i assume are the ones relevant today — perhaps some modern intel chips too, but the intel block is very specific about some very old chips used mostly in very old — read 10+ years — notebooks) there is no override of the first line of allowdevice, so you could not set those to 1 either — it’s already 1 from the general setting of the first line.

the rest of the settings are so old by now, they probably aren’t relevant vor most anybody and will be ignored if you don’t use a graphics card of those vendors (or specific models).

so thanks for your input, but this really is not the current problem people have starting the game.

i’d assume the problem is more in the line of an incompatibility with windows 8.1u (at least that’s what i’m running and the game doesn’t start for me — doesn’t write logs either, which it would do if it only did find the wrong graphics setting — i tested this by setting the general allowdevice to 0 — in that case the graphics config utility does not work — with setting to 1 the graphic configuration works, i can test the settings, see the space marine, finish the graphics config and then the game does nothing).

if it’s not windows 8.1u, it probably is an error which got introduced with the last patch. this is the reason why so many people want to hear from relic.

also: i ran dow goty on this specific machine earlier this year. could have been before the windows 8.1 update, definitely was before the windows 8.1u update. but hardware is the same. which further leads to the conclusion it is either windows 8.1u incompatibility — anyone here got the game running on win8.1u with a radeon graphics card? — or a patch problem specific to some of the users setups.

i would guess it’s nothing graphics related at all — after all i can view that space marine test from the graphics config utility. but what the real reason is? beats me.

also, i read somewhere here on the forums that someone had found an error message (i didn’t) saying something about an error with ntdll.dll which is not part of the game but part of windows. so from that info i gathered it might be a compatibility problem. sadly using the «compatibility settings» you can set for any executable in windows does not help me.

I made this post in january 2013, and for some reason it has got a lot more views in the past days.
I haven´t played the game for a long time, so this post was made as a solution that worked at that time.
You can`t (appearently) count it as input for the current issue, but if there is people out there with older systems who can solve their problems by using the solution i posted 1,5 years ago, then that´s fine.
I didn´t make this post 1,5 years ago, because I had a timetraveling evil plan about posting wrong fixes for issues that would first occur 1,5 years after the post was made.

I´m not trying to act like an idiot by giving people wrong fixes here; I have no way of knowing that it doesn´t work anyway as I don´t have the game installed currently.
The post was highly relevant and helpful at the time it was made — if that´s not the case anymore then that´s unfortunate, but you can´t blame my Jan 2013 post for that.

Источник

I’ve had a few issues with Dawn of War over the years, so I thought I’d share my experiences. You’ve mentioned that you’ve done some of these steps, but for sanity’s sake I’m going to list them all anyway:

Working with what you’ve got

Sometimes Windows’ permissions & security can get in the way of you actually using your PC.

• Navigate to where the Dawn of War folder was installed. It’s probably C:Program Files (x86)THQDawn of War.
• Find the game’s application .exe file.
• Right Click -> Properties -> Compatibility tab
  • Check ‘Run this Program in Compatibility mode’ and select Windows 7 (to start with, try Windows XP SP3 if 7 doesn’t work)
  • Check ‘Run this program as an Administrator’ as well.
• Try to run the game.

Drivers, Updates and Installations

Assuming you’ve made it this far then there is a high likelihood you will need to try installing again. but first, we can try updating your PC, and installing necessary drivers.

• If you have pending updates, restart your PC to install them. It’s entirely possible that one of these updates contains the missing or updated Direct X library or some other driver you need.
• Check for and install the latest version of your Graphics Card drivers
• Completely uninstall the games, and install them again, one at a time and confirm they work.
  • If during installation the game asks if you want to install Direct X as well, make sure you click ‘Yes’ and follow the prompts. (It’s been so long since I installed the standalone version that I can’t remember if Dawn of War does this).
  • Start with Dawn of War, then Winter Assault, and finally Dark Crusade (even though it’s a standalone, do it last).

Desperate Times

So, you’ve gotten through the above and the game still isn’t running. According to a source on Relic’s forums, you may need to play around with some config files.

To summarise the steps in the link:

1. Have Dawn of War & Expansions fully installed

2. Navigate to the Dawn of War directory C:Program Files (x86)THQDawn of War.

3. Find the Drivers folder. Inside this folder there are two files, spdx9_config.txt, and nvidia.txt

4. Create a folder called something like Originals and move these files into it. You may need the original files later if/when you need to download and install updates.

5. Create two empty files with the same names as the files above.
6. Place the dummy files into Drivers and run the game. It should hopefully launch fine.

The author advises not going for the Window option on configure as he found it buggy.

Edit: I did some more investigating, and what the spdx9_config.txt file actually does is lists compatible graphics cards. Unfortunately the game was built to take this list seriously, and as the list has never been updated (from a fresh install perspective at least), the game fails when it can’t find your graphics card on the list.

Luckily, I’ve found an updated file (as of Dec 19, 2012 at least), which I’ve pasted here. Copy the entirety of this scroll area into your new (empty) spdx9_config.txt file.

;;;;


;
; spDx9_config.txt : configuration for the Dx9 PC spooge driver
;

; configfile : set of shader compiler scripts

; allowdevice : allows cards to always fail initialization
allowdevice 1

; allowhwtnl : allows hardware TnL to be used
allowhwtnl 1

; allowtfactor : allows the TFactor to be used as a constant colour
allowtfactor 1

; allowhwcursor : allows the use of the Dx8 cursor system
allowhwcursor 1

; allow32bitdisplay : allows 32bit display modes
allow32bitdisplay 1

; disableslowalpha : when alpha flipping is not available, don't allow dest alpha
disableslowalpha 1

; allowrgba4np2 : allows D3DFMT_A4R4G4B4 for NP2 textures
allowrgba4np2 1

; isslowcard : used as a hint to automatic configuration to use lower numbers
isslowcard 0

; togglemodeonstartup : tells the driver to toggle the bit depth before starting the device
; fixes problems with running after an OpenGL game

; maxstage : sets a maximum number of texture stages to use
; maxtexture : sets a maximum number of textures to use (in one pass)
; allowtfactor : allows compiler to use tfactor (it is sometimes emulated using the diffuse channel)
; allowtemp : allows compiler to use D3DTA_TEMP as a result
; allowlookupdudv : allows EMBM texturing
; allowrender2texture : allows render to texture
; allowpalettedtextures : allows paletted textures to be created

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; 3dfx
;
begin vendor 0x121a
; Disabled cards (below min-spec)
allowdevice 0
end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; ATI
;
begin vendor 0x1002

configfile ati.txt

allowlookupdudv 0

; Disabled cards (below min-spec)
; RAGE MOBILITY 128 M4 (RAGE 128 PRO based)
begin device 0x4D46
allowdevice 0
end
begin device 0x4D4C
allowdevice 0
end
; RAGE MOBILITY 128 M3 (RAGE 128 PRO based)
begin device 0x4C45 0x4C46
allowdevice 0
end
; RAGE 128 PRO ULTRA
begin device 0x5446
allowdevice 0
end
begin device 0x544C
allowdevice 0
end
begin device 0x5452 0x5455
allowdevice 0
end
; RAGE 128 4X
begin device 0x5345 0x5348
allowdevice 0
end
begin device 0x534B 0x534E
allowdevice 0
end
; RAGE 128 PRO GL
begin device 0x5041 0x5046
allowdevice 0
end
; RAGE 128 PRO VR
begin device 0x5047 0x5058
allowdevice 0
end
; RAGE 128 GL
begin device 0x5245 0x5246
allowdevice 0
end
begin device 0x534B 0x534D
allowdevice 0
end
; RAGE 128 VR
begin device 0x524B 0x524C
allowdevice 0
end
begin device 0x5345 0x5347
allowdevice 0
end
; RAGE MOBILITY M/M1/P (RAGE PRO based)
begin device 0x4C4D
allowdevice 0
end
begin device 0x4C52
allowdevice 0
end
; RAGE LT-PRO (RAGE PRO based)
begin device 0x4C42
allowdevice 0
end
begin device 0x4C49 0x4C50
allowdevice 0
end
; RAGE LT (RAGE II based)
begin device 0x4C47
allowdevice 0
end
; RAGE XL (RAGE PRO based)
begin device 0x474D
allowdevice 0
end
begin device 0x474F
allowdevice 0
end
begin device 0x4752
allowdevice 0
end
; RAGE XC (RAGE PRO based)
begin device 0x474C
allowdevice 0
end
begin device 0x474E
allowdevice 0
end
; RAGE PRO
begin device 0x4742
allowdevice 0
end
begin device 0x4744
allowdevice 0
end
begin device 0x4749 0x4750
allowdevice 0
end
; RAGE IIC AGP
begin device 0x4757
allowdevice 0
end
begin device 0x4759 0x475A
allowdevice 0
end
; RAGE IIC PCI
begin device 0x4756
allowdevice 0
end
begin device 0x5656
allowdevice 0
end
; RAGE II+
begin device 0x4755
allowdevice 0
end
; RAGE II
begin device 0x4754
allowdevice 0
end

; Radeon 7000
        begin device 0x5159
allowdevice 0
end


; Slow cards
; Radeon 7500
begin device 0x5157
isslowcard 1
end
; Mobility Radeon 7500
begin device 0x4C57
isslowcard 1
end
; Radeon/Radeon 7200
begin device 0x5144 0x5147
isslowcard 1
end
; Radeon IGP
begin device 0x4336 0x4337
isslowcard 1
end
; Radeon IGP
begin device 0x4437
isslowcard 1
end
; Radeon VE/Radeon 7000
begin device 0x515A
isslowcard 1
end
; Mobility Radeon
begin device 0x4C59 0x4C5A
isslowcard 1
end
end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; nVidia
;
begin vendor 0x10DE

configfile nvidia.txt'

; disable drivers prior to version 52.16 (previous versions have quirks with directx 9 in win98)

begin version 0x0000 0x000D
allowdevice 1
end
begin subversion 0x0000 0x0009
allowdevice 1
end

begin build 0x0000 0x1459
allowdevice 1
end

; Disabled cards (below min-spec)
; RIVA TNT
begin device 0x0020
allowdevice 0
end
; RIVA TNT2/TNT2 Pro
begin device 0x0028
allowdevice 0
end
; RIVA TNT2 Ultra
begin device 0x0029
allowdevice 0
end
; Vanta/Vanta LT
begin device 0x002C
allowdevice 0
end
; RIVA TNT2 Model 64/Model 64 Pro
begin device 0x002D
allowdevice 0
end
; Aladdin TNT2
begin device 0x00A0
allowdevice 0
end

; NV1x (GeForce 256/2/2mx/4mx)
begin device 0x0100 0x01FF
allowrgba4np2 0
isslowcard 1
end

        ;  nvidia genius reused a segment inside the 0x01.. range of ids for the NV43 line
        ;  turn on what has been turned off by previous group of devices for this cards
        ;       NV43 Geforce 6200,6600/6610 GT/PCI, Quadro FX540,  line
        begin device 0x0140 0x014F
              isslowcard 0
              allowrgba4np2 1
              allowhwtnl 1
        end
end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; Matrox
;
begin vendor 0x102b

; G550
begin device 0x2527
allowdevice 0
end

; G400/G450
begin device 0x0525
allowdevice 0
end

end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; Intel
;
begin vendor 0x8086

isslowcard 1

; 810 (and 810e)
begin device 0x7121 0x7123
allowdevice 0
end

; Intel(R) 82810E
begin device 0x7125
allowdevice 0
end


end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; S3
;
begin vendor 0x5333

isslowcard 1

; Savage4
begin device 0x8a22
allowdevice 0
end

; ProSavage
begin device 0x8A26
allowdevice 0
end

; ProSavageDDR
begin device 0x8D02
allowdevice 0
end

begin device 0x8D04
allowdevice 0
end

; Savage 2000
begin device 0x9102
allowdevice 0
end

end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; SiS
;
begin vendor 0x1039

isslowcard 1

; 315/315e
begin device 0x0325
allowdevice 0
end

; xabre
begin device 0x0330
allowdevice 0
end

; 630/730
begin device 0x6300
allowdevice 0
end

; SIS (M)650, 651
begin device 0x6325
allowdevice 0
end
end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; Trident
;
begin vendor 0x1023
; Blade XP
begin device 0x9910
allowdevice 0
end

; CyberBlade XP
begin device 0x8820
allowdevice 0
end
end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; PowerVR
;
begin vendor 0x104A
end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; VIA/S3G
;
begin vendor 0x1106

isslowcard 1

; UniChrome Graphics, KM400/KN400
begin device 0x7205
allowdevice 0
end

; UniChrome Graphics, KM400/KN400
begin device 0x9910
allowdevice 0
end

end
;;;

I’ve had a few issues with Dawn of War over the years, so I thought I’d share my experiences. You’ve mentioned that you’ve done some of these steps, but for sanity’s sake I’m going to list them all anyway:

Working with what you’ve got

Sometimes Windows’ permissions & security can get in the way of you actually using your PC.

• Navigate to where the Dawn of War folder was installed. It’s probably C:Program Files (x86)THQDawn of War.
• Find the game’s application .exe file.
• Right Click -> Properties -> Compatibility tab
  • Check ‘Run this Program in Compatibility mode’ and select Windows 7 (to start with, try Windows XP SP3 if 7 doesn’t work)
  • Check ‘Run this program as an Administrator’ as well.
• Try to run the game.

Drivers, Updates and Installations

Assuming you’ve made it this far then there is a high likelihood you will need to try installing again. but first, we can try updating your PC, and installing necessary drivers.

• If you have pending updates, restart your PC to install them. It’s entirely possible that one of these updates contains the missing or updated Direct X library or some other driver you need.
• Check for and install the latest version of your Graphics Card drivers
• Completely uninstall the games, and install them again, one at a time and confirm they work.
  • If during installation the game asks if you want to install Direct X as well, make sure you click ‘Yes’ and follow the prompts. (It’s been so long since I installed the standalone version that I can’t remember if Dawn of War does this).
  • Start with Dawn of War, then Winter Assault, and finally Dark Crusade (even though it’s a standalone, do it last).

Desperate Times

So, you’ve gotten through the above and the game still isn’t running. According to a source on Relic’s forums, you may need to play around with some config files.

To summarise the steps in the link:

1. Have Dawn of War & Expansions fully installed

2. Navigate to the Dawn of War directory C:Program Files (x86)THQDawn of War.

3. Find the Drivers folder. Inside this folder there are two files, spdx9_config.txt, and nvidia.txt

4. Create a folder called something like Originals and move these files into it. You may need the original files later if/when you need to download and install updates.
5. Create two empty files with the same names as the files above.
6. Place the dummy files into Drivers and run the game. It should hopefully launch fine.

The author advises not going for the Window option on configure as he found it buggy.

Edit: I did some more investigating, and what the spdx9_config.txt file actually does is lists compatible graphics cards. Unfortunately the game was built to take this list seriously, and as the list has never been updated (from a fresh install perspective at least), the game fails when it can’t find your graphics card on the list.

Luckily, I’ve found an updated file (as of Dec 19, 2012 at least), which I’ve pasted here. Copy the entirety of this scroll area into your new (empty) spdx9_config.txt file.

;;;;


;
; spDx9_config.txt : configuration for the Dx9 PC spooge driver
;

; configfile : set of shader compiler scripts

; allowdevice : allows cards to always fail initialization
allowdevice 1

; allowhwtnl : allows hardware TnL to be used
allowhwtnl 1

; allowtfactor : allows the TFactor to be used as a constant colour
allowtfactor 1

; allowhwcursor : allows the use of the Dx8 cursor system
allowhwcursor 1

; allow32bitdisplay : allows 32bit display modes
allow32bitdisplay 1

; disableslowalpha : when alpha flipping is not available, don't allow dest alpha
disableslowalpha 1

; allowrgba4np2 : allows D3DFMT_A4R4G4B4 for NP2 textures
allowrgba4np2 1

; isslowcard : used as a hint to automatic configuration to use lower numbers
isslowcard 0

; togglemodeonstartup : tells the driver to toggle the bit depth before starting the device
; fixes problems with running after an OpenGL game

; maxstage : sets a maximum number of texture stages to use
; maxtexture : sets a maximum number of textures to use (in one pass)
; allowtfactor : allows compiler to use tfactor (it is sometimes emulated using the diffuse channel)
; allowtemp : allows compiler to use D3DTA_TEMP as a result
; allowlookupdudv : allows EMBM texturing
; allowrender2texture : allows render to texture
; allowpalettedtextures : allows paletted textures to be created

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; 3dfx
;
begin vendor 0x121a
; Disabled cards (below min-spec)
allowdevice 0
end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; ATI
;
begin vendor 0x1002

configfile ati.txt

allowlookupdudv 0

; Disabled cards (below min-spec)
; RAGE MOBILITY 128 M4 (RAGE 128 PRO based)
begin device 0x4D46
allowdevice 0
end
begin device 0x4D4C
allowdevice 0
end
; RAGE MOBILITY 128 M3 (RAGE 128 PRO based)
begin device 0x4C45 0x4C46
allowdevice 0
end
; RAGE 128 PRO ULTRA
begin device 0x5446
allowdevice 0
end
begin device 0x544C
allowdevice 0
end
begin device 0x5452 0x5455
allowdevice 0
end
; RAGE 128 4X
begin device 0x5345 0x5348
allowdevice 0
end
begin device 0x534B 0x534E
allowdevice 0
end
; RAGE 128 PRO GL
begin device 0x5041 0x5046
allowdevice 0
end
; RAGE 128 PRO VR
begin device 0x5047 0x5058
allowdevice 0
end
; RAGE 128 GL
begin device 0x5245 0x5246
allowdevice 0
end
begin device 0x534B 0x534D
allowdevice 0
end
; RAGE 128 VR
begin device 0x524B 0x524C
allowdevice 0
end
begin device 0x5345 0x5347
allowdevice 0
end
; RAGE MOBILITY M/M1/P (RAGE PRO based)
begin device 0x4C4D
allowdevice 0
end
begin device 0x4C52
allowdevice 0
end
; RAGE LT-PRO (RAGE PRO based)
begin device 0x4C42
allowdevice 0
end
begin device 0x4C49 0x4C50
allowdevice 0
end
; RAGE LT (RAGE II based)
begin device 0x4C47
allowdevice 0
end
; RAGE XL (RAGE PRO based)
begin device 0x474D
allowdevice 0
end
begin device 0x474F
allowdevice 0
end
begin device 0x4752
allowdevice 0
end
; RAGE XC (RAGE PRO based)
begin device 0x474C
allowdevice 0
end
begin device 0x474E
allowdevice 0
end
; RAGE PRO
begin device 0x4742
allowdevice 0
end
begin device 0x4744
allowdevice 0
end
begin device 0x4749 0x4750
allowdevice 0
end
; RAGE IIC AGP
begin device 0x4757
allowdevice 0
end
begin device 0x4759 0x475A
allowdevice 0
end
; RAGE IIC PCI
begin device 0x4756
allowdevice 0
end
begin device 0x5656
allowdevice 0
end
; RAGE II+
begin device 0x4755
allowdevice 0
end
; RAGE II
begin device 0x4754
allowdevice 0
end

; Radeon 7000
        begin device 0x5159
allowdevice 0
end


; Slow cards
; Radeon 7500
begin device 0x5157
isslowcard 1
end
; Mobility Radeon 7500
begin device 0x4C57
isslowcard 1
end
; Radeon/Radeon 7200
begin device 0x5144 0x5147
isslowcard 1
end
; Radeon IGP
begin device 0x4336 0x4337
isslowcard 1
end
; Radeon IGP
begin device 0x4437
isslowcard 1
end
; Radeon VE/Radeon 7000
begin device 0x515A
isslowcard 1
end
; Mobility Radeon
begin device 0x4C59 0x4C5A
isslowcard 1
end
end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; nVidia
;
begin vendor 0x10DE

configfile nvidia.txt'

; disable drivers prior to version 52.16 (previous versions have quirks with directx 9 in win98)

begin version 0x0000 0x000D
allowdevice 1
end
begin subversion 0x0000 0x0009
allowdevice 1
end

begin build 0x0000 0x1459
allowdevice 1
end

; Disabled cards (below min-spec)
; RIVA TNT
begin device 0x0020
allowdevice 0
end
; RIVA TNT2/TNT2 Pro
begin device 0x0028
allowdevice 0
end
; RIVA TNT2 Ultra
begin device 0x0029
allowdevice 0
end
; Vanta/Vanta LT
begin device 0x002C
allowdevice 0
end
; RIVA TNT2 Model 64/Model 64 Pro
begin device 0x002D
allowdevice 0
end
; Aladdin TNT2
begin device 0x00A0
allowdevice 0
end

; NV1x (GeForce 256/2/2mx/4mx)
begin device 0x0100 0x01FF
allowrgba4np2 0
isslowcard 1
end

        ;  nvidia genius reused a segment inside the 0x01.. range of ids for the NV43 line
        ;  turn on what has been turned off by previous group of devices for this cards
        ;       NV43 Geforce 6200,6600/6610 GT/PCI, Quadro FX540,  line
        begin device 0x0140 0x014F
              isslowcard 0
              allowrgba4np2 1
              allowhwtnl 1
        end
end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; Matrox
;
begin vendor 0x102b

; G550
begin device 0x2527
allowdevice 0
end

; G400/G450
begin device 0x0525
allowdevice 0
end

end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; Intel
;
begin vendor 0x8086

isslowcard 1

; 810 (and 810e)
begin device 0x7121 0x7123
allowdevice 0
end

; Intel(R) 82810E
begin device 0x7125
allowdevice 0
end


end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; S3
;
begin vendor 0x5333

isslowcard 1

; Savage4
begin device 0x8a22
allowdevice 0
end

; ProSavage
begin device 0x8A26
allowdevice 0
end

; ProSavageDDR
begin device 0x8D02
allowdevice 0
end

begin device 0x8D04
allowdevice 0
end

; Savage 2000
begin device 0x9102
allowdevice 0
end

end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; SiS
;
begin vendor 0x1039

isslowcard 1

; 315/315e
begin device 0x0325
allowdevice 0
end

; xabre
begin device 0x0330
allowdevice 0
end

; 630/730
begin device 0x6300
allowdevice 0
end

; SIS (M)650, 651
begin device 0x6325
allowdevice 0
end
end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; Trident
;
begin vendor 0x1023
; Blade XP
begin device 0x9910
allowdevice 0
end

; CyberBlade XP
begin device 0x8820
allowdevice 0
end
end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; PowerVR
;
begin vendor 0x104A
end


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; VIA/S3G
;
begin vendor 0x1106

isslowcard 1

; UniChrome Graphics, KM400/KN400
begin device 0x7205
allowdevice 0
end

; UniChrome Graphics, KM400/KN400
begin device 0x9910
allowdevice 0
end

end
;;;