InstallShield hanging

[d00nicus]

Attempting to install multiple programs that use the old InstallShield (that requires a 16 bit stub) results in the messages below, and a frozen progress bar

version: 1070 5ca8:fixme:module:LoadModule_wine_implementation 1299: Strange error set by CreateProcess: 740 04fc:err:file:RedirectDriveRoot 166: c:\stopthis.now => C:\otvdm\c\stopthis.now

After the CreateProcess error, a UAC elevation prompt appears, and once acknowledged, the second error will appear (sometimes multiple times depending on the version of InstallShield.

(X-Wing vs TIE Fighter, or A-10 Cuba! are two of the programs I've seen this with so far, but I'd expect any InstallShield installer of the same age to behave the same as it was pretty standardised)

[skipnyip]

This issue appears to still be present in V0.7.0

version: 1056
6414:fixme:module:LoadModule_wine_implementation 1299: Strange error set by CreateProcess: 740
11d8:err:file:RedirectDriveRoot 166: c:\stopthis.now => C:\OTVDM-~1\c\stopthis.now
11d8:err:file:RedirectDriveRoot 166: c:\stopthis.now => C:\OTVDM-~1\c\stopthis.now

[cracyc]

Get the newest build from https://ci.appveyor.com/api/buildjobs/n4nw6xv4ct136wxv/artifacts/otvdm-master-1552.zip

[skipnyip]

cracyc,

Thanks for the updated version. I gave it a shot, but it appears the issue is still present. Thanks.

version: 1552
019c:err:file:RedirectDriveRoot 166: C:\AUTOEXEC.BAT => C:\OTVDM-~2\C\AUTOEXEC.BAT
534c:fixme:module:LoadModule_wine_implementation 1317: Strange error set by CreateProcess: 740
6a0c:err:file:RedirectDriveRoot 166: c:\stopthis.now => C:\OTVDM-~2\c\stopthis.now
6a0c:err:file:RedirectDriveRoot 166: c:\stopthis.now => C:\OTVDM-~2\c\stopthis.now

[cracyc]

I tried A10 cuba and the zork nemesis demo that comes with it and neither showed any problem. I'd need more info, which software causes the problem for you, your windows version, etc and a trace to attempt to solve it.

[skipnyip]

https://drive.google.com/open?id=1iugUzHHUr9ojL2887gCIgfjmUXMXMp4Y is the program I'm trying to run. This is on a Windows 10 Pro laptop, as well as a Windows 10 Home 1903.

\08.02\rslogix5000_v8_02_2001_06_14\ENGLISH\RSLogx5k\setup.exe
and
\08.02\cflash_rs5k_v8_megabundle_2001_06_14\setup.exe
have similar issues.

I will admit that I don't actually know how to provide you with a trace.

Thanks

Edit:

So, on my home computer, it ended up launching, but it took quite while, and it actually launched after I had closed out of otvdm.exe. I'm looking at it closer, and this time the progress bar in the Setup is actually making progress, but seems to chunk every time a new stopthis.now message is displayed. Let me try this again on my pro computer, but it will be after Wednesday.

Thanks again.

[cracyc]

Strange. For me it goes quickly and only shows the message once. The cflash installer prints a error after the 32bit part run another 16bit program unelevated so it doesn't work properly but the program does install, don't know if it works. The rslogix installer prints a lot of dll errors but it's a 32bit dll so there's nothing that winevdm can do about it. To do a trace "set WINEDEBUG=+relay" then run otvdm.exe from the command line. It's very verbose so you'll want to redirect stderr with "2> out.txt".

[OldClassicGamer]

I have exact same problem.

[cracyc]

Again, need a trace.

[OldClassicGamer]

How to provide a trace?
The above description "set WINEDEBUG=+relay" then run otvdm.exe from the command line does not help me as I still don't understand how to do it. Any chance you can post some tutorial with screenshots?

[agreatwizard]

I am getting the same error trying to install Autocad 14.

[Piotr333]

I had the same.
The solution is.
Run cmd.exe as administrator. cmd.exe is located in C: \Windows\System32
Write if it solved the problem.

[slapshot2213]

I am getting the same error trying to install SimTower.

[cracyc]

Again, i can't reproduce this. It can't get fixed without a detailed trace.

[OldClassicGamer]

Again, I can't reproduce this. It can't get fixed without a detailed trace.

And you still did not tell me how can I provide a detailed trace?
I asked this back on September 30 2020 and you ignored me.
How am I supposed to provide a detailed trace when I don't know how to do it?
This is clearly a widespread problem that is happening to multiple people and you don't tell us how to provide detailed trace.
Sorry if I sound rude but I think it's rather unprofessional to ignore instead of guiding others on how to provide this detailed trace that you need in order to tell us how to fix it...

[cracyc]

It's described in the issue template which are the steps to take before reporting a bug. https://github.com/otya128/winevdm/blob/master/.github/ISSUE_TEMPLATE/bug_report.md