have installed SUSE 9.2 on my computer but it need the installation CD for booting any time I want to work with my computer. Also, I should change the resolution in the first dialoge to 800*600 from 1024*768 otherwise the system will not boot. I should say that I had the same problem for installing the OP and I did the same to be able to install SUSE.
Another strange thing is that while automatically installing SUSE, my hard disk was named as /dev/hdc (instead of being /dev/hda).

Thank you for your cooperation and hope to hear from you soon.

For better analysis of your problems, please post the output of

fdisk -l
cat /boot/grub/menu.lst
cat /etc/grub.conf
cat /boot/device.map

(as root).
Resolution for your framebuffer (vga=) is changed in /boot/grub/menu.lst according to the following table:

These are the outputs of the mentioned commends.


salri:/home/salari # fdisk -l

Disk /dev/hdc: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 1 2550 20482843+ c W95 FAT32 (LBA)
/dev/hdc2 * 2551 9964 59552955 f W95 Ext'd (LBA)
/dev/hdc5 2551 5100 20482843+ b W95 FAT32
/dev/hdc6 5101 7650 20482843+ b W95 FAT32
/dev/hdc7 7771 9964 17623273+ 83 Linux
/dev/hdc8 7651 7713 506016 82 Linux swap / Solaris

Partition table entries are not in disk order
salri:/home/salari #

----------------------------

alri:/home/salari # cat /boot/grub/menu.lst
# Modified by YaST2. Last modification on Mon Aug 28 18:42:36 2006


color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,6)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 9.2
kernel (hd0,6)/boot/vmlinuz root=/dev/hdc7 vga=0x314 selinux=0 splash=silent resume=/dev/hdc8 desktop elevator=as showopts
initrd (hd0,6)/boot/initrd

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
root (hd0,0)
chainloader +1

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
root (fd0)
chainloader +1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 9.2
kernel (hd0,6)/boot/vmlinuz root=/dev/hdc7 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0 3
initrd (hd0,6)/boot/initrd

###Don't change this comment - YaST2 identifier: Original name: memtest86###
title Memory Test
kernel (hd0,6)/boot/memtest.bin
------------------------------------------
alri:/home/salari # cat /etc/grub.conf
root (hd0,6)
install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0) /boot/grub/stage2 0x8000 (hd0,6)/boot/grub/menu.lst
quit
salri:/home/salari #
---------------------------------------------
salri:/home/salari # cat/boot/device.map
bash: cat/boot/device.map: No such file or directory
-------------------
Hope to hear from you soon. Thank you in advance

It's a bit strange that your drive is detected as hdc. BTW: I gave you the wrong path to device.map. Have a look in /boot/grub/device.map. In this file, the drive should be mapped to a device, e.g. "(hd0) /dev/hdc". You could try changing this to /dev/hda. In this case you may need to change the root= entry in menu.lst as well.

But try another trick first: When the boot menu appears, open the grub command-line with (I think) F3 and type "ide=reverse", then boot from HDD.

I also recognised, that your extended partition is marked active. It could help to mark hdc1 as active (in case Windows doesn't boot properly).

I hope something helps.

My windows is working properly. I wonder if I change "/hdc" to "/hda", it would affect the windows performance and my data on HHD would not be lost.

It shouldn't affect windows, as this notation is not used by Windows nor the grub bootloader. But try the "ide=reverse" trick first. Since this is temporary, you won't break anything. To make it permanent (in case it helps), you need to add this option to menu.lst.

I didn't manage to overcome this problem when using GRUB boot loader. Finally I decided to use LILO and now SUSE boots. What are special for grub that i might miss using LILO?