Install Windows Xp Ntfs Or Fat32

Install Windows Xp Ntfs Or Fat32

Install Windows Xp Ntfs Or Fat32 Average ratng: 4,8/5 2743 votes

A bootable USB key is a handy tool for a variety of purposes. Most of the people use BartPE to install light-weight windows on their USB key. Booting from 2GB+ (4/8/16GB) FAT32 formatted flash disk (thumb-drive) needs a work-around procedure. Jul 16, 2013  Microsoft introduced NTFS in 1993, as a component of the corporate-oriented Windows NT 3.1 and then Windows 2000, though it didn't become common on consumer PCs until Windows XP in 2001.

OK, I got a box with XP pro already on it in NTFS file sys.Needs to be redone, a new install. I learned the hard way that I can't use a DOS boot disk to FDISK then format the HD, because xp won't see it. So I boot off the XP CD. I agree to the sign your first born and all life to Bill aggrement.Known to some as F8.I get to the option where I should be able to choose which filesystem I want to format with an I only get a NTFS option.

No FAT choice. And I have no clue as to why?The PC was already NTFS, but that should not make any difference at this point in the setup should it?Could someone please explain what is happening here? And how I can get the FAT option to format it to?Thanks I appreciate any help sent my wayBpeace be with you. Well, U have given me the closest answer that I can sink my teeth into. But I am still at a loss. I got it working, thats not the problem, I just still do not understand what U R saying.

I assumed that as long as you were using the XP CD to do the formating, and install, it would see either FAT or NTFS? During the install, it (XP) gives u the option to del. The partition. Obviously U R correct, because it did not give me the option, I just thought it should, I guess. It would have made more sense to me had I had NT4 and tried to load 98, with diff file systems.Hey, I dont know if any of that made sense, but to make it simple, I thank you for your time.(iirc, the del comes right before the format opt.)-:peace be with you.

You must have run into an unknown problem while doing this, because I've used a standard Win98 boot disk and the FDISK command to create partitions many times in the past before installing WinXP. Just be certain that you add no switches to the FORMAT command (such as /s) because you do not want system files to be transferred off the floppy. This will result in two operating systems showing up in the boot.ini file, which you'd have to edit later on.

This could also create some confusion during the installation about where the OS should be installed, if WinXP 'thinks' Win98 or another operating system is already present on the hard drive.Note: I usually create a primary, active DOS partition of 5-7GB when installing WinXP. With the assumption in mind beforehand that most large applications (such as games) will be installed to a drive letter other than C.Note: FDISK has problems with partitions over 137GB in size, because DOS doesn't support 48-bit logical block addressing.Check out this guide to brush up on the instructions for how to use FDISK correctly:FDISK SIMULATIONAnd be sure that your boot disk contains the latest version of FDISK:FDISK Does Not Recognize Full Size of Hard Disks Larger than 64 GB. One, if the partition you've created is over 32GB in size, the only file system option will be NTFS.Limitations of the FAT32 File System in Windows XPAnd so, if during the installation, WinXP detects a partition over 32GB in size that is already FAT32, you can't allow the OS CD to format the partition again, or you'll end up with NTFS.

You have to choose to leave the file system intact, and then choose the first option 'To set up Windows XP on the selected item, press ENTER.' You really should have seen an option during the WinXP setup to delete or create a new partition as shown on this page:Partitioning A Blank Hard Drive During XP InstallationNote: If this is a proprietary system, you might find it best to download and create a floppy disk with tools from the hard drive manufacturer to low level format (actually, a middle level format that writes ones and zeros to the drive) the disk before creating new partitions. The hard drive might have a hidden partition that contains files for system recovery, which really should be removed.Once the drive has been basically wiped clean, use FDISK to create your partitions, and format the primary, active partition where the OS will be installed. If you have no program such as Partition Magic, format all partitions that will be FAT32 before the OS installation, because WinXP has no option from within the GUI to format partitions over 32GB in size, either. It's not just something that happens during setup.

However, if you have a third-party disk partitioning program, you can format other partitions at a later time.Remember that the entire hard drive must be partitioned off with FDISK, regardless of the size of the primary partition. Primary, extended, and then logical drives. And if you remove them, you have to delete them in the order of creation. In other words, logical, extended, and then primary. And the primary partition must be set as active for everything to go smoothly.Questions?ToeyMy System RigsBTVILLARIN.com - Your Computer Questions Answered. I think Klutz has the real cause.

You say you loaded the cd and started going then tried to format the existing partion-created in ntfs (New Technology File System). A NTFS partion won't see FAT (File Allocation Table). You must delete the partion and creat a partion and then format it in FAT (recommend FAT32). Think of it like this, your ntfs partion speaks French, you are trying to communicate to it in English (FAT)-it won't understand. Toeham is correct in what he is saying, I just got the feeling it was a little over your head. If it wasn't, please forgive me I didn't mean to insult your intelligence. Obviously, the user really wasn't paying that much attention to the set up, and missed the point where the partition could be deleted, and a new one created.To my way of thinking, this means the only partition currently on the disk was NTFS.

And if it was 137GB or better, there would be no option for FAT or FAT32.The two more remote possibilities could be that no partition was detected, or the current partition information was invalid. Again, forcing Windows to be installed in a new, single, large partition, due to lack of user intervention during the process.Klutz said. That's not only not true, but it's a weird statement, if you give it some thought. It's not the file system that determines what kind of partitions are 'visible', so to speak, whether from the command line, or from within a GUI.Two examples. Lets say the disk had two partitions, with one being NTFS, and the other FAT16. Windows NT 4.0 is installed in a 2GB FAT16 partition. Are both partitions visible from within the GUI?

Because the operating system supports both kind of file systems.Now. Lets assume the disk has a single NTFS 5 partition.

The system is booted with a Win98 boot disk. Is the partition visible?Yes.It will show up as being a non-DOS partition. Occasionally, with older versions of FDISK, it could be misidentified as an HPFS partition, with read-only access.Now.

Here's the important question: can FDISK delete a non-DOS partition?Yes. This option is available, as shown on this page.I also wish to make this clear. Any Windows operating system meant for home use that supports NTFS can also see and use a FAT32 or FAT16 partition.The only truly important aspect of this entire endeavor is that DOS cannot create or format a NTFS partition, and that WinXP cannot re-format an NTFS partition as FAT or FAT32 which seems to be what everyone was attempting to say, in a circuitous manner, of sorts. At least, that's what appears to be happening in the thread.The type of partition that should be created is entirely dependent on what the operating system environment can use and support.I hope you understand, this post is just about clarity, and nothing against anyone's intelligence.

If it so happens that my original post was over the user's head, I'll just go right on and apologize for being obtuse, although if the user clicked on the links I provided, everything should have been made clear, with only a few minutes of study. Which really is my point. Education is more important than just explaining something, bit by bit, as if the user is incapable of rational, constructive thought.If the latter is the case, then nothing either you OR I can say is going to make difference. That's just beating a dead horse for refusing to drink.

Some things are just a waste of time and energy.In the interests of science, here's a chart you might find useful:PC Operating System and File System Cross-ReferenceAnd another link, just to complete the preceding information: q310561Later.ToeyMy System RigsBTVILLARIN.com - Your Computer Questions Answered.

Join GitHub today

GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.

Sign up New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments

commented Nov 12, 2016

Having checked and understood the following:

Could you please clarify why is NTFS the default for BIOS mode and FAT32 the default for UEFI?

Top runescape ps. Runescape Private Servers. RSPS list containing the most popular servers ranked by players. Choose from our topsite the most popular runescape private server to play online. The auction for rank 1 to 3 is now open: Place your bid. Toggle navigation New servers. All Versions.

Is this made as an attempt to avoid the firmware reading the EFI files when it is created in BIOS mode?

Thanks!

commented Nov 12, 2016

NTFS can't (usually) be read by UEFI, except if you add a driver (which Rufus can do through UEFI:NTFS).

So by using NTFS, and not adding the driver, Rufus can enforce BIOS or UEFi-CSM booting, on systems that would have been able to boot the USB in pure UEFI mode otherwise.

Also, the BIG advantage of using NTFS is you're not limited to 4GB when it comes to the install.wim.

I'd rather not have to go through a long speech, with people who might not be that computer literate, about limitations of FAT32.

I believe the current defaults are both NTFS for BIOS and UEFI, though I allow FAT32 for UEFI in case the user wants it, and there doesn't exist a large file.

Anyway, you'd better believe that Rufus always tries to pick the option that is best for you. If Rufus picks a file system, then you really ought to stick with that one, unless you know what you're doing.

Hope that answers your questions.

closed this Nov 12, 2016

commented Nov 13, 2016

@pbatard Thank you so much for the clarification. And thank you again for Rufus.

Just a point, currently if you select BIOS, NTFS gets selected, and if you select UEFI then FAT32 gets selected. Anyway FAT32 always shows as '(default)', which is a little being confusing since Rufus is selecting one and calling default the other.

bot commented Apr 7, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

bot locked and limited conversation to collaborators Apr 7, 2019
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.