Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!uwvax!dogie.macc.wisc.edu!csd4.milw.wisc.edu!leah!rpi!crdgw1!steinmetz!sungod!davidsen
From: davidsen@sungod.steinmetz (William Davidsen)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Lharc self-extraction problem
Keywords: lharc
Message-ID: <13810@steinmetz.ge.com>
Date: 15 May 89 16:59:06 GMT
References: <2267@Portia.Stanford.EDU>
Sender: news@steinmetz.ge.com
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: General Electric CRD, Schenectady, NY
Lines: 20

In article <2267@Portia.Stanford.EDU> roller@Jessica.stanford.edu (Jason Deines) writes:
| Hello everyone.  I have a problem with a self-extracting file a friend gave
| me which was created with lharc 1.0.  Quite simply, my friend wasn't
| thinking, and the resultant executable code winds up being 650K, too big to
| run.

  There are MS-DOS systems which are not PC compatible. The 640k limit
is an artifact of bad design of the original PC. Using a Tandy 2000, for
instance, you can run a 768k version of DOS, while my old S100 system
supports a full MB.

  What you need to do is to find someone who has one of these systems
and beg them to execute your program. However, if there is just a header
on the front of the normal lharc, you can strip it with DEBUG or a tiny
program. That might give you a normal lharc file. You can do this with
some other archive formats, but I haven't played with lharc enough to
determine just what it does.
	bill davidsen		(davidsen@crdos1.crd.GE.COM)
  {uunet | philabs}!crdgw1!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me