At Fri, 17 Apr 2009 11:28:45 -0400 CentOS mailing list <centos at centos.org> wrote: > > Sorin Srbu wrote: > > > > Apparantely Windows can bork up after a while if the system files aren't on > > C:. I was thinking the Windows installer will see the linux partitions and > > try to name them C: and D: etc, thus Windows will be installed on E: or F:, > > which might not go down well with some programs. > > > > Unless you install Linux on FAT, Winblows won't see it. If MS-Windows can't install itself on the first drive (as seen by the BIOS eg /dev/hda(1) or /dev/sda(1)), it won't install. *MS-Windows* (AFAIK) simply won't install itself anyplace but C: (at least for the core system). I once spent a day or so trying to install MS-Windows NT 4.0 (the pre-cursor to Win2K/WinXP/etc.) on a machine which had a working Linux install on its SCSI disk (SCSI ID 0). I had added a *second* drive (SCSI ID 1). The MS-Windows installer saw the second drive, would format it, but then would claim that there was no drive space to install MS-Windows on. I want through this loop several times. The installer's error messages were quite unhelpful, at least to someone not used to the Redmond mentality. I ended up swaping drive ID jumpers, making the Linux install on drive #1 (/dev/sdb*) and the new disk drive #0 (/dev/sda*). MS-Windows installed itself then (and I had to do a rescue boot to re-install Lilo on the new drive #0). > > > > Guy Boisvert, ing > IngTegration inc. > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > > -- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller at deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/