SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
You need to let people know the partition scheme of your hard disk which is obtainable in Suse by typing
at command prompt after log in as root first (or type su followed by root password)
Then to repair the booting copy and paste your
here. It is the menu for Grub to control your booting.
If you did not have a partition scheme before Sue installation then you could have instruct Suse to overwrite the FAT and NTFS partitions. However if Suse has picked out Windows 1 and 2 that means it had left these two partitions alone.
No command.com means Suse was booting a unbootable drive, a D holding data only. That is all.
You must know what partitions and space in your hard disks before doing any multi-boot. Suse can be made to boot 50 systems if you wish but it you who must arrange which system to go to which partition.
Have an idea about what inside the hard disk is a necessary start.
You have hda1 marked hidden. This is OK possibly left by Grub since the last booting attempt. Grub hides hda1 in order to boot your hda2 into a "C" drive. That is all.
Since you have 2 Windows my guess is that you may be using XP to dual boot the other. If this is the case then it may make one of the Windows more difficult to boot.
I know you are using a notebook. Can't you confirm if it has a bootable floppy drive before I give you the instructions?
It is important for you to understand that
(1) All your data is safe as long as you donot format any of the partitions.
(2) Your original Windows booting system can be reinstated by unhiding hda1 and restore the MBR. The former is achieved by using Suse's cfdisk command at terminal mode as root and the latter is achieved by a bootable DOS floppy (with fdisk.exe inside) or XP's installation CD.
(3) Suse can be booted up any time if you have a floppy drive to make a bootable Grub floppy. No floppy then you need to get hold of a copy of Linux rescue CD or just use Suse's installation CD.
Let us know if there is a floppy drive that boots in your notebook.
Regarding the access to /boot/grub/menu.lst you need to log in as root in order to have the privilege to change the system files. /boot/grub/menu.lst is just a text file containing the instructions for Grub to boot your system. It would have the following entries for your hda1 and hda2
title windows 1
title windows 2
The hide instruction prevents the BIOS from booting hda1 when you want hda2. Makeactive is to make your root directory bootable. Grub counts from 0 and so hda1=(hd0,0) and hda2=(hd0,1)
Your booting problem lies most likely with the XP dualing boot if you do have two Windows operating.
i don t have a floppy drive but i think i can boot with my usb drive.
i am using a notebook and i only have one windows which is XP
i do not know why suse think i have two windows.
btw chosing winddos 1 will see win 98s start up logo for one sec befor that command.com error messeage comes up in DOS.
i had a look at this, will this solve my problem?
i notice that it is for ver.9.1 not ver.9.3
I think I might know the root cause of your problem. If you claim you have only one Windows then the first partition hda1 could have been left there by someone else or youself in the past. It sounds like a dual boot system to me because of the short Win98 display.
What could have happened is Suse did not know it and tried to boot either. It does this by hiding hda1 when boot hda2 and vice versa. Windows own dual-boot method requires both hda1 and hda2 to be unhided. Therefore Suse fails to boot your Windows because one of the partition is always hidden in order to allow the booting your Windows into a "C" drive.
Now the fix
List your /boot/grub/menu.lst and /boot/grub/device.map here
You can try to takout one of the Window booting options and concentrate on having the following lines in the remaining booting choice for Windows
The above lines mean unhide both hda1 and hda2, regard hda1 as the root partition (for mounting the filing system) no need to verify if it is a Linux partition or not, chain-load its boot loader into memory starting from the 2nd sector (+1 position).
Ah, I was thinking Ubuntu when you said you can't log in as root user.
Yes it is a pain the the arxe but for Suse you should be able to log in as root before starting the desktop. However it is also possible in different distributions the un-paid versions may have less root access to the desktop. You can certainly view and edit the files in terminal mode.
So just click terminal mode at the desktop, type su and then the password for root. To edit file /boot/grub/menu.lst you type
and will be able to do whatever you want. I just tried it myself in Suse 10.