Error installing iKernel.exe: (0x1400) with patch this time

Tony Lambregts tony_lambregts at telusplanet.net
Sat Feb 8 18:32:19 CST 2003


Dan Kegel wrote:

 > This is something I see frequently.  Here's my little FAQ about it:
 >
 > When running an Installshield 6 installer:
 >
 > If you get the error "Error installing iKernel.exe: (0x1400)" at any
 > point,
 > it's probably because there are leftover processes from a previous try.
 > You can verify this with the command
 > $ ps augxw | grep wine
 >
 > If that command shows old copies of wine running your setup,
 > you need to kill them before you can run the setup program.
 > If there are no other Wine programs running, you can kill them
 > all with the command
 > $ killall wine
 > If you're also running Wine programs you care about, you'll
 > have to kill off the old Setup instances one by one using
 > kill and the individual PIDs (or perhaps Wine's spiffy Task Manager,
 > which doesn't exist yet).
 >
 > Then repeat the ps to make sure the old wines are gone.
 > - Dan

Credit goes to Dan.<g>

Change log: Add entry for "Error installing iKernel.exe: (0x1400)" in
wine FAQ.

Files Changed: documentation/faq.sgml

-- 

Tony Lambregts



-------------- next part --------------
Index: faq.sgml
===================================================================
RCS file: /home/wine/wine/documentation/faq.sgml,v
retrieving revision 1.5
diff -u -u -r1.5 faq.sgml
--- faq.sgml	24 Dec 2002 00:56:33 -0000	1.5
+++ faq.sgml	9 Feb 2003 00:00:48 -0000
@@ -1366,6 +1366,39 @@
         </para>
       </answer>
       </qandaentry>
+      <qandaentry>
+      <question id="Error-with-installshield-6">
+        <para>
+          I get <quote>Error installing iKernel.exe: (0x1400)</quote>
+          when running an Installshield 6 installer
+        </para>
+      </question>
+      <answer>
+        <para>
+          If you get the error "Error installing iKernel.exe: (0x1400)" at any
+          point, it's probably because there are leftover processes from a
+          previous try. You can verify this with the command
+        </para>
+        <para><command>$ ps augxw | grep wine</command></para>
+        <para>
+          If that command shows old copies of wine running your setup,
+          you need to kill them before you can run the setup program.
+          If there are no other Wine programs running, you can kill them
+          all with the command
+        </para>
+        <para><command>$ killall wine</command></para>
+        <para>
+          If you're also running Wine programs you care about, you'll
+          have to kill off the old Setup instances one by one using
+          kill and the individual PIDs (or perhaps Wine's spiffy Task Manager,
+          which doesn't exist yet).
+        </para>
+        <para>
+          You should repeat the <command>ps</command> to make sure the old 
+          wines are gone. 
+        </para>
+       </answer>
+      </qandaentry>
     </qandadiv>
      
     <qandadiv id="Getting-help">


More information about the wine-patches mailing list