Cant install app (Winexec error 0002H)

  • Thread starter Thread starter Juergen Seyffer
  • Start date Start date
J

Juergen Seyffer

Hello,

I can't install a specific application on an XPe system.
After starting setup.exe, a box comes up with "Can't start
Setup-application! (WinExec() Error 0002H).
It seems to be a Visual Basic 4.0 application, which runs fine on XP Pro or
Windows 2000.

I already included DOS on Windows Support, Windows Installer, VB5.0 and
VB6.0 support.
VB4.0 Runtime dll's are included with the package.

If I try Dependency Walker on it, I also got an error message.
No PE signature found. This appears to be a 16-bit Windows module.

All hints are welcome

Juergen
 
Juergen:

Do you have the "Application Compatibility Core" component in your image?

HTH... Doug
 
Hello Doug,

Yes, I have included
Application Compatiblity Core Hotfix Q824704
Application Compatiblity Support Tools
Application Compatiblity User Interface

Thanks for that quick reply

Juergen
 
Hello KM,

I allready found this page while googeling for Winexec 0002H.
I cant find any sw*.ini file on my XPe build, nor on my W2K and XP Pro
Workstation, where I can install and run the application.
I assume it's more related to VB 4.0 compliler.

There is no chance running Dependency Walker on it.
I also tried Regmon and Filemon without success.

It's a very old program, which also runs on Windows 3.x, 9x and NT.

any idea ?

Regards

Juergen
 
Juergen,
I allready found this page while googeling for Winexec 0002H.
I cant find any sw*.ini file on my XPe build, nor on my W2K and XP Pro
Workstation, where I can install and run the application.
I assume it's more related to VB 4.0 compliler.

I thought the sw*.ini files belong to the VB4 runtime (IDE) - configuration files. You called that compiler" but it is not. It is an
interpreter :-)

Well.. you can also try to follow a procedure to install 16-bit VB 4.0 app without running the setup app. At least you can extract
all the files properly. http://www.kbalertz.com/kb_152559.aspx
There is no chance running Dependency Walker on it.

Have you tried Profiling with the Dependency Walker? I am not sure if it will work for you but still worth to mention.
I also tried Regmon and Filemon without success.

It is still possible to analyze the file dependencies by exploring the PE file (it is slighly different PE, though, from Win32).
And, of course, you always have a good old hex editor.

And I am not sure why Filemon did not help you.
It's a very old program, which also runs on Windows 3.x, 9x and NT.
any idea ?


If you can, you may send me the file to konstmor @ no_spam_hotmail . com email address and I will check the file here. Maybe I can
find a way of figuring out its dependencies.

KM
 
Back
Top