I need help installing Suse Linux 9.1

[EnDaRi]

ok, so im getting the NTLDR missing error

but im thinking that I need a boot disk to bypass this.

I got my suse linux 9.1 on CD and have a floppy to make a boot disk.

The instructions for installation are:

Preparation

o booting from CD

Download the iso image boot/boot.iso and burn a CD with it.

o booting from floppy

Download the floppy disk image boot/bootdisk as well as the module disk
image files you need (at least boot/modules1 and likely the network
modules from boot/modules3).

Write the images to floppy disks using the 'dd' command:

dd if=[path_to_image] of=/dev/fd0 bs=36b

On non-linux systems, use the rawrite utility from the dosutils/rawrite
directory (rawrite.exe).

Installation

Boot from CD/floppy and at the bootpromt enter the installation source:

linux26 install=ftp://ftp_server/directory

Remember to substitute 'ftp_server' and 'directory' with the appropriate
values (e.g. install=ftp://[IP-ADDRESS]/pub/suse/i386/9.1 if you're
installing from the SUSE ftp server).

Alternatively, choose 'manual installation' and configure the network in
the installation program.

Could someone please interpret this giving step by step instructions to make the boot disk?

I have had no prior experience using boot disks...

 

[smeager]

NTLDR is the bootloader for Microsoft Windows. While you installed SuSE 9.1 did you configure the bootloader for it to be on the first sector of the drive (bootloader being LILO or GRUB) If not that is what you will have to do and the easiest way I know how to do it is to go through the installation process again and configure it that way.

 

[earthman]

Sounds like you didn't install GRUB. Just run the installation again and do the boot loader install again. You don't have to reinstall the system.

 

[EnDaRi]

this may sound noobish, but how do i install grub?

if i need to put it on a floppy, how do i do that?

 

[EnDaRi]

Nvm, I installed it correctly... Turns out it was a bad PC133 SDRAM stick.

 

[Kasper4christ]

odd that a peice of RAM was causing a HDD problem...
with computers, anything goes...