🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: borland.public.cppbuilder.deployment
7 messages
7 total messages Started by pk Tue, 03 Jan 2006 12:17
exe problem on winxp
#188
Author: pk
Date: Tue, 03 Jan 2006 12:17
7 lines
1308 bytes
Hello.
I have created a project and compiled it(I have included all the necessary
packages). The appn runs well on other computers (even without BCB
installed). However, when I try to run it on WinXP, nothing happens(no error
messages....). Could anyone be having an idea on what is wrong with my exe?
Regards,
PK.
Re: exe problem on winxp
#189
Author: Roddy Pratt
Date: Tue, 03 Jan 2006 18:34
16 lines
1435 bytes
"pk" <thekariuki@yahoo.co.uk> wrote in message 
news:43ba6a9f@newsgroups.borland.com...
> Hello.
> I have created a project and compiled it(I have included all the necessary
> packages). The appn runs well on other computers (even without BCB
> installed). However, when I try to run it on WinXP, nothing happens(no 
> error
> messages....). Could anyone be having an idea on what is wrong with my 
> exe?
> Regards,
> PK.

Does the XP system have DEP (Data Execution Protection) enabled? That can 
cause problems with some BCB/Delphi apps...

 - Roddy 
Re: exe problem on winxp
#190
Author: pk
Date: Wed, 04 Jan 2006 12:38
10 lines
1517 bytes
>
> Does the XP system have DEP (Data Execution Protection) enabled? That can
> cause problems with some BCB/Delphi apps...
>
I have noticed that the exe runs in the WinXP environment on the computer in
which it was made. The WinXP computer is able to run an exe compiled in it
but is unable to run an exe compiled from another computer.
If the same exe(which runs on the WinXP computer in which it was compiled)
is taken to another WinXP computer, it does not run.
Re: exe problem on winxp
#191
Author: Ed Mulroy
Date: Wed, 04 Jan 2006 16:49
14 lines
1530 bytes
It could also be that in the path used by the operating system on the second 
computer a DLL that the program needs could not be found.

.  Ed

> pk wrote in message
> news:43bbe5f3@newsgroups.borland.com...
>
> I have noticed that the exe runs in the WinXP environment on the
> computer in which it was made. The WinXP computer is able to
> run an exe compiled in it but is unable to run an exe compiled
> from another computer. If the same exe(which runs on the WinXP
> computer in which it was compiled) is taken to another WinXP
> computer, it does not run.
Re: exe problem on winxp
#192
Author: pk
Date: Thu, 05 Jan 2006 05:08
13 lines
1703 bytes
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.
Re: exe problem on winxp
#193
Author: Ed Mulroy
Date: Thu, 05 Jan 2006 12:25
54 lines
3457 bytes
> 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.
Re: exe problem on winxp
#194
Author: pk
Date: Fri, 06 Jan 2006 15:42
4 lines
1376 bytes
Thanks for the infor.
I  however notice that the problem gets solved when I use an installation
software e.g installshield to install my application in winxp.
thanks once again.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads