Re: Format a 60 gig in win 2000
Re: Format a 60 gig in win 2000
[ Follow Ups ] [ Post Followups ] [ FAQ ] [ Back to Messages ]
Posted by Claudia on August 12, 2002 at 14:05:56:
In Reply to: Format a 60 gig in win 2000 posted by Marc on August 12, 2002 at 10:43:29:
: Just switched from Mac and I'm a bit confused. Windows 2000 doesn't format disks over 32 gig? Is there a way around this? I just bought a Maxtor 60 gig, and their Maxwhatever software won't format a FAT32 disk over 32 megs. Thanks in advance.
Regarding your questions, please read the following excerpt taken from content at Anantech.com
The following limitations exist using the FAT32 file system with Windows 2000 and Windows XP:
"Clusters cannot be 64 kilobytes (KB) or larger. If clusters were 64 KB or larger, some programs (such as Setup programs) might calculate disk space incorrectly.
A volume must contain at least 65,527 clusters to use the FAT32 file system. You cannot increase the cluster size on a volume using the FAT32 file system so that it ends up with less than 65,527 clusters.
The maximum possible number of clusters on a volume using the FAT32 file system is 268,435,445. With a maximum of 32 KB per cluster with space for the file allocation table (FAT), this equates to a maximum disk size of approximately 8 terabytes (TB).
The ScanDisk tool included with Microsoft Windows 95 and Microsoft Windows 98 is a 16-bit program. Such programs have a single memory block maximum allocation size of 16 MB less 64 KB. Therefore, the Windows 95/98 ScanDisk tool cannot process volumes using the FAT32 file system that have a FAT larger than 16 MB less 64 KB in size. A FAT entry on a volume using the FAT32 file system uses 4 bytes, so ScanDisk cannot process the FAT on a volume using the FAT32 file system that defines more than 4,177,920 clusters (including the two reserved clusters). Including the FATs themselves, this works out, at the maximum of 32 KB per cluster, to a volume size of 127.53 gigabytes (GB).
You cannot decrease the cluster size on a volume using the FAT32 file system so that the FAT ends up larger than 16 MB less 64 KB in size.
You cannot format a volume larger than 32 GB in size using the FAT32 file system in Win2K/XP. The Win2K/XP FastFAT driver can mount and support volumes larger than 32 GB that use the FAT32 file system (subject to the other limits), but you cannot create one using the Format tool. This behaviour is by design. Microsoft recommends using NTFS for partitions greater than 32GB.
If you need to format a FAT32 partition greater than 32GB, you will need to do it under Windows 98/SE/ME.
NTFS is the native file system that Windows 2000 and Windows XP uses.
Security is one of the most often touted advantages of NTFS: the administrator can assign various rights to each file and/or directory on an NTFS partition. Rights can be assigned according to individual users or groups of users, allowing or denying reading, writing, execution, deletion, and other attributes.
One key advantage of NTFS is that it is a recoverable file system because it keeps track of transactions against the file system. When a CHKDSK is performed on FAT32, the consistency of pointers within the directory, allocation, and file tables is being checked. Under NTFS, a log of transactions against these components is maintained so that CHKDSK need only roll back transactions to the last commit point in order to recover consistency within the file system. Under FAT, if a sector that is the location of one of the file system's special objects fails, then a single sector failure will occur. NTFS avoids this in two ways: first, by not using special objects on the disk and tracking and protecting all objects that are on the disk. Secondly, under NTFS, multiple copies (the number depends on the volume size) of the Master File Table are kept. The role of the MFT is critical in NTFS, and it is easily fragmented: regular use of a good defragmentation tool is recommended. Programs such as Diskeeper, PerfectDisk and O&O Defrag will do the job. The Defragmentation Tool that ships with Win2K and WinXP DOES NOT defrag the MFT.
Another key feature of NTFS is the ability to encrypt files and directories; this process is transparent to the user. Win2K/XP includes the ability to encrypt data directly on volumes that use the NTFS file system so that the data cannot be used by any other user. Files and folders can be encrypted by setting an attribute in the object's Properties dialog box. The Encrypting File System (EFS)is the file encryption technology Microsoft uses to encrypt data directly on volumes that use the NTFS file system. You can use the encrypted data the same way you use non-encrypted data. In addition, you can configure permissions for your encrypted data to prevent unauthorized use. Someone who does not have the correct permissions receives an Access Denied error message if they try to open, copy, move, or rename an encrypted file or folder.
NTFS also has a disk quota system, where disk space can be allocated to different users: again this is transparent, the user simply sees the disk space available to them. Administrators can limit the amount of disk space users can consume on a per-volume basis. The three quota levels are: Off, Tracking, and Enforced.
As drive sizes and the sheer number of files on a partition increases, NTFS's performance does not degrade. On partitions or directories with several thousands of files, FAT32 operations slow to a crawl.
Mounted drives, also known as volume mount points or drive paths, are volumes attached to an empty folder on an NTFS volume. Mounted drives function the same way as any other volume, but are assigned a label or name instead of a drive letter. Mounted drives are robust against system changes that occur when devices are added or removed from a computer. They are not subject to the 26-volume limit imposed by drive letters, so you can use them for access to more than 26 volumes on your computer.
You can use the fsutil hardlink create command to create hard links. A hard link is an NTFS-based link to a given file. When you create a hard link to a file on an NTFS volume, NTFS adds a directory entry for the hard link without duplicating the original file. You can use the same file name as the original file but appear in different folders; use different file names from the original file but appear in the same folder and use different file names from the original file and appear in different folders.
Sparse files provide a method of saving disk space for files that contain meaningful data as well as large sections of data composed of zeros. If an NTFS file is marked as sparse, then NTFS allocates disk clusters only for the data explicitly specified by the application. Non-specified ranges of the file are represented by non-allocated space on the disk. When a sparse file is read from allocated ranges, the data is returned as it was stored. Data read from non-allocated ranges is returned as zeros. An example of a program that uses sparse files is Indexing Service, which stores its catalogs as sparse files on NTFS volumes.
Finally, if you do a lot of file searching, the indexing feature greatly speeds up searches by maintaining an index of all files on a drive.
All of the above does have its impact on performance though, and it is recommended that you disable any features that are not needed if you use NTFS. If you encounter problems, remember that you will not have the comfort of being able to boot into DOS: installation of Microsoft's Recovery Console, or some other recovery software is recommended.
You can access the Recovery Console from Win2K/XP's boot menu, or selecting Repair when you boot up from the Win2K/XP CDROM.
From the above, it can be seen that NTFS is the better file system with many advantages over FAT32. In most cases where Win2K is going to be the only Operating System, it would be best to use NTFS. However, there are times when you should consider FAT32.
If you're setting up a dual-boot configuration, you should probably use FAT or FAT32.
If you're dual booting Win2K/XP and another operating system, choose a file system based on the other operating system, using the following criteria:
Format the partition as FAT if the installation partition is smaller than 2 gigabytes (GB), or if you're dual booting Win2K/XP with MS-DOSŪ, Windows 3.1, Windows 95, Windows 98, or Windows NT.
Use FAT32 for use on partitions that are 2 GB or larger. If you choose to format using FAT during Win2K/XP Setup and your partition is greater than 2 GB, Setup automatically formats it as FAT32.
If you're using a dual-boot configuration (using both Win2K/XP and another operating system on the same computer), you may not be able to gain access to files on NTFS partitions from the other operating system on your computer. For this reason, you should probably use FAT32 or FAT if you want a dual-boot configuration. The NTFS used by Win2K/XP is not compatible with the version used by Windows NT4. There are programmes available that will make NTFS partitions accessible under Windows 98/ME such as NTFS for Win98 and NTFSDOS Professsional Edition.
Note that FDISK in Win98 has troubles with drives greater than 64GB. For more information and an update to FDISK.EXE, please see this page at Microsoft.
Also note that Windows 95 WILL NOT support drives larger than 32GB in size."
More info can be obtained via the site or by conducting a search via a search engine or Microsoft Knowledge Base.
Post a Followup