[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: Need help installing RH7.0 on 486 w/ Orchid SW32



Title: RE: Need help installing RH7.0 on 486 w/ Orchid SW32

Reply in line with message:

<snip />
>
> Sorry, I was out sick, and didn't see this.

No problem, life and our vocations seem to have a way of interfering with our avocations.

> Boris Kortiak wrote:
>
> > There are two hard drives connected to the single ide
> controller on the mother
>
>
> Only one IDE connector on board? Uggh! 2 hard drives? do you need both?

Probably not, but I'd like to keep them both.

<snip />
> > Now, that's what I need.  Ok, so to make sure I've got this
> right.  Install RH
> > Linux on another PC.  Using the new install, look for a file called
> > "oldcdrom.img".  Where exactly do I find the non-ide
> drivers?  Is this in one of
> > the HOW-TO's?
>
>
> If you have a Linux machine, mount the cd, then:
> dd if=/mnt/cdrom/images/oldcdrom.img of=/dev/fd0
>
> If you have a windows/dos machine you can use rawrite
> to do it. rawrite.exe is in the dosutils directory
> on the cd along with usage instructions. The input file
> for rawrite is <CDDRIVE>:/images/oldcdrom.img

Ok, so I'm creating a boot disk using <CDDRIVE>:\images\oldcdrom.img?  Once I boot from this boot diskette, how do I select the appropriate driver from the CD?  Would it be easier to create a driver diskette on another machine and then use it when asked in the startup questions (3rd or 4th screen)?

> > This might be an option.  The only problem is that the HD
> is larger than the BIOS
> > supports (by 5-10 MB), what would happen when I install on
> a newer PC that has a
> > BIOS that will support the whole hard drive.
>
>
> So configure using CHS mode, not LBA on the other system.
> Make the first partition 5-10 MB, and mount it as /boot
> (should be a default mountpoint in the installer)
>
> When you put it back, only LILO/GRUB will use BIOS
> to access the disk, and it only needs to access the
> files in /boot. After that the kernel will access the
> rest of the disk on it's own, and work around the BIOS
> problems.

Wait a minute, since this will be a Linux only machine (no need to lilo, I think), does this mean I will be able to access the entire drive?  An added bonus to converting :)

<snip />

Thanks for all the help.  I am beginning to see the light.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]