I have tried to install win4lin as an upgrade using the downloaded
installer. The net effect has been that I cannot run win4lin at all. Let

me describe the complete set of events:

1. First, before installing win4lin 3.0, I upgraded my Red Hat 7.0
 to Red Hat 7.1.

2. Then, after I checked to be sure Red Hat 7.1 was working, I
went ahead with the downloaded upgrade win4lin-install program. It
seemed to work fine - that is, I entered my registration, followed
the directions, it downloaded a new win4lin and kernel for my Red
Hat 7.1, it installed them, and, then, it asked me to reboot. I did.

3. Here it gets a bit interesting. First of all, the default boot was
linux not win4lin. As I recall from before, the default boot after
installing 2.0 was the win4lin linux. Second, when I tried choosing
win4lin at boot time, it simply froze there. When I tried linux, it
loaded properly but gave a strange error just after win4lin came up
in the boot sequence which said that hdc was reporting 250xxxxxx but
its size was actually 250yyyyyy.

4. After the boot finished I could log on and everything except
win4lin worked fine. However, when I tried to use win4lin, it said
that win4lin driver not loaded or open limit exceeded. (I expected
something like this since before I had had to run the win4lin linux
at boot time for win4lin to work.)

5. So what was the matter. Something must be wrong with either the
/boot files or with the lilo.conf. Here is the contents of /boot:

total 4704
-rw-r--r--    1 root     root          512 May 13  2000 boot.0300
-rw-r--r--    1 root     root         5824 Feb 23 13:33 boot.b
-rw-r--r--    1 root     root          612 Feb 23 13:33 chain.b
lrwxrwxrwx    1 root     root           14 Jun 21 16:34 kernel.h ->
kernel.h-2.4.2
-rw-r--r--    1 root     root          405 Jun 21 16:34 kernel.h-2.4.2
-rw-------    1 root     root        23040 Jun 21 17:05 map
-rw-r--r--    1 root     root        23108 Feb 23 13:33 message
-rw-r--r--    1 root     root        21282 Feb 23 13:33 message.ja
lrwxrwxrwx    1 root     root           19 Jun 21 16:34 module-info ->
module-info-2.4.2-2
-rw-r--r--    1 root     root        13598 Apr  8 19:57
module-info-2.4.2-2
-rw-r--r--    1 root     root          640 Feb 23 13:33 os2_d.b
lrwxrwxrwx    1 root     root           18 Jun 22 00:45 System.map ->
System.map-2.4.2-2
-rw-r--r--    1 root     root       410990 Apr  8 19:57
System.map-2.4.2-2
-rw-r--r--    1 root     root       415367 Jun  9 03:04
System.map-2.4.2-win4lin
lrwxrwxrwx    1 root     root           20 Jan 10 19:46
System.map-pre-win4lin -> System.map-2.2.16-22
-rwxr-xr-x    1 root     root      2280836 Apr  8 19:57 vmlinux-2.4.2-2
lrwxrwxrwx    1 root     root           15 Jun 21 16:34 vmlinuz ->
vmlinuz-2.4.2-2
-rw-r--r--    1 root     root       781806 Apr  8 19:57 vmlinuz-2.4.2-2
-rw-r--r--    1 root     root       783275 Jun  9 03:04 win4lin

and here is the contents of /etc/lilo.conf:

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux
message=/boot/message
linear

image=/boot/vmlinuz-2.2.16-22
 label=linux
 read-only
 root=/dev/hda2

other=/dev/hda1
 label=dos
# Added by NeTraverse for Win4Lin kernel
image = /boot/win4lin
label = win4lin
root = /dev/hda2

This confuses me since it seems to say that the image is the
(non-existant)
file vmlinuz-2.2.16-2 even though when I boot linux it works just fine
and
shows that it is version 2.4.2-2.

Help, please!

Lynn Ziegler


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

Reply via email to