Larry,
   OK, here's the state of things:

1) I never rebooted. The failure happened immediately after hitting Y on the
keyboard. I think that the install never happened and it never did anything.

2) The machine is remote on the network with no monitor. I can't choose a
specific kernel at boot time, short of editing lilo.conf and rerunning lilo
if I want to, which is what I do. I can drag is out of the garage, if
necessary. I am doing the installation via an xterm which worked on 2.2.14.

3) The file /usr/bin/install-win4lin.sh exists. I suspect it's left over
from my 2.2.14 installation, but I don't know for sure. It is dated Jan. 1,
which is about the time I got around to upgrading to Win4Lin-Rev-2.0 under
2.2.14. (The licenses came out on 12/15. I didn't mess with it right away.)

4) /etc/lilo.conf still has a Win4Lin option in it. I suspect that it was
not removed by NeTraverse's removal scripts, but I do not know this for
sure. Default boot is still 2.2.16 following my kernel build last night.

5) There's nothing in the /opt directory....

6) There is a file called win4lin in /boot dated Mar. 29, 2000. I suspect
that this was from my 2.2.14 installation, but I do not know for sure. I'm
not clear whether this is the kernel that used to boot, and wasn't removed,
or was this some other file.

Here's the /boot directory contents:

[root@godzilla /boot]# dir
total 6100
drwxr-xr-x   2 root     root         4096 Jan 20 05:34 .
drwxr-xr-x  24 root     root         4096 Jan  1 22:29 ..
lrwxrwxrwx   1 root     root           17 Jan 20 05:34 System.map ->
System.map-2.2.16
-rw-r--r--   1 root     root       203645 Mar  8  2000 System.map-2.2.14-5.0
-rw-r--r--   1 root     root       197489 Mar 29  2000
System.map-2.2.14-win4lin
-rw-rw-r--   1 root     root       187600 Jun 13  2000 System.map-2.2.15
-rw-r--r--   1 root     root       179959 Jan 20 04:06 System.map-2.2.16
lrwxrwxrwx   1 root     root           21 Jan  1 21:35
System.map-pre-win4lin -> System.map-2.2.14-5.0
-rw-r--r--   1 root     root       179035 Jan 20 03:27 System.map.old
-rw-r--r--   1 root     root          512 May  7  2000 boot.0300
-rw-r--r--   1 root     root         4568 Feb  2  2000 boot.b
-rw-r--r--   1 root     root          612 Feb  2  2000 chain.b
-rw-r--r--   1 root     root          237 May  7  2000 kernel.h
-rw-------   1 root     root        31232 Jan 20 05:33 map
lrwxrwxrwx   1 root     root           22 May  7  2000 module-info ->
module-info-2.2.14-5.0
-rw-r--r--   1 root     root        11773 Mar  8  2000
module-info-2.2.14-5.0
-rw-r--r--   1 root     root          620 Feb  2  2000 os2_d.b
-rwxr-xr-x   1 root     root      1615706 Mar  8  2000 vmlinux-2.2.14-5.0
lrwxrwxrwx   1 root     root           14 Jan 20 04:06 vmlinuz ->
vmlinuz-2.2.16
-rw-r--r--   1 root     root       622249 Mar  8  2000 vmlinuz-2.2.14-5.0
-rw-rw-r--   1 root     root       577169 Jun 13  2000 vmlinuz-2.2.15
-rw-r--r--   1 root     root       566387 Jan 20 04:06 vmlinuz-2.2.16
-rw-rw-r--   1 root     root       604899 Oct 19 00:45 vmlinuz-2.2.17
-rw-r--r--   1 root     root       556901 Jan 20 03:27 vmlinuz.old
-rw-r--r--   1 root     root       611593 Mar 29  2000 win4lin


ANY THOUGHTS??????

Thanks,
Mark








-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Larry
Marshall
Sent: Saturday, January 20, 2001 1:56 PM
To: [EMAIL PROTECTED]
Subject: Re: [Win4Lin-users] Problems getting Win4Lin installed


>From you description, I don't think you're doing anything wrong Mark.

> After installing the kernel, the system will reboot.

Did this happen?

> Login as root and run "sh /usr/bin/install-win4lin.sh"

Look in this script and make sure that there's a line in it that
describes your kernel.  Also, while you're at it, check /boot and see
if there is the standard kernel you put there and a second one which
will match the lilo nomenclature for the win4lin boot item.

Hmm...this just jogged my brain a bit.  When you rebooted, did you
explicitly tell lilo you wanted win4lin?  The auto script adds the
stuff to lilo but it doesn't set it up as the default so if you simply
let lilo do its default thing you're still running the unpatched
2.2.16 kernel.  Before you do anything, do a reboot and when the lilo
prompt comes up, hit a tab.  You should see both your default linux
boot and a new win4lin.  type win4lin and then see if you can get any
joy from that script.

Hope this helps.

Cheers --- Larry
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users


_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users

Reply via email to