🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.amiga.networking
4 messages
4 total messages Started by MushyPea Wed, 17 Apr 1996 22:54
Parnet problems
#227
Author: MushyPea
Date: Wed, 17 Apr 1996 22:54
25 lines
1755 bytes
Hiya, everybody,

I have an A1200 and an A500, and am trying to link them via parnet.
I've installed, and re-installed the parnet software several times, I've
checked and double-checked the cable several times - hey, I've even read the
documentation! ;)  But, it still doesn't work. :(

First I run netpnet-server on one machine, and then on the other (taking care
to use the opposite number for the unit as the one that is in the parnet
mountlist entry.  Then I mount the NET: device on both machines.  So far so
good.  I type CD NET: on one machine, and the Network disk icon appears, and
the current directory becomes NET:.  I do the same on the other machine, the
same happens.  So, feeling adventurous, I try a CD NET:RAM/ on one of the
machines.  At this point, the shell appears to stop responding to the
system... the CD command does not return, and CTRL-C does not work.  I've
tried using different commands, eg. dir or copy, and I get the same result. 
A dead shell, with CTRL-C being ignored.

Help!  Any ideas?

-- 
MushyPea/EtCetera (Ian Marsh) [680x0 coder, musician]      ___MMM___
Email: MushyPea@etchq.demon.co.uk (EtCetera HQ)              (O O)
-WWW-: http://www.cus.umist.ac.uk/~mushypea/          ---oOO--(_)--OOo---
A1200-030 10Mb SCSI2 700MbHD 3xCD 28800Vfc PGPv2.6ui
Re: Parnet problems
#228
Author: Ian Stonelake
Date: Thu, 18 Apr 1996 23:58
21 lines
1762 bytes
MushyPea (MushyPea@etchq.demon.co.uk) wrote:
>First I run netpnet-server on one machine, and then on the other (taking care
>to use the opposite number for the unit as the one that is in the parnet
>mountlist entry.  Then I mount the NET: device on both machines.  So far so

This maybe an obvious question but I presume you are running netpnet-server
with different unit numbers on each machine? ie netpnet-server UNIT 0 and 
UNIT=1 in the mountlist entry and vice versa on the other machine.

>good.  I type CD NET: on one machine, and the Network disk icon appears, and
>the current directory becomes NET:.  I do the same on the other machine, the
>same happens.  So, feeling adventurous, I try a CD NET:RAM/ on one of the
>machines.  At this point, the shell appears to stop responding to the
>system... the CD command does not return, and CTRL-C does not work.  I've
>tried using different commands, eg. dir or copy, and I get the same result. 
>A dead shell, with CTRL-C being ignored.

If it's still failing you must either have corrupt software or a faulty 
parallel port.
-- 
Ian Stonelake - ian@uncanny.demon.co.uk (Workers' Fight)
Re: Parnet problems
#230
Author: Geoff Taylor
Date: Fri, 19 Apr 1996 15:38
40 lines
2183 bytes
Dear MushyPea...

I know the feeling!! Been there.

I have my A3000 and trust old A500 linked with parnet so I can access an A570 CD drive 
on the A500. I must have spent six months trying to find fault with the parnet cables 
and software setup.

In my case it was the CIA chips (8520) in both machines which were at fault.
These chips are used to control a variety of functions, including the parallel port
and they are notoriously easy to 'fry', particularly if you use a variety of 
periferals connected to the parallel port. (My VidiAmiga killed the CIAs when used 
with a port switching box- it was supposed to be a break before make switch!)
You may find that a printer connected to the port will work fine, but parnet will not.

They are available quite cheaply and replacing them is quite straightforward.

I hope this gives you an avenue to pursue (:>) 


MushyPea wrote:
> 
> Hiya, everybody,
> 
> I have an A1200 and an A500, and am trying to link them via parnet.
> I've installed, and re-installed the parnet software several times, I've
> checked and double-checked the cable several times - hey, I've even read the
> documentation! ;)  But, it still doesn't work. :(

> 
> Help!  Any ideas?

-- 
Regards                        "May the groundtruth be with you"
Geoff Taylor                   (motto of the Aus Globe Program)
====================================================================
Science Department          Web:  http://vianet.net.au/~carinehs
Carine Senior High School     	        
Western Australia             		
====================================================================
Re: Parnet problems
#229
Author: MushyPea
Date: Fri, 19 Apr 1996 19:31
32 lines
1839 bytes
On Thu, 18 Apr 96 at 23:58:59, Ian Stonelake wrote:

IS> MushyPea (MushyPea@etchq.demon.co.uk) wrote:
IS> >First I run netpnet-server on one machine, and then on the other
IS> >Then I mount the NET: device on both machines.
IS> This maybe an obvious question but I presume you are running netpnet-server
IS> with different unit numbers on each machine? ie netpnet-server UNIT 0 and 
IS> UNIT=1 in the mountlist entry and vice versa on the other machine.

Yes, I've checked that several times.  netpnet-server is run with the
opposite unit number to the one in the mountlist.  On both machines.

IS> If it's still failing you must either have corrupt software or a faulty 
IS> parallel port.

That's what I thought - although I have used ParNET from three different
sources (two CD-ROMs and AmiNet download), and both machines print with no
problems...

Frankly, I'm baffled.

And I've checked and re-checked the cable (with a multimeter) and all the
appropriate pins are connected.

Argh!  Help!

Ian.
-- 
MushyPea/EtCetera (Ian Marsh) [680x0 coder, musician]      ___MMM___
Email: MushyPea@etchq.demon.co.uk (EtCetera HQ)              (O O)
-WWW-: http://www.cus.umist.ac.uk/~mushypea/          ---oOO--(_)--OOo---
A1200-030 10Mb SCSI2 700MbHD 3xCD 28800Vfc PGPv2.6ui
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads