On each one, when run (in Admin mode) I get an error 'You must start the game with PrinceOfPersia.EXE", then another error from the actual game itself (eg title is 'Prince of Persia : Sands of Time' saying 'An copy of the launcher is already running!', and then it goes fullscreen, shows the DXWnd logo, then runs the game fullscreen. I have checked compatibility mode on each. I'm running DXWnd 2.06.11, though I tried 2.06.06 too.
Oh, on Two Thrones the first time I ran it I got a warning about what I think was SafeDisk1, though I didn't make a note of it, and I haven't seen it since; the others might have had the same warning but ran them directly the first time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First thing to say, I do not provide support for Steam releases (unless someone buys a copy of the game as a gift for me) because I can't buy all sort of games for free: I'd bankrupt in no time!
This said, something must have happened since the original CD release. Assuming that Steam release is like the GOG release, I see that there is a mandatory launcher PrinceOfPersia.exe to run the real game engine POP.exe. This can be easily managed by DxWnd using the hook inheritance. The attached profile works for me with the GOG release and could work also with Steam, just try it.
To use it, you must locate the PrinceOfPersia.exe file in the Steam folders, hook it and set the window size and mode as you prefer (by default, my profiles are always set to a small 800 x 600 window).
If this works, it may (or may not) fix the other two games of the series. Just let me know ...
Hi, thank you so much for giving it a go (and I understand completely about Steam games).
Interestingly, it worked perfectly... it ran in the 800x600 borderless window, and all was well.
And then I quit it, and ran it again at 1200x900, and it fullscreened.
Then I set it back to 800x 600, and it fullscreened.
Then I deleted the profile, reloaded it, and it fullscreened.
Then I shut down DxWnd (without saving the task), reloaded, put in the profile again, and it looked like it was working (given the location of the splash window), and then it fullscreened - and then it hung, and I had to force it to shut down. And when I ran it again through the profile, it fullscreened and worked.
So... how weird is that? If you are interested in exploring this, then is there any information I can give, or things I can try and report back?
But if - as stated - that's that, then I understand completely. I wish I had the moolah handy to gift it to you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One bad habit of DxWnd (until I find and fix it) is that sometimes the first game run can leave some bad status somewhere and the second runs may have odd behaviors. I apologize, but usually you can bypass the problem by terminating DxWnd (with the "File > eXit" menu command or clicking on the cross button on the window titlebar) and starting it again before a second run of the game.
Another possible reason could be Windows itself that may apply compatibility layers (this happens more likely if Windows detects a failure or a game crash). You may try setting the "Main > No SHIMs" flag.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I've checked PCGamingWiki, which matches Ghotik's previous comments on how to make the steam version of these work, but it still isn't.
https://www.pcgamingwiki.com/wiki/Prince_of_Persia:_The_Sands_of_Time#Windowed
https://www.pcgamingwiki.com/wiki/Prince_of_Persia:_Warrior_Within#Windowed
https://www.pcgamingwiki.com/wiki/Prince_of_Persia:_The_Two_Thrones#Windowed
On each one, when run (in Admin mode) I get an error 'You must start the game with PrinceOfPersia.EXE", then another error from the actual game itself (eg title is 'Prince of Persia : Sands of Time' saying 'An copy of the launcher is already running!', and then it goes fullscreen, shows the DXWnd logo, then runs the game fullscreen. I have checked compatibility mode on each. I'm running DXWnd 2.06.11, though I tried 2.06.06 too.
Oh, on Two Thrones the first time I ran it I got a warning about what I think was SafeDisk1, though I didn't make a note of it, and I haven't seen it since; the others might have had the same warning but ran them directly the first time.
First thing to say, I do not provide support for Steam releases (unless someone buys a copy of the game as a gift for me) because I can't buy all sort of games for free: I'd bankrupt in no time!
This said, something must have happened since the original CD release. Assuming that Steam release is like the GOG release, I see that there is a mandatory launcher PrinceOfPersia.exe to run the real game engine POP.exe. This can be easily managed by DxWnd using the hook inheritance. The attached profile works for me with the GOG release and could work also with Steam, just try it.
To use it, you must locate the PrinceOfPersia.exe file in the Steam folders, hook it and set the window size and mode as you prefer (by default, my profiles are always set to a small 800 x 600 window).
If this works, it may (or may not) fix the other two games of the series. Just let me know ...
Hi, thank you so much for giving it a go (and I understand completely about Steam games).
Interestingly, it worked perfectly... it ran in the 800x600 borderless window, and all was well.
And then I quit it, and ran it again at 1200x900, and it fullscreened.
Then I set it back to 800x 600, and it fullscreened.
Then I deleted the profile, reloaded it, and it fullscreened.
Then I shut down DxWnd (without saving the task), reloaded, put in the profile again, and it looked like it was working (given the location of the splash window), and then it fullscreened - and then it hung, and I had to force it to shut down. And when I ran it again through the profile, it fullscreened and worked.
So... how weird is that? If you are interested in exploring this, then is there any information I can give, or things I can try and report back?
But if - as stated - that's that, then I understand completely. I wish I had the moolah handy to gift it to you.
One bad habit of DxWnd (until I find and fix it) is that sometimes the first game run can leave some bad status somewhere and the second runs may have odd behaviors. I apologize, but usually you can bypass the problem by terminating DxWnd (with the "File > eXit" menu command or clicking on the cross button on the window titlebar) and starting it again before a second run of the game.
Another possible reason could be Windows itself that may apply compatibility layers (this happens more likely if Windows detects a failure or a game crash). You may try setting the "Main > No SHIMs" flag.
p.s. I tested now the same profile on "Prince of Persia - Warrior Within" and it seem to work.