CompuServe Thread

Enforcer Help

14 messages in this thread
#43135From: Wayne ColeOct 16, 1994 12:04 AM
I have two Amiga 2000's connected together by a PArnet cable. One end is connected at the Amiga parallele port, the other at port0 of a MulitFace II card. If I'm running enforcer in the Amiga with the cable at the Amiga par port, and I use the enforcer that writes to that port, how do I get the output at the other end into a file to read later? wmc – via Autopilot!
#43156From: SyndesisOct 16, 1994 2:43 PM
I don't recall any terminal programs that can use the parallel port… but you could always use Enforcer output through the serial port, and easily capture that on the other side. For that matter, I think there's even a way to divert the Enforcer output to a terminal program running on the same machine, but I can't remember how that's done. I use Enforcer through the serial port connected to a PC running a telecom program.
#43165From: Wayne ColeOct 17, 1994 2:32 AM
John, I figured I could do it that way, but since I already had a PARNet between the two I thought I'd try to use the existing cable (laziness is the mother of invention…) wmc – via Autopilot!
#43176From: SyndesisOct 17, 1994 7:56 PM
Did you check the Enforcer docs? There must've been something like this available, I do have a vague memory that it's possible. We just need to find how to receive the parallel data on the receiving end.
#43182From: Wayne ColeOct 18, 1994 2:27 AM
John, There is an icon set up to run enforcer with output directed to the par port. But the docs say nothing about how to get the data off the other end. Wonder if it's as simple as "Copy PAR: filename" or something like that… NAW – tooo easy… wmc – via Autopilot!
#43184From: SyndesisOct 18, 1994 8:49 AM
I'm sure some people simply dumped the output to a printer. I know I couldn't debug that way, but to each his own… Tricks like CMD of course would only keep the data on the machine you were debugging. What, you have all your serial ports tied up?
#43188From: Werner KazmierzakOct 18, 1994 5:49 PM
John, sure people do send the output to a printer. I did it every time I had to debug programs which make use of the internal serial device… 🙂 – wkc – … via AP from Hamburg, Germany
#43232From: Wayne ColeOct 19, 1994 5:46 AM
Amilink, PSFC, External TBC with software control, and a modem – ties up a few serial ports… :^} wmc – via Autopilot!
#43236From: SyndesisOct 19, 1994 10:02 AM
I have several switch boxes in sequence to help select between four devices…
#43279From: Wayne ColeOct 20, 1994 2:41 AM
I tried adding one in at the video deck end of the AmiLink and PSFC cables, but they didn't like that (probably not enough isolation for RS 422…) wmc – via Autopilot!
#43197From: ShraddhanOct 18, 1994 6:11 PM
Wayne, Usually when I run Enforcer, I direct its output to a file in a recoverable RAM drive. I use Richard Waspe's Stat-RAM which seems to survive even the worst crashes. Regards, Shraddhan (via AP from Hertfordshire, England)
#43233From: Wayne ColeOct 19, 1994 5:46 AM
I'll be on the lookout for it – thanks wmc – via Autopilot!
#43160From: Nevil UnderwoodOct 16, 1994 5:21 PM
Wayne, how about dumping the parallel output straight to a printer? I run enforcer and NComm set to ASCII capture. With the enforcer output set to serial the data is bounced off the modem (full duplex) to a file of my choosing. This is a long shot because I think it will only work for writes but would CMD par: dh0:myfile (or similar) work? Hope this helps. Nev.
#43166From: Wayne ColeOct 17, 1994 2:32 AM
I'm trying to get the output remotely as the crash locks the host machine in a screen that I can't tell if anything is goin' on and seems to happen alot on HD access. Remote output will hopefully tell me whats going on when the 'local' writes to a file can't happen. wmc – via Autopilot!