Anyone know how to get the games in winxp (ie internet heart, etc) to work in win 2003?

Just by coping the whole directory over does not work.

Copy the exe over. If it complains thatits missing a dll, then copy over the dll into the same directory as hearts. Repeat this procedure until it works. Do not put the dll's into \winnt\system32

he also asked:


"would be nice if someone knows the exact files
for at least internet heart, internet checkers and internet spade cause these are the only three i will ever touch, heh"

thank you for your help

quoted from http://www.etplanet.com/cgi-bin/board_other/ultimatebb.php?ubb=get_topic;f=2;t=000071;p=1#000005

he also posted

"there is no complain about missing dll or i would of done it already

"Hearts is unable to start. Close some other programs and try again, or try reinstalling Hearts using Add/Remove Programs in the Control Panel." is the error msg

i have posted this to other forums as well, but no working suggestion at the moment"

second post of his :


Copy only exe, gives a error msg that it needs UniAnsi.dll
Copy uniansi.dll there and it gives "Hearts is unable to start. Close some other programs and try again, or try reinstalling Hearts using Add/Remove Programs in the Control Panel." is the error msg

Tried running this in other compatible mode and still does not work.

"he also posted

"there is no complain about missing dll or i would of done it already

"Hearts is unable to start. Close some other programs and try again, or try reinstalling Hearts using Add/Remove Programs in the Control Panel." is the error msg

i have posted this to other forums as well, but no working suggestion at the moment"

second post of his :


Copy only exe, gives a error msg that it needs UniAnsi.dll
Copy uniansi.dll there and it gives "Hearts is unable to start. Close some other programs and try again, or try reinstalling Hearts using Add/Remove Programs in the Control Panel." is the error msg

Tried running this in other compatible mode and still does not work."

Sounds like whoever built it, either:

1.) Hardcoded the library declaration in their code

2.) Hardcoded a LoadLibrary call in their code instancing it that way & demanding that file be in some certain folder/directory or subfolder/subdirectory

3.) The UniAnsi.dll file just plain-jane does API calls that will not work on 2003 (you have not hit that yet, does not sound it, because your game does not seem to start up yet finding the function calls it needs from that file in the first place, period... hence, my next set of suggestions!).

* Putting it into the %WinDir%\system32 folder might be ok, at least temporarily (see if there is already a file there named that, & be sure to turn on the options in Explorer.exe to show system files too)... if you find a version of that file there already? RENAME IT to UniAnsi.old & copy yours in or back that one up/copy it elsewhere temporarily for now.

Then, you can test!

I can see why you were told NOT to do that, but thank goodness for System File Protection & Windows File Protection: You can copy that file over & the system can replace it if you want to when it kicks up, but before you commit a change to change it back to its OS shipped version (assuming there is one), try your game first.

(System File Protection/Windows File Protection can save you from overwritten .DLL files & such even in installers don't catch this happening in their code!)



WFP/SFP = Good Stuff!

APK

P.S.=> Most .dll files are shipped nowadays & also in the past to install as PUBLICLY accessible .dll files, meaning on the system pathway & %WinDir%\system32 is as close to the meaning of that as it gets, guaranteed to be on the %PATH% variable (unless someone trimmed that out on your system)... installation programs nowadays do version checking to stop overwrites, & the OS itself has protection mechanisms... but, they're of NO USE if a programmer hardcodes a path to his .dll files he/she/they call.

Of course, some folks do this on purpose to avoid .dll mismatch/dll hell... they put the .dll into the same folder/directory as their program, avoiding overwriting Windows own versions of the files of the same name (but, diff. build version)... they tell the program to extract/find it's OWN location path on the disk & load the libs/dlls from there! AVG AntiVirus is one that I believe does it that way, & also, that extracting/finding its own path is just a failsafe really... programs look inside their own folder FIRST before anyplace when calling .dlls... if they are not hardcoded in their declarations, or are not instanced via LoadLibrary calls in hardcoded paths! apk