Eko wrote:
>Perhaps Bernie could make a slight change in the APM
>manager, so it would accept a range of valid Arachne
>versions (i.e. in APM.ID)? There should be a way to get
>the current Arachne version from within APM manager, so
>it could decide either continue installing or not.
I need to implement another thing first into unarj, unpacking a selected
file from the arj file (apm.id in this case). Otherwise there would be no
point since we would unpack over core.exe and the other files anyway (this
is on my to-do list).
I need to "revisit" apm.c anyway since there are some things in there for
added compatibilty with Linux that's useless since arj files can't be
created in non-DOS OS this must be changed into .tar.gz support (where I do
know how to unpack a single file).
I was actually working on just that when I stole the source for 1.62 so you
might understand why I haven't finished apm yet ;-)
And how do you propose I get apm.exe (a standalone program after all) to
know what version core.exe is? I've had bad experiencing (1.60B1 IIRC) with
increasing the number of arguments sent to apm.exe through mime.cfg (I
never had any problems but others had).
>This way (IMHO), Michael should be able to safely offer
>"Arachne Upgrade" APMs for users who already have certain
>previous version(s) fully installed on their system.
>
>BTW, how many of you really want this option? ;-)
I would probably just download and store them on my HD but never actually
use them ;)
//Bernie
http://bernie.arachne.cz/ DOS programs, Star Wars ...
