Xref: utzoo comp.binaries.ibm.pc.d:237 rec.games.hack:2527 comp.sys.ibm.pc:15532 Path: utzoo!attcan!uunet!husc6!bbn!rochester!ritcv!ritcsh!dani From: dani@ritcsh.UUCP (Dani Kadoch) Newsgroups: comp.binaries.ibm.pc.d,rec.games.hack,comp.sys.ibm.pc Subject: Re: Good version of PC NetHack 2.2 at simtel20 Summary: How to access it thru BITNET Message-ID: <2336@ritcsh.UUCP> Date: 13 May 88 15:52:22 GMT References: <1741@silver.bacs.indiana.edu> Reply-To: dani@ritcsh.UUCP (Dani Kadoch) Organization: Computer Science House @ RIT, Rochester, NY Lines: 104 In article <1741@silver.bacs.indiana.edu> creps@silver (Steve Creps) writes: > I understand that simtel20.arpa is also accesible from bitnet through >LISTSERV@RPICICGE.BITNET, but don't ask me how; I don't know. The following is a copy of instructions I received a little while ago: Selected portions of the SIMTEL20 public domain software archives are available via a file server at RPICICGE.BITNET. At present the collections include the following directories: PD1: -- The Info-CPM archive (CP/M machines) PD1: -- The SIG/M User Group archive (CP/M machines) PD1: -- The Miscellaneous archives PD1: -- The IBM-PC/MSDOS archives PD1: -- The PC-Blue User Group archive (MSDOS machines) Planned: PD1: -- The CP/M User Group archive. The way all this works is by sending a mail message with a list of commands to a user called LISTSERV at RPICICGE. The two basic commands have the following form: /PDGET simtel.filename < ( encoding > /PDDIR simtel.pattern The <...> mark things that are optional. * "simtel.filename" specifies the name of a file to be delivered to the user. Names are usually of the form "PD1:name.type" * "simtel.pattern" specifies a search pattern used in generating a directory listing. The form of the pattern is like the filename mentioned above, but asterisks (*) may be used freely in the subdir, name, and type parts as wild cards (but not in the dir field.) * "format" specifies the method of transmission to be used: NETDATA -- suitable for transfer to Bitnet hosts that can accept files in IBM Netdata format. PUNCH -- suitable for transfer to Bitnet hosts that can accept files but cannot decode the Netdata format. Files are sent as 80-byte card-images. MAIL -- suitable for transfer to hosts that can accept only mail or are accessible to Bitnet only through gateways. Large files sent via mail are split into several smaller files that the recipient must reassemble. If the format is omitted, NETDATA is assumed for Bitnet hosts and MAIL for all others. * "encoding" specifies any special encoding of the file data: ASIS -- suitable for hosts that can receive binary data. The file is sent exactly as it is stored on RPICICGE: CP/M sector images, binary mostly. ASIS may be used only with format NETDATA. UUENCODE -- suitable for hosts that cannot receive binary data. The file is sent uuencoded. TRANSLATE -- suitable for any host, but only when the file actually represents readable text. The file is translated into character data format. If the encoding is omitted, files are sent ASIS if the transmission format is NETDATA, and UUENCODEd otherwise. /PDDIR Examples: ================ (1) The user is looking for the ARC programs. /PDDIR PD1:ARC*.* (2) The user wants a listing of the full MSDOS collection. /PDDIR PD1: /PDGET Examples: ================ In each of the following examples the user wants the -FILES.DOC file to examine on his host and the PKX35A35.EXE file to download to his micro, both from the MSDOS collection. Note that none of the examples have a closing parenthesis! (1) The user is on an IBM host directly connected to Bitnet: /PDGET NETDATA PD1:-FILES.DOC (TRANSLATE /PDGET NETDATA PD1:PKX35A35.EXE (2) The user is on a non-IBM host directly connected to Bitnet and can receive Netdata files: /PDGET NETDATA PD1:-FILES.DOC (TRANSLATE /PDGET NETDATA PD1:PKX35A35.EXE (UUE (3) The user is on a non-IBM host directly connected to Bitnet and can receive punch files: /PDGET PUNCH PD1:-FILES.DOC (TRANSLATE /PDGET PUNCH PD1:PKX35A35.EXE (UUE (4) The user is on some host somewhere: /PDGET MAIL PD1:-FILES.DOC (TRANSLATE /PDGET MAIL PD1:PKX35A35.EXE (UUE You may also want to send a "HELP" request, which will cause LISTSERV to mail you a copy of its list of commands, with brief explanations. -- +/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/+ > Dani Kadoch @ Computer Science House @ Rochester Institute of Technology < > UUCP: {allegra,seismo}!rochester!ritcv!ritcsh!dani BITNET: dnk8842@ritvax < +\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\+