> 
> I am still having probs with my modem and NetBSD 1.3, but I don't think
> they are as easily solvable as getting a new script.
> Correct me if I'm wrong, but if my modem's /dev/tty00, this command should
> reset the line:
> echo atz^M > /dev/tty00
> (the ^M for the return)
> 
> Yes, I know it should, because it does.  However, if I would do this
> command 5 times in a row, (or, say, five "ath0^M") only every other one
> would go through.  This seems to be part of the problem.  The other problem
> is that _every_ time I try an atdt command, it will _not_ go through.
> Example:
> echo atdt123456789^M > /dev/tty00
> This should pick up and dial 123456789, but the modem is not touched.  In
> fact, the command will stall NetBSD only to be fixed by ^C.

No, that won't actually pick up and dial the phone.

The problem is that, by default, tty's look for carrier detect before
outputting data. The modem's probably not asserting DCD, so things will
hang.

Unfortunatly the UNIX device system isn't terribly friendly toward direct
access of the serial ports. :-(

To do what you're trying, I'd suggest running dt. In one window type
"cat /dev/tty00" In another window, type "stty -f /dev/tty00 clocal".
The latter command will disable the "wait for carrier" attribute. The
first command will keep the tty open so settings will stick (they get
reset to the defaults  when the tty goes from closed to open).

Now in this other screen, type all the echo > /dev/tty00 stuff you
want, and it should work right.

You don't need dt, but the cat might get messy.

Also, you can change baud rates with the stty command above.

> This may be related to the problem with pppd, in which pppd turns off
> promptly after running a script.  The command:
> /etc/ppp/ppp-up
> used to work (once, at least :), and start up pppd, which would remain
> active.  using the command
> ps -xua
> you could see pppd working.  However, when I run the /etc/ppp/ppp-up script
> now (unchanged), there is no pppd to be found.  I believe this is very
> likely because of the prob w/
> echo atdt* ^M > /dev/tty00
> Any help on the matter? Please private email to picasso@centuryinter.net

?? You're saying /etc/ppp/ppp-up used to work and now doesn't? Sounds like
a file got messed up. Didn't you have a lot of file system damage once?
Boot single-user and fsck the root partition (fsck -f /) and make sure
everything's ok. Then rebuild devices, and re-install the ppp kit after
saving your chat script. I had similar problems once when I had a sick fs;
pppd would fail silently. You might also have to re-install /usr/sbin/pppd.

> On a further note, my LC520 (68030, 25mhz) seems to be far too slow to
> compile programs.. On compiling ircII, everything went fine in the hour
> that it took.  When I tried compiling other programs, however, things did
> not run smoothly and I got many errors.  I don't have the time/energy to
> compile everything for myself on NetBSD, so I was wondering if there are
> any other more compatible UNIX's out there that will run on my LC520 68030.
> I know this is a bad question for this list, and I do appreciate all the
> help everyone's been, and how great it was the NetBSD actually ran on my
> computer, but I may need something else.

Compatable with what? And hey, you're mac's faster than mine (unless you
have 16-bit memory). I have a IIsi (20 MHz 030)!

What didn't compile?

You should check out both:

1) the NetBSD-amiga archives. There's a mirror on ftp.netbsd.org. This
site conatins a LOT of pre-compiled programs.

2) the pkgsrc system. It's an adaptation of the FreeBSD ports collection,
where folks have supplied sets of patches for outside binaries. You have the
pkgsrc on your computer, and type "make" in the right directory. The
computer will then make sure you have the right version of the source,
even ftp ing it if needed, and then will compile it.

Compiling will still be slow, but it should work. :-)

You don't have much in the way of alternatives. A/UX is dead. There are some
under-MacOS UNIXies around, but I've not heard how they do. Linux-mac68k
seems to be alive, but I think we're farther ahead on having stuff work.
OpenBSD is around, too. But they aren't a choice if you want compiles-out-of
-the-box source as I think if it compiles for OpenBSD (and is user code)
it will probably (95% chance) compile for NetBSD. Said differently, if
it didn't compile for NetBSD, I think chances are slim it'd compile for
OpenBSD.

I really think NetBSD is still the best choice. But then I'm biased. :-)

Take care,

Bill