So InstallShield manages to extract all of its files now, but then falls over trying to read a file named inst16.ex. Which is interesting because it doesn't extract such a file. It does, however, extract a file named inst32i.ex.
One theory is that the frontend decides this is a 32-bit system and extracts a 32-bit installer, but when it comes time to launch, they use different logic and conclude that this is a 16-bit system after all.
I did notice an attempt to dynamically load W32SYS.DLL, which is part of Win32s, so I went ahead and implemented the GETWIN32SINFO function they want to call in there. But after that, they still try to access inst16.ex.
Wonder if there are any detailed breakdowns of InstallShield's files and behaviors lurking on the interwebs....
Add comment