Hi dudes. A question about the latest vintage wine on Fedora Core 1. Installshield installers won't work. I have read all the advice on the net (replacing with native dlls and tlb files) but still no luck. The error I get is "The installshield kernel (ikernel.exe) could not be launched. (0x80010100)" . Apparently this error code relates to the inability to allocate some resource, but the documentation I found could not be more specific. Any clues? TIA John
Disable exec-shield and run wine again. Ivan.
Hello, I had same problem with a Red Hat Workstation on a very slow machine. Don't think it's a general problem, because same app installs fine on SuSE and Debian. When i slows down another machine dramatically, the problem comes on SuSE too, but the error code is not the same. I stopped determining the problem when discovering that it only occurs during first X session after booting. When i logged out and in again, it works :-) It was an installshield 6.3 app and i can provide a setup for reproducing, if wanted by the developers. Greetings from Hamburg Sven John Williams schrieb:> Hi dudes. A question about the latest vintage wine on Fedora Core 1. > > Installshield installers won't work. > > I have read all the advice on the net (replacing with native dlls and > tlb files) but still no luck. > > The error I get is "The installshield kernel (ikernel.exe) could not be > launched. (0x80010100)" . Apparently this error code relates to the > inability to allocate some resource, but the documentation I found could > not be more specific. Any clues? > > TIA > > John
Thanks to those who have replied. I have tried Ivan's suggestion of disabling exec-shield. This makes no difference. I have also tried Rick's suggestion of putting the session in a non-managed window. This also makes no difference. Sven's observations did not correspond with mine (re-starting X makes no difference). Again, thanks to the people who offered help. Any other clues? In particular, what _exactly_ does the error code 0x80010100 mean in this context? Also, is there some way of determining what version of installshield is used? I extracted the strings from the binary but there were no clues there. Thanks again, John
John Williams schrieb:> Again, thanks to the people who offered help. Any other clues? In > particular, what _exactly_ does the error code 0x80010100 mean in this > context?Google says: EOLE_RPC_E_SYS_CALL_FAILED : INTEGER -2147417856; -- 0x80010100 -- Could not allocate some required resource (memory, events, ...) Logging shows that it makes something with the rpcrt4.dll in the case that it runs. When reproducing the problem, there comes an exception in a thread. But maybe it is only an aftereffect.> Also, is there some way of determining what version of installshield is > used? I extracted the strings from the binary but there were no clues > there.Just right click on the setup.exe in windows and get the version information (i.g. 6, 31, 100, 1190 means an installshield 6.3 version). Greetings Sven
> I have tried Ivan's suggestion of disabling exec-shield. This makes no > difference.The problem is that to avoid buffer overflow attacks, RH/Fedora loads libraries in the low part of the memory, but most windows programs require to be loaded in the high part of the memory (Linux sees windows programs in wine as libraries). There is a fix in the current CVS version of Wine, you may want to try and upgrade. It is reported to work, but you must have both prelink and exec-shield ON. Ivan.
> 1. Should I have done that?I have no idea if it will work or not. The best thing you can do is install the latest CVS version, that has been reported to work, following the instructions at http://www.winehq.com/site/cvs If you have wine-20040505.tar.gz, decompress it, don't' apply any patches, then, from the top source directory, just run cvs update -PAd note that you must have CVS installed. Then rebuild wine, and the program should work. Ivan.