I'm setting up a Dell that came with windows XP installed on its hard
drive. I've added another drive, configured to be the master, and
changed the original drive to be the slave. I installed 10.1 on the
new drive and had lilo self-install on the MBR of that drive. The
install script recognized the windows partition on the original drive
and added an entry for it (on /dev/hdb2 with table=/dev/hdb). While
booting into Linux works exactly as expected (the original drive is
also accessible), if I try to boot into the windows partition the
system hangs. One exception to this behavior is when I set the boot
flag on windows partition; now the system boots directly into windows,
and I never see the LILO menu.

Any suggestions?

David

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware ronis-REM0VE@ronispc-d0t-chem-d0t-mc...quebec-is.invalid wrote:
> I'm setting up a Dell that came with windows XP installed on its hard
> drive. I've added another drive, configured to be the master, and
> changed the original drive to be the slave. I installed 10.1 on the
> new drive and had lilo self-install on the MBR of that drive. The
> install script recognized the windows partition on the original drive
> and added an entry for it (on /dev/hdb2 with table=/dev/hdb). While
> booting into Linux works exactly as expected (the original drive is
> also accessible), if I try to boot into the windows partition the
> system hangs. One exception to this behavior is when I set the boot
> flag on windows partition; now the system boots directly into windows,
> and I never see the LILO menu.
>
> Any suggestions?

I've always left the windoze partition as the master.

cordially, as always,

rm

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBQhDq8eEckfDWS6x8EQLnDwCg6ok8aeTre+PsIpcmN5E4gc P1lFwAn2rk
/rDZshWnXIiSvTeuO/wyloha
=mhRE
-----END PGP SIGNATURE-----

maybe put a:

other=/dev/hdb
label=xp
map-drive = 0x82
to 0x80
map-drive = 0x80
to 0x82

in your /etc/lilo.conf

and of course run lilo.

0x82 could be 0x81 if the drive is on the same cable as your first
drive. (ide1)
0x80 is on ide0 normally.

This immediately above assumes your linux drive is /dev/hda on ide0 as
master and your xp drive is /dev/hdb on ide1
if you are on ide2 then the bios number is 0x82

EC<:-}

ronis-REM0VE@ronispc-d0t-chem-d0t-mc...QUEBEC-IS.invalid

wrote:
> I'm setting up a Dell that came with windows XP installed on its hard
> drive. I've added another drive, configured to be the master, and
> changed the original drive to be the slave. I installed 10.1 on the
> new drive and had lilo self-install on the MBR of that drive. The
> install script recognized the windows partition on the original drive

ronis-REM0VE@ronispc-d0t-chem-d0t-mc...QUEBEC-IS.invalid

wrote:
> I'm setting up a Dell that came with windows XP installed on its hard
> drive. I've added another drive, configured to be the master, and
> changed the original drive to be the slave. I installed 10.1 on the
> new drive and had lilo self-install on the MBR of that drive. The
> install script recognized the windows partition on the original drive
> and added an entry for it (on /dev/hdb2 with table=/dev/hdb). While
> booting into Linux works exactly as expected (the original drive is
> also accessible), if I try to boot into the windows partition the
> system hangs. One exception to this behavior is when I set the boot
> flag on windows partition; now the system boots directly into windows,
> and I never see the LILO menu.
>
> Any suggestions?
>
> David
>
>
Hi!
NOT a lilo problem!
The MS-Glassware retains its install configuration and remembers that it
is "egoistic" only resident of your box residing on primary master drive
and on primary partition.
So in the usual Linux way lets teach it that WE tell the software who is
the boss.
Now to work:
You swapped the drives, so something has to tell XP what happened.
Lilo can do it, so can the BIOS. You can instruct a modern BIOS to boot
from various drives but it is "last resort".
The usual (at least for me) way is to utilise the flexibility that is in
lilo and cheat the software to believe that it is on primary master
drive. It is called mapping the drives. Assignments are:
Primary master = IDE0(hda) = 0x80
Primary slave = IDE1(hdb) = 0x81
Secondary master=IDE2(hdc) = 0x82
Secondary slave =IDE3(hdd) = 0x83

So in the stanza that calls your XP install you add
map-drive=0x81 to=0x80
map-drive=0x80 to=0x81

Assuming that the master slave change was on primary IDE.

And rerun lilo so this change is recorded in booting choices.

Have fun

Stanislaw
Slack user from Ulladulla.

On Mon, 14 Feb 2005 18:18:03 GMT, ronis-REM0VE@ronispc-d0t-chem-d0t-mc...QUEBEC-IS.invalid wrote:

> One exception to this behavior is when I set the boot
>flag on windows partition; now the system boots directly into windows,
>and I never see the LILO menu.
>
>Any suggestions?

You can boot linux from windows 'boot.ini' with the help of
bootpart tools (command line, I don't use it any more), but
trying the bootpart tools will confirm whether windows sees
itself - excerpt from my c:\boot.ini:

"default=multi(0)disk(0)rdisk(1)partition(1)\WINDO WS"

Perhaps that default= line and the matching control line need
adjusting?

I do dual boot windows differently, leave windows owning the
MBR and set a linux primary as active to get control at boot.

But there are many correct ways to dual boot, I found bootpart
useful some time ago, when I was more in the ms-dos mindset:

http://www.winimage.com/bootpart.htm

Cheers,
Grant.

I agree, if the Windows Drive is now the second or slave after the
Linux drive. The 'rdisk' (or is it the 'disk') needs to be bumped up
from 0 (zero) to 1 (one).

(All my dual-boot installations uses M$ boot loader to either go to
Windows or Linux. See the HOW-TO on the www.ldp.org for the dual boot
howto on this, if you are interested.)

HuMJohn

yes, my syntax was wrong. After the "to" is an "=" as below.

other=/dev/hdb
label=xp
map-drive = 0x82
to = 0x80
map-drive = 0x80
to = 0x82

If your cable is the same for both drives then change the 0x82 to 0x81.


EC<:-}

> in your /etc/lilo.conf
>
> and of course run lilo.
>
> wrote:
>
>> I'm setting up a Dell that came with windows XP installed on its hard
>> drive. I've added another drive, configured to be the master, and
>> changed the original drive to be the slave. I installed 10.1 on the
>> new drive and had lilo self-install on the MBR of that drive. The
>> install script recognized the windows partition on the original drive
>
>

In alt.os.linux.slackware ronis-REM0VE@ronispc-d0t-chem-d0t-mc...quebec-is.invalid wrote:

> I'm setting up a Dell that came with windows XP installed on its hard
> drive. I've added another drive, configured to be the master, and
> changed the original drive to be the slave. I installed 10.1 on the
> new drive and had lilo self-install on the MBR of that drive. The
> install script recognized the windows partition on the original drive
> and added an entry for it (on /dev/hdb2 with table=/dev/hdb). While
> booting into Linux works exactly as expected (the original drive is
> also accessible), if I try to boot into the windows partition the
> system hangs. One exception to this behavior is when I set the boot
> flag on windows partition; now the system boots directly into windows,
> and I never see the LILO menu.
>
> Any suggestions?

The suggestions about map-drive worked; however, the same is
accomplished with the boot-as option. I simply added:

boot-as = 0x80

to the windows section of lilo.conf and voila. Thank's for all the help.


David

Congratulations! You are the first person this thread to actually be
helped in the last ten years!

For that signal honour you are required to contribute to the Linux
Widows and Orphan's Fund. The fund, established in 1972, takes care of
providing the small amount of bread and the few bottles of bitter,
putrid water, heavily contaminated by fermented grains, for the
underprivileged Linux Admins, Programmer's and Users. Some Linux people
are down to a scant dozen of these malt and barley contaminated water
bottles. It doesn't sound like much, but for just a few pennies per day
you can be of infinite help. You can provide a Linux user, stranded in
these hostile parched deserts without even any Windows in their mud hut
to look out of, a half dozen extra bottles of barley water for as little
as 10 dollars a week. A godsend in these desperate parts of the world.

Send 50 dollars to the return email address by pay-pal and we will make
sure the money finds its way to the proper places.

EC<:-}

> In alt.os.linux.slackware ronis-REM0VE@ronispc-d0t-chem-d0t-mc...quebec-is.invalid wrote:
>
>
>>I'm setting up a Dell that came with windows XP installed on its hard
>>drive. I've added another drive, configured to be the master, and
>>changed the original drive to be the slave. I installed 10.1 on the
>>new drive and had lilo self-install on the MBR of that drive. The

> The suggestions about map-drive worked; however, the same is
> accomplished with the boot-as option. I simply added:
>
> boot-as = 0x80
> to the windows section of lilo.conf and voila. Thank's for all the help.
> David

ronis-REM0VE@ronispc-d0t-chem-d0t-mc...QUEBEC-IS.invalid

wrote:

> The suggestions about map-drive worked; however, the same is
> accomplished with the boot-as option. I simply added:
>
> boot-as = 0x80
>
> to the windows section of lilo.conf and voila. Thank's for all the help.
>
>
> David

Good god!

So sending someone to "man" page is actually efficient.
And I believed that it is some kind of offence in this "point and click"
age.

Have fun

Stanislaw
Slack user from Ulladulla