Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!cs.utexas.edu!evax!cs4344af From: cs4344af@evax.arl.utexas.edu (Fuzzy Fox) Newsgroups: comp.sys.cbm Subject: Re: .sfx Download problems Keywords: sfx files Message-ID: <1991Jan18.055011.171@evax.arl.utexas.edu> Date: 18 Jan 91 05:50:11 GMT References: <1991Jan15.162852.9307@evax.arl.utexas.edu> <1991Jan17.130511.25579@vlsi.polymtl.ca> Organization: Computer Science Engineering Univ. of Texas at Arlington Lines: 23 This is all very strange about .SFX file problems. When I created an .SFX file to send to someone over the net, after it was created, I then loaded it up and dissolved it in 64 and 128 mode to see if it was working properly. (By the way, this is something everyone should do when they make any sort of ARC, Lynx, or whatever file -- Test it to see if it dissolves correctly!) Anyway, the file DID work correctly, and the program ran just fine. So, I uuencoded the file and mailed it off to him. When he decoded it and tried it out, it exhibited just the behavior you have been describing here, saying 'ALL DONE' without doing anything. I didn't know what the problem was, so I just took the same binary files, encoded them again, and mailed them again. Then when he tried it out, it worked just fine for him. This is not a good sign. What could have gone wrong? Why did it go right again when I sent it out the second time? I did NOT re-make the .SFX file! -- begin 644 .signature G5&AI