Re: !!! URGENT !!! Can't boot back to Win95
On Tue, 26 May 1998 [EMAIL PROTECTED] wrote: > Use the kernerl-source-2.0.33-9.deb (latest) as the kernel source package > to recompile. The standard 2.0.33 source package (sunsite, tsx-11, etc) > does NOT have the latest patches. I made the mistake of trying to add the > patches to the debian source package (which already had them) and it > REMOVED the patches (reverse patch). This is the default action of patch, > and I didn't know what it (I) was doing at the time. I think the fat-32 > option is in the internal code section (code page) of the menuconfig script > as it is bundled with other stuff. > Conversely, if you want to try the 2.0.34prexx patches, it's probably best to not use the Debian kernel-source package, as some of that appears to be included (at least patch thinks so). Bob Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] http://www.primenet.com/~nielsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
>> If you downloaded it not in .deb form, the patch for FAT32 support is not >> included... The .deb version does... I had to figure that out about 3 >> weeks ago.. >> >I would really suggest not using .deb kernels. The reason they have FAT32 >support is because they are just the standard default bins. They are not >configured to run on your system. They therefore are not very high >performance. They usually take up way too much memory because they include >all kinds of things you probably dont even have. It is always good to >compile your own kernels. Try it, you'll find it makes a HUGE difference. Use the kernerl-source-2.0.33-9.deb (latest) as the kernel source package to recompile. The standard 2.0.33 source package (sunsite, tsx-11, etc) does NOT have the latest patches. I made the mistake of trying to add the patches to the debian source package (which already had them) and it REMOVED the patches (reverse patch). This is the default action of patch, and I didn't know what it (I) was doing at the time. I think the fat-32 option is in the internal code section (code page) of the menuconfig script as it is bundled with other stuff. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
On Fri, 22 May 1998, Brian Weiss wrote: > > > On Sat, 23 May 1998, Michael Beattie wrote: > > > On Fri, 22 May 1998, Ionut Borcoman at musa wrote: > > > > > Hi, > > > > > > Unfortunately, I've panicked and reinstalled all Win95. Fortunately, all > > > my personal data and files are on a different partition (sda5 and sda6) > > > so nothing important was lost, excepting my time and yours. With this > > > occasion I have also changed sda1 from FAT32 to VFAT as my newly 2.0.33 > > > kernel didn't recognize it. Any idea about this ? The original kernel > > > that come with hamm had had no problem to mount that partition. > > > > If you downloaded it not in .deb form, the patch for FAT32 support is not > > included... The .deb version does... I had to figure that out about 3 > > weeks ago.. > > > > I would really suggest not using .deb kernels. The reason they have FAT32 > support is because they are just the standard default bins. They are not > configured to run on your system. They therefore are not very high > performance. They usually take up way too much memory because they include > all kinds of things you probably dont even have. It is always good to > compile your own kernels. Try it, you'll find it makes a HUGE difference. > > Brian > What I really meant was to use the .deb kernel sources... But thats my fault.. I didnt make that clear. Michael Beattie ([EMAIL PROTECTED]) --- Does The Little Mermaid wear an algebra? --- Debian GNU/Linux Ooohh You are missing out! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
On Fri, May 22, 1998 at 05:40:59PM -0700, Brian Weiss wrote: > I would really suggest not using .deb kernels. The reason they have FAT32 > support is because they are just the standard default bins. They are not > configured to run on your system. They therefore are not very high > performance. They usually take up way too much memory because they include > all kinds of things you probably dont even have. It is always good to > compile your own kernels. Try it, you'll find it makes a HUGE difference. I only use .deb kernels. However, I make them myself. Check out kernel-package. Manoj has done a great job with it. pgp3DqbK50tF0.pgp Description: PGP signature
Re: !!! URGENT !!! Can't boot back to Win95
On: Fri, 22 May 1998 14:14:24 + Ionut Borcoman at musa writes: > > Hi, > Unfortunately, I've panicked and reinstalled all Win95. Fortunately, > all my personal data and files are on a different partition (sda5 > and sda6) so nothing important was lost, excepting my time and > yours. With this occasion I have also changed sda1 from FAT32 to > VFAT as my newly 2.0.33 kernel didn't recognize it. Any idea about > this ? The original kernel that come with hamm had had no problem to > mount that partition. Visit http://bmrc.berkeley.edu/people/chaffee/fat32.html for a kernel patch. You will get Joliet support for free if you install it. Torsten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
Brian Weiss wrote: > > On Fri, 22 May 1998, Ed Cogburn wrote: > > > > > It's not clear from the previous thread whether they are referring to > > kernel-image-xxx or kernel-source-xxx debs. The kernel-image-xxx > > (pre-compiled) > > debs aren't too useful because they tend to have everything and the kitchen > > sink > > compiled in, as Brian suggests. However this doesn't apply to > > kernel-source-xxx > > debs. *Use them*. The recent kernel-source-2.0.33-xxx has the FAT32 > > support in > > it. Use it to build a kernel for your system. > > > > Ed > > > > Very very good point Ed, however all kernel source has FAT32 support, you > just say yes to it in the config :). But anyway, I haven't personally used > the .deb source files but I would suggest giving them a try if you don't > quite feel comfortable with the regular source yet. > > Brian Actually, kernel-source-2.0.32-xxx deb did not have the FAT32 support in it. Neither does the 'official' 2.0.33 kernel source tarball. Only when I heard of kernel-source-2.0.33-xxx deb that was recently put up on ftp.debian.org did I get one with the FAT32 support already integrated into the kernel source package. I'll bet your referring to the development kernels. IIRC, FAT32 support was integrated into 2.1.xx kernel series fairly early on. Second, there isn't that much of a difference between the official source tarballs and the kernel-source-xxx deb files except that the deb packages will update the symlinks and the .linux-versions file in /usr/src/linux for you. With kernel-source-2.0.33-xxx deb a big difference is that the maintainer thoughtfully incorporated the FAT32 patch for the rest of us not using the development kernel. Ed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
On Sat, 23 May 1998, Michael Beattie wrote: > On Fri, 22 May 1998, Ionut Borcoman at musa wrote: > > > Hi, > > > > Unfortunately, I've panicked and reinstalled all Win95. Fortunately, all > > my personal data and files are on a different partition (sda5 and sda6) > > so nothing important was lost, excepting my time and yours. With this > > occasion I have also changed sda1 from FAT32 to VFAT as my newly 2.0.33 > > kernel didn't recognize it. Any idea about this ? The original kernel > > that come with hamm had had no problem to mount that partition. > > If you downloaded it not in .deb form, the patch for FAT32 support is not > included... The .deb version does... I had to figure that out about 3 > weeks ago.. > I would really suggest not using .deb kernels. The reason they have FAT32 support is because they are just the standard default bins. They are not configured to run on your system. They therefore are not very high performance. They usually take up way too much memory because they include all kinds of things you probably dont even have. It is always good to compile your own kernels. Try it, you'll find it makes a HUGE difference. Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
On Fri, 22 May 1998, Nils Rennebarth wrote: > On Fri, May 22, 1998 at 11:50:09PM +1200, Michael Beattie wrote: > > On Fri, 22 May 1998, Ionut Borcoman at musa wrote: > > > It's a little bit humorous, but I'm unable to boot back to WIn95. And my > > > boss is in a hurry ! I've played a little with the kernel and now it > > > didn't recognize the vfat2 partition. Anything else is working, just > > > this is not. I have installed the lilo and I cannot remove it. The > > > method with booting from floppy and giving fdisk /mbr doesn't work. > > I dont want to upset you, but I _think_ you have fried your win95 > > partition... > Yes, but don't panic, lilo had made a backup. > > Use lilo -u /dev/sda1 to restore the old one. Verify before that > /boot/boot.0801 has the expected modification date (i.e. when you installed > lilo with the boot=/dev/sda1 option) [snip] My apologies... I forgot about that... Michael Beattie ([EMAIL PROTECTED]) --- WinErr: 003 Dynamic linking error - Your mistake is now in every file --- Debian GNU/Linux Ooohh You are missing out! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
On Fri, 22 May 1998, Ionut Borcoman at musa wrote: > Hi, > > Unfortunately, I've panicked and reinstalled all Win95. Fortunately, all > my personal data and files are on a different partition (sda5 and sda6) > so nothing important was lost, excepting my time and yours. With this > occasion I have also changed sda1 from FAT32 to VFAT as my newly 2.0.33 > kernel didn't recognize it. Any idea about this ? The original kernel > that come with hamm had had no problem to mount that partition. If you downloaded it not in .deb form, the patch for FAT32 support is not included... The .deb version does... I had to figure that out about 3 weeks ago.. Michael Beattie ([EMAIL PROTECTED]) --- WinErr: 00C Reserved for future mistakes by our developers --- Debian GNU/Linux Ooohh You are missing out! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
On Fri, 22 May 1998, Ionut Borcoman at musa wrote: > Hi, > > Unfortunately, I've panicked and reinstalled all Win95. Fortunately, all > my personal data and files are on a different partition (sda5 and sda6) > so nothing important was lost, excepting my time and yours. With this > occasion I have also changed sda1 from FAT32 to VFAT as my newly 2.0.33 > kernel didn't recognize it. Any idea about this ? The original kernel > that come with hamm had had no problem to mount that partition. This problem is probably caused by not having support for FAT32 compiled into your new kernel. The standard kernels that come with most distributions all have FAT32 support compiled in, which would explain why you didn't have any problems with the original kernel. When compiling your new one you probably forgot to add the FAT32 support. It's under the section "fs" if you use menuconfig or xconfig. If not, it'll just be somewhere near the end. > Now, the Win95 is working again and sda1 is simple vfat partion. I used > loadlin to boot linux, but I would like to use lilo. So here is my new > lilo.conf. Please tell me if it is good. I don't want to be again in the > position to install Win95. 8-) > > boot=/dev/sda > root=/dev/sda3 > compact > install=/boot/boot.b > map=/boot/map > vga=normal > delay=20 > default=win95 > > image=/vmlinuz > label=linux > read-only > root=/dev/sda3 > > image=/vmlinuz.old > label=old > read-only > root=/dev/sda3 > > other = /dev/sda1 > label=win95 > table = /dev/sda > > > A question related is this: my computer has 128M RAm, but linux see just > 64M. I have read that you can put mem=128M at the LILO: prompt or to > include it in the lilo.conf. Also, it is stated that, even when you have > 128M physical RAM, some RAM can be mapped and used by BIOS. SO, how do I > know how much RAM to declare to LILO and how do I do this in lilo.conf. I too have 128mb of physical RAM so i share your pain. If you want linux to recognize all of this, simply put the following line in the global section of lilo.conf (the top part): append="mem=128M" That should fix things up. Good luck Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
Hi, The lilo.conf it's working. So, if you have time, please just tell me how to configure the memory. TIA, Ionutz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
Hi, Unfortunately, I've panicked and reinstalled all Win95. Fortunately, all my personal data and files are on a different partition (sda5 and sda6) so nothing important was lost, excepting my time and yours. With this occasion I have also changed sda1 from FAT32 to VFAT as my newly 2.0.33 kernel didn't recognize it. Any idea about this ? The original kernel that come with hamm had had no problem to mount that partition. Now, the Win95 is working again and sda1 is simple vfat partion. I used loadlin to boot linux, but I would like to use lilo. So here is my new lilo.conf. Please tell me if it is good. I don't want to be again in the position to install Win95. 8-) boot=/dev/sda root=/dev/sda3 compact install=/boot/boot.b map=/boot/map vga=normal delay=20 default=win95 image=/vmlinuz label=linux read-only root=/dev/sda3 image=/vmlinuz.old label=old read-only root=/dev/sda3 other = /dev/sda1 label=win95 table = /dev/sda A question related is this: my computer has 128M RAm, but linux see just 64M. I have read that you can put mem=128M at the LILO: prompt or to include it in the lilo.conf. Also, it is stated that, even when you have 128M physical RAM, some RAM can be mapped and used by BIOS. SO, how do I know how much RAM to declare to LILO and how do I do this in lilo.conf. I will wait your answers till make a new step. 8-) Thanks, Ionutz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
Michael Beattie wrote: > On Fri, 22 May 1998, Ionut Borcoman at musa wrote: > > > Hi, > > > > It's a little bit humorous, but I'm unable to boot back to WIn95. And my > > boss is in a hurry ! I've played a little with the kernel and now it > > didn't recognize the vfat2 partition. Anything else is working, just > > this is not. I have installed the lilo and I cannot remove it. The > > method with booting from floppy and giving fdisk /mbr doesn't work. > > > > Here is my lilo.conf: > > I dont want to upset you, but I _think_ you have fried your win95 > partition... I believe that your 'boot=/dev/sda1' has killed the windows > loader... I dont know how to best explain how it works, as I dont know for > sure... I use 'boot=/dev/hda' <-- no "1" I knew when I looked at that lilo.conf something was wrong...however...it looks like just the boot information was screwedI think this can be fixed > > boot=/dev/sda1 > > root=/dev/sda3 > > compact > > install=/boot/boot.b > > map=/boot/map > > vga=normal > > delay=20 > > > > image=/vmlinuz > > label=linux > > read-only > > root=/dev/sda3 > > > > image=/vmlinuz.old > > label=old > > read-only > > root=/dev/sda3 > > > > other = /dev/sda1 > > label=win95 > > table = /dev/sda > > the 'other = /dev/sda1' line says "boot off of /dev/sda1", but you have > installed LILO there, that is why you get it again... > > > It registers the win95 entry, but, if I type win95 at the LILO: prompt, > > I just receive another LILO: prompt. Also, it will be better if the > > Win95 will be default SO. > > When you get it going... a 'default=win95' in the section at the top will > fix it... > > I hope this reason for your problem is not the case for you, But I have > done this myself once, and It was not a pleasant feeling in my gut when I > realized. > After reading all of this...here is what I would dowrite down where your linux root is... boot a windows 95 disk...you should be able to c: to get onto the hard drive. from there fdisk /mbr this will destroy lilo and reinstall the Win95 boot loader... then get out your linux emergency boot disk (you do have one right?... ig no tlook for Tom's Unix on a Floppy (as the lsm for it says sunsite.unc.edu /pub/Linux/system/recovery tomsrtbt-1.1.4.38.tar.gz ) mount yout root partition and then cd /mnt/etc edit lilo.conf to aply the fix above then lilo -C lilo.conf (from /mnt/etc) NB: I have not done THIS specifically...This is however what I would personally do (remember don't fdisk /mbr unless when you boot off of the floppy for win95 you can see and use the C: drive) Good Luck...hopefully you wont need it -Steve -- ** Stephen Carpenter ** ** ** ** ** ** ** ** ** ** ** ** [EMAIL PROTECTED] ** "We must respect the other fellow's religion, but only in the sense and to the extent that we respect his theory that his wife is beautiful and his children smart." -- H. L. Mencken (1880-1956) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
On Fri, May 22, 1998 at 11:50:09PM +1200, Michael Beattie wrote: > I dont want to upset you, but I _think_ you have fried your win95 > partition... I believe that your 'boot=/dev/sda1' has killed the windows > loader... I dont know how to best explain how it works, as I dont know for > sure... I use 'boot=/dev/hda' <-- no "1" It's not just a matter of killing the Windows loader, Windows actually stores partition meta-information in the superblock, which lilo will write in to. Fortunately you can restore it as other people have suggested. (Linux doesn't do this, so it is safe to use boot=/dev/sda2 if sda2 is your Linux partition. The default for Debian, even.) Hamish -- Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
I think that LILO anyway saves the old boot sector, so maybe not everything is lost ... >From 'man lilo': -s save-file When lilo overwrites the boot sector, it preserves the old contents in a file, by default /boot/boot. where depends on the device. This option specifies an alternate save file for the boot sector. (Or, together with the -u option, specifies from where to restore the boot sector.) I've never used LILO with -s option but it anyway created the /boot/boot.0303 and /boot/boot.0300 files on my box. I'm not expert in lilo, so I don't know if it really can help... Wojtek Zabolotny [EMAIL PROTECTED] On Fri, 22 May 1998, Michael Beattie wrote: > On Fri, 22 May 1998, Ionut Borcoman at musa wrote: > > > Hi, > > > > It's a little bit humorous, but I'm unable to boot back to WIn95. And my > > boss is in a hurry ! I've played a little with the kernel and now it > > didn't recognize the vfat2 partition. Anything else is working, just > > this is not. I have installed the lilo and I cannot remove it. The > > method with booting from floppy and giving fdisk /mbr doesn't work. > > > > Here is my lilo.conf: > > I dont want to upset you, but I _think_ you have fried your win95 > partition... I believe that your 'boot=/dev/sda1' has killed the windows > loader... I dont know how to best explain how it works, as I dont know for > sure... I use 'boot=/dev/hda' <-- no "1" > > > > boot=/dev/sda1 > > root=/dev/sda3 > > compact > > install=/boot/boot.b > > map=/boot/map > > vga=normal > > delay=20 > > > > image=/vmlinuz > > label=linux > > read-only > > root=/dev/sda3 > > > > image=/vmlinuz.old > > label=old > > read-only > > root=/dev/sda3 > > > > other = /dev/sda1 > > label=win95 > > table = /dev/sda > > the 'other = /dev/sda1' line says "boot off of /dev/sda1", but you have > installed LILO there, that is why you get it again... > > > It registers the win95 entry, but, if I type win95 at the LILO: prompt, > > I just receive another LILO: prompt. Also, it will be better if the > > Win95 will be default SO. > > When you get it going... a 'default=win95' in the section at the top will > fix it... > > > I hope this reason for your problem is not the case for you, But I have > done this myself once, and It was not a pleasant feeling in my gut when I > realized. > > >Michael Beattie ([EMAIL PROTECTED]) > > --- >WinErr: 00C Reserved for future mistakes by our developers > --- > Debian GNU/Linux Ooohh You are missing out! > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: !!! URGENT !!! Can't boot back to Win95
On Fri, May 22, 1998 at 11:50:09PM +1200, Michael Beattie wrote: > On Fri, 22 May 1998, Ionut Borcoman at musa wrote: > > It's a little bit humorous, but I'm unable to boot back to WIn95. And my > > boss is in a hurry ! I've played a little with the kernel and now it > > didn't recognize the vfat2 partition. Anything else is working, just > > this is not. I have installed the lilo and I cannot remove it. The > > method with booting from floppy and giving fdisk /mbr doesn't work. > I dont want to upset you, but I _think_ you have fried your win95 > partition... Yes, but don't panic, lilo had made a backup. Use lilo -u /dev/sda1 to restore the old one. Verify before that /boot/boot.0801 has the expected modification date (i.e. when you installed lilo with the boot=/dev/sda1 option) Now make sure you have a floppy handy from which you could boot Linux. Next switch on the bootable flag of the /dev/sda1 partition using cfdisk. Switch it off for all other partitions. Now you should be able to reboot to Windows 95, provided you did the fdisk/mbr before. To really make booting as you wanted it replace boot=/dev/sda1 with boot=/dev/sda and run lilo -v (after booting to Linux of course :-) Nils -- *-* | Quotes from the net: L> Linus Torvalds, W> Winfried Truemper | | L>this is the special easter release of linux, more mundanely called 1.3.84 | | W>Umh, oh. What do you mean by "special easter release"?. Will it quit | * W>working today and rise on easter? * pgpKBp3V9Dlsz.pgp Description: PGP signature
Re: !!! URGENT !!! Can't boot back to Win95
On Fri, 22 May 1998, Ionut Borcoman at musa wrote: > Hi, > > It's a little bit humorous, but I'm unable to boot back to WIn95. And my > boss is in a hurry ! I've played a little with the kernel and now it > didn't recognize the vfat2 partition. Anything else is working, just > this is not. I have installed the lilo and I cannot remove it. The > method with booting from floppy and giving fdisk /mbr doesn't work. > > Here is my lilo.conf: I dont want to upset you, but I _think_ you have fried your win95 partition... I believe that your 'boot=/dev/sda1' has killed the windows loader... I dont know how to best explain how it works, as I dont know for sure... I use 'boot=/dev/hda' <-- no "1" > boot=/dev/sda1 > root=/dev/sda3 > compact > install=/boot/boot.b > map=/boot/map > vga=normal > delay=20 > > image=/vmlinuz > label=linux > read-only > root=/dev/sda3 > > image=/vmlinuz.old > label=old > read-only > root=/dev/sda3 > > other = /dev/sda1 > label=win95 > table = /dev/sda the 'other = /dev/sda1' line says "boot off of /dev/sda1", but you have installed LILO there, that is why you get it again... > It registers the win95 entry, but, if I type win95 at the LILO: prompt, > I just receive another LILO: prompt. Also, it will be better if the > Win95 will be default SO. When you get it going... a 'default=win95' in the section at the top will fix it... I hope this reason for your problem is not the case for you, But I have done this myself once, and It was not a pleasant feeling in my gut when I realized. Michael Beattie ([EMAIL PROTECTED]) --- WinErr: 00C Reserved for future mistakes by our developers --- Debian GNU/Linux Ooohh You are missing out! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
!!! URGENT !!! Can't boot back to Win95
Hi, It's a little bit humorous, but I'm unable to boot back to WIn95. And my boss is in a hurry ! I've played a little with the kernel and now it didn't recognize the vfat2 partition. Anything else is working, just this is not. I have installed the lilo and I cannot remove it. The method with booting from floppy and giving fdisk /mbr doesn't work. Here is my lilo.conf: boot=/dev/sda1 root=/dev/sda3 compact install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label=linux read-only root=/dev/sda3 image=/vmlinuz.old label=old read-only root=/dev/sda3 other = /dev/sda1 label=win95 table = /dev/sda It registers the win95 entry, but, if I type win95 at the LILO: prompt, I just receive another LILO: prompt. Also, it will be better if the Win95 will be default SO. TIA, Ionutz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
