Serial port / Windows NT question
Mike Fink
I'm trying to port some PERL code from UNIX to Windows NT that makes use of
the cu
(UUCP) program. This application currently drives a (VT100) console
attached to another UNIX system.
Today, we run something like:
cu -ml tty0 > tty.log
and then look at tty.log to see what's being sent to the console. If we
want to write to the console, we simply print commands to /dev/tty0.
Unfortunately on WinNT, I can't do something similar (at least with the
default setup). In my fantasy world, I'd like to be able to run:
copy COM1 tty.log
echo "commands" > COM1
Since I can only do one of those operations at a time, it won't work real
well with our existing code.
As an alternative, I installed the CYGWIN software in hopes that the /dev
directory would give me similar functionality as our UNIX box. However,
after a vanilla install, no /dev directory was created.
If anyone knows how I could get the /dev directory to show up in CYGWIN or
knows of a utility that would accomplish what I'm trying to do...I'd
appreciate the help!
I've read the FAQ and other docs and haven't seen an explanation as to why
the /dev directory doesn't show and I have found some other utils like
Hyperterm and Kermit-95...however, I was hoping to find something a little
more primitive so we don't have to relearn another terminal scripting
language and pay a licensing fee.
Thanks!
Mike
If you want to respond to me directly, remove the NOSPAM from my email
address.
Mike Fink
FAQ and it said that if you do an ls on /dev you won't see anything, but
/dev/tty0 will show you a tty device. That worked, and I even compiled the
UUCP package and got cu to run in the CYGWIN environment...BUT I had to run
cu -l COM1 and I still couldn't echo anything to /dev/tty0 or COM1 :-(
-Mike
"Mike Fink" <mfink...@us.ibm.com> wrote in message
news:9r77n6$vig$1...@news.rchland.ibm.com...