-
Indeed, changing the scanTime value did allow me to read in the saved profile.
I can't imagine that my Date & Time settings could possibly be affecting the value returned by your scanTime, but 'just in case':
Day & Time: Set date & time automatically: Apple Americas/U.S. (time.apple.com) Date: Year/Month/Day Time: Hour:Minute:Second
Time Zone = MST, Closest City = Phoenix, AZ {which doesn't...
2009-07-12 01:29:31 UTC in GrandPerspective
-
It occurs to me that the directory I told it to scan was '/' -- that is, the entire partition. I don't know if that folder name should equate to "" in the XML file or not. ^^;.
2009-07-08 22:42:14 UTC in GrandPerspective
-
I too, have had the exact same problem occur. And indeed, the person perfectly described the popup window that displays the error, except that 'NSXMLParserErrorDomain38' is spelled with 'Error' correctly (the first person obviously made a typo). [I can't be sure if 38 has a space before it or not, since it appears on the next line immediately after NSXMLParserErrorDomain.] This is indeed the...
2009-07-08 22:14:28 UTC in GrandPerspective
-
Nope, still appending '.bz' to the end of the dmg file, even after reboot.
Sigh.
Setting all the file extensions and file type back to The Unarchiver 1.6.1.
2009-06-30 06:13:19 UTC in Vienna
-
Sadly, indeed, both the methods you describe result in '.bz' appendages. So there's no need to send you the database.
When I open a context menu for the .bz files, The Unarchiver is indeed the default Open application. [You might want to consider using an application like XRay {alas, not free!} for this in the future, as it can even show you the entire...
2009-06-30 05:53:29 UTC in Vienna
-
Your argument is compelling.
However...
If I uncheck the Bzip2 File and the Bzip2 Tar Archive values within The Unarchiver, the problem still occurs. I even rebooted to verify it wasn't a problem with cached values or persistent variables.
Also, if it were a problem with Webkit (or a baser framework), why is it that Safari is unaffected? That is, you can happily download the dmg file with...
2009-06-30 01:51:03 UTC in Vienna
-
I tried turning JavaScript off, quitting Vienna, restarting Vienna, and trying to download the file again, and it still has the '.bz' appended, so the JavaScript setting has no effect on the outcome.
2009-06-29 23:19:05 UTC in Vienna
-
Well, yes, of course! [Everyone must have some way to read those silly stuffit files, after all!]
I currently use The Unarchiver 1.6.1 for most of my uncompression needs. I think I've set it as the default for most of my expansions.
I do have a Stuffit Expander lying around in Applications, I think it's an older one at 9.0. And I even have Zipeg 2.7.1 and Gumby 50c around in Utilities...
2009-06-29 23:07:34 UTC in Vienna
-
If my suspicion is correct, the download dmg file must have internal bzip2 compression. Since this type of file is not usable by people of < 10.4, most developers don't use this kind of compression. They are relatively rare, and I can't imagine how I can find them in the current releases of Macupdate except by trying to download every single file, and see if any are of that type. ^^;
In fact,
2009-06-29 22:16:17 UTC in Vienna
-
I using Safari 4.0, which I guess may affect the NSURLDownload class. However, as I said, only Vienna has the problem.
To completely reproduce on a 10.4.11 PowerPC machine with Vienna 2.3.1.2302:
Subscribe to MacUpdate
Select MacUpdate, scroll through the list of updates until you reach the article 'Mail Scripts 2.9.1 - AppleScripts for Mail.app...
2009-06-29 20:54:24 UTC in Vienna
