Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!randy From: randy@athena.mit.edu (Randall W Winchester) Newsgroups: comp.sys.cbm Subject: Re: .sfx Download problems Keywords: sfx files Message-ID: <1991Jan18.143431.25543@athena.mit.edu> Date: 18 Jan 91 14:34:31 GMT References: <1991Jan15.162852.9307@evax.arl.utexas.edu> <1991Jan17.130511.25579@vlsi.polymtl.ca> <1991Jan18.055011.171@evax.arl.utexas.edu> Sender: news@athena.mit.edu (News system) Reply-To: randy@mit.edu (Randall W Winchester) Organization: Massachusetts Institute of Technology Lines: 37 In article <1991Jan18.055011.171@evax.arl.utexas.edu> cs4344af@evax.arl.utexas.edu (Fuzzy Fox) writes: >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! Just one idea: did you save the SFX after running it? The documentation specifically says not to do this. SFX files relocate themselves when they are run, which enables them to run on both the 64 and 128. Saving an SFX after running it, then trying to run it again can cause the results you've described. I've uploaded a few SFX files to Milton, and they've all worked just fine. >-- >begin 644 .signature >G5&AI >end ******************************************************************************* * Randy Winchester * randy@mit.edu * PO Box 1074, Cambridge, MA 02142 * *******************************************************************************