New: Gopherus (Feb 14, 2023), Platform 24.1 (Feb 13, 2023)
450+ real apps (49GB), 1 billion downloads, Please donate.
I tried compacting an app that was on a UNC path (network share into my virtual machine) and AppCompactor went crazy indexing ~5000 folders although there were only a couple of files in the folder before I killed it.
Maybe a warning would be nice for the next version.
UNC paths are \\server\path; this issue (I reported it some time ago personally, I think it's been lost in the mists of time) is that it doesn't work with network drives. It just doesn't hit its terminating condition; I didn't get round to checking out why.
but the path starts with \\ so I thought it was UNC.
Lets hope it gets a second round of attention now 
\\server\path is a UNC path. X:\foo when 
is a network share is a network drive, not a UNC path. As you described it as a "network share into my virtual machine" I presumed you were talking about a network drive rather than UNC path? Anyway, whichever it is (I've never tried a UNC path directly, it should work fine from my understanding of the techniques employed), network drives don't work.
My exact path was "\\Vboxsvr\papps\Diffpdf\App".
I've fixed this in 2.1 by detecting it and rejecting it on the directory selection screen.
Personally I would not call this fixed. I'd call it avoiding the issue; I'll put it on my list of things to take a look at it some time as I would rather like it to work on network drives, to make it work with virtual machine shared drives.
As both 7za.exe and upx.exe are command line tools, I don't think either will properly support UNC paths anyway, so it's a bit moot. Either way, no apps support UNC officially, making this a feature request if someone wants it enabled.
It's network drives that I care about more - not UNC paths. Network drives don't work with this.
As long as you assign a drive letter, it works just fine. The issue here is UNC paths. If it's anything other than a drive letter, it doesn't work.
I've tried using mapped network drives on three separate machines (one VM connected to VirtualBox shared folders) and two at Uni (connected to Uni servers) and had it fail in the same way each time.
I just tested it under VirtualBox using a \\vboxsvr\ share (which appears to Windows as a network drive) and it worked just fine compressing Miranda IM Portable when mapped to the drive.
It's definitely not working for me; it's going wacky during the first ${GetSize} call.
I've been on XP every time. Never tried it on another OS as I don't have another in a VM handy (wait a week and I should have got round to setting up 7 x86 and x64).
I was on XP as well where it worked fine.
it works ok for me too.
I'll need to investigate considerably deeper, then. Can't think of any more differences which could be distinctive.
What if you just screen record the whole process, then John or somebody can say what they were doing differently, if anything?
Visit the Community page
Join our forums