NTFS Partition VS Fat32

I have this funny feeling that NTFS is required for the latest Quicktime/iTunes.
It's not stated in the system requirements, but I just have this feeling.
If anybody has successfully installed the latest Quicktime/iTunes on a FAT32
partition with Win 2000 or XP please post it here so we can eliminate that as a possible problem.
Thanks
Jim

Hi Rachyl
When Parky Boy said he didn't have the security tab, the only reason I could think of was he had a FAT32 partition.
I gave him instructions on how to convert FAT32 to NTFS.
I'm still waiting to see if it worked for him.
It got me to thinking about how many people may have reinstalled Win 2000 or XP and chose FAT32 as the format.
No security features in FAT32.
I was going to post SFC /Checknow, but many people don't have a Win 2000 or XP CD handy so I didn't.
I hope the conversion works for Parky Boy and QT/iTunes.
I'm patiently wating.
G4 Mac OS X (10.4.3) WIN 2000 /XP

Similar Messages

OMG Please help with Win XP partition issue FAT32 NTFS

I know that there are other posts about this, but I have not been able to find the answers to my problems
I had the issue that others had with not getting the option to format the bootcamp partition during my XP Pro install. I used the FreeDOS solution to format the drive, but I am now left with an 80gb FAT32 partition which is not really what I wanted.
Reading other posts, resizing the partition does not seem to be an option. I guess that I use Winclone to backup my XP partition, wipe out the partition using Bootcamp, but where do I go from here????
A couple of questions:
1) Can a backup of a FAT32 partition be restored to an NTFS partition?
2) How the bl**dy **** do I format the bootcamp partition as NTFS if I do not get the option of formatting during the XP install and FreeDOS wants to format as FAT32.
By the way if anyone has the answer that involves not having to wipe the FAT32 partition but shrink / reduce it to say 15gb and allow me to create a 65gb NTFS partition - there is a big sloppy kiss waiting!!!!
I was hoping that I could just use something like Partition Magic within my 80gb bootcamp partition to resize the FAT32 then create and format the NTFS partition?
Sorry for babbling and thanks for reading and hopfully ending my pain.
Ian.

I have found this http://support.microsoft.com/kb/307881 that allows the conversion of a FAT32 partition to NTFS. . . . looks like I will give this a go tonight.
Ian.

No option to make an NTFS partition

Hello
I try to install Windows XP 32bits SP3 with Bootcamp, but when i get to select partition and i select BOOTCAMP FAT32 partition on 32GB my windows just starts to install. i do not get the option to do an format of disc to NTFS. Windows just starts to install and when my mac reboots all i get is Disc Error and i have to boot back to MAC OS.
Did anyone else have this problem before or?
Tnx to all that replays

It is a bad version of XP if it doesn't stop and ask, that does happen. Heck, some are so bad they wipe out the whole hard drive and use the entire Mac HD partition.
PS: don't ever use Disk Utility to create a partition for Windows XP, it doesn't work and not sure where you came up with that idea. Only Boot Camp Assistant works with XP and where installing Windows on same drive as Mac OS.
The BOOTCAMP partition is MSDOS/FAT32 and a 'proper' Windows installer will give you option to choose where target volume, click on ADVANCED OPTIONS to format or delete and create NTFS partition.

Mount NTFS Partition

Hej!
How can I mount a NTFS partition under Solaris 10?
thx

NTFS = New Tecnology File System is completly different from the FAT32.
FAT and FAT32 is from the old DOS Systems. DOS was removed as a OS on Windows NT. Support for DOS remains in NT as a NTVDM. NT Virtual Dos Machine that runs as a Subprocess on top of the NT. kernel.
There exists a driver for the NTFS somwhere on internet, I tried it a copule of years ago on a Solaris8. The driver was then a readonly driver. I have lost the driver now, but info about it should be possible to find on internet with google or similar.
This applys to localy mounting a NTFS.
When mounting over the network, its different. The filesystem on the network does not use FAT or NTFS.
Insted it uses NETBios (MSB). Samba has a client for this, if I remember correct.
But it would be better install a NFS Server software on the Windows OS.

How to mount SATA Ntfs Partitions on Arch Linux

Please help me mounting sata ntfs partitions.
Here is my fdisk -l :
[kaola@ArchHost ~]$ sudo fdisk -l
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x020e020e
Device Boot Start End Blocks Id System
/dev/sda1 1 371 2980026 82 Linux swap / Solaris
/dev/sda2 * 372 2803 19535040 83 Linux
/dev/sda3 2804 6450 29294527+ 83 Linux
/dev/sda4 6451 6463 104422+ 83 Linux
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd7a23d33
Device Boot Start End Blocks Id System
/dev/sdb1 2 5875 47182905 5 Extended
/dev/sdb2 * 5876 9139 26218080 7 HPFS/NTFS
/dev/sdb5 2 3918 31463271 7 HPFS/NTFS
/dev/sdb6 3919 5875 15719571 7 HPFS/NTFS
Disk /dev/sdc: 4043 MB, 4043308544 bytes
255 heads, 63 sectors/track, 491 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00050ebd
Device Boot Start End Blocks Id System
/dev/sdc1 1 491 3943926 b W95 FAT32
As far as I know, the sata ntfs partitions are those with (sdb#).
I tried mounting one of them but this is what it shows:
[kaola@ArchHost ~]$ sudo mount /dev/sdb6
mount: can't find /dev/sdb6 in /etc/fstab or /etc/mtab
Please help me, this is very annoying compared to ubuntu which does do the job pretty well. By the way, I'm using kde as my DE. Dolphin sees the partitions but cant access.
It says:
An error occured while accessing 'Backup2 HD2', the system responded:
org.freedesktop.Hal.Device.Volume.UnknownFailure: TODO:
have to rethink extra options
Reading some tutorials on ntfs-3g wiki, I've modified my fstab. Still, I can't read the partitions...Please help me, this is my fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
UUID=2167baaa-d1e0-4719-920c-0bc09fa56caa / reiserfs defaults 0 1
UUID=3e2250a0-ac45-458c-ba40-44ddbe8af54d /boot ext2 defaults 0 1
UUID=cbf76343-12cf-4975-9284-3360735be927 /home reiserfs defaults 0 1
UUID=f39da452-efe4-49d0-abd4-bb5246b83b33 swap swap defaults 0 0
/dev/cdrom /media/cdrom auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
UUID=2167baaa-d1e0-4719-920c-0bc09fa56caa / reiserfs defaults 0 1
UUID=3e2250a0-ac45-458c-ba40-44ddbe8af54d /boot ext2 defaults 0 1
UUID=cbf76343-12cf-4975-9284-3360735be927 /home reiserfs defaults 0 1
UUID=f39da452-efe4-49d0-abd4-bb5246b83b33 swap swap defaults 0 0
/dev/sdb1 /mnt/ntfs1 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_US.utf8 0 0
/dev/sdb2 /mnt/ntfs2 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_US.utf8 0 0
/dev/sdb5 /mnt/ntfs3 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_US.utf8 0 0
/dev/sda6 /mnt/ntfs4 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_US.utf8 0 0
Last edited by kaola_linux (2008-10-04 14:51:24)

AD28 wrote:
For seamless integration similar to Ubuntu:
Follow this wiki for ntfs-3g installation and fstab configuration.
For basic on-demand support:
# pacman -Sy ntfs-3g
and mount with:
# mount -t ntfs-3g /dev/sdbX /mnt
Now that did the trick!!!!!
A happy Arch Linux user here!!!!hehee
Any idea how to automate this? I want it to be automatically mounted so that it would be easy to transfer files...Pleasssseeeeee.....Thanks

Windows XP not finding NTFS partition when connected to AEBS

Here is my setup:
I have the current AEBS with firmware 7.4.1 connected to a Windows XP w/SP3. I also have my Macbook Pro running wirelessly as well as another XP laptop. I have wireless connections, a bit slower than I had hoped as I get further away from the AE but its OK.
I also have an Acomdata Pure Drive 1tb connected to the AE. I partitioned the drive half HFS+ and half NTFS. I confirmed and re-confirmed that both partitions are OK by connecting them via USB to all of my machines.
When connected to AEBS, the hard drive appears as a shared device rather than as a hard disk on my Macbook pro, which was not what I expected but is ok. Only the HFS+ partition appears, which is as expected.
However, on both windows machines, the HFS+ partition is also the only one that appears, and the file structure under disk properties shows as FAT32! I've searched and have been unsuccessful in getting the XP machines to locate the NTFS partition. Can anyone help?
Mahalo,
Mike

Thanks again for the replies, and I have a follow up question. Apologies in advance since I am a noob with Macs.
I reformatted my USB drive with one HFS+ and one FAT32 partition. Works great on my Macbook (I formatted using Disk Utility), both partitions are visible as shared drives.
On one of my XP laptops, both partitions also appear, and I am able to copy files to both, even the HFS+ formatted partition. When I check formatting in My Computer, both partitions indicate FAT32. When I check formatting on my Mac, it indicates HFS+ and FAT32, respectively.
I expected that the Mac would be able to use both drives, but I expected that only the FAT32 drive would be write-accessible on the XP. So what did I mess up this time?
Mahalo,
Mike

Where has my NTFS Partition gone in Windows 8.1? Shows in Mavericks fine!

I have set up a new external HDD (USB 3.0) to use on my mac with 3 partitions a Mac Journeled Partition, a FAT32 partition, and an NTFS partition. I set up the portioning in Disk utility and set it to use a GUID partition table. Initially the NTFS partition was created as a FAT32 partition, then reformatted to NTFS through Windows 8.1 This all worked fine until I installed a version of Mac Os X to an External HDD so I can dual boot a test configuration.
Now when I'm in Bootcamped Windows 8.1 the HFS partition and the FAT32 Partition show but not the NTFS one. Looking in Computer Management it shows 2 unallocated partitions where the NTFS one should be. However, when I go into Mac Os x (either installed version the partition is there, and fully readable! I'm very confused as to why Windows can't read the partition! I'd like to try and fix it without losing data or having to reinstall the Mac OS Installation if possible.
Has anyone encountered this before?
Many thanks,
John

Hello and Thanks MeipoXu, Well it's to late! I got frustrated after searching windows and microsoft websites and forums, so, I chatted with a damg geek squad "agent" and he talked me into doing what I knew I could do four hours before I got them
and had him do a remote assistance. Well to make a long story short we faut for a while and he led me to believe there was no other way except to reformat the drive and loose all of my files! I got ahold of them thinking they would have a solutiion to the
problem not reformat and loose everything! I'm very upset with the geek idiots and I've left terrible feedback as I do every time I talk with those idiots. All may not be lost though, I also have a WD MyCloud 3TB network drive and I'm hoping and praying that
most if not all of my files are on it. I sure wish I'd have waited till I got an answer here before I contacted the geeks. I don't know anything about powershell at all, but, lately I've been trying to learn some of the commands and what you can do with it,
and it seems like it would be very useful and I hope I can learn it. It seems very complicated right now and I don't understand it all, I even tried some commands I found on the forum to try to dislodge my drive from the storage space and pool and they did
not work. I typed the command word for word I don't know what I did wrong. I sure want to learn it though it would save me a lot of headaches. Thank you very much for the reply though I just wish I'f have waited to hear from someone on the forum before I contacted
the geeks. Thanks again! Turbo930.

Can't mount ntfs partition

hi.. i am running tiger, have no boot camp, but decided to run windows on it.. i've divided the drive into 2 partitions, mac and fat32. everything looked ok until i formatted the fat32 drive to ntfs using the partition utility on a windows xp install cd. since then, mac doesn't mount the ntfs drive. i wanted to copy my windows via some ntfs driver on my mac, but it doesn't want to mount it and i can't mount it via disk utility either.. any ideas??
thanx much

ok, here's the story:
when i had leopard, i ran also windows xp via boot camp, i remember that when i formatted the windows partition from fat32 (default boot camp filesystem), leopard stopped mounting it after restart. that changed when i actually installed windows and started using it (i am almost sure boot camp made leopard be able to mount it normally (read only though, which changed when i installed mac fuse)). so after boot camp took care of the partition, leopard was able to mount it. now i am having this sort of problem: i am running tiger (downgraded back to it because of some bugs in leopard i dislike pretty much) but i cannot run boot camp any more. i partitioned the disk using disk utility (by default into fat32 fs) before installing of tiger. then i used a windows installation cd to reformat the windows partition to ntfs, and from that point on, i can see the disk in terminal (/dev/disk0s3 as well as in disk utility-unmounted) but i am unable to mount it, nobody knows why (i was able to do so when it was fat32). i have already installed the mac fuse with the ntfs driver, but nothing changed, the partition remains unmounted after reboot... this is what boot camp could handle, but unfortunately i have no boot camp any more... i also tried installing refit, an alternative bootloader, hoping it would help with this issue, but nothing works...
i hope u get what i'm talking about now:)
the only thing i want to do is to mount the ntfs partition, because i have backed my old windows up and just want to copy it back with help of mac fuse.
anyone has any ideas??
thanx a lot

Restored NTFS partitions are no longer bootable?

After using Boot Camp to create a FAT32 partition, I restored an image to that partition from my previous NTFS partition using Disk Utility. The restore was successful except that now my NTFS is no longer bootable. Can anyone help me out?

Don't use Quick Format

How do I write to my boot camp partition with Paragon NTFS that comes with Mountain Lion? Or how do I get my boot camp partition to show up in Paragon's "Available NTFS partitions:" panel like my external hard drive does?

I've just set up boot camp on my MacBookPro with a freshly installed Mountain Lion and Windows 7.
I would like to read and write in both directions from drive to drive if possible. I've hunted around quite a bit to try and work this out, and so far I understand that one can write to or transfer files from one drive to the other with Paragon NTFS among other softwares.
I noticed when I looked in my system preferences the utility "Paragon NTFS for Mac OS X" came with Mountain Lion and it will recognize an external hard drive when I have one plugged in under "Available NTFS partitions:". However, it does not automatically recognize my NTFS boot camp partition nor does it automatically give me write access.
Is the Paragon NTFS that comes with Mountain Lion limited in some way?
Do I still need to purchase and download the software of the same name from Paragon to get the full write privilidges I want or is there something I can do to get the version of Paragon on my MAC to recognize and give me write priviledges to my boot camp partition?
I'm open to all suggestions to get the read / write access between partitions in my boot camped drive.
MacFUSE is also listed in the System Preferences of my machine (it also came with Mountain Lion), if that helps. I'm still working out exactly what each of these is supposed to do and how I can use it to accomplish the task at hand.
My boot camp drive does appear normally in other contexts and in disk utility it indicates that the drive is mounted.
Thank you for any guidance you can give me.

Interesting. Comes with? you didn't have either before? Paragon is commercial and is now v. 10.0, they were the only one keeping updated and was supporting 10.7.4. I would not enable more than one.
For writing to HFS Paragon has theirs but probably give the nod to MacDrive there.
I never do an upgrade to a new OS over the old system, I backup (clone) and format the drive with the new OS and do the install so whatever is there I know is clean and also to keep from carrying around leftovers from years and systems past.
I would assme Paragon is limited. Try their site and knowledge base?
MacDrive
http://www.mediafour.com/updates/macdrive
Paragon HFS
http://www.paragon-software.com/home/hfs-windows/
Paragon NTFS
http://www.macupdate.com/app/mac/26288/ntfs-for-mac-os-x
http://www.paragon-software.com/home/ntfs-mac/

Arch and Win7 cannot open an NTFS partition created by the other

This is almost certainly related to another post where I was struggling to create logical partitions from Windows. Basically, Linux and Minitool Partition Wizard agreed that there were no logical partitions, but the built-in Windows disk utility said there was. I ended up using fdisk from Arch install media, and Minitool and Arch now both saw the logical partitions (Windows shows a big extended partition of free space). I installed Arch just fine, can boot to it and win7... life is good.
Not so much. A key to my setup is having an encrypted partition to share data between OS's. I used TrueCrypt with great success on my former laptop and am now having great difficulty!
Some preliminary information:
# fdisk -l /dev/sda
Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1e6513b3
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 2101247 2099200 1G 7 HPFS/NTFS/exFAT
/dev/sda2 2101248 172433407 170332160 81.2G 7 HPFS/NTFS/exFAT
/dev/sda3 172433408 390537215 218103808 104G 7 HPFS/NTFS/exFAT
/dev/sda4 390537216 500118191 109580976 52.3G 5 Extended
/dev/sda5 390539264 391587839 1048576 512M 83 Linux
/dev/sda6 391589888 500118191 108528304 51.8G 83 Linux
I also went partition by partition to check Minitool's agreement on sectors (they match perfectly with the exception that it doesn't show the extended /dev/sda4 container). I triple checked the Minitool partition info properties as you can't copy and paste from it's window, and pasted the fdisk output to minimize errors. I'm showing a column for mini/Arch for both start/stop sectors, and just subtracted them to make sure I got 0. Appears to be perfect alignment:
| part | start (mini) | start (arch) | diff | | end (mini) | end (arch) | diff |
|------+--------------+--------------+------+---+------------+------------+------|
| sda1 | 2048 | 2048 | 0 | | 2101247 | 2101247 | 0 |
| sda2 | 2101248 | 2101248 | 0 | | 172433407 | 172433407 | 0 |
| sda3 | 172433408 | 172433408 | 0 | | 390537215 | 390537215 | 0 |
| sda4 | 390539264 | 390539264 | 0 | | 391587839 | 391587839 | 0 |
| sda5 | 391589888 | 391589888 | 0 | | 500118191 | 500118191 | 0 |
- Screenshot of how Minitool sees my disk
- Screenshot of how Windows disk utility sees my disk
I used TrueCrypt 7.1a on both OS's. I created a non-system encrypted partition using the GUI on Arch with the AES cipher/sha-512 hash, with filesystem as "none." Once created I did:
$ sudo cryptesetup --type tcrypt open /dev/sda3 vault
That worked fine, which I followed with:
$ sudo mkfs.ntfs /dev/mapper/vault
It initialized the device with zero's and then gave me the success/have a nice day message. Closed the volume and rebooted. When I tried to open the device from win7, I got "Incorrect password or not a TrueCrypt volume." Hmmm. I guess I'll try in reverse. I duplicated the procedure exactly as above from win7, this time having TrueCrypt automatically format with NTFS. All succeeds and I can open the device. Reboot into Arch and I get the same message from TrueCrypt! If I try with cryptsetup, it's "No device header detected with this passphrase."
Next, I tried just doing NTFS with no encryption. From Arch:
$ sudo mkfs.ntfs /dev/sda3
All goes well and I can mount it. I boot into Windows and it's not even listed! I used Minitool to issue it a drive letter, at which point clicking that pops up a windows dialog box asking me if I want to format the disk. Format the partition with NTFS in Windows, reboot into Arch and I get:
[jwhendy@arch_zbook ~]$ sudo mount /dev/sda3 /mnt/scratch/
NTFS signature is missing.
Failed to mount '/dev/sda3': Invalid argument
The device '/dev/sda3' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Doesn't matter if I add "-t ntfs" or "-t ntfs-3g." I get the same result.
Just to add a couple more oddities... when I created the NTFS partition in Arch, I also created a file called vault.tc as a TrueCrypt file-based encrypted container. My thinking was that the issue was with TrueCrypt full-partitions and that I could get around it with a plain partition containing an encrypted file. Reboot into windows and the partition isn't shown (as stated above). From Minitool, if I right click the partition and choose "Explore," it lists the partition contents and there is my vault.tc file. Windows thinks it's unformatted!
I noticed the option to backup/restore a TrueCrypt header, and gave a shot at backing up the working TrueCrypt setup on windows to a flash drive, booting to Arch, and then restoring the /dev/sda3 header from the flash drive file. Arch still couldn't open it.
Lastly, I noticed when I go to select a device to encrypt in TrueCrypt, my logical partitions aren't showing up (just like Windows only sees the end of the disk as free space). I just can't help but think something is tweaked in the partition table... basically:
- TrueCrypt sees what Windows sees
- Arch sees what Minitool sees
How could I go about diagnosing further or fixing the issue. This is driving me crazy!
I'd hate to do this given that I already setup my wm, configs, packages, etc... but my last resort attempt would be to wipe my logical partitions and see if I can at least get the win7 disk utility, minitool, arch, and truecrypt to like each other with respect to /dev/sda1-3... and then try to re-add the logicals afterward and re-install arch? I honestly don't know why this would be any different, but was just a thought. The issues from the other post seem to arise with logical partitions not being recognized the same between win/linux.
Or figure out how to just use primaries (like dedicated boot on a USB drive or something). Or fiddle with growing/shrinking windows to see if I can undo whatever is telling windows where/what things are? Really grasping at straws here.
Last edited by jwhendy (2015-06-10 23:32:22)

Hi Ramesh,
Please install the hotfix package and test the issue again:
http://support.microsoft.com/kb/2817576/en-us
In addition, try uncheck the option “confirm open after download” per:
http://jritmeijer.wordpress.com/2006/08/20/some-files-can-harm-your-computer-if-the-file-information-looks-suspicious-or-you-do-not-fully-trust-the-source-do-not-open-the-file/
Regards,
Rebecca Tu
TechNet Community Support

Easy to install Lion with BootCamp + Win 8 + NTFS partition for data?

Hey, I have a MacBook Pro (2011) currently on OS X 10.6.8, but I bought Lion 10.7 and want to use that.
Here's what I want to do:
* install Lion (fresh, not upgrade)
* install BootCamp
* install Win 8 (DevEd) (for games and some other apps)
And here are my questions:
1) What's the best (free) way to save/"ghost" the current OS so I can quickly get back to that in case something happens when I install Lion?
2) What order do I install BootCamp and Win 8 in? Any fool-proof tutorial for how to do this?
3) If I do a backup with Time Machine as the last thing I do before installing Lion, I just copy the data back from the TM drive after install, right?
4) I would like to use Win 8 and some programs there to read and write to the HFS+ OS X partition - is there a free and/or good way to do that?
5) On PC I can use WinAmp, the great plugin "DeleteCurrentSong" and a shortcut key to delete the currently playing track. Is there a way to do something similar in any program in OS X?
6) If not, would it be possible to - early in the install process - make a big NTFS partition and put most of my data there so it can be accessed from both OS X (with Paragon) and Windows? And Time Machine wouldn't back it up as long as it's NTFS, right?
Thanks a lot for any answers!

Answer to question 1:
a. Get a USB disc the same size or better larger than your internal HD
b. Download Carbon Copy Cloner (free)
c. Clone the internal HD to the external disc
d. Reboot with the 'option' key held down. Choose the external disc to check that the clone was successful and is bootable.
e. If yes, reboot again, hodling down the 'option' key. Choose the internal HDD.
f. Dismount/eject the external HD and disconnect it from your computer.
g. Go to app store and download Lion.
h. When the download is complete, DO NOT run it. First, copy the file (Applications > Lion Install.app) to another location on your disc (the downloads folder will do). This is because after you run the installer it will delete itself from the Applications folder, and you may very well either want/need to do a re-install later without wanting to wait for hours for the download.
i. Run Applications > Lion Install.app

How do I create a Boot Camp partition with Windows & blank NTFS partitions?

I'm trying to create this kind of setup:
OS X partition
Windows 7 partition
blank NTFS partition (no OS)
blank NTFS partition (no OS)
This would be much easier if I created just the OS X partition and the Windows 7 partition with the Boot Camp Assistant tool (done this many times before successfully on other computers). The problem begins when I try to split the Boot Camp partition through the Windows 7 DVD partition manager during setup by deleting the Boot Camp partition, and recreating three partitions from the unallocated space. After installing Windows 7 on one of those new three partitions, I'm getting all kinds of startup errors when I try to install the Boot Camp drivers.
What would the best way to achieve this setup?

Yes, I researched many options for three partition dual boot set ups. After many trials and tribulations, there is a simple method that I have used on multiple MBPs.
1. Run Boot Camp Assistant, as per the Boot Camp Installation and Setup Guide. Once you have Mac OS X and Windows 7 set up, check the partitions and back them up (with Time Machine, and Winclone).
2. Get iPartition, and resize the Mac and Windows partitions to what you want, say 100GB each, and set up your other partitions to the size you want. I put mine "after" the Windows partition, at the end of the disk, and have had no problems. It takes a few minutes to create the bootable CD for iPartition, but you get everything you need to do so from Coriolis Systems. You will need your Mac OS X installl disc.
3. Install Paragon's HFS+ for Windows and NTFS for Mac, and everybody can read and write everything.
4. I have both Time Machine and Norton 360 back up the Data partitions, just in case -- to an external drive, of course.
You can boot to either OS and access any partition.

I am unable to mount my NTFS partition after the last update

I usually mounted my NTFS partition with the "gnome-disk" utility. It works no longer, only if I start it with "sudo". But in this case the mount point will be in a directory called "root" and this cause several problems, eg.: old hardcoded paths stop working in scripts. What can I do to make the gnome-disk utility work as an ordinary user.

Thx, maybe I could use the fstab to mount the partition, am I right? But I don't know how to do it properly, because when I tried it in the past native hungarian characters iny the file and directory names always caused problems. If I somehow could capture the command sequence which the gnome-disk utility passes to the kernel / bash, would be helpful.

Renaming files with invalid characters in their names on NTFS partitions, introduced by operating systems other than Windows

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

NTFS Partition VS Fat32

Similar Messages

Maybe you are looking for