Tried FreeDOS again, and DOS proved to be diagnositcally worthless, as it won't even see devices unless they're seen by the bios at boot time. To be fair, this motherboard also has the world's least cooperative bios I've ever used.
I'm going to try Gentoo linux (if I can figure out how to install in on the hard drive) because apparently linux's gunzip utility writes images, which *should* make life easier.
A weird thing though, I tried installing FreeBSD on the harddrive and booting that...but...it locked up when I tried to boot it on the firewall motherboard, it said something about my keyboard and then stopped booting. How can monowall boot but not freebsd? There's pleanty of ram...and the core is 366MHz, it's not like it can't handle a full BSD install...
So, FreeDOS was a bust...I'll get around to Gentoo today sometime....maybe try FreeBSD again if Gentoo doesn't work.....and then...NetBSD....
FreeDOS by the way, has been at it's V1.0 milestone release "final" phase for over a year now. Yet...the OS won't boot from a hard drive unless you type in "sys c:" after it tells you that the install was successful and all you need to do is reboot. If you Install the OS in full, and reboot, it just says "boot error" and gives *no* error message of value. How hard could it possibly have been for them to script "sys c:" into the OS installer? How do they expect recreational users to ever be able to use their software without error messages that actually tell you what's wrong? Ugh. I was convinced that my hard drive was actually unusable because of how FreeDOS reacted to....its own installer. I've done several scans of the drive since then and it's perfectly fine.
If anyone knows anything about the installation of these OSes, particularly Gentoo, please please PLEASE post info here...most tutorials I find either lie, or are out of date.
|