Some less intrusive suggestions:

- Use ScummVM
- Try ddhack https://solhsa.com/ddhack/ / https://github.com/jarikomppa/dxwrapper

thp wrote on 2024-11-24, 19:01:

Some less intrusive suggestions:

- Use ScummVM
- Try ddhack https://solhsa.com/ddhack/ / https://github.com/jarikomppa/dxwrapper

I'd rather avoid ScummVM. I'm interested in getting things working natively, if possible. 😀 But thanks for pointing me to the DirectDraw Hack. I'll give that a try and see.

Doubt it is very easy to downgrade direct x. probably easier just reinstall windows on a second hdd and just go with the version the game came with.

For science you can then upgrade it incrementally until you get the error. sounds like a wonderful weekend activity. you can even live stream it. i will pop some popcorn.

Joakim wrote on 2024-11-24, 20:49:

Doubt it is very easy to downgrade direct x. probably easier just reinstall windows on a second hdd and just go with the version the game came with.

For science you can then upgrade it incrementally until you get the error. sounds like a wonderful weekend activity. you can even live stream it. i will pop some popcorn.

Lol. Not much of a weekend left now. But there are no errors to speak of; just horrible flickering.

Hi, you can try to place a copy of Windows XP's ddraw.dll in the game/application directory.
This should trigger software rendering for this game/application.

I've used this little trick many years ago for running Virtual PC 2007 on Windows 7.
Back then, the DDraw output was incredibly slow when using Virtual PC 2007.
Using software rendering solved the issue for me.

Jo22 wrote on 2024-11-24, 21:43:

Hi, you can try to place a copy of Windows XP's ddraw.dll in the game/application directory. This should trigger software render […]
Show full quote

Hi, you can try to place a copy of Windows XP's ddraw.dll in the game/application directory.
This should trigger software rendering for this game/application.

I've used this little trick many years ago for running Virtual PC 2007 on Windows 7.
Back then, the DDraw output was incredibly slow when using Virtual PC 2007.
Using software rendering solved the issue for me.

Ooh. Interesting. I don't think I've ever tried that method before. I don't believe it's on the XP disc itself, right? I'd have to install it on a virtual machine otherwise.

thp wrote on 2024-11-24, 19:01:

Some less intrusive suggestions:

- Use ScummVM
- Try ddhack https://solhsa.com/ddhack/ / https://github.com/jarikomppa/dxwrapper

I can’t seem to get either of these to work. 😕 The first I tried adding the cfg file where the game’s executable is, and I even added to command to show the logo to see if it works, but there’s no change in the game. In fact, trying it today, the flickering problem is even worse.
The Dxwrapper I can’t figure out how to get working at all. I can’t find any clear readme on how to set it up with a game.

EDIT: In fact, putting all the files in the game directory (I missed the cfg file and .dll file last time), gives me this error when I try to load:

“A device attached to the system is not functioning”

And…

“The file expects a newer version of Windows. Upgrade your windows version.” I would have uploaded a photo, but they’re being stupid.

Jo22 wrote on 2024-11-24, 21:43:

Hi, you can try to place a copy of Windows XP's ddraw.dll in the game/application directory. This should trigger software render […]
Show full quote

Hi, you can try to place a copy of Windows XP's ddraw.dll in the game/application directory.
This should trigger software rendering for this game/application.

I've used this little trick many years ago for running Virtual PC 2007 on Windows 7.
Back then, the DDraw output was incredibly slow when using Virtual PC 2007.
Using software rendering solved the issue for me.

I managed to find one for XP on a site somewhere, but I can’t get it to work. It won’t let me overwrite the existing one in System32, and putting it with the executable doesn’t appear to do anything. In fact, the problem is worse. Even removing the file hasn’t helped. 😕

DustyShinigami wrote on 2024-11-25, 17:16:

Jo22 wrote on 2024-11-24, 21:43:

Hi, you can try to place a copy of Windows XP's ddraw.dll in the game/application directory. This should trigger software render […]
Show full quote

Hi, you can try to place a copy of Windows XP's ddraw.dll in the game/application directory.
This should trigger software rendering for this game/application.

I've used this little trick many years ago for running Virtual PC 2007 on Windows 7.
Back then, the DDraw output was incredibly slow when using Virtual PC 2007.
Using software rendering solved the issue for me.

I managed to find one for XP on a site somewhere, but I can’t get it to work. It won’t let me overwrite the existing one in System32, and putting it with the executable doesn’t appear to do anything. In fact, the problem is worse. Even removing the file hasn’t helped. 😕

Sorry to hear. 🙁
It wasn't a joke, though, it really worked for me.
I posted this in 2016: Re: Final Reality on Windows 10?

Jo22 wrote on 2024-11-25, 19:01:

Sorry to hear. :( It wasn't a joke, though, it really worked for me. I posted this in 2016: Re: Final Reality on Windows 10? […]
Show full quote

DustyShinigami wrote on 2024-11-25, 17:16:

Jo22 wrote on 2024-11-24, 21:43:

Hi, you can try to place a copy of Windows XP's ddraw.dll in the game/application directory. This should trigger software render […]
Show full quote

Hi, you can try to place a copy of Windows XP's ddraw.dll in the game/application directory.
This should trigger software rendering for this game/application.

I've used this little trick many years ago for running Virtual PC 2007 on Windows 7.
Back then, the DDraw output was incredibly slow when using Virtual PC 2007.
Using software rendering solved the issue for me.

I managed to find one for XP on a site somewhere, but I can’t get it to work. It won’t let me overwrite the existing one in System32, and putting it with the executable doesn’t appear to do anything. In fact, the problem is worse. Even removing the file hasn’t helped. 😕

Sorry to hear. 🙁
It wasn't a joke, though, it really worked for me.
I posted this in 2016: Re: Final Reality on Windows 10?

Not to worry. I have managed to solve the problem finally. 😁 I noticed in that thread you linked that there's also a file called d3drm.dll? Does that also need to go with the ddraw.dll file?

But anyway, I've managed to uninstall DirectX using this tool - https://www.majorgeeks.com/files/details/dire … eradicator.html

It completely uninstalls whatever version the PC has and then puts another tool on the desktop after restart, which re-installs DirectX 6.1a. The same version that was on after installing Windows 98 SE. Sadly, the flickering wasn't cured in Broken Sword, but it was cured in the DirectDraw test. I did discover though, that if I disable DirectDraw or Direct3D in the DirectX Diagnostics Tool, it cures the problem! No more flickering. 😁 It also fixes a weird graphical glitch at the beginning of Simon the Sorcerer as well. 😀