Nice post. BTW, Ed, if you don't change that picture I'm going to be physically unable to respond to any of your posts because I'll be rolling on the floor... :-D

>I have found the solution and I guess that I should respond to my own post for anybody who searches the archives in the future.
>
>I need to thank Waleed Hasan who actually gave me fix in the first place, which I had mis-read untile now, and told me about the Windows\AppLog directory and the .lgc log files that can be used for tracking the execution of programs.
>
>I had studied the windows\applog\hexedit.lgc file and could see where the execution was stopping but this didn't give me any clue as to what was needed for the program to proceed.
>
>I finally found the solution by installing VFP 6.0 on the Hebrew Win 98 machine and then running the HexEdit.exe again. Hexedit ran this time so obviously the VFP installation added a file that was missing from the original Hebrew Win 98 install and not included as part of the VFP setup wizard distribution files. I went back to the hexedit.lgc file and saw that the next file to run after the point were it was stopping before was VBAME.DLL in the Windows\System directory.
>
>That did the trick and so I will distribute this with my app in the future. I assume that "AME" stands for American English. When I had read Waleed's solution to his problem, since he was from Egypt, I had assumed that the "ME" stood for "Middle East" or something and so I looked for a similar file like maybe VBENG.DLL for English. I really feel stupid now. I guess that I just speed of chaseing other theories instead of actually thinking.
>
>Anyway that's the solution and, Waleed, thanks again.
>
>Ed
>
>
>
>
>>VFP 6.0 executables will not run on Foreign Language Windows 98. They will not even get to the first line of code but will crash with an empty "Microsoft Visual FoxPro" dialog box with an "OK" and "Help" button at the bottom. This dialog box never gets the focus and after beeping four times the box goes away and that is it.
>>
>>A client sent me a Hebrew Windows 98 CD to use in order to test this problem that he was having with my application. To make sure that it was not something that is unique to my app, on my American English Win 98 machine I went to VFP98\Tools\Hexedit and compiled the hexedit.pjx project without touching anything before hand.
>>
>>Booting from floppy, I installed Hebrew Enabled Win 98 on a freshly formatted hard drive doing a "Typical" installation. I selected all defaults when given a choice and did not touch anything after installation.
>>
>>Immediately after installation and bootup I copied Hexedit.exe over to Drive C: and ran it. I got the same error.
>>
>>I have checked the version numbers of all "Setup" files and files that run during setup and everything is the same on Hebrew Win 98 as they are in English Win98 (msvcrt.dll, mscvrt40.dll, vfp6r.dll, vfp6renu.dll, oleauth32.dll, ole32.dll, shell32.dll, condlg32.dll, ver.dll, mmsystem.dll, etc.)
>>
>>I have had several other reports from users that have experienced the same thing and I do not think that this is restricted to just the Hebrew version of Windows 98.
>>
>>I have the VFP Service Pack 2 installed.
>>
>>Can anybody duplicate this problem on other Foreign Language versions of Win 98 (compiling hexedit.pjx with English Win 98/English VFP 6.0 and then running the executable on a Foreign Language version?
>>
>>Is there something that I don't know that I should about cross-language executables?
>>
>>Any help of suggestions on where to look would be most welcome. I've spent a lot of time doing searches on UT and MSDN but so far nothing.
>>
>>TIA
>>
>>Ed

------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05