The BOOT.INI file in Windows maps where it expects to find certain files.
And it includes partition and drive information in it. You have to edit
this file even if just a partition before Windows changes on a single hard
drive.
In your case (I haven't tried this, adding another hard drive with W
you might need to recreate and re-install LILO. LI at
bootup means 'LILO is f*cked up' :). Just to check if
your win2k drive is still bootable, set your BIOS boot
sequence to start from the second drive.
For LILO, you might need to recheck the /etc/lilo.conf
if you can boot into single or rescue
>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: Re: please..anyone dual boot linux w2k frustrations
>Date: Tue, 30 Jul 2002 13:15:21 +0700
>
>On Tue, 30 Jul 2002 04:49:11 +, Tom wrote:
>
> >
> >LI is LILO starting up.
> >I don't
On Tue, 30 Jul 2002 04:49:11 +, Tom wrote:
>
>LI is LILO starting up.
>I don't know exactly where it dies, but the letters correspond to sections
>of the boot process. So, Lilo is dying after the second part of the boot
>process.
>[big snip, please don't overquote]
Not quite, according
now how to read NTFS drives and so cannot boot a
windows that is installed on an NTFS drive (I might be mistaken on that
though, but in my experience that has proved correct).
Tom
>From: script this <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subj
ginal Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> On Behalf Of Kevin Myers
> Sent: Monday, July 29, 2002 12:15 PM
> To: [EMAIL PROTECTED]
> Subject: Re: please..anyone dual boot linux w2k
> frustrations
>
> On Sun, 28 Jul 2002 08:29:18 -0
These lines take care of windoze need to be first:
map-drive = 0x80
to = 0x81
map-drive = 0x81
to = 0x80
and this line actually takes care of the above lines,
so including both would be the same as including
neither i believe:
loader=/boot/os2_d.b
--- "Rev. David P. Giffen" <[EMAIL PROTECTED]>
As a few people have mentioned, you _can_ install and run Win2k on a
non-primary drive, likewise linux, and many other Win version. The key word
there though was _install_.
Modern OSs i.e. Win2K, linux, don't use the bios to talk to the disks once
they are loaded, they talk directly to the hardwa
On Mon, 29 Jul 2002 00:00:32 -0500, David wrote:
>As far as I know Win2K needs to be on the primary drive. At least that is
>how I have dual booted a machine and havin't had any problems.
Not so. I have Win2k, XP, ME and linux here. All except the ME are on a
second drive.
___
As far as I know Win2K needs to be on the primary drive. At least that is
how I have dual booted a machine and havin't had any problems.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of script this
> Sent: Sunday, July 28, 2002 10:29 AM
> To: [EMAIL
On Mon, 29 Jul 2002 12:21:28 +0800, Pranay wrote:
>On Behalf Of Kevin Myers
???
___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
]]
On Behalf Of Kevin Myers
Sent: Monday, July 29, 2002 12:15 PM
To: [EMAIL PROTECTED]
Subject: Re: please..anyone dual boot linux w2k frustrations
On Sun, 28 Jul 2002 08:29:18 -0700 (PDT), you wrote:
>scenario:
>
>running redhat linux 7.2 for over a year on
>preinstalled hd. purchased
On Sun, 28 Jul 2002 08:29:18 -0700 (PDT), you wrote:
>scenario:
>
>running redhat linux 7.2 for over a year on
>preinstalled hd. purchased second drive with w2k
>preinstalled. hooked up second drive as secondary ide
>drive (hdb), kept primary drive with linux as hda.
>
>problem:
>
>w2k will no
I have had similar problems your solution is in linux in a nutshell. It
is something to do with copying nt boot onto you r boot loader. This is
if win2k is ntfs. Hope this helps.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of script this
Sent: 28 July 2
14 matches
Mail list logo
