Thee clean re-instals and still one major problem ... need some 'expert' advice please

NTFS does not mess with FAT32 and vice versa.

They are seperated cleanly at a very, very low level in Windows.

- JB

Why don't you tell how your drives are configured? IDE, or SATA which one
is master or are you using cable select with the 80 pin cable, etc.

Clark

"GeoffP" <> wrote in message
news:...
> Have clean installed x86 three times now on different partitions/hard
> disks. I appear to be one of the 'lucky' ones as on each occasion
> everything has worked just as it should (printer, network, scanner,
> internet) but have persistent 'corrupt disk/file' after running Vista
> after each installation and in the process of running chkdsk as advised I
> am losing files (some critical some not so critical).
>
> I'm trying to troubleshoot the problem and although both drives are fairly
> new (Maxtors & Seagate drives), I have checked the physical condition of
> each hard disk with the manufacturers software and independent software
> and no signs of failing disks, and have fitted new cables, which appears
> to eliminate a hardware problem. No one in these groups appears to be
> experiencing a similar problem, so that appears to eliminate a Vista 'bug'
> but has been reported just in case.
>
> I know little or nothing about NTFS, but could some of you knowledgeable
> people out there tell me if the NTFS file system is like to be affected by
> other drives/partitions on the system being FAT32 (a hangover from days of
> a three-way boot to Win98SE/Win2000 & WinXP Pro). I have been assured that
> they should live together in harmony, but as I am rapidly running out of
> ideas wondered if Vista's accessing of the other drives could be having an
> adverse effect on Vista itself.
>
> Any advice would be appreciated
>
>
> GeoffP
>
>
>
> ---
> avast! Antivirus: Outbound message clean.
> Virus Database (VPS): 0626-2, 28/06/2006
> Tested on: 29/06/2006 13:44:10
> avast! - copyright (c) 1988-2006 ALWIL Software.
> http://www.avast.com
>
>
>

If windows vista notices something wrong with your hard disks or if it is
having trouble writing data, it will log it in the event log.

Start -> Control Panel -> System and Maintenance -> Administrative Tools ->
Event Viewer

Expand Windows Logs, then System, and look for the source to be NTFS or
something related to hard disks, and see if you have any errors.

I can only speculate as to the problem at this point; could be a hardware
error, a bug in the device driver that controls your hard disk, or hardware
malfunction are my guesses.

- JB

Apparently in all your troubles your clock somehow got set to the wrong
date.

--
Kerry
MS-MVP Windows - Shell/User

GeoffP wrote:
> Have clean installed x86 three times now on different partitions/hard
> disks. I appear to be one of the 'lucky' ones as on each occasion
> everything has worked just as it should (printer, network, scanner,
> internet) but have persistent 'corrupt disk/file' after running Vista
> after each installation and in the process of running chkdsk as
> advised I am losing files (some critical some not so critical).
>
> I'm trying to troubleshoot the problem and although both drives are
> fairly new (Maxtors & Seagate drives), I have checked the physical
> condition of each hard disk with the manufacturers software and
> independent software and no signs of failing disks, and have fitted
> new cables, which appears to eliminate a hardware problem. No one in
> these groups appears to be experiencing a similar problem, so that
> appears to eliminate a Vista 'bug' but has been reported just in case.
>
> I know little or nothing about NTFS, but could some of you
> knowledgeable people out there tell me if the NTFS file system is
> like to be affected by other drives/partitions on the system being
> FAT32 (a hangover from days of a three-way boot to Win98SE/Win2000 &
> WinXP Pro). I have been assured that they should live together in
> harmony, but as I am rapidly running out of ideas wondered if Vista's
> accessing of the other drives could be having an adverse effect on
> Vista itself.
> Any advice would be appreciated
>
>
> GeoffP
>
>
>
>
> ---
> avast! Antivirus: Outbound message clean.
> Virus Database (VPS): 0626-2, 28/06/2006
> Tested on: 29/06/2006 13:44:10
> avast! - copyright (c) 1988-2006 ALWIL Software.
> http://www.avast.com

Nothing on Event Logs for this installation so far despite the fact that I
have had the error reported a couple of times, but on previous instals NTFS
was reporting some File/Index recovery/repair but only a fraction of those
when running chkdsk.

I suspect a hardware problem (possibly with the Motherboard controller) but
I have now checked all possibilities on the drives themselves and the
connections. I will see what the event log says the next time it happens as
no doubt it will.

Thanks for your suggestions

GeoffP

> Apparently in all your troubles your clock somehow got set to the wrong
> date.
>
I don't think it's that. I think it's the old 'I'm better than everyone else
and I want to stay at the top of the list until my question is answered.'
They set their clocks ahead purposely. It happens too often. I wish no one
would answer them.

"Recycle Ben" <> wrote in message
news:...
>> Apparently in all your troubles your clock somehow got set to the wrong
>> date.
>>
> I don't think it's that. I think it's the old 'I'm better than everyone
> else and I want to stay at the top of the list until my question is
> answered.' They set their clocks ahead purposely. It happens too often. I
> wish no one would answer them.

See the thread on sarcasm. I know why the clock was set wrong :-)

--
Kerry Brown
MS-MVP - Windows Shell/User

"Recycle Ben" <> wrote in message
news:...
>> Apparently in all your troubles your clock somehow got set to the wrong
>> date.
>>
> I don't think it's that. I think it's the old 'I'm better than everyone
> else and I want to stay at the top of the list until my question is
> answered.' They set their clocks ahead purposely. It happens too often. I
> wish no one would answer them.

Sorry, hate to spoil your day, but you are very wrong there, until Kerry
brought the matter up (Thank you Kerry) I wasn't even aware of the change of
date (see my other posts in this and other groups - made on the correct
date). Looking at the Vista event viewer for reasons elsewhere in this
thread, the date was changed during the latest installation of Vista late
yesterday. Before you start flaming, I suggest you make sure of your facts!

GeoffP

Shortly after reading through these groups I had just started installing
Office Beta, when as predicted, the 'Corrupt Disk' Message appeared. Kicked
me out of the installation, wouldn't let me into Windows Mail, nor Admin
Settings to check the event log.

Ran CHKDSK from XP Disk Manager with 60 index entries being deleted and the
recovery of three orphaned files. Went back to Vista and event viewer
reports 105 NTFS error messages (Event ID: 55) in the space of 90 minutes.
No hardware errors were reported and nothing else that looked to be related.

Cannot find anything on Event ID:55 on MS Site so not sure where to go from
here.

GeoffP

PS: Apologies to anyone who thought I was trying to 'queue jump' with the
wrong system date, it was not intentional and appeared to have happened
during the course of the latest installation of Vista last night.

Here's info on that error:

http://www.eventid.net/display.asp?e...55&source=Ntfs

Basically it says that internal file system structures are out of whack.
This is very bad.

The most likely causes for this would be hardware malfunction or a bug in a
device driver (most likely the hard drive device driver, but possibly in
ntfs itself).

Since you don't have this problem on Windows XP, and you have had this
problem on Vista in 3 different partitions, I find it hard to believe it is
a hardware problem. However, here are some comments I've seen from people on
the internet:

1) try moving your pagefile to another hard drive / partition
2) test your RAM to make sure it is OK
3) Make sure your computer is not overheating

You should file a bug report using the feedback reporting tool (you can
download that from the feedback icon on your desktop).

Using that tool will send your event logs to Microsoft so perhaps they can
figure out what's going on.

- JB