Loading Profile...
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
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
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?We'll download those guys right away and look into it.
-
Inappropriate?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. -
Inappropriate?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...
I’m sad
-
Inappropriate?Turns out the issue is that ForkLift has some hardcoded device types it chooses to view, and also some path names that it chooses to hide
If you create a symbolic link to your /Volumes directory, it will show up correctly in ForkLift, and you can easily access your drives that are mounted with ExpanDrive
do this in the terminal
ln -sf /Volumes /MyVolumes
and it'll show up when you click your hard drive
I'm still checking into muCommander -
Inappropriate?This workaround addresses the problem, but will you be making a change so that the expandrive drives will show up in the devices pane? -
Inappropriate?dbarrett -
ExpanDrive shows up in the devices pane in Finder and all of the system dialog boxes. However, given that ForkLift is a custom application - they choose to only include specific thing in their devices pane. It is misleading, in a sense, because it looks exactly like Finder's.
I would recommend emailing them asking if it is possible in a future release, sorry!
-Jeff -
Inappropriate?Sorry I was bouncing back and forth and meant to enter this in the forklift forum, not here.
-
Inappropriate?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. -
Inappropriate?Korim -
Interesting observation. I'll see if we can tweak that to work.
-Jeff -
Inappropriate?I have our drives showing up in Forklift now, but I'm still investigating any potential implications of setting our fsname to /dev/ExpanDrive1 Comment
Add a comment
This solves the problem
-
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. -
Inappropriate?That's really good news. I hope next public release will have that.
Thanks for make this happen.
I’m happy
-
Inappropriate?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.
EMPLOYEE
EMPLOYEE
