Access! Registration?
5 messages in this thread
Keith: In another thread (and, I think, another forum), somebody mentioned
to somebody else (her great-aunt's father's hairdresser's plumber, I think
🙂 that that person should talk to you and try to get you to release your
custom version of "AUX:" to shareware. I'm just being nosy, and wondering
what you've done to "AUX:"…I have a semi-professional interest (working
on a project that could use an AUX: with more features)…might you
elaborate on how you've modified it?
Actually, what I had done was take the PD aux: driver (I don't recall
off-hand who wrote/modified it) and made some changes to it to… 1) open
the serial port in SHARED mode. 2) have it _not_ send out a read-request
(or write-request for that matter) until it needed to. When 1.3 came out,
they changed the official AUX: to open the device in SHARED mode, but it
still sends out a read-request (of course, for the intended purpose, it
needs to… so it can accept in-comming data). What I wanted to use it for
was mostly outgoing re-direction, so I didn't want the read-request sent
out. (I was using it for things like 1> type >aux: dh0:docfile ). The
code I started with is here in AmigaTech in lib 9 if you're interested (I
think it's "AUX1A.ARC" ).
Did I understand what you said? Here's what I do. Don't scream. 🙂 I
have a BBS program running on my PC, connected to the modem, on my second
phone line. I have a serial cable between my A2000 and the second serial
port on the AT. The BBS can "link" the two machines such that everything I
type at a remote computer will be transfered to the Amiga. So I say
"newwsh aux:" to access both the Amiga and the PC. But I'd like to be able
to transfer a file from the Amiga to the remote computer, via a CLI-based
Amiga terminal program that would use the current console window (aka AUX:)
instead of the serial port. (This would be fine with the PC side, it is
absolutely transparent…) So what do I need to do this?
Use the RM Function to read
these messages.