Bill Ridgeway
> Is it considered safe to convert a FAT32 volume to NTFS (having first made
> a backup, of course)?
Yes.
http://aumha.org/win5/a/ntfscvt.htm - Converting FAT32 to NTFS by Alex
Nichol
Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ
Very safe, but a backup is always good to have in case something goes wrong.
__
http://www.bootstrike.com/ComputerService/
Singapore Computer Home Remote On-Site Repair Service
"Bill Ridgeway" <in...@1001solutions.co.uk> wrote in message
news:eVMiiiW%23JHA...@TK2MSFTNGP03.phx.gbl...
Exactly what you said, reverse the first two words and change the question
mark to a period.
--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
The consensus of opinion confirms my view that it IS safe to convert a FAT32
volume to NTFS. OK now that's been established now for the crunch question.
I converted my Garmin SatNav (mass storage device) in the expectation it
would increase the speed of operation - as it normally does. The outcome
was a SatNav which failed to boot up. I can only assume that the cause was
the conversion to NTFS - unless, by co-incidence, something else was in
play.
Is there something peculiar to mass storage devices that would cause this
problem?
Bill Ridgeway
The operating system that Garmin uses most likely does not read NTFS
formatted drives. This is the case with most portable devices. You will need
to move all data out, format to FAT32 and move the data back in.
By 'safe', we meant that the data would not get corrupted during the
conversion process and XP would still be able to boot up with a drive
converted to NTFS from FAT.
__
http://www.bootstrike.com/ComputerService/
Singapore Computer Home Remote On-Site Repair Service
"Bill Ridgeway" <in...@1001solutions.co.uk> wrote in message
news:ujAakHZ%23JH...@TK2MSFTNGP05.phx.gbl...
Bill Ridgeway
"Singapore Computer Service" <singaporecom...@bootstrike.com>
wrote in message news:u2Z4hUZ%23JHA...@TK2MSFTNGP04.phx.gbl...
In most cases, yes.
You can safely convert your current hard drive to NTFS whenever
desired, without having to format the partition and reinstall
everything. As always when performing any serious changes, back up any
important data before proceeding, just in case. A little advance
preparation is also strongly recommended, so you can avoid any
performance hits caused by the default cluster size:
Converting FAT32 to NTFS in Windows
http://www.aumha.org/a/ntfscvt.htm
--
Bruce Chambers
Help us help you:
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/default.aspx/kb/555375
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. ~Benjamin Franklin
Many people would rather die than think; in fact, most do. ~Bertrand Russell
The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot
By default, user-permissions will be added, which may have implications if
there are shared folders within userprofiles. If you don't want this to
happen, add the /nosecurity switch.
Anteaus wrote:
> I've yet to have the conversion process go wrong. A powercut could
> be serious, though. So don't try it whilst Thor is doing his
> hammer-workout!
>
> By default, user-permissions will be added, which may have
> implications if there are shared folders within userprofiles. If
> you don't want this to happen, add the /nosecurity switch.
In this case - it was not the conversion process that went awry - but
converting somehting that should not have been converted.
In other words - a poor decision due to lack of knowledge due to lack of
research. ;-)
Entire conversation:
http://groups.google.com/group/microsoft.public.windowsxp.hardware/browse_frm/thread/b31f5d95412f591/ff2895fb1347fb95
Relevant section below...
Bill Ridgeway wrote:
> The consensus of opinion confirms my view that it IS safe to
> convert a FAT32 volume to NTFS. OK now that's been established now
> for the crunch question. I converted my Garmin SatNav (mass storage
> device) in the expectation it would increase the speed of operation
> - as it normally does. The outcome was a SatNav which failed to
> boot up. I can only assume that the cause was the conversion to
> NTFS - unless, by co-incidence, something else was in play.
>
> Is there something peculiar to mass storage devices that would
> cause this problem?
So converting your third party device (like a Garmin) to NTFS is bad -
because it is unlikely said device is running an application that would be
able to read NTFS. ;-)