> 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.
Ok...then what's happened (I'm pretty sure), is that script has
compared /proc/version to its list of possible kernels and come up
without a match. I suspect the reason for that may be the sub-version
of 2.2.16 you're running. The script is a bit limited in this
regard. What I'd try is editing that script so that it does match and
download the 2.2.16 win4lin kernel and install it for you.
If that doesn't work, you can always go to the site and download it
yourself. Since you've already dealt with lilo.conf and such you know
how to set things up.
> 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
Ok...then you have to set the win4lin kernel as the default. I
suspect you must have done this with your previous setup and the real
problem is that you don't have a win4lin kernel. What' hard to follow
is why you didn't have a real problem with booting if your lilo.conf
was trying to boot a win4lin kernel that wasn't there.
> 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.
If that the win4lin option is the default, what kernel is it using if
the download script failed to download one?
> 5) There's nothing in the /opt directory....
I think that's because the install script says you don't have a
win4lin kernel.
> 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.
This would be my guess as well and answers my question above. I
didn't realize that you hadn't eliminated your old installation before
proceeding.
> ANY THOUGHTS??????
Hard to know from afar but my guess is that your best bet is to
download the win4lin kernel and replace the one that's in your /boot
with it. Then, make sure that lilo.conf defaults to that kernel when
it boots. My only experience with 'you ain't running a valid kernel'
msgs have been due to:
1) didn't have a valid kernel
2) didn't boot using the valid kernel
Wish I could provide more help.
Cheers --- Larry
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
