two FSCKED-UPS

[Kurt Wall]

In a 1.2K blaze of typing glory, Bob wrote:
> Gentle Helpers, I have really screwed up, again.  First, I installed a Suse
> 9.0 on hda5&6.  Boot on 5 and root on 6, swap on 2.  I left 1 and 3 blank
> when I installed Suse 9.0 on 5, boot, 6.  I put a hdb on with Win98 on it to
> do my blood glucose meter program.  Every thing was going well until I
> installed RH 9.0 on 1 & 3 and grub on the MBR.  Now I can't get my Windoze
> to load or my Suse.  Can't even get my Suse to load using the CDROM..  What
> do I need to do to get back into my Suse?

Boot with the boot floppy you made during installation? Boot SUSE's
emergency mode from the CD-ROM?

> #2.  On my RH, something went haywire with my modem.  I've tried to get kppp
> "Settings" -> "Query Modem" to fix it, but I keep getting either, "The modem
> is busy" on ttyS1, S2.  On /dev/ttyS0 I get "The modem does not Respond",
> and on /dev/modem I get "Unable to open modem".  Seems like a couple of
> years ago I had this problem with one of the  Caldera, 1.3, 2.2, 2.3 or e2.4
> and I don't remember what I had to do?

Make sure /dev/modem points to the proper serial device:

$ ls -l /dev/modem

Look through dmesg's output to see which serial device(s) the kernel
detects during boot and make sure that the modem lives on a detected
serial port. 

Have a look at the setserial program. Perhaps your modem isn't configured
properly.

Kurt
-- 
Only presidents, editors, and people with tapeworms have the right to
use the editorial "we."