I don't know if this is a unique problem, but here goes.
In a laboratory here, we had Windows 3.1 and linux working together under
umsdos. Students could boot to either one, and the linux was used to run an
x-windows emulator, allowing remote computing over the internet, to a "foreign"
It took quite an effort (and some help from this group) to get this going, but
we did, several years ago.
Then, someone, presumably a student, trashed something, most likely by editing
a linux file under MSDOS (or Windows) and we lost the entire system.
I attempted all kinds of fixes, none of which worked, and so decided to
I have the new slackware 3.2 A1-9 disk set on the hard drive, scsinet.s and
umsdos.gz on floppies, and can boot OK, but when under setup the following
wierd behavior occurs:
1) if I choose TARGET, it asks about dev/hda1 and when I press ENTER, it
freezes up, and needs rebooting.
2)if I choose source, it rejects all attempts to enter /dos/slack or slack, or
/dev/hda1/slack when C:\slack is the directory off of which A1-9 are located.
It keeps requiring /mnt, and there is no help, no diagnostics, etc., to help me
figure out what I'm doing wrong.
Can someone help?
I finally erased the entire old c:\linux directory, so the system should be
clean, but I'm not understanding something.
Thanks in advance, and could you reply directly, since this group is hard to
monitor from the IBM mainframe which I have to use.
Thanks in advance.