Re: installation problems

"Andreas K. Foerster" <[email protected]>
Newsgroups gmane.os.freedos.devel
Message-ID <[email protected]>
On Tue, Oct 29, 2002 at 01:51:50PM -0500, Bart Oldeman wrote:

> On Tue, 29 Oct 2002, Andreas K. Foerster wrote:
> 
> > Is it possible to boot FreeDOS from the second harddisk?
> 
> yes, but it will read config.sys from C:\

Hmm... :-\

> > 1. to boot from floppy and enter "sys a: d:" and put the following into
> > the lilo.conf:
> > other = /dev/hdb1
> >   label=FreeDOS
> 
> What happens? Apart from "it doesn't work"?

It sais "ROOT FAT KERNEL GO!" and then reboots.

On my first tries it just said "ROOT FAT" and then hung -
but I can't remember what was different then.

BTW. the trick with swapping the drives works with Win95. Some time ago
I had my Win on the second drive and it worked!
Pity that it doesn't work with FreeDOS.

> You could also try to boot from C: without damaging your Win95
> installation, as follows:
> sys a: c: bootsect.fd
> this will not overwrite your boot sector on C: but create a boot sector
> file (see also sys /?).
> 
> Then copy bootsect.fd to /boot in Linux and use
> 
> other = /dev/hda3
> 	loader=/boot/bootsect.fd
> 	Label=FreeDOS
> 
> Rerun lilo and try again. Use fdconfig.sys if you want a different
> config.sys than the one used for Win95.

Thanks, but it is not quite correct, as you wrote it. 
The keyword "loader" is for the chain-loader, not for the boot image.

I fiddled around with it and found a surprising solution...
Ty syntax for lilo is simply:

other = /boot/bootsect.fd
      Label=FreeDOS

Yes, you really needn't mention the drive at all! It's all in the file. 
Now it works! :-)

It's even not important to copy it to the Linux partition, it just has
to be mounted somewhere, while you install lilo.


P.S.:
Would be nice if one could boot FreeDOS from a deliberate drive in the
future, and if it seeks the config.sys on the drive, it is loaded from.

-- 
Tschuess
	Andreas
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.