Re: Lilo and Win98 Q's
KC6SBJ wrote: Has anyone found Lilo not to be written over while installing Win98 on c: (hda1). Try fdisk /mbr from a DOS/Win9x boot floppy (it'll have to have fdisk on it, of course). This will wipe the master boot record (leaving the rest of the disk/partitions intact). Then, if you've already reinstalled Win98, you'll have to do a sys c from a Win98 boot disk. Then you can reconfigure lilo.conf and rerun lilo if you want to set up a dual boot.
Lilo and Win98 Q's
Has anyone found Lilo not to be written over while installing Win98 on c: (hda1). Why is Windows going back on my machine. The Kids Games that caused it to crash. I am still booting Storm / Debian potato and Windows will not reload. Even after formating C: (hda1). Glad somthing is working, Even if Stormmix is having $$$'s problems. Tobad... Lowell Voelker [EMAIL PROTECTED] My ISP is getting rid of Shell accounts too. That drove me to Storm/Debian
Re: Lilo and Win98 Q's
on my dual boot machine, a windows reinstall always overwrites the mbr to boot straight into windows. I always keep boot floppy around so i can boot and re-lilo the thing. If you are having problems getting lilo to load windows, the line i have in my lilo.conf to do this is other=/dev/hda1 label=win table=/dev/hda and that works for me. You may also want to change the Delay=20 line to something more than 2 seconds, as its easy to miss that window if you arent paying attention to yuor machine booting. -Casey On Mon, 29 Jan 2001, KC6SBJ wrote: Has anyone found Lilo not to be written over while installing Win98 on c: (hda1). Why is Windows going back on my machine. The Kids Games that caused it to crash. I am still booting Storm / Debian potato and Windows will not reload. Even after formating C: (hda1). Glad somthing is working, Even if Stormmix is having $$$'s problems. Tobad... Lowell Voelker [EMAIL PROTECTED] My ISP is getting rid of Shell accounts too. That drove me to Storm/Debian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: chos, lilo, linux, win98, oh my!
Robbie Huffman wrote: I would go back to using lilo, but after running lilo I still get chos at boot time. Any help with either would be greatly appreciated. See if you have chos installed in the hard disk boot area and lilo installed in a partition boot area. If so, you could use the dos fdisk /mbr to blow away chos. -- Charles B. (Ben) Cranston mailto:[EMAIL PROTECTED] http://www.wam.umd.edu/~zben
chos, lilo, linux, win98, oh my!
Has anyone out in debian-userland managed to get chos to boot Win98? I have
it installed on a small drive at /dev/hdc1. If I set my bios to boot drive D
Win98 works great. But the following entry with chos gives me errors.
bootsect Windows 98 {
color=lightblue
image=/dev/hdc1
}
I would go back to using lilo, but after running lilo I still get chos at
boot time. Any help with either would be greatly appreciated.
Sincerely confused,
Robbie
Re: chos, lilo, linux, win98, oh my!
That config doesn't really sound right... I mean, image=/dev/hdc1 would
imply that the image IS that drive. Shouldn't it be something more like
root=/dev/hdc1 or something like a lilo config? I would seriously just go to
lilo. Can you not remove the ``chos'' package through dselect? If not, just
remove it from the initialization scripts in /etc/init.d/
-dan
From: Robbie Huffman [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Subject: chos, lilo, linux, win98, oh my!
Date: Sat, 10 Jul 1999 01:49:22 -0400
Has anyone out in debian-userland managed to get chos to boot Win98? I have
it installed on a small drive at /dev/hdc1. If I set my bios to boot drive
D
Win98 works great. But the following entry with chos gives me errors.
bootsect Windows 98 {
color=lightblue
image=/dev/hdc1
}
I would go back to using lilo, but after running lilo I still get chos at
boot time. Any help with either would be greatly appreciated.
Sincerely confused,
Robbie
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED]
/dev/null
___
Get Free Email and Do More On The Web. Visit http://www.msn.com
Re: chos, lilo, linux, win98, oh my!
On Sat, Jul 10, 1999 at 06:21:19AM +, Dan wrote: That config doesn't really sound right... I mean, image=/dev/hdc1 would imply that the image IS that drive. Shouldn't it be something more like root=/dev/hdc1 or something like a lilo config? I would seriously just go to lilo. Can you not remove the ``chos'' package through dselect? If not, just remove it from the initialization scripts in /etc/init.d/ -dan That config is the best I could make of the example file in /usr/doc/chos. There doesn't seem to be a root= sort of option. As for removing the package, well, I could, but that would still leave chos installed as the bootloader. I can't get lilo to replace it. Hope that clarifies the situation. Many thanks, Robbie
Re: lilo and win98
On Mon, 21 Jun 1999 14:28:54 -0500 (CDT), Brad [EMAIL PROTECTED] wrote: On Mon, 21 Jun 1999, Gertjan Klein wrote: Interesting to see that this works for W9x. Just out of curiousity: if you go to Control Panel - System and press the device tab, does it say the File System is 32-bit? i haven't explicitly checked, but logically it must. Before i installed Linux the filesystem was FAT32 and i did no reformatting of the windows partition. If it were not reading a FAT32 filesystem, windows wouldn't even boot because it could not possibly find any file correctly. Would you mind checking? The information on that tab doesn't actually apply to the filesystem itself, but to the disk I/O driver. W9x says the filesystem is 32 bit if it has completely replaced the BIOS disk drivers with its own, protected mode (32-bit) drivers. Reasons for not doing so include the presence of older, 16-bit drivers in config.sys. W9x does some tests when booting: it reads a couple of sectors through BIOS, and then the same sectors by directly accessing the harddisk. If it encounters differences, (i.e., doesn't get the same sectors back from both reads), it will keep on using the BIOS routines for disk I/O. There are two reasons why W9x could support the drive swapping that LILO does on your system. It could recognise the actual swapping for what it is and implement it in it's own (32-bit) driver. Alternatively, it could see that something is messing with the drive mapping and leave it alone; it would keep on using the BIOS for disk I/O. In the latter case, it would report the filesystem as 16-bit. I'm just curious what it does. Gertjan. -- Gertjan Klein [EMAIL PROTECTED] The Boot Control home page: http://www.xs4all.nl/~gklein/bcpage.html
Re: lilo and win98
On Tue, 22 Jun 1999, Gertjan Klein wrote: Would you mind checking? The information on that tab doesn't actually apply to the filesystem itself, but to the disk I/O driver. W9x says the filesystem is 32 bit if it has completely replaced the BIOS disk drivers with its own, protected mode (32-bit) drivers. Reasons for not Ah, when you said File System is 32-bit i thought you meant just that, and not the filesystem io. Checking, the io is indeed 32 bit. Also, as a further test i created a FAT partition on hda3 (windows is on hdb1 and hdb5). Drive C was still hdb1, but drive D became hda3 and drive E was hdb5. There are two reasons why W9x could support the drive swapping that LILO does on your system. It could recognise the actual swapping for what it is and implement it in it's own (32-bit) driver. Alternatively, it could see that something is messing with the drive mapping and leave it alone; it would keep on using the BIOS for disk I/O. In the latter case, it would report the filesystem as 16-bit. I'm just curious what it does. My guess is that for booting it uses the bios, and is therefore fooled by the swapping. Later on, it installs its own drivers. It automatically uses whichever partition it was booted from as C: (which is already 'mounted' by this time anyway, otherwise we couldn't have even gotten to this point). It then scans the hard drives, without using the bios, and mounts all FAT partitions as it finds them.
Re: lilo and win98
On Tue, 22 Jun 1999 13:29:53 -0500 (CDT), Brad [EMAIL PROTECTED] wrote: Ah, when you said File System is 32-bit i thought you meant just that, and not the filesystem io. Ah, but this isn't about what _I_ mean, but what terminology W9x uses... Checking, the io is indeed 32 bit. Also, as a further test i created a FAT partition on hda3 (windows is on hdb1 and hdb5). Drive C was still hdb1, but drive D became hda3 and drive E was hdb5. The way W9x assigns drive letters to partitions is, as far as I know, unchanged from how DOS used to do it (although I don't know how the new partition types fit into the picture). These rules are a bit complicated, and can be found in the Boot Control documentation if anyone is interested (see my .sig). It is interesting to see, though, that apparently W98 recognises drive swapping and implements it in it's own driver. I'll have to do some experiments with this as soon as I've got sufficient hardware for testing. (Currently my only PC with two HDs is a 386 with 4 MB, and I'm not even going to try installing W98 to that; it is running Debian, functioning as an IP masquerading Internet gateway for my local network, without any problems. Beat that, W9x or NT!) Gertjan. -- Gertjan Klein [EMAIL PROTECTED] The Boot Control home page: http://www.xs4all.nl/~gklein/bcpage.html
Re: lilo and win98
On Sun, 20 Jun 1999, Sander Balkenende wrote: hi I have problems starting win98 on hdb1 with Lilo. When trying to start win (shift, dos), nothing happens. Linux (hda1) starts fine. I have the exact same setup (unless you have the new release of '98), even the same partition numbers. First, i'll assume that your Windoze partition is bootable if you tell bios to boot from the second drive, or switch the drives around. Don't actually do it for keeps, but it's a good way to check that it can boot on its own ;) Then, this lilo.conf should work. This is an exact copy of my current conf with comments added. boot=/dev/hda vga=normal map=/boot/map # Next three or four lines are for my boot menu prompt timeout=100 message=/boot/startup-msg default=Linux # Normal Linux image image=/vmlinuz root=/dev/hda1 label=Linux read-only alias=1 # # Backup, if you use make-kpkg or the kernel debs, it automatically # symlinks vmlinuz.old to the kernel you just replaced image=/vmlinuz.old root=/dev/hda1 label=oldLinux read-only alias=3 # # Here's the windoze boot, in case i ever need it other=/dev/hdb1 table=/dev/hdb # Next 4 lines tell bios to make windows think it's on the first HD map-drive = 0x80 to = 0x81 map-drive = 0x81 to = 0x80 # chain.b is implied. label=win alias=2 Until i added the map-drive options, windows would refuse to boot; it would freeze after Lilo said Loading win... and tried to hand control to the MBR. Wonder if micros~1 will somehow render this ineffective when they release W2K?
Re: lilo and win98
On 20 Jun 1999 23:43:06 +0200, Rui Zhu [EMAIL PROTECTED] wrote: other=/dev/hdb1 label=win map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 Interesting to see that this works for W9x. Just out of curiousity: if you go to Control Panel - System and press the device tab, does it say the File System is 32-bit? Gertjan. -- Gertjan Klein [EMAIL PROTECTED] The Boot Control home page: http://www.xs4all.nl/~gklein/bcpage.html
Re: lilo and win98
I resolved the problem of booting Linux by making my win98 drive hda again and reinstalled Debian on hdb (at the moment, I am just experimenting with Linux). This works fine, I have to fine-tune loadlin, but that works. When trying to load loadlin from config.sys with the [menu] command, it works the first time, but after that, windoze has rewritten the config.sys and erased the line that loads linux.bat (which activates loadlin). Has anyone experiences with that? other=/dev/hdb1 label=win map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 Interesting to see that this works for W9x. Just out of curiousity: if you go to Control Panel - System and press the device tab, does it say the File System is 32-bit? Gertjan.
Re: lilo and win98
On Mon, 21 Jun 1999 17:39:56 +0200, Sander Balkenende [EMAIL PROTECTED] wrote: I resolved the problem of booting Linux by making my win98 drive hda again and reinstalled Debian on hdb (at the moment, I am just experimenting with Linux). This works fine, I have to fine-tune loadlin, but that works. When trying to load loadlin from config.sys with the [menu] command, it works the first time, but after that, windoze has rewritten the config.sys and erased the line that loads linux.bat (which activates loadlin). Has anyone experiences with that? Weird. You may want to try installing LILO in the MBR of the first harddisk, so you can choose before W98 even start and won't need loadlin. Gertjan. -- Gertjan Klein [EMAIL PROTECTED] The Boot Control home page: http://www.xs4all.nl/~gklein/bcpage.html
Re: lilo and win98
On Mon, 21 Jun 1999, Gertjan Klein wrote: On 20 Jun 1999 23:43:06 +0200, Rui Zhu [EMAIL PROTECTED] wrote: other=/dev/hdb1 label=win map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 Interesting to see that this works for W9x. Just out of curiousity: if you go to Control Panel - System and press the device tab, does it say the File System is 32-bit? i haven't explicitly checked, but logically it must. Before i installed Linux the filesystem was FAT32 and i did no reformatting of the windows partition. If it were not reading a FAT32 filesystem, windows wouldn't even boot because it could not possibly find any file correctly.
Re: lilo and win98
I have problems starting win98 on hdb1 with Lilo. When trying to start win (shift, dos), nothing happens. Linux (hda1) starts fine. my lilo.conf: other=/dev/hdb1 label=dos a look at my lilo.conf reveals: other=/dev/hda1 label=DOS table=/dev/hda could it your missing ´table´? sorry, too much time has gone since i wrote my .conf (: hafi
Re: lilo and win98
I have problems starting win98 on hdb1 with Lilo. When trying to start win (shift, dos), nothing happens. Linux (hda1) starts fine. my lilo.conf: other=/dev/hdb1 label=dos could it your missing ´table?' I added the line table=/dev/hdb and after doing /sbin/lilo, no result. (message: loading dos, nothing happens after that) Sander
Re: lilo and win98
Sander Balkenende wrote: table=/dev/hdb hm, hm, i try to remember and... yes. to boot dos (or win) this hd must be the first. how about the exchange of the hd´s? or, maybe, if you make your hdb bootable... good luck hfi
Re: lilo and win98
Sander Balkenende wrote: hi I have problems starting win98 on hdb1 with Lilo. When trying to start win (shift, dos), nothing happens. Linux (hda1) starts fine. my lilo.conf: I believe that Windows 98 (like DOS and Windows95) must be on the first partition of the first hard drive. Remember one of the Ten Commandments of Microsoft: Thou shalt have no other operating systems before me. So basically, put win98 on hda1 and linux on hdb1, with lilo on hda's MBR. My lilo.conf is attached. --- Greg Starkes, Computing Communications, Memorial University of Newfoundland. e-mail: [EMAIL PROTECTED]www: http://www.cs.mun.ca/~gstarkes/ You can twist perceptions, reality won't budge. -Neil Peart, Rush, Show Don't Tellboot=/dev/hda root=/dev/hdb1 install=/boot/boot.b map=/boot/map vga=normal delay=50 read-only image=/vmlinuz label=Linux other=/dev/hda1 label=98 table=/dev/hda
Re: lilo and win98
Hartmut Figge wrote: to boot dos (or win) this hd must be the first. how about the exchange of the hd´s? or, maybe, if you make your hdb bootable... i just looked into /usr/doc/lilo/manual.txt.gz and found MAP-DRIVE=bios_device_code Instructs chain.b to installs a resident driver that re-maps the floppy or hard disk drives. This way, one can boot any operating system from a hard disk different from the first one, as long as that operating system uses _only_ the BIOS to access that hard disk.* This is known to work for PC/MS-DOS. this option wasn`t available when i wrote my lilo.conf. irecommend that you look into this file. hafi
Re: lilo and win98
I have problems starting win98 on hdb1 with Lilo. When trying to start win (shift, dos), nothing happens. Linux (hda1) starts fine. my lilo.conf: boot=/dev/hda1 root=/dev/hda1 install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label=Linux read-only other=/dev/hdb1 label=dos Change 'boot=/dev/hda1' to 'boot=/dev/hda'. -- An eye for an eye will leave the whole world blind (Gandhi)
Re: lilo and win98
In a message dated 6/19/99 10:20:07 PM Central Daylight Time, [EMAIL PROTECTED] writes: CC: debian-user@lists.debian.org I don't know how lilo works exactly. but,the general rule is that the partition for win98 must be bootable itself. Then MBR is capable of switching to win98 booting area by looking at the partition table.
Re: lilo and win98
On Sat, 19 Jun 1999 21:23:38 -0230, Greg Starkes [EMAIL PROTECTED] wrote: I believe that Windows 98 (like DOS and Windows95) must be on the first partition of the first hard drive. There is no requirement that W98 be on the first partition, but none of DOS/W95/W98 directly support being booted from a second harddisk. I've got it to work for DOS once, but it required patching the DOS partition bootsector, and I don't know how to do that for W9x (the bootsector is different). Gertjan. -- Gertjan Klein [EMAIL PROTECTED] The Boot Control home page: http://www.xs4all.nl/~gklein/bcpage.html
Re: lilo and win98
Sander Balkenende [EMAIL PROTECTED] writes: hi I have problems starting win98 on hdb1 with Lilo. When trying to start win (shift, dos), nothing happens. Linux (hda1) starts fine. my lilo.conf: boot=/dev/hda1 root=/dev/hda1 install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label=Linux read-only other=/dev/hdb1 label=dos can anyone help me? Thanx, Sander I boot my win95 on hdb ok, here is my lilo.conf, you may get idea. boot=/dev/hda1 compact install=/boot/boot.b map=/boot/map vga=normal delay=30 default=deb image=/vmlinuz label=deb root=/dev/hda1 read-only image=/vmlinuz.old label=deb.old root=/dev/hda1 read-only other=/dev/hdb1 label=win map-drive=0x80 to=0x81 map-drive=0x81 to=0x80
lilo and win98
hi I have problems starting win98 on hdb1 with Lilo. When trying to start win (shift, dos), nothing happens. Linux (hda1) starts fine. my lilo.conf: boot=/dev/hda1root=/dev/hda1install=/boot/boot.bmap=/boot/mapvga=normaldelay=20image=/vmlinuz label=Linux read-onlyother=/dev/hdb1 label=dos can anyone help me? Thanx, Sander
Re: W95 defrag [also lilo+Linux+Win98 FAT32]
On 23 Apr 99, at 23:45, Matt Folwell wrote about Re: W95 defrag [also lilo+Linux+Win: On Thu, Apr 22, 1999 at 05:42:09PM -0500, Brad wrote: For quite a while, Windows refused to boot at all from lilo. i finally solved the problem by using some obscure commands buried deep in TFM. Probably you won't need them, but they're here for a reference anyway. other=/dev/hdb1 table=/dev/hdb # The map-drive directives make windows think it's on the primary # master drive instead of the primary slave. Windows would think # Linux was on the slave if it could see it. map-drive = 0x80 to = 0x81 map-drive = 0x81 to = 0x80 label=win alias=2 Which FM did you find this is? I've been unable to boot windows from lilo /usr/docs/lilo/manual.txt.gz (or something like that, case might be off) since I moved it (windows) to /dev/hdc. I'd guess I need to use 0x82 where you've used 0x81, but I'd rather make sure before I risk it, and I can't see map-drive mentioned in the lilo.conf man page. You can try it, but you might have a problem booting windows off anything other than the first 2 drives. The one thing about MS OS's in general (except for NT) they need to boot off of the the primary, active partition, and I believe it can be the only primary partition visible on the drive. For a while I was able to boot windows using other=/dev/hdc but this suddenly stopped working, saying Missing Operating System Does anyone know what could cause that? What primary partitions do you have on the first 2 drives? Did this change between then and now? TTFN TIA, Matt -- Matt Folwell, Trinity College, Cambridge. CB2 1TQ [EMAIL PROTECTED] -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null == Jan M.- mailto:[EMAIL PROTECTED] PGP key mailto:[EMAIL PROTECTED] Fingerprint:397D 093C E802 964E 5316 B90A 93CE 6696 Thought for the day: 'Gratitude': An imaginary emotion that rewards an imaginary behavior,'altruism.' Both imaginaries are false faces for selfishness, which is a real and honest emotion. -- Maureen Johnson, 'To Sail Beyond the Sunset' (Robert Heinlein)
Re: W95 defrag [also lilo+Linux+Win98 FAT32]
On Fri, Apr 23, 1999 at 09:39:12PM -0400, Jan Muszynski wrote: On 23 Apr 99, at 23:45, Matt Folwell wrote about Re: W95 defrag [also lilo+Linux+Win: Which FM did you find this is? I've been unable to boot windows from lilo /usr/docs/lilo/manual.txt.gz (or something like that, case might be off) D'oh! Now why didn't I think of that? since I moved it (windows) to /dev/hdc. I'd guess I need to use 0x82 where you've used 0x81, but I'd rather make sure before I risk it, and I can't see map-drive mentioned in the lilo.conf man page. You can try it, but you might have a problem booting windows off anything other than the first 2 drives. The one thing about MS OS's in general (except for NT) they need to boot off of the the primary, active partition, and I believe it can be the only primary partition visible on the drive. For a while I was able to boot windows using other=/dev/hdc but this suddenly stopped working, saying Missing Operating System Does anyone know what could cause that? What primary partitions do you have on the first 2 drives? Did this change between then and now? It works now, thanks. I did need 0x81, which I suppose is consistent with my bios setup - of ide-0, -1, -2 and -3 I have to use ide-1 to boot the second hard drive, even though it's the third ide device. Maybe I should have given more details of my setup: /dev/hda has 2 primary partitions for linux- / and swap, and an extended partition with a few linux partitions and one fat32 one. /dev/hdb is my cd rom drive /dev/hdc has my primary win95 partition and another swap partition for linux (also primary) Anyway, either of these entries in lilo.conf will now boot windows: other=/dev/hdc label=Win95 map-drive = 0x80 to = 0x81 map-drive = 0x81 to = 0x80 other=/dev/hdc1 label=Win2 table=/dev/hdc map-drive = 0x80 to = 0x81 map-drive = 0x81 to = 0x80 I wonder which is better. I also now have 2 boot menus to go through before windows loads, and they both default to linux :-) -- Matt Folwell, Trinity College, Cambridge. CB2 1TQ [EMAIL PROTECTED]
Re: W95 defrag [also lilo+Linux+Win98 FAT32]
On Thu, Apr 22, 1999 at 05:42:09PM -0500, Brad wrote: For quite a while, Windows refused to boot at all from lilo. i finally solved the problem by using some obscure commands buried deep in TFM. Probably you won't need them, but they're here for a reference anyway. other=/dev/hdb1 table=/dev/hdb # The map-drive directives make windows think it's on the primary # master drive instead of the primary slave. Windows would think # Linux was on the slave if it could see it. map-drive = 0x80 to = 0x81 map-drive = 0x81 to = 0x80 label=win alias=2 Which FM did you find this is? I've been unable to boot windows from lilo since I moved it (windows) to /dev/hdc. I'd guess I need to use 0x82 where you've used 0x81, but I'd rather make sure before I risk it, and I can't see map-drive mentioned in the lilo.conf man page. For a while I was able to boot windows using other=/dev/hdc but this suddenly stopped working, saying Missing Operating System Does anyone know what could cause that? TIA, Matt -- Matt Folwell, Trinity College, Cambridge. CB2 1TQ [EMAIL PROTECTED]
Re: W95 defrag [also lilo+Linux+Win98 FAT32]
On Thu, 22 Apr 1999, H C Pumphrey wrote: Greetings, fellow Debian fans, Greetings (: This is only a proto-debian question, I'm afraid, but I have tried to RTFM, honest. I'm trying to defrag the disc on a W95 laptop prior to using FIPS to re-partition it so I can put Debian on it as well[1]. W95 defrag will move a lot of stuff (which it colours turquoise) to the beginning of the disc, but One piece of advice: back up everything you want to keep! i used fips on my Win98 FAT32 drive at one point, and even though it didn't appear to wreck anything Windoze refused to start until i restored from a backup i made (in my case it was easy, two HDs). Second piece of advice: don't use the M$ backup to do it, if you need to use the CD to boot it makes you reinstall windows before it'll read the thing no matter what. [[[SNIP]]] A related question: the Linux+Win95 mini-HOWTO says that if you have FAT32 you should not try using LILO. Is this info up-to-date? What about the business about the Linux boot partition having to start below sector 1024 (assuming LILO can be used ). i have no trouble using lilo with Linux+Win98's FAT32. My setup is for a two-drive system, but it _should_ work for a single drive multi-partition system. In my setup, the Linux drive is hda (on partition hda2), while windows is on hdb (partition hdb1) The Linux section of my lilo.conf is vanilla: image=/vmlinuz root=/dev/hda2 label=Linux read-only alias=1 For quite a while, Windows refused to boot at all from lilo. i finally solved the problem by using some obscure commands buried deep in TFM. Probably you won't need them, but they're here for a reference anyway. other=/dev/hdb1 table=/dev/hdb # The map-drive directives make windows think it's on the primary # master drive instead of the primary slave. Windows would think # Linux was on the slave if it could see it. map-drive = 0x80 to = 0x81 map-drive = 0x81 to = 0x80 label=win alias=2 [1] Yes I know. I should nuke W95 entirely, but I want to be sure that (a) I never use it and (b) all the hardware works OK in Linux. Understandable, i did the same thing. I only use windows now when extenuating circumstances force me (i.e. i need the windows-only printer diagnostics). Windows was quite helpful in verifying my hardware settings, especially the soundcard and printer. Although it turned out they were exactly as i would have suspected from the docs. [2] Not sure how to find this out. To find if it's a FAT32? You should be able to right click on the drive icon in windows and look in the properties. Or else, a good partitioning program should tell you.
