FO1: DirectX error with sfall on Vista

[404notfound]

Although sfall works nicely for me on my XP computer, Fallout won't even start on my Vista laptop. I have 32-bit Vista Home Premium, and trying to start Fallout using the sfall ddraw.dll throws an error at me: "Could not load DirectX - This program requires Windows 95 with DirectX 3.0a or later or Windows NT version 4.0 with Service Pack 3 or greater."

I've tried messing around with the compatability, but it doesn't seem to help. The game works fine if I get rid of the sfall version of ddraw.dll, but then I lose all the benefits of sfall.

Oddly, Fallout 2 doesn't suffer from this problem.

Edit: More details is always better, I suppose.

I'm using the version of Fallout from GoodOldGames, which is v1.2 with no children. In addition to sfall, I applied the children patch, TeamX's v1.3.3 patch, the dialog fix patch, and the high-res patch. However, as far as I can tell, none of these have anything to do with the issue I'm having, as I also tried reinstalling and using sfall on a fresh v1.2 install, which still gave the same error.

 

[Brother None]

It's not the first time I've heard of there being problems with running Timeslip's stuff on Good Old Games. Maybe he can take a look at it later, but so far the only answer I can offer is: sfall simply does not work with the GOG version of Fallout 1/2

 

[404notfound]

It's not the first time I've heard of there being problems with running Timeslip's stuff on Good Old Games. Maybe he can take a look at it later, but so far the only answer I can offer is: sfall simply does not work with the GOG version of Fallout 1/2

It does work with GOG, though. On my XP computer, both Fallout 1 and Fallout 2 work just fine with sfall, and Fallout 2 works on my Vista laptop. It's just Fallout 1 on Vista that doesn't want to cooperate with Timeslip's ddraw.dll.

As far as I can tell, the GOG versions are just 1.2 with no children and 1.02d with children, respectively. It doesn't look like they've modified it any further than applying the latest official patches.

 

[404notfound]

I didn't know there would be relevant info in there, but I skimmed the last couple of pages of the sfall thread for Fallout 2, and my exact problem is mentioned, along with a fix. I don't know why renaming the executable works, but it does. Oh, well.