Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!bobmon
From: bobmon@iuvax.cs.indiana.edu (RAMontante)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: anarkey/zoo incompatible?
Keywords: anarkey zoo
Message-ID: <35459@iuvax.cs.indiana.edu>
Date: 10 Feb 90 18:15:08 GMT
References: <4048@cbnewsl.ATT.COM>
Reply-To: bobmon@iuvax.cs.indiana.edu (RAMontante)
Organization: malkaryotic
Lines: 26

rl@cbnewsl.ATT.COM (roger.h.levy) <4048@cbnewsl.ATT.COM> :
-After reading all the kudos for anarkey, I decided to try it.  I used
-the -U option to recognize "/" as path separators and I asked anarkey
-to place most of itself in extended memory.  By chance, practically
-the first thing I did afterward was a "zoo -extract" command.  Zoo
-(2.01) failed - it only gave me a brief message explaining how to get
-help.  After rebooting without anarkey, zoo was OK.  Can anyone explain
-this behavior?  Should I be afraid of what anarkey might do to other
-programs?

I don't have the doco. handy, but I think your -U option turns "/" into
"\" and "-" into "/" to generate the COMMAND.COM-style dir and option
markers.  This is to run things that have "\" and "/" hardcoded.

I avoid that issue by using Anarkey's -us option, which (again, I'm
trying to remember...) only turns single "/"'s into "\" and is
transparent to "\" and "-".  (Or maybe it's that -x\ option.)  Anyway,
zoo and anarkey get along okay for me.

Actually, my full installation line is:

c:\bin\looz xx \system\anarkey3  anarkey -E -a400 -h4000 -s2 -us -c -iif -x\

as I keep it tucked into an archive.  All my startup files are smaller that
way, and I just count on getting a cup of coffee while the monitor warms and
the AUTOEXEC finishes...