Member
Join Date: Jan 2007
|
^-- Paste here what you used for your locale.
|
quote |
New Member
Join Date: Feb 2007
|
That list which i got after entering locale -a ?
That is longer than 200 lines! by just entering locale i got this Quote:
|
|
quote |
Travels via TARDIS
Join Date: Aug 2005
Location: Earthsea
|
For German, the following will probably work as you intend, causing the volume to be mounted under the German locale:
Hopefully that helps... |
quote |
New Member
Join Date: Feb 2007
|
*smile* i just found your posting at page 4 of this topic (last posting on that page).
I tried all the de_DE settings I found. And now is see why.... there is a - missing in the .ntfs-locale file name, in that posting. Thanks a lot! With the right file name it is working now! correction: now i'm able to see the files and i'm also able to access directorys with äöü in the name. But the finder doesn't allows me to copy the directory or files with äöü in the name. even more strange is that the preview of those files doesn't work. i copied a MP3 on a windows computer to the harddisk and renamed one of this clones to üöä.mp3 this file will open in iTunes but doesn't allows me to play it in the preview. The same file as uoa.mp3 works fine, even with a preview. Last edited by AssetBurned : 2007-02-27 at 20:54. Reason: Posts merged |
quote |
Travels via TARDIS
Join Date: Aug 2005
Location: Earthsea
|
Yeah, the old versions did specify .ntfslocale, but I changed the naming scheme to be more consistent (and readable), so it's now .ntfs-locale.
I have no idea what would cause the Finder problems though. I'm no expert on character encodings, so you might want to look elsewhere (NTFS-3g or MacFUSE) for more details on that. I just provided a hack to make it automatically mount with a locale setting. Apparently I call the cops when I see people litter. |
quote |
New Member
Join Date: Feb 2007
|
Hi, I just come across this fabulous tool and apart from somewhat slow transfer speeds, I really enjoyed not needing to boot to windows to modify files......
.......until I tried with the files with korean names I used 'ko_KR' on .ntfs-locale to mount my vista bootcamp partition and my usb external NTFS drive. It seems like Finder is acting like the files with the korean filename aren't even there. The file is present and I can see them, but I can't move, copy, delete, or open the file (or whatever file operation you can imagine) in any way. How do I fix this? The 'ko_KR' and 'ko_KR.UTF-8' are the only locales that work for me - at least it shows that the file is there, just that I can't do anything with them. |
quote |
Travels via TARDIS
Join Date: Aug 2005
Location: Earthsea
|
I have no idea where the international character problems are originating. I don't know if it's a MacFUSE or NTFS-3G problem. We're telling NTFS-3G to mount with a given locale, so my best guess is that something inside MacFUSE isn't entirely Unicode-friendly as the Finder might expect.
That's just a guess, and by no means an accusation. Unfortunately, I can't help. Apparently I call the cops when I see people litter. |
quote |
New Member
Join Date: Feb 2007
|
Well I recall being able to work with the international filename files with the earlier versions. Not sure if it's from MacFUSE or NTFS-3G or the MacFUSE tools. I used MacFUSE Core 0.21, MacFUSE tools 0.17 r1, and NTFS-3G 02/07/07 build. I was able to work with them just fine with those versions.
|
quote |
New Member
Join Date: Feb 2007
|
I recently found out about this forum while desperately trying to find a way to write to my NTFS formatted Windows XP partition on my Imac HD. I found out the hard way that OSX can only read NTFS drives... I wanted to use the NTFS drive as my main storage drive, that way XP and OSX would have access to this data (MP3s, pictures, videos, photoshop files...). Fortunately I discovered MacFUSE, NTFS-3G and you guys.
A few minutes ago I updated my system with the latest packages from ShadowOfGed and everything went smoothly. Transfer rate from HFS+ to NTFS is very satisfying (684.5MB in 67 seconds). I also took the time to make a back-up of my data. And I also found out how to replace the network drive icon to something better (the normal HD icon lol) All this to say thank you ShadowOfGed and chucker for the incredible work and support!!! |
quote |
Travels via TARDIS
Join Date: Aug 2005
Location: Earthsea
|
The tools serve only two temporary purposes:
I don't know where it is, though... sorry I'm not much help in this regard. Apparently I call the cops when I see people litter. |
quote |
New Member
Join Date: Feb 2007
|
I agree with you that the tools wouldn't be a problem, so I guess it either comes down to the NTFS-3G or MacFUSE, though I'm leaning towards NTFS-3G. I might try the earlier 02/07/07 release and see what happens.
And yes, thanks ShadowOfGed for all the work you do. I'm looking forward to it. |
quote |
New Member
Join Date: Feb 2007
|
switching to 02/07/07 build didn't work. I guess this is a MacFUSE problem now.....
I'll try reverting back to 0.21 and see what happens. |
quote |
Member
Join Date: Jan 2007
|
Quote:
You can try mounting the drive in windows or linux so it can read/write the problem folder. Create a new directory and copy the files contained in that folder to the new one you created. |
|
quote |
New Member
Join Date: Feb 2007
|
Further observation showed that this is indeed not a problem with any MacFUSE and NTFS-3G tools. It has something to do with the permission. I found out that the ones with full control for everyone can be accessed normally while the ones with limited permission (which vista defaults on, unfortunately) can't be moved/copied/opened. Seems like I need to fiddle around with the permissions here.
|
quote |
Member
Join Date: Jan 2007
|
Yes, it's the same as if you are in Linux trying to access HFS partitions/drives. You have to be root to be able to open dirs and files located on HFS partitions.
The limitation documentations is missing in the how to i have seen with MacFUSE/NTFS-3G. Normal users think they can access any ntfs partitions as long as they have FUSE installed. It does get messy. |
quote |
New Member
Join Date: Feb 2007
|
Quote:
Quote:
CU AssetBurned |
||
quote |
|
Hi!
I've discovered these tools and well... I'm not a novice on Mac, but I'm one on the Terminal stuff... And after installing both MacFuse and NTFS-3G, nothing happens! I see my external NTFS HD on Disk Utility but am not able to mount it... Could someone tell me why or show me on which page of this post (or else) I could find my answer... Thanx |
quote |
|
Hi everyone,
I tried formatting a FAT32 partition into NTFS using the "diskutil eraseVolume" command and everything works as expected under os x (thanks to the whole team, you guys rule). But I am running into a problem when I try to mount the volume on a home media player appliance. The media player either retains the volume's old name and tells me that the volume is empty, or tells me that the volume name is "untitled" and shows me the right number of files and folders. Did I format my volume the right way? I tried renaming the volume through the Finder or with the "diskuitl rename" command to no avail. Could this have anything to do with the partition scheme? (FDisk_partition_scheme) Should I try the "duskutil eraseDisk" command; in that case what would the right syntax be? |
quote |
‽
|
Quote:
Quote:
|
||
quote |
New Member
Join Date: Mar 2007
Location: Manhattan NYC NY USA
|
Hello! Newbie checking in. Everything works wonderfully.
More wonderfully than I was expecting. Yesterday afternoon I hooked a newly-formatted NTFS external drive to my PowerBook, followed the instrux (opened Disk Utility, unmounted it, then remounted it from the command line as described back on page 1; had to repeat the mount command, it error-messaged me the first time Quote:
This evening I hook it up again, expecting to again have to unmount it in Disk Util then remount it using Terminal command, but lo and behold, the sucker mounted in read-write mode from the get-go!? What, did I make that volume editable to MacOS X permanently somehow? My entire computer's been rebooted since then! What the heck is persisting, and how? Now I'm curious to see how it behaves the next time I have a chance to hook up a different NTFS drive. |
|
quote |
|
Hey guys, Ive spent the last four hours trying to setup NTFS writing on my Mac but Im running into problems.
After installing everything and rebooting my NTFS mounts but as a read only. If I unmount it using disk utility and try mounting via Terminal I get this: Macintosh:~ brycenathanhawkins$ sudo mkdir /Volumes/"External" Password: Macintosh:~ brycenathanhawkins$ ntfs-3g /dev/disk1s1 /Volumes/"External" -o ping_diskarb,volname="External" Volume is scheduled for check. Please boot into Windows TWICE, or use the 'force' mount option. When I try using the force mount option I get this returned: Macintosh:~ brycenathanhawkins$ ntfs-3g /dev/disk1s1 /Volumes/"External" -o ping_diskarb,force,volname="External" WARNING: Dirty volume mount was forced by the 'force' mount option. kextload: /Library/Extensions/fusefs.kext loaded successfully mount_fusefs: fusefs@0 on /Volumes/External: Operation not permitted Im completely confused and dont know what else to try.. any suggestions? Im running: MacFUSE Tools: MacFUSE Tools 0.2.2.dmg NTFS-3G: NTFS-3G 1.0.dmg MacFUSE Core: 0.22 |
quote |
New Member
Join Date: Mar 2007
Location: Manhattan NYC NY USA
|
Quote:
• Did not auto-mount as editable. Auto-mounted read-only in the Finder. • Unmounting w/Disk Util, then creating mountpoint and mounting via cmd line worked fine. Didn't have time to reboot and see if it auto-mounted editable next time around w/o any intervention on my part or not. Got to the office, and hooked up the original NTFS drive, though, and it once again mounted as an editable NTFS volume just by being hooked up and the power switched on. Is that how it works for everyone else who has it working? |
|
quote |
Travels via TARDIS
Join Date: Aug 2005
Location: Earthsea
|
Quote:
Because of a quirk with DiskArbitration (the Apple software that takes care of automatically mounting disks), you'll have to reboot your machine the very first time you install this NTFS-3G package. The reason is that DiskArbitration only scans for known filesystems when it boots. Thus, after your first install, it doesn't know that NTFS-3G is there. After rebooting, however, NTFS-3G updates should take effect immediately. Quote:
However, you should probably get a Windows machine to verify the drive and mark it as clean so that the built-in tools can mount it automatically. Apparently I call the cops when I see people litter. Last edited by ShadowOfGed : 2007-03-05 at 12:03. Reason: Posts merged |
||
quote |
New Member
Join Date: Mar 2007
Location: Manhattan NYC NY USA
|
Quote:
THEN I unmounted the NTFS drive and THEN I rebooted my compute and THEN I reattached the NTFS drive and, hey, it mounted and, without so much as a single character being typed by me at the Terminal command line, it's in editable mode from the get-go! And it's persistently so. I've since rebooted yet again, attached a different NTFS drive then gone back to the original and it still mounts as a completely, totally editable volume. I was not expecting that. I thought I'd have to unmount it every time, then remount it from the command line using the arguments that mount it with write privs. That's not so. It's doing it on its own now. |
||
quote |
Travels via TARDIS
Join Date: Aug 2005
Location: Earthsea
|
Quote:
That's the entire point of this package. You'll see that there's an ntfs-3g.fs bundle installed in /System/Library/Filesystems. Once the system knows about that, it will automatically mount any NTFS volume using NTFS-3G, thus making it read/write. In some cases, there are people who don't want that behavior on select volumes, thus the .ntfs-readonly file that's mentioned repeatedly. Glad that you're happy to have a Mac-friendly NTFS-3G installed. Apparently I call the cops when I see people litter. |
|
quote |
New Member
Join Date: Jan 2007
|
I wanted to say thanks to all for their help once again on this. I ended up uninstalling though because I couldn't deal with the slow shut downs. I haven't checked out any new developments on this lately though. Even though I uninstalled everything, I still somehow have fuse_daemon running in memory everytime I boot up and I can't get it to turn off or delete it. Shadow, how would I go about stopping this from running completely and erase it for good?
Note: Everything is uninstalled but yet fuse_daemon still exists and still runs. |
quote |
Travels via TARDIS
Join Date: Aug 2005
Location: Earthsea
|
Quote:
If you used the uninstaller script I posted a long time ago, I'm surprised anything is left behind. Anyhow, there are a bunch of binaries in /usr/local/bin. Also, fuse_daemon is started as a launchd task, so to make it stop, do: That should axe it. Apparently I call the cops when I see people litter. |
|
quote |
New Member
Join Date: Jan 2007
|
Quote:
|
|
quote |
New Member
Join Date: Mar 2007
|
I've got the latest installed (mac combo package 0.2.2) and I can write to my mount (/Volumes/C ) until..... I try to use a symlink. I'm trying to use my windows partition to store all my photos for iPhoto, and read that symlinks work fine. But... doesn't seem to be the case with ntfs-3g and/or macFUSE in the mix. As soon as I try to write a file via:
lrwxrwxrwx 1 cpn cpn 36 Mar 6 01:36 iPhoto Library@ -> /Volumes/C/DOCS/PICS/iPhoto Library/ I get an input/output error which won't go away until I unmount and remount C: laptop:~/Pictures cpn$ touch /Volumes/C/DOCS/PICS/iPhoto\ Library/test.txt touch: /Volumes/C/DOCS/PICS/iPhoto Library/test.txt: Input/output error Anyone have any ideas? My best guess as to how to proceed now is forget about the symlink thing (and give up solving why it's borked) and modify iPhoto to go directly to /Volumes/C....../iPhoto Libary/ (involves modifying a couple plist files I believe). But I'd love to know why the symlink creates chaos, plus it's be more obvious as to what's going on and should survive iPhoto updates. T.I.A. all CPngN |
quote |
Travels via TARDIS
Join Date: Aug 2005
Location: Earthsea
|
I've no idea how well symlinks work on NTFS.
I know in Windows you can create them, but recall reading that it's a mild hack. However, that's a problem beyond our scope... I'd check out the NTFS-3G website to find out more about it. Apparently I call the cops when I see people litter. |
quote |
Posting Rules | Navigation |
Page 10 of 13 First Previous 6 7 8 9 [10] 11 12 13 Next |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Firefox 2.0 for Mac: User Interface Grievances (Redux!) | Brad | Third-Party Products | 42 | 2006-11-06 13:33 |
Stupid Mac graphics card options | Luca | Third-Party Products | 33 | 2005-07-01 01:34 |
Games specifically for Mac | Banana | General Discussion | 24 | 2005-03-28 14:03 |
Of All Things: PowerMac vs. Mac mini?!?!? | Wraven | Purchasing Advice | 20 | 2005-01-25 21:25 |
Apple releases updated Power Mac G5s | staph | Apple Products | 43 | 2004-06-09 13:20 |