Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!sdics!hartung
From: hartung@sdics.ucsd.EDU (Jeff Hartung)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Need general info
Message-ID: <625@sdics.ucsd.EDU>
Date: 2 Sep 88 03:37:49 GMT
References: <2514@mtuxo.att.com> <5193@pasteur.Berkeley.EDU> <3091@ttidca.TTI.COM>
Reply-To: hartung@sdics.UUCP (Jeff Hartung)
Distribution: comp.binaries.ibm.pc.d
Organization: U.C. San Diego, Institute for Cognitive Science
Lines: 22

In article <3091@ttidca.TTI.COM> svirsky@ttidcc.tti.com (William Svirsky) writes:
>In article <5193@pasteur.Berkeley.EDU> e299-an@sim.UUCP (David Egert) writes:
>+3) I downloaded haunted.arc using xmodem to send text.  
>
>An .arc file is a *binary* file.  Use xmodem/binary to download it to your PC.
>

I uudecoded haunted on a vax under 4.3BSD then used c-kermit on the vax
(remote), remembering to "set file type binary" and ms-kermit on an
ibm-pc, making sure that the parity was off, and transfered the files
to the PC.  Although every other file I've tried this on comes through
fine, and I can then use pkxarc to unarchive the .EXE files, etc.,
haunted gave me a warning when I pkxarc'd the file and  sure enough, it
doesn't run either.  Too bad, it looked kind-of interesting.  Did
anyone else have this problem?  I went back to comp.binaries.ibm.pc
*three* times, wrote it out, uudecoded it, transfered it, etc. but
always the same thing.

-- 
 --Jeff Hartung--                        
                                         
 ARPA - hartung@sdics.ucsd.edu          
 UUCP - !ucsd!sdics!hartung