Message-ID: <67BAFB085CD7D21190B80090273F74A45B7CF4@emwatent02.meters.com.au> From: "Da Silva, Joe" To: "'opendos AT delorie DOT com'" Subject: RE: G(un)zip alternatives (was Overclocking, Linux issues) Date: Wed, 25 Oct 2000 17:36:35 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Reply-To: opendos AT delorie DOT com See below ... Joe. > -----Original Message----- > From: Rob McGee [SMTP:i812 AT iname DOT com] > Sent: Wednesday, 25 October 2000 14:20 > To: opendos AT delorie DOT com > Subject: Overclocking, Linux issues: was Re: About Micro$quash... > ---- snip ---- > I recommend "mc", the Midnight Commander, a visual file manager which is > a good aid for learning your way around. (With current versions of > ZipSlack you have to install ap1/mc.tgz and d1/ncurses.tgz first.) > > > [snip] > > requirements are for his latest version, but you must have at least a > 386sx > > and 2MB RAM to run Linux. Most likely his latest version requires 4MB > RAM > > and 8 MB for x-windows, unless something has changed. This has been the > > requirements need for Slackware distribution for many years. But I would > > highly recommend 16MB and to get by without any swapfile or swap > partiton > > 32MB should do it for a single computer. You can get by with 24MB, but > one > > You can run on 4MB, but it's painful. It's very difficult to *install* > on only 4MB, but that's not an issue with a DOS- or Windows-based setup. > (ZipSlack requires a 32-bit unzip utility such as WinZip. I don't know > if it can be done in DOS, even DPMI.) > [da Silva, Joe] On a related side-issue, what is a good program to handle (eg. decompress), in DOS, Unix-ish files like "*.tar.gz" and "*.tar.z" ... ? I have tried 'gunzip' and some un-tar thing whose name escapes me, but they are user-vicious (particularly gzip/gunzip) ...