To: opendos AT delorie DOT com, caldera-opendos AT rim DOT caldera DOT com X-Comment-To: Lars-Einar Jansson References: <11181446546015 AT 2 DOT sbbs DOT se> Message-Id: From: "Arkady V.Belousov" Date: Fri, 20 Nov 1998 14:59:32 +0300 (MSK) Organization: Locus X-Mailer: dMail [Demos Mail for DOS v2.07a] Subject: Re: Packed file is corrupt? Lines: 27 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Reply-To: opendos AT delorie DOT com X-Comment-To: Lars-Einar Jansson Hi! 21-ξΟΡ-98 02:39 lars_einar DOT jansson AT 2 DOT sbbs DOT se (Lars-Einar Jansson) wrote to opendos AT delorie DOT com, caldera-opendos AT rim DOT caldera DOT com: LJ> When trying to launch a couple of applications residing on the C- LJ> drive, among them PCTOOLS' PCShell, in a version from 1991, I got the LJ> error message "Packed file is corrupt". I'm not running any kind of LJ> disk-compression. When MS-DOS 5.0 arrived with self-upper loading, there is new problem appear - programs, packed by old version of PKLITE (or MS's EXEPACK?) can't correctly start, when loaded at first 64K, so MS's add "fix" to DOS. Start such application with LOADFIX as prefix: LOADFIX yourpgm LJ> However, when trying to launch the same applications from Norton LJ> Commander, 1988 version, everything seemed to be quite normal. Also, LJ> when trying to launch the same applications from the commandline LJ> after having booted the computer up from a floppy with DR-DOS 7.02 or LJ> MS-DOS 6.0, nothing peculiar happened. Of course - NC eats for his own resident part about 12K and thus "emulating" LOADFIX. And I think, when you boot from diskette, you have empty CONFIG.SYS and not so optimally managed memory.