"Andy" <1@2.3> wrote in message
news:v3ih249tg8n3qa2qppcbdfr86kuld4qcp1@4ax.com...
> On Mon, 12 May 2008 14:15:29 +0100, "Seeker" <alec@thefrosts.f2s.com>
> wrote:
>
>
>>
>>Sorry I forget to mention.
>>This will be my second hard drive.
>>As my existing WinXP system disk is FAT32 I have to format this FAT32 too.
> Wrong.
>
>>Also I need FAT32 for access over the network.
> Also wrong.
>
>>
>
> ** Posted from http://www.teranews.com **
"If you have the opportunity to select a system from these to format your
Hard Disk, be aware that these system are not generally forwards-compatible.
To clarify this, Operating Systems installed on Hard drives using FAT16 will
not be able to access files on another Hard Drive (or partition) which has
been formatted using FAT32 or NTFS.
The same can be said for FAT32 and NTFS. However, FAT32 can read FAT16 and
NTFS is clever enough to read both FAT16 and FAT32."
So believing my FAT32 Win XP could not access NTFS partitions I assumed the
same was true over the network.
> I have seen many comments that the file system type is not forward
> compatible,
> I quote from http://www.buildyourown.org.uk/pc-ar.../fdisk-format/
>
> "If you have the opportunity to select a system from these to format
> your Hard Disk, be aware that these system are not generally
> forwards-compatible. To clarify this, Operating Systems installed on
> Hard drives using FAT16 will not be able to access files on another Hard
> Drive (or partition) which has been formatted using FAT32 or NTFS.
>
> The same can be said for FAT32 and NTFS. However, FAT32 can read FAT16
> and NTFS is clever enough to read both FAT16 and FAT32."
>
> So believing my FAT32 Win XP could not access NTFS partitions I assumed
> the same was true over the network.
None of this is true.
The only thing required to access a file system on the base machine is a
driver for it for the OS you are running. Win XP has drivers for all
previous MS file systems, so it can access fat16, fat32, ntfs, out of the
box and there are also hpfs, ext3, and a multitude of other file system
drivers for it.
As for accessing files over a network, all it needs is for the network to
use the same protocol. The file system on either machine is irrelevant
since the file is processed by the local machine and sent over the network
using the network protocol.
So you can mix your winXP drives up with any file system it supports.
Personally, I'd format the new drive with ntfs. Back up the fat32
partitions to it and then reformat the main drive with ntfs, and copy it
back. Fat32 is not designed for really large drives of today and is really
wasteful of space using 32K blocks iirc. Thus using 32K of space minimum
even for a 10 byte file or an extra 32K block for every file on the system
that goes over the 32K boundary by just 1 byte. This means you are
probably wasting 30-50% of your drive space that you could recoup by
changing to ntfs.
On Tue, 13 May 2008 14:53:12 +0100 'Seeker'
wrote this on alt.comp.periphs.mainboard.abit:
>
>"Andy" <1@2.3> wrote in message
>news:v3ih249tg8n3qa2qppcbdfr86kuld4qcp1@4ax.com.. .
>> On Mon, 12 May 2008 14:15:29 +0100, "Seeker" <alec@thefrosts.f2s.com>
>> wrote:
>>
>>
>>>
>>>Sorry I forget to mention.
>>>This will be my second hard drive.
>>>As my existing WinXP system disk is FAT32 I have to format this FAT32 too.
>> Wrong.
>>
>>>Also I need FAT32 for access over the network.
>> Also wrong.
>>
>>>
>>
>> ** Posted from http://www.teranews.com **
>
>I have seen many comments that the file system type is not forward
>compatible,
>I quote from http://www.buildyourown.org.uk/pc-ar.../fdisk-format/
>
>"If you have the opportunity to select a system from these to format your
>Hard Disk, be aware that these system are not generally forwards-compatible.
>To clarify this, Operating Systems installed on Hard drives using FAT16 will
>not be able to access files on another Hard Drive (or partition) which has
>been formatted using FAT32 or NTFS.
>
>The same can be said for FAT32 and NTFS. However, FAT32 can read FAT16 and
>NTFS is clever enough to read both FAT16 and FAT32."
>
>So believing my FAT32 Win XP could not access NTFS partitions I assumed the
>same was true over the network.
That is all true afaik. NTFS is the way to go IMVHO.
On Tue, 13 May 2008 16:12:48 GMT, Wes Newell
<w.newell@TAKEOUTverizon.net> wrote:
>So you can mix your winXP drives up with any file system it supports.
>Personally, I'd format the new drive with ntfs. Back up the fat32
>partitions to it and then reformat the main drive with ntfs, and copy it
>back. Fat32 is not designed for really large drives of today and is really
>wasteful of space using 32K blocks iirc. Thus using 32K of space minimum
>even for a 10 byte file or an extra 32K block for every file on the system
>that goes over the 32K boundary by just 1 byte. This means you are
>probably wasting 30-50% of your drive space that you could recoup by
>changing to ntfs.
I run XP and my backup drive is a 500GB drive formatted in FAT32.
The "FAT 32 wastes space" argument depends on the type of data you're
storing. Most people don't have an abundance of tiny files on their
system. A drive devoted to multimedia (or backups, as in my case)
would waste virtually no space.
FAT32 is the only choice if you plan on accessing the data via other
operating systems such as Linux, or if you plan on manipulating the
data using something like a DOS boot disk (which is why my backup
drive is FAT32... if I need to recover a blown drive, it's a lot
easier to restore from a FAT32 drive using low-level utilities).
And you can't "format the main drive in NTFS and copy back". That
just doesn't work for a boot drive. You *can* use XP's built in
"convert to NTFS" utility, but most people would advise against that
also.
The OP's system is running fine using FAT32 so why suggest he jump
through a bunch of hoops to get to NTFS?
Seeker wrote:
> "Andy" <1@2.3> wrote in message
> news:v3ih249tg8n3qa2qppcbdfr86kuld4qcp1@4ax.com...
>> On Mon, 12 May 2008 14:15:29 +0100, "Seeker" <alec@thefrosts.f2s.com>
>> wrote:
>>
>>
>>> Sorry I forget to mention.
>>> This will be my second hard drive.
>>> As my existing WinXP system disk is FAT32 I have to format this FAT32 too.
>> Wrong.
>>
>>> Also I need FAT32 for access over the network.
>> Also wrong.
>>
>> ** Posted from http://www.teranews.com **
>
> I have seen many comments that the file system type is not forward
> compatible,
> I quote from http://www.buildyourown.org.uk/pc-ar.../fdisk-format/
>
> "If you have the opportunity to select a system from these to format your
> Hard Disk, be aware that these system are not generally forwards-compatible.
> To clarify this, Operating Systems installed on Hard drives using FAT16 will
> not be able to access files on another Hard Drive (or partition) which has
> been formatted using FAT32 or NTFS.
>
> The same can be said for FAT32 and NTFS. However, FAT32 can read FAT16 and
> NTFS is clever enough to read both FAT16 and FAT32."
>
> So believing my FAT32 Win XP could not access NTFS partitions I assumed the
> same was true over the network.
That looks like a very old article meant to keep beginners out of
trouble. There's not really enough there to make informed decisions.
Even the documentation and disk prep software that came with my recent
Seagate were "dumbed down" to keep beginners safe, and failed to provide
info that I needed. The lack of info misled me to think that my new
160GB drive would be fine for Win98 as long as I partitioned it. So I
was happily using it for months, until I learned that some time in the
future my files on it may be trashed.
On Tue, 13 May 2008 16:12:48 GMT 'Wes Newell'
wrote this on alt.comp.periphs.mainboard.abit:
>On Tue, 13 May 2008 14:53:12 +0100, Seeker wrote:
>
>> I have seen many comments that the file system type is not forward
>> compatible,
>> I quote from http://www.buildyourown.org.uk/pc-ar.../fdisk-format/
>>
>> "If you have the opportunity to select a system from these to format
>> your Hard Disk, be aware that these system are not generally
>> forwards-compatible. To clarify this, Operating Systems installed on
>> Hard drives using FAT16 will not be able to access files on another Hard
>> Drive (or partition) which has been formatted using FAT32 or NTFS.
>>
>> The same can be said for FAT32 and NTFS. However, FAT32 can read FAT16
>> and NTFS is clever enough to read both FAT16 and FAT32."
>>
>> So believing my FAT32 Win XP could not access NTFS partitions I assumed
>> the same was true over the network.
>None of this is true.
NTFS and FAT32 are backwards compatible.
They are not forward compatible.
You seem to have a problem understanding what the previous poster
was trying to explain.
On Tue, 13 May 2008 12:10:33 -0700, Beryl
<flyingterrapin@chillybits.org> wrote:
>Seeker wrote:
>> "Andy" <1@2.3> wrote in message
>> news:v3ih249tg8n3qa2qppcbdfr86kuld4qcp1@4ax.com...
>>> On Mon, 12 May 2008 14:15:29 +0100, "Seeker" <alec@thefrosts.f2s.com>
>>> wrote:
>>>
>>>
>>>> Sorry I forget to mention.
>>>> This will be my second hard drive.
>>>> As my existing WinXP system disk is FAT32 I have to format this FAT32 too.
>>> Wrong.
>>>
>>>> Also I need FAT32 for access over the network.
>>> Also wrong.
>>>
>>> ** Posted from http://www.teranews.com **
>>
>> I have seen many comments that the file system type is not forward
>> compatible,
>> I quote from http://www.buildyourown.org.uk/pc-ar.../fdisk-format/
>>
>> "If you have the opportunity to select a system from these to format your
>> Hard Disk, be aware that these system are not generally forwards-compatible.
>> To clarify this, Operating Systems installed on Hard drives using FAT16 will
>> not be able to access files on another Hard Drive (or partition) which has
>> been formatted using FAT32 or NTFS.
>>
>> The same can be said for FAT32 and NTFS. However, FAT32 can read FAT16 and
>> NTFS is clever enough to read both FAT16 and FAT32."
>>
>> So believing my FAT32 Win XP could not access NTFS partitions I assumed the
>> same was true over the network.
>
>That looks like a very old article meant to keep beginners out of
>trouble. There's not really enough there to make informed decisions.
>
>Even the documentation and disk prep software that came with my recent
>Seagate were "dumbed down" to keep beginners safe, and failed to provide
>info that I needed. The lack of info misled me to think that my new
>160GB drive would be fine for Win98 as long as I partitioned it. So I
>was happily using it for months, until I learned that some time in the
>future my files on it may be trashed.
Did you install the updated esdi_506.pdr driver solution??
> On Tue, 13 May 2008 16:12:48 GMT, Wes Newell
> <w.newell@TAKEOUTverizon.net> wrote:
>
>>So you can mix your winXP drives up with any file system it supports.
>>Personally, I'd format the new drive with ntfs. Back up the fat32
>>partitions to it and then reformat the main drive with ntfs, and copy it
>>back. Fat32 is not designed for really large drives of today and is
>>really wasteful of space using 32K blocks iirc. Thus using 32K of space
>>minimum even for a 10 byte file or an extra 32K block for every file on
>>the system that goes over the 32K boundary by just 1 byte. This means
>>you are probably wasting 30-50% of your drive space that you could
>>recoup by changing to ntfs.
>
> I run XP and my backup drive is a 500GB drive formatted in FAT32.
>
My backup is a JFS formatted raid0 pair of drives.
> The "FAT 32 wastes space" argument depends on the type of data you're
> storing. Most people don't have an abundance of tiny files on their
> system. A drive devoted to multimedia (or backups, as in my case) would
> waste virtually no space.
>
True, the larger the file, the less wasted space, but XP has thousands of
files. He's wasting lots of space with just the base install assuming it's
using 32K blocks.
> FAT32 is the only choice if you plan on accessing the data via other
> operating systems such as Linux, or if you plan on manipulating the data
> using something like a DOS boot disk (which is why my backup drive is
> FAT32... if I need to recover a blown drive, it's a lot easier to
> restore from a FAT32 drive using low-level utilities).
>
Well, I don't have that problem since I don't run MS OS's. And I could
read/write NTFS if I had an ntfs partition. :-)
> And you can't "format the main drive in NTFS and copy back". That just
> doesn't work for a boot drive. You *can* use XP's built in "convert to
> NTFS" utility, but most people would advise against that also.
>
So it's even easier than copying the system. BTW, I've copied windows
drives before and didn't have a problem getting them to boot.
> The OP's system is running fine using FAT32 so why suggest he jump
> through a bunch of hoops to get to NTFS?
Jump through what hoops? You just said XP will convert the system to NTFS
automatically.:-)
On Tue, 13 May 2008 21:06:52 +0100, abit.user wrote:
> On Tue, 13 May 2008 16:12:48 GMT 'Wes Newell' wrote this on
> alt.comp.periphs.mainboard.abit:
>
>>On Tue, 13 May 2008 14:53:12 +0100, Seeker wrote:
>>
>>> I have seen many comments that the file system type is not forward
>>> compatible,
>>> I quote from http://www.buildyourown.org.uk/pc-ar.../fdisk-format/
>>>
>>> "If you have the opportunity to select a system from these to format
>>> your Hard Disk, be aware that these system are not generally
>>> forwards-compatible. To clarify this, Operating Systems installed on
>>> Hard drives using FAT16 will not be able to access files on another
>>> Hard Drive (or partition) which has been formatted using FAT32 or
>>> NTFS.
>>>
>>> The same can be said for FAT32 and NTFS. However, FAT32 can read FAT16
>>> and NTFS is clever enough to read both FAT16 and FAT32."
>>>
>>> So believing my FAT32 Win XP could not access NTFS partitions I
>>> assumed the same was true over the network.
>
>
>>None of this is true.
>
> NTFS and FAT32 are backwards compatible. They are not forward
> compatible.
>
> You seem to have a problem understanding what the previous poster was
> trying to explain.
I understand he's running XP, which supports both fat32 and ntfs. There's
nothing else to understand.