Loading Profile...
Recent activity
Subscribe to this feed
A comment on the problem "ForkLift, muCommander issues with ExpanDrive..." in ExpanDrive:
It seems that your/our solution of Forklift problem didn't get into the new public release 1.3.2.
I just downloaded it and the drivers still don't show up into the ForkLift. :-(
Have you found some issue about the renaming the fsname? Could you do the fsname change optional in the preferences, please?
Thanks for your answers. – Korim, on December 02, 2008 13:46-
Korim replied on November 30, 2008 05:41 to the problem "ForkLift, muCommander issues with ExpanDrive..." in ExpanDrive:
It seems that your/our solution of Forklift problem didn't get into the new public release 1.3.2.
I just downloaded it and the drivers still don't show up into the ForkLift. :-(
Have you found some issue about the renaming the fsname? Could you do the fsname change optional in the preferences, please?
Thanks for your answers. -
Korim replied on October 24, 2008 15:26 to the problem "ForkLift, muCommander issues with ExpanDrive..." in ExpanDrive:
That's really good news. I hope next public release will have that.
Thanks for make this happen. -
Korim replied on October 09, 2008 20:42 to the problem "ForkLift, muCommander issues with ExpanDrive..." in ExpanDrive:
It seems that ForkLift shows only devices from Volumes which have in Device name string like /dev/something... Of course it's just guess.
Your drivers have always as Device: ExpanDrive string.
I can see this in Path Finder when I right click on a disk and select the Get Info command. There are information like
Kind: Volume
UTI: public.volume
...
...
Format: fusefs
Mount Point: /Volumes/MyDisk
Device: ExpanDrive
If I mount a DMG file or real external drive, they have as Device: /dev/disk2s2 or some variation with /dev/...
Maybe this has something to do with showing up into ForkLift. I am not sure if you can change Device name to /dev/ExpanDrive and test it.
Thanks. -
Korim replied on July 09, 2008 22:05 to the problem "ForkLift, muCommander issues with ExpanDrive..." in ExpanDrive:
I just tested the 1.2.7 version (bought the license) and ForkLift still doesn't see the expandrives...
Is this problem on your list, please?
Very sad... -
Korim replied on July 09, 2008 22:00 to the problem "Apple backup doesn't see drives" in ExpanDrive:
Do you think that this problem happens for the same reason why I cannot see the ExpanDrives into ForkLift? -
Korim started following the problem "Apple backup doesn't see drives" in ExpanDrive.
-
Korim replied on June 27, 2008 14:38 to the problem "ForkLift, muCommander issues with ExpanDrive..." in ExpanDrive:
Hello,
I can see that you have released 1.2.6 version. I would like to test it if you had resolved my issue above (ForkLift doesn't see the ExpanDrive's drives at all).
Unfortunately I cannot test it since I am getting that my trial period for this copy has ended. I would buy the license, but ForkLift problem is deal breaker for me. I have to wait with the purchase until this problem will be fixed.
Please could you let me know if my issue has been fixed and if I can somehow test it before purchase?
Thanks. -
Korim reported a problem in ExpanDrive on May 22, 2008 17:51:
ForkLift, muCommander issues with ExpanDrive...I would like to use some 2 panels file manager with ExpanDrive's drives. I have tried:
a) muCommander - It can see the ExpanDrive's drive, but cannot see the correct 'X' permission. For example the file permission 755 shows as 644 in muCommander. And of course if I copy this file to my local disc, I get 644 instead of correct one (755).
b) ForkLift and Drive Order - both CANNOT see the ExpanDrive's drive at all.
Are these problems fixable on ExpanDrive side or they have to be addressed by developers of those file managers?
ExpanDrive 1.2.2 works correctly with Finder so far. Do you have any idea why ForkLift doesn't see the drives created by ExpanDrive?
Please let me know if you can fix it.
Thanks.
I am using Mac OS X 10.5.2, ForkLift 1.5.2, ExpanDrive 1.2.2, muCommander 0.8.2
