see bottom for update:

one thing at a time...

I can mount my Windows XP partition which also won't boot so I can recover data. Grub seems to work fine. I'm just not proficient in it yet.

we can fix that. what partition is xp on? mine is on hdb1 or in grub
speak (hd1,0) so I have in my menu.lst

title MS Windows XP
root (hd1,0)
savedefault
makeactive
chainloader +1

and that worked fine for me until i killed windows.
However, I did get aptitude to upgrade to its latest version 0.4.4 that Joey Hess mentioned in a previous post. I'm getting there but can still use helpful comments.

sometimes for big upgrades you have to run it multiple times to get it
through all the way. what exactly have you run so far? and did it run
to completion?
A


My system has exhibited weird behavior. It now boots into Windows. I can get to the Linux partition with the rescue mode of the original network installation CDROM for etch with kernel 2.6.15.

Also, the boot priority suddenly changed to the harddrive. I had to change the boot priority in the BIOS to boot from CDROM.

I had also looked at the system with the installation CDROM's for Windows XP Professional. I'm not aware that I told it to change anything; however, it may have 'volunteered quietly.'

Also, the ASUS CPU Parameter Recall (ASUS CPR), a feature of their AI motherboards, may have activated.

Oh well, I'm going to back up my Windows data and then be ready to repair the Debian GNU/Linux etch installation still on /dev/hda6.

I'm swearing off eggnog (except at Mother's) and grub-install to avoid ruining the MBR.

What can we do with the rescue mode of the installation beta2 CDROM?
I got an external harddrive to back up my data. The latest etch network install file (debian-testing-i386-netinst.iso) was downloaded and created. I booted off it and had it to erase the contents of /dev/hda6 when the basic system install aborted. Fortunately I had no data worth keeping, just a few game scores. It was necessary to use adduser as root to get an ordinary user account. The installer also reinstalled grub correctly and updated it correctly when the system downloaded updates. The update also gave me the 2.6.18 kernel in addition to the 2.6.17 kernel on the installation CDROM. (I got the smp kernel I wanted to make use of the Pentium 4 Prescott hyperthreading.) The desktop is GNOME. The network install CDROM seems to set that up by default. I may get KDE when it seems safe.

So the worse problem was solved by 'cutting the Gordian knot' with a reinstallation.

   My thanks to Sackville and others that responded!




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to