Mail Archives: opendos/2000/11/09/13:21:17
Hi,
Right now I cannot remember who it was, but a couple of weeks
ago someone mentioned that he was not able to use PKZIP 2.50 for
DOS under DR-DOS, while PKZIP 2.04 worked OK for him.
I have run some tests and have come to the conclusion, that
PKZIP 2.50's DPMI support fails under EMM386.EXE when DPMI
is enabled (so far I tested only EMM386 3.27 as of DR-DOS 7.03).
PKZIP 2.04 has (almost) no problems to use EMM386 DPMI support
(but there have been a number of other problems).
As long as PKWare does not fix these problems (has anyone already
reported this to them?), a workaround is to set up an environment
variable %PKWARE.INC% to point to the PKZIP 2.50 directory, for
example:
SET PKWARE.INC=c:\utl\archiver\pkzip.250
Place a PKWARE.INI file in this directory with the following
contents (only the DPMI= directive is actually necessary):
[PKZIP]
COMPRESS=extreme
LISTCHAR=@
DPMI=disable
USELFN=disabled
[PKUNZIP]
DIRECTORIES=enabled
DPMI=disable
LISTCHAR=@
This will forbid PKZIP/PKUNZIP to use DPMI. The backdraw is
a noticeable performance fit (maybe 20%), but who cares, it's
still fast enough IMHO... (BTW. PKZIP 2.04 sensed for a "PKZIP.CFG"
variable and file name instead of PKWARE.INI.)
Alternatively you can also disable DR-DOS' DPMI support by just
typing "DPMI off" at the prompt, but this would also effect other
programs (run in that task).
It might also be useful to add something like:
SET TEMP=c:\tmp
SET TMP=%temp%
SET PKTMP=%temp%
to AUTOEXEC.BAT as well.
Hope it help,
Matthias
-------------------------------------------------------------------
Matthias Paul, Ubierstrasse 28, D-50321 Bruehl, Germany
eMail: <Matthias DOT Paul AT post DOT rwth-aachen DOT de>
Web : http://www.rhrz.uni-bonn.de/~uzs180/mpdokeng.html
-------------------------------------------------------------------
- Raw text -