🚀 go-pugleaf

> Am wondering whether the problem lies with WinXP.

I agree.  It is likely that the problem is related to Windows XP.

The symptoms do suggest a problem with a DLL.  The algorithm Windows XP uses 
to find a DLL needed by a program is different than that used by previous 
versions of Windows.

You can determine the DLLs the program needs with a command like this:

  tdump -em. ProgName.exe
  (don't overlook the period at the end of the "-em.")

For all items in the list that are not provided by Windows it is prudent to 
repeat the above for them to see what DLLs they need.

Afterwards check that the items listed are available in the system path. 
For any that are not in that path, you can try putting a copy of the item in 
the same directory as the executable.

If my guess is the source of the problem then the symptom of no error 
message given suggests that the problem may not derive from an item directly 
needed by the program but rather by an item needed  by a DLL the program 
loads.  For example, if the program needs abc.dll and abc.dll needs 123.dll 
then the inability to find 123.dll is less likely to generate an error 
dialog when the load for it fails.

Also if a dll is explicitly loaded with LoadLibrary or LoadLibraryEx then 
any complaint to the user for the dll not being found must be generated by 
the code loading it and not by the operating system.  A common error in code 
is to not generate a user error when that happens.  Note that the 'tdump' 
command I show above would not show the need for explicitly loaded DLLs.

.  Ed

> pk wrote in message
> news:43bca93a@newsgroups.borland.com...
>
>I dont think the problem is with a dll. Look at the following two 
>scenarios:
> Scenario 1:
> Project1.exe (BCB6)was compiled in a Win2k enviroment. It runs well in the
> win2k environ. It also runs well when taken to a Windows Me environment 
> but
> refuses to run in a WinXP environment.
>
> Scenario 2:
> Project2.exe (BCB5)was compiled in a WinXP environment. It runs well in 
> the
> WinXP environment(where it was compiled). It also runs well in a different
> computer running on Windows Me but refuses to run in another computer
> running on WinXP.
>
> Am wondering whether the problem lies with WinXP.