Corrupt NTFS filesystem

kony wrote:
On 24 Oct 2006 12:07:53 -0700, wrote:
VWWall wrote:
Citizen Bob wrote:
On 24 Oct 2006 01:02:18 -0700, wrote:

FAT32 max partition size is 30G, which is its biggest limitation. NTFS
is a much more secure and reliable fs as well as being more fully
featured.

This is generally untrue.

UNLESS you set encryption or permissions, NTFS gains nothing
security wise. Maybe he would, but the security is not
better just because of NTFS.

As for reliability, not really. The vast majority of
problems with FAT32, would effect NTFS as well.


Eg FAT has 2 copies of the FAT, and when an error ocurs, as
they do, scandisk just picks one at random and overwrites the other.

If you have errors, fix the problem.

nice idea, but optimistic


50% of the time tis works... and 50% of the time you lose data. NTFS
has 3 copies, so this problem doesnt happen. FAT has no password
security system, ntfs does, so fat is 100% accessible to viri and any
user.

Where does a virus tend to put itself? OS partition. Are
you seriously claiming everyone with NTFS on Winxp, has
never had a virus on their OS partition?

Never claimed any such thing.


Maybe you dont need the features of ntfs and fat32's limitations arent
a problem. FAT32 does give more OS options than ntfs, handy if dual
booting, running dos apps, or swapping discs with winDOS systems.

I'm not suggesting FAT32 is better than NTFS, but
practically speaking everyone repeats the marketing blurb
you did, too, without really considering the application,
whether it'll matter.

OK I'll accept most of what you say. I've mostly stayed with fat for
compatibility reasons. I guess the experienced difference is down to os
more than fs, fat has not proved robust.


NT

On Thu, 26 Oct 2006 05:25:47 +1000, "Rod Speed"
wrote:

I'd cut to the chase and move to XP.
Install that on one of your spare drives, apply SP2 and the online updates.

I will consider it.

Install all those apps, dont worry about the settings/config stuff for those.

What apps are you talking about? What exactly do you mean by
"install"?

Use the files and settings transfer wizard in XP to get the settings
and config stuff and files from the 2K install you are currently using.

I presume this is a new version of the IPU.

See how you like that XP install, particularly that the wizard has got
all the settings etc across fine.

Is there an easy way to do that or do I have to test each app one at a
time?

If they are mostly fine and it just hasnt
got the settings for a few apps across, do those manually, if necessary
repeatedly rebooting between 2K and XP to check the original settings etc.

I can handle manually installing a few apps.

Once its working fine, break out the champagne and get on with your 'life'

My life is already as "gotten on with" as it can get.


--

"Nothing in the world can take the place of perseverence. Talent
will not; nothing is more common than unsuccessful men with talent.
Genius will not; unrewarded genius is almost a proverb. Education
will not; the world is full of educated derelicts. Persistence and
determination alone are omnipotent."
--Calvin Coolidge

On Wed, 25 Oct 2006 19:57:01 -0400, kony wrote:

You might take it the other way 'round though, get the clean
Win2k SP4 installation working and before trying to change
it, first compare it... for example, what's sitting in your
system32/drivers folder, if all the hardware works on the
new installation, take a hard look at what's *extra* on your
old installation.

That's as much work, if not more, than just reinstalling everything.

If I screw up even one Registry Key, it could impact the behavior of
the new system and I'd be back where I started.

I am still testing this new NTFS filesystem, the one I copied
everything in from the FAT32 partition. Thus far it has not gotten
corrupted. Maybe there was some kind of screwball entity in the
pagefile or MFT and by creating a new NTFS partition I got rid of it.

One thing I do notice is that Windows loads faster now. But it still
creates two devices for each partition which show up in defraggers but
not Disk Management.


--

"Nothing in the world can take the place of perseverence. Talent
will not; nothing is more common than unsuccessful men with talent.
Genius will not; unrewarded genius is almost a proverb. Education
will not; the world is full of educated derelicts. Persistence and
determination alone are omnipotent."
--Calvin Coolidge

On Thu, 26 Oct 2006 05:17:16 +1000, "Rod Speed"
wrote:

since changing to FAT32 fixed
the corruption but not the extra entry for each partition.

I di dnot test the FAT32 filesystem long enough to be certain that it
fixed the corruption problem. Of course, there can be no "NTFS
corruption" with a FAT32 partition.

Now that I am using a new NTFS partition, we will see if it gets
corrupted. It takes a week or two to make sure.

A retrospective abortion may well be the only solution.

That is not a nice thing to say about my son.

That was a joke, Joyce.

It's not funny. It's sick.

Obviously you do not have a son you can be proud of. Pity you.


--

"Nothing in the world can take the place of perseverence. Talent
will not; nothing is more common than unsuccessful men with talent.
Genius will not; unrewarded genius is almost a proverb. Education
will not; the world is full of educated derelicts. Persistence and
determination alone are omnipotent."
--Calvin Coolidge

Citizen Bob wrote
Rod Speed wrote

since changing to FAT32 fixed the corruption
but not the extra entry for each partition.

I did not test the FAT32 filesystem long enough
to be certain that it fixed the corruption problem.

Why not when that involves running chkdsk ?

Of course, there can be no "NTFS corruption" with a FAT32 partition.

Sure.

Now that I am using a new NTFS partition, we will see if
it gets corrupted. It takes a week or two to make sure.

No it doesnt if you run chkdsk.

A retrospective abortion may well be the only solution.

That is not a nice thing to say about my son.

That was a joke, Joyce.

It's not funny. It's sick.

That was a joke, Joyce.

Obviously you do not have a son you can be proud of. Pity you.

That was a joke, Joyce.

Citizen Bob wrote
Rod Speed wrote

I'd cut to the chase and move to XP.
Install that on one of your spare drives,
apply SP2 and the online updates.

I will consider it.

Install all those apps, dont worry about the settings/config stuff for those.

What apps are you talking about?

All those you have got installed.

What exactly do you mean by "install"?

You must know what installing apps is about.

Use the files and settings transfer wizard in XP to get the settings
and config stuff and files from the 2K install you are currently using.

I presume this is a new version of the IPU.

Nope.

See how you like that XP install, particularly that
the wizard has got all the settings etc across fine.

Is there an easy way to do that

Nope.

or do I have to test each app one at a time?

Yep.

If they are mostly fine and it just hasnt got the settings for
a few apps across, do those manually, if necessary repeatedly
rebooting between 2K and XP to check the original settings etc.

I can handle manually installing a few apps.

You should be able to handle manually installing all those apps.

Not a shred of rocket science required at all.

Once its working fine, break out the champagne and get on with your 'life'

My life is already as "gotten on with" as it can get.

Easy to claim when you are crippling along using a
****ed install of 2K when the world has moved on.

On 26 Oct 2006 00:17:27 -0700, wrote:

kony wrote:
On 24 Oct 2006 12:07:53 -0700, wrote:
VWWall wrote:
Citizen Bob wrote:
On 24 Oct 2006 01:02:18 -0700, wrote:

FAT32 max partition size is 30G, which is its biggest limitation. NTFS
is a much more secure and reliable fs as well as being more fully
featured.

This is generally untrue.

UNLESS you set encryption or permissions, NTFS gains nothing
security wise. Maybe he would, but the security is not
better just because of NTFS.

As for reliability, not really. The vast majority of
problems with FAT32, would effect NTFS as well.


Eg FAT has 2 copies of the FAT, and when an error ocurs, as
they do, scandisk just picks one at random and overwrites the other.

If you have errors, fix the problem.

nice idea, but optimistic

Not at all, NTFS is not a solution to a serious problem like
continual corruption of your filesystem. Optimistic would
be hoping that if you run NTFS, somehow the machine will
decide to only corrupt tables and nothing more.

On Thu, 26 Oct 2006 08:40:16 GMT, (Citizen Bob)
wrote:

On Wed, 25 Oct 2006 19:57:01 -0400, kony wrote:

You might take it the other way 'round though, get the clean
Win2k SP4 installation working and before trying to change
it, first compare it... for example, what's sitting in your
system32/drivers folder, if all the hardware works on the
new installation, take a hard look at what's *extra* on your
old installation.

That's as much work, if not more, than just reinstalling everything.


Define work? Time or what?
It's the computer doing it, automated, right now I could
export the 3 keys, copy the program files folders, and
compare files and Device Manager entries in under 10
minutes, maybe more than 10 minutes to copy 100's of apps if
it was being done over a slow LAN instead of drive to drive.

You do understand that to export registry entries, you dont'
select each individual one, you highlight the subkey and all
children under that subkey are exported with one go.
Exporting the keys I'd mentioned and merging them takes
under 1 minute and maybe 20 mouse clicks (grand total for
mundane things like choosing where to save the files, etc).



If I screw up even one Registry Key, it could impact the behavior of
the new system and I'd be back where I started.

Regedit has this feature, for this purpose, so what can I
say? It's like telling you to print something and you
write "what if I screw up the printing".

On Thu, 26 Oct 2006 08:56:09 -0400, kony wrote:

It's the computer doing it, automated, right now I could
export the 3 keys,

Which 3 keys - my Registry has 5 hive keys.

I must have missed something along the way, because I do not see how
exporting hive keys is going to do any good. If the Registry is
screwed up, then exporting hive keys is going to carry the screwed up
parts along.


--

"Nothing in the world can take the place of perseverence. Talent
will not; nothing is more common than unsuccessful men with talent.
Genius will not; unrewarded genius is almost a proverb. Education
will not; the world is full of educated derelicts. Persistence and
determination alone are omnipotent."
--Calvin Coolidge

On Thu, 26 Oct 2006 20:21:38 +1000, "Rod Speed"
wrote:

I did not test the FAT32 filesystem long enough
to be certain that it fixed the corruption problem.

Why not when that involves running chkdsk ?

I ran chkdsk. The corruption problem occurs seemingly at random. The
longer I go between reboots, the more likely corruption is. I have
gone as long as a week with no problems only to have it back again on
the next day.

Now that I am using a new NTFS partition, we will see if
it gets corrupted. It takes a week or two to make sure.

No it doesnt if you run chkdsk.

You don't seem to understand the exact nature of this problem. I have
to reboot to run chkdsk, and that is when the corruption shows up. It
does not show up unless I reboot.

Ironically, if the corruption occurs, Win2K runs chkdsk for me at boot
time. Sometimes the corruption is so extensive that I get a BSOD.
That's when I have to mount the disk as D: and run chkdsk from another
boot disk. When that happens chkdsk spews forth page after page of
security descripters for kazillions of files that are presumably
corrupted too.

I have always been able to recover with one exception involving a
BSOD. That one was so bad the disk would not mount in Win2K, so
obviously I could not run chkdsk.


--

"Nothing in the world can take the place of perseverence. Talent
will not; nothing is more common than unsuccessful men with talent.
Genius will not; unrewarded genius is almost a proverb. Education
will not; the world is full of educated derelicts. Persistence and
determination alone are omnipotent."
--Calvin Coolidge