Forum unknown
· Utilities
#AB prog
3 messages in this thread
I have just uploaded my preliminary IBMPC version of AB: my AmigaBinary
packer/unpacker. I hacked it together in my free time the past few days
using a VAX & VMS C plus Unix C as a double-check. Then I ported it DRC on
the IBM to check out the short ints & give it to you. I haven't started
using Amiga C yet, but I plan to get going by porting it to the Amiga next
(where it belongs!)
This isn't a full implementation yet, though it does support files/.info
files and subdirectories. Since I wrote it in standard C, I haven't put in
time/date stamping or disk labels. Because it uses DRC's standard
wild-carder, you must specify multiple directories separately, without using
paths (Ugh!) e.g. To pack all files in D:\dir & D:\dir\sub1 & D:\dir\sub2
into COMBO.AB including the directory separations, you could:
C>CD D:\DIR
C>AB C COMBO.AB D:*.* ; Create COMBO.AB
C>CD D:SUB2
C>AB -DSUB1 A COMBO.AB D:*.* ; Add files into SUB1
C>cd D:..\SUB2
C>AB -DSUB2 A COMBO.AB D:*.* ; Add files into SUB2
Notice I suggested working on drive C:, so that the CD's don't take you away
from the COMBO.AB library. This will definitely change in future releases.
Let me know what you think about the user interface, if you have the time
and/or desire to look at it. Its in DL6, by the way. >>Wayne<<
Wayne… here's my report. First, as you noted, date/time isn't implemented
yet. I couldn't get it to work with files greater than 32K, getting an
"unexpected EOF". Wildcards also didn't work — specifying a wildcard caused
it to use only the first file that matched the wildcard spec. Also as you
noted, directory support is poor. When you're extracting, it was my intention
that a directory specification really means "move to that directory". In
other words, go to a pre-existing directory, and IF it doesn't exist, create
it. You're creating a directory every time, which causes it to give up if
that directory already exists. Also, I found the method of adding new
directories (particularly having to tell it what level to put it at) a little
hard to work with. I had some initial trouble with the fact that -Options
much precede the actual command character. Over all, looks great! The CRCs
and headers are correct throughout (except for the lack of valid date/time),
including the byte order of word and longword fields. (I was worried that
maybe I hadn't been clear enough about that in the spec). – Bela
Wayne… here's my report. First, as you noted, date/time isn't implemented
yet. I couldn't get it to work with files greater than 32K, getting an
"unexpected EOF". Wildcards also didn't work — specifying a wildcard caused
it to use only the first file that matched the wildcard spec. Also as you
noted, directory support is poor. When you're extracting, it was my intention
that a directory specification really means "move to that directory". In
other words, go to a pre-existing directory, and IF it doesn't exist, create
it. You're creating a directory every time, which causes it to give up if
that directory already exists. Also, I found the method of adding new
directories (particularly having to tell it what level to put it at) a little
hard to work with. I had some initial trouble with the fact that -Options
much precede the actual command character. Over all, looks great! The CRCs
and headers are correct throughout (except for the lack of valid date/time),
including the byte order of word and longword fields. (I was worried that
maybe I hadn't been clear enough about that in the spec). – Bela