xadunfile no paths

Moved on from the LhA extract single file issue. Now using xadunfile. Having the same problem.

I want to extract a single file from an archive to the current path, but without any sub-drawers.

xadunfile from "amistore.lha" destdir "ram:" file "DATA/IMAGES/BANNERS/A-EonVideoCollection_LG.png" noabs

That creates all the drawers. Using notree instead extracts nothing. Using both together does nothing.

What I want is the png to end up in root of ram:.

What am I missing?

@mritter0

It looks like the xadunfile NOTREE option should do what you want but it does nothing for me. However something like this did work for me:

lha e -x2 amistore.lha DATA/IMAGES/BANNERS/A-EonVideoCollection_LG.png ram:

Right. It says "Nothing processed." I can do it with LhA, but not with xadunfile.

Just use the filename not fullpath+filename.


Tried here (with ftpd.lha archive):

#c:xadunfile SDH1:Comm/FICHEROS/ftpd.lha ram: ToDo NOTREE
Wrote 158 bytes: ram:TODO
Wrote 1404 bytes: ram:TODO
Processed 2 files.

So here it works fine. Try this xadunfile version:

http://jabirulo.site90.com/temp/xadunfileTEST.lha

My version is 1.22 and only 8KB.
Your version is 1.26 and 146KB.

Is there a newer package out there? Mine is what came with OS4.1FE.


Not specifying the entire path, just the name, works. But that will cause problems if there is more than one file with the same name, but in different drawers. Your example extracted two files with the same name.

Not good enough for me.

@mritter0

It's a test build (I hope), anyway it hasn't been stripped which will probably drop the filesize below 40k.

It's a self build (little update of some deprecated functions or alike). And it's "big" 'cos isn't stripped (as Severin posted)

So, then someone is still working on xadunfile? This issue will be addressed? Soon?

I don't understand how no one has brought this up before. This is a huge bug.

Thanks, guys.

@mritter0

Probably because most users are lazy, extract everything to ram, get the file they want and delete the rest, which can all be done with a mouse so they don't have to get their hands dirty in a shell.

To whomever is doing the latest update:

In the header line, the Size and CrndSize fields have been increased from 8 to 9 each. (I would increase them to 10). This is fine, but not for when you are parsing the output.




It may seem menial at this time, but it is very critical.

@mritter0

1. Perhaps you should make your parsing code more robust so it can deal with arbitrary white space? Otherwise you will be stuck relying on specific versions being installed, and you just know some user is going mess that up, they have knack for that sort of thing

2. or maybe even be using xadmaster direct rather than via a command line tool, that being the whole point of xadmaster to not need command line tools?


I'm a bit uncertainly of xadmasters status, isn't it open source?

@mritter0
Quote:
As far as I can tell, the XAD command line utilities included with OS4 have always been the original 68k versions.

@broadblues
Quote:

https://sourceforge.net/projects/libxad/

I would rather use the xadmaster.library and do things internally. But I haven't found a good source code example on what to do. The only example I have is terribly written and makes little sense. I was PMing with a guy on OS4Coding and he said the same thing.

My current parser accommodates for any length of text/data. It will work with any version just as long as the columns line up consistently.

@mritter0

the code to the tools is here: http://libxad.cvs.sourceforge.net/vie ... ibxad/amiga/source/tools/

must give some clues I would have thought, though I never used it so can't give much more help than that.