ParNet and OS 3.0?
19 messages in this thread
I have been trying to use ParNet to access the HD's of my 500+ with
my A4000. I think that ParNet doesn't work on OS 3.0 or maybe I'm
just doing something wrong.
Does anyone have any experience with ParNet or is there a version
that works with 3.0?
— Quinten
Well, I have some experience with Parnet (since I wrote it, with
advice from John Toebes) – but I don't have any idea whether it
would work under OS 3.0. What are the symptoms?
–Doug
Actually it was my mistake. I omitted the UNIT keyword, thus both
amigas were trying to serve on the same unit. It works fine now.
I've got a suggestion though. It would be nice if there would be a
.backdrop on NET: so the drawer icons could be left out.
Thanks anyway,
— Quinten
Yes, that would be nice. Unfortunately, I don't have anyplace to
store a .backdrop file.
You can leave out the individual sub-drawers in NET:, though.
–Doug
Sorry to butt in here, but I've posted a note in the amigauser section wrt
parnet and wasn't able to get help, so maybe I could ask here???? What I
need to know is if parnet will support printer sharing as well as
file/program access. I have an A1000 and A3000 connected together.
Everything is working well wrt files, but I'd like to have the A1000 use
the printer attached to the A3000's serial port. Is there any way to do
this. Using type > net:pprt seems to work from the shell, but copy to
net:prt just hangs the A1000 system. I've also tried using CMD to capture
and redirect the printer output, but it says it can't get the printer
device and it doesn't like it at all when I say the printer is a serial
device. So… any ideas?? I need to have output from word processors,
spreadsheet programs, etc. (basically anything routed to prt: go accross
the network to the printer on the other machine). Oh, the operation of the
serial printer on the A3000 seems uneffected by the parnet network (which I
would expect). Thanks.
Hmmm… Let's see; you have a printer hooked up to the serial port
of an A3000 and parnet between the A3000 and the A1000, right?
You should be able to use CMD to capture the printer.device output
to a file, then
copy <file> net:ser
You don't want to use net:prt because that's the printer.device
level of access, and you've already let printer.device at your
stuff.
So the thing to do is to set up on the 1000 as a serial printer just
like on the 3000, but then use CMD to redirect printer output to
NET:SER. I *think* that will work, but it's stretching the design
of parnet a little bit, and I'm not 100% sure; please let me know
what happens when you try it.
–Doug
OK, will do. Thanks for the help. I should know by the weekend or so…
drt
Well, I set things up with both printers going to serial.device and CMD
redirecting output on the A1000 to net:ser. When I try a copy <file> to
prt:, an error window from CMD comes up saying that output is terminated
due to a CMD file error. (Sorry, no other details) If I directly try a copy
<file> to net:ser from the A1000, the shell window hangs — no crash, just
nothing happens and I need to reboot both machines to re-establish the
network.
Could this be due to SER: not being seen as the same sort of device as a
disk or an assign? I mean that in programs such as AmigaUtil, etc. when a
list of devices (volumes) is requested, SER: PAR: RAW: AUX: are not
included in the resulting list. Has PARNET been written to access only
certain types of devices?
Thanks for the help. drt
Well, I didn't write it to access SER:, but I had hoped that it would
work. Apparently not. More information for the files, I suppose…
–Doug
Any chance for a Christmas present enhancement??? Would enticements
help???
I can't do enhancements to parnet. I don't have the source
rights any more.
–Doug
> I don't have the source rights any more.
Doug, who would be good to contact about future directions for parnet?
Did you sell the package?
=Tom=
Sorry to hear that. Does this mean PARNET may be coming commercial?
One other bit of information that might help:
I use CMD to redirect printing to a file. Then I have a script file which
waits for that file to appear. It copies it somewhere else, then deletes
the printed file. The script uses a program called NOTIFY (AmigaDOS 2.0
specific) to wait on the file to appear. I have done the same thing in 1.3
using the IF EXISTS in a loop with a delay to only check for the file every
minute or so. Run that one from ram:.
Maybe if you redirect printing to a file and then COPY the file to the
net:ser printer. Or use a background script on the second machine to wait
for the file to be printed to appear.
-Jerry
Thanks for the info. I tried that, by running Notify and PSPOOL on my 3000
and CMD on the 1000, but apparently the PARNET handler does not use DOS to
create the files (or there's some other reason Notify couldn't see it)
because the appropriate spool files were created on the 3000, but the
spooler didn't pick them up. Oh well. Thanks for your help.
Doug: Do you know if Parnet will work with the 4000? I'm thinking of using
Parnet to go between the 4000 <–> 3000, using the 3000 as a server. Hey,
what better way to get a SCSI controller for the 4000 8^)
Sorry this reply took so long, you must have posted minutes after
my last login before my trip to Germany!
I have no idea if parnet will work on an A4000, but I have no reason
to believe that it WON'T work. It should work. If you try it,
let me know 8^)
–Doug
Yep, I did try Parnet on the 4000 and it worked beautifully. I was able to
easily transfer all the files on my 3000 over to my new toy a heck of a
lot faster than doing it by floppy backup. Since I did all that most of my
friends are setting up their own Parnet cables for the day they get their
1200's or 4000's 8^) I'm not using it now since I sold the 3000 and have a
SCSI controller in the 4000 but I want to thank you for the great program.
It sure saved me a lot of work!!
Good, glad it works. And now I know for the next person that asks…
–Doug