Existing users, 
 Xfile Test Drive - 2.0.1.5ACP file management utilities, including Xfile. |
|
||||||||||||||||
|
|||||||||||||||||
Feedback Summary:
| Version 2.0.1.5: | |||||
| Overall Rating: |  (5.0) |
Features: | (4.5) |
Support: | (4.5) |
| Ease of Use: | (4.5) |
Quality / Stability: | (5.0) |
Price: | (4.5) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
Finder No Longer Enough - Version: 2.0.1.5, 4/15/2009 07:04AM PST
(2 of 4 users found this comment useful)
CozyNicki
I've been satisfied with the Finder for a long time. But I don't work in graphics and I don't think Cover Flow is a replacement for file system control. I don't understand why Apple programmers hate the command line and yet with the Finder force you to go back to it time and again. Ubuntu has a file manager that works properly. Why can't Apple have one? Until that day (if ever) Xfile is the only practical alternative on Mac OS X.
Gives you what you need - Version: 2.0.1.5, 4/14/2009 12:09PM PST
(1 of 3 users found this comment useful)
Kugo
I've had this for some time. When our Finder gets nuttier for each release it's good to know there are utilities that still give you what you need. These apps are incredibly fast and thorough and Xfile itself has a lot of protection against mishaps in the file system.
Re: - Version: 2.0.1, 10/16/2008 07:47PM PST
(3 of 5 users found this comment useful)
rixstep
Alberto, that is totally unnecessary. No one was wrong - save perhaps the Safari development crew. What happened was the result of a four part bug.
1. Since OS X 10.3.6 Safari's increased its timeout from one minute to ONE YEAR.
2. Users upgrading from Tiger to Leopard experienced corruption of the keychain.
3. When Safari couldn't read the keychain it would incorrectly think it had not reached the site - result: keep hammering away with thousands of hits in a minute or two.
4. Another bug caused Safari to loop out of control after a few minutes and crash.
It's all documented here and it occurs on upgrades and when accessing site URLs that require authentication.
http://rixstep.com/2/4/20080516,00.shtml
As far as we know this has not been fixed by Apple. On the other hand the cure is easy: simply remove the corresponding entries in the keychain and log in again, this time submitting username and password.
The 'one year timeout' does remain what we know in Safari.
This was about half a year ago; it was a panicky time for all. If you don't have our tools then run netstat in a loop when using Safari in this fashion; if you see a sudden blizzard of connections then quit Safari and take the above steps.
Cheers.
1. Since OS X 10.3.6 Safari's increased its timeout from one minute to ONE YEAR.
2. Users upgrading from Tiger to Leopard experienced corruption of the keychain.
3. When Safari couldn't read the keychain it would incorrectly think it had not reached the site - result: keep hammering away with thousands of hits in a minute or two.
4. Another bug caused Safari to loop out of control after a few minutes and crash.
It's all documented here and it occurs on upgrades and when accessing site URLs that require authentication.
http://rixstep.com/2/4/20080516,00.shtml
As far as we know this has not been fixed by Apple. On the other hand the cure is easy: simply remove the corresponding entries in the keychain and log in again, this time submitting username and password.
The 'one year timeout' does remain what we know in Safari.
This was about half a year ago; it was a panicky time for all. If you don't have our tools then run netstat in a loop when using Safari in this fashion; if you see a sudden blizzard of connections then quit Safari and take the above steps.
Cheers.
Most Recent Replies: View All 2 Replies
- Re: (1 replies)
