RICK@QUCDNEE.BITNET (Rick Pim) (09/29/90)
earlier this week, a friend of mine tried to install the software distillery's serial port network (v2.4) with dnet (v 2.10.11? i think so) between a 2000 running 1.3 and a 3000 running 2.0. the sernet documentation indicates that it functions under 2.0. as near as we can tell, everything was installed in the correct places, everything necessary was mounted. clearly we were wrong: if we did a "dir net:", then an icon labelled "Network" would appear. a workbench 'info' would indicate that "Network:" was validating, while a CLI 'info' would indicate "no disk in drive". this held true on both the 2000 and 3000. attempting to access anything within NET: would guru the 2000 or hang the 3000. is there anything subtle about the sernet installation that we're missing? everything in the doc file looked pretty straightforward, but obviously we missed something.... =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rick Pim bitnet:rick@qucdnee Department of Electrical Engineering rick@qucdnee.ee.queensu.ca Queen's University, Kingston (bitnet:rick@qucdnast) (613) 545-6772 (rick@bill.phy.queensu.ca) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "What are your general areas of interests?" "Aerodynamics. Designer jeans. Roofing supplies. That sort of thing." "What sort of thing?" "You know, liquidity. Point-of-sale. Margin accounts. Fast lane."
walker@unx.sas.com (Doug Walker) (10/02/90)
In article <9009282141.AA17340@lilac.berkeley.edu> RICK@QUCDNEE.BITNET (Rick Pim) writes: >earlier this week, a friend of mine tried to install the software >distillery's serial port network (v2.4) with dnet (v 2.10.11? i think >so) between a 2000 running 1.3 and a 3000 running 2.0. the sernet >documentation indicates that it functions under 2.0. > >as near as we can tell, everything was installed in the correct >places, everything necessary was mounted. clearly we were wrong: > It sounds like either your DNET connection is not working, or NET: can't find the server. When you start DNET, a little window should appear on the workbench screen. If you type into the window, you should see the characters on the other Amiga's DNET window. If you don't see the characters, you don't have a good DNET connection. If you do see the characters, select START DNET from the menu. Both windows should go away. Try using a PUTFILES command now to put a file to the ram disk on the remote machine: PUTFILES -dram: filename If this works, you have an active DNET connection. Next, make sure there is an entry in the S:DNET.SERVERS file for NET:. (This is on the machine you are NOT mounting NET: on). The path for the server should be the path of whereever you put netdnet-server. Then mount NET: and refer to it - it should hit the disk on the remote side to load the server. ***** =*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 = *|. o.| || | o |// For all you do, this bug's for you! ====== usenet: ...mcnc!rti!sas!walker plink: dwalker bix: djwalker