Installation of EXE (VB) => slow, error; change name => quick

[Johannes]

Hi,

I got a strange prblem when using InnoSetup to deploy an
EXE made with VB6 on WinXP:

If I run the setup the ABC.EXE is installed without
problems. But when I start the ABC.EXE it is extremely
slow and produces an error when it is closed (in
ntdll.dll).
If I change the name of ABC.EXE after installation to
A.EXE, it is quick again and runs without problems.

Does anyone have an idea? It looks like XP treats the
ABC.EXE differently because it "knows" its name.
Any ideas?

Thanks a lot,
Johannes

[Chris Dunaway]

On Mon, 24 Nov 2003 10:43:07 -0800, Johannes wrote:

EXE made with VB6 on WinXP:

I don't have a clue, and as this newsgroup is for VB.Net, it is probably
not the best place to ask. Try Microsoft.Public.Vb.General.Discussion

--
Chris

To send me an E-mail, remove the underscores and lunchmeat from my E-Mail
address.

[Herfried K. Wagner [MVP]]

* "Johannes" <an*******@discussions.microsoft.com> scripsit:

I got a strange prblem when using InnoSetup to deploy an
EXE made with VB6 on WinXP:

If I run the setup the ABC.EXE is installed without
problems. But when I start the ABC.EXE it is extremely
slow and produces an error when it is closed (in
ntdll.dll).
If I change the name of ABC.EXE after installation to
A.EXE, it is quick again and runs without problems.

Does anyone have an idea? It looks like XP treats the
ABC.EXE differently because it "knows" its name.
Any ideas?

What's if you don't install the EXE using InnoSetup?

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[One Handed Man]

Unfortunately this the VB.NET newsgroup not the VB6 newsgroups, please
repost to other group.

BTW, that is weird, good luck..

Regards OHM
Johannes wrote:

Hi,

I got a strange prblem when using InnoSetup to deploy an
EXE made with VB6 on WinXP:

If I run the setup the ABC.EXE is installed without
problems. But when I start the ABC.EXE it is extremely
slow and produces an error when it is closed (in
ntdll.dll).
If I change the name of ABC.EXE after installation to
A.EXE, it is quick again and runs without problems.

Does anyone have an idea? It looks like XP treats the
ABC.EXE differently because it "knows" its name.
Any ideas?

Thanks a lot,
Johannes