Thee clean re-instals and still one major problem ... need s

thee clean re instals still one major need s

Thee clean re-instals and still one major problem ... need s

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

"Clark" wrote in message

I am certainly not an expert here, but I would probably try removing the other controller and try running the system without it for a while. If the errors stop, then you know what might be upsetting the system. If you don't want to remove it, maybe moving it to another PCI slot.
Clark

Did that for Instal No 2 (took it out completely), but made no difference. There was someone on the hardware group, who has the same card (and driver version) and to date he hasn't reported any problems. So still looking for solutions.
GeoffP

Is the BIOS up to date?
"GeoffP" wrote in message

"Jon Abbott" wrote in message
You aren't the only one. I've seen corruption on the odd occasion as well, in fact I posted a few weeks ago that a critical system file was corrupt. On that occasion, checking the disk in XP resulted in quite a few corrupt files and tables being reported.
Jon
Sorry, but must have missed your post, I won't say that I'm pleased that someone else is suffering but it is nice to know that I'm not on my own. My major concern is this isn't an occasional thing, I've had two 'bashing' in the past five hours, the latest produced a 3 page CHKDSK report. I want to use and test this thing out but with the risk of loss of software and driver files (in particular my anti-virus and WinMail files, which appear to suffer the most), I just can't risk doing much other than a quick look at these newsgroups.
GeoffP

"Colin Barnhorst" wrote in message

Is the BIOS up to date?

Hadn't thought about that one, but on checking yes it is. But do wonder about the VIA chipset drivers supplied by Microsoft as there does seem to be a few problems with the nVidia nForce & Intel chipsets, but nothing that I have seen relating to VIA
GeoffP

I hate to say it but I thought the same thing. Some people do change their date so their posts stay at the top of the list if you sort by date. It's a pain in the a%&.
-- Kerry MS-MVP Windows - Shell/User
GeoffP wrote:

"Recycle Ben" wrote in message 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

Yup, I've been around Usenet for longer than I can care to remember (including setting up a uk. newgroup) and know most of the tricks used but that wasn't intended to be one of them. I still can't figure out how it managed to get changed during the install as it definitely wasn't at the setting date and time stage. Hopefully no harm done apart from a short 'flame' and I've experienced a lot worse for a lot less,
GeoffP
"Kerry Brown" wrote in message

I hate to say it but I thought the same thing. Some people do change their date so their posts stay at the top of the list if you sort by date. It's a pain in the a%&.
-- Kerry MS-MVP Windows - Shell/User

I still can't figure out how it managed to get changed during the install as it definitely wasn't at the setting date and time stage.

Actually ... it probably was.
There's a bug in Vista where when you select your timezone during install, it changes your time.
- JB

"Jimmy Brush" wrote in message

I still can't figure out how it managed to get changed during the install as it definitely wasn't at the setting date and time stage.
Actually ... it probably was.
There's a bug in Vista where when you select your timezone during install, it changes your time.
- JB

Hmm wasn't aware of that one - thanks.
Incidentally this Corrupt Disk problem appears to be deteriorating fast, was up to the early hours sorting out last night's problems, booted straight into Vista this morning and 'Corrupt Disk' messages all over the place and hadn't done a thing. I think I might try downloading another copy of the ISO file and doing yet another re-instal as having eliminated hardware problems it is beginning to look as if it is a Vista 'problem' and as it is isolated to NTFS it may just may be the result of a bad download.
GeoffP

--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0626-2, 28/06/2006 Tested on: 29/06/2006 11:58:58 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

Before you install Vista, you should do these things from within XP:
- Delete the partition you are going to use (im assuming here that its one of the failed ones or is empty) - Apply the delete (closing disk management should do this) - Create the partition again - Format it with NTFS - run chkdsk on it from XP
I've seen someone else on the forum had a problem with a ntfs filesystem and doing these steps helped him. Of course, his problem wasn't anything like yours ... but you never know.
- JB

"Jimmy Brush" wrote in message

Before you install Vista, you should do these things from within XP:
- Delete the partition you are going to use (im assuming here that its one of the failed ones or is empty) - Apply the delete (closing disk management should do this) - Create the partition again - Format it with NTFS - run chkdsk on it from XP
I've seen someone else on the forum had a problem with a ntfs filesystem and doing these steps helped him. Of course, his problem wasn't anything like yours ... but you never know.
- JB

This is exactly what I have done for the three instals that's what makes me think that it was actually a bad download. This morning's problems resulted in an Event Log of 1,318 NTFS reported errors with 58 being repaired (and that's just from a boot up). The Chkdsk output was over 10 pages of A4. Lost my anti-virus and goodness knows what else. So its definitely a new download of the ISO file and try again later.
Incidentally do you (or anyone else) know if the 'Bug' Report tool can be run from XP, I've got all the files saved (away from Vista) but just don't trust this installation now and until I've got a reliable installation will leave it alone.
GeoffP

--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0626-2, 28/06/2006 Tested on: 29/06/2006 12:41:13 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

Yes, the tool can be ran from XP :)
- JB

Are you installing by starting the machine and booting from the Vista DVD, or starting your normal Windows version, and running the setup program on the Vista DVD. I had two installs fail booting from the DVD, but running setup from Windows work correctly first time. If you do install from Windows, accept the option to download updates while you still have a working net connection.
On your very first post you say you have installed on different partitions/hard disks. My failed installs were caused because setup running from the DVD was not identifying my Maxtor 200GB drive correctly and trying to use 36bit addressing. This doesn't however explain why you can't get a working copy on the Seagate drive, as this is less than 137GB and doesn't require 48bit addressing like the Maxtor.
Regards Mike
"GeoffP" wrote in message

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

"Jon Abbott" wrote in message

You aren't the only one. I've seen corruption on the odd occasion as well, in fact I posted a few weeks ago that a critical system file was corrupt. On that occasion, checking the disk in XP resulted in quite a few corrupt files and tables being reported.
Jon

Sorry, but must have missed your post, I won't say that I'm pleased that someone else is suffering but it is nice to know that I'm not on my own. My major concern is this isn't an occasional thing, I've had two 'bashing' in the past five hours, the latest produced a 3 page CHKDSK report. I want to use and test this thing out but with the risk of loss of software and driver files (in particular my anti-virus and WinMail files, which appear to suffer the most), I just can't risk doing much other than a quick look at these newsgroups.
GeoffP

Done the first two and am trying to find a Motherboard Monitor that will work with Vista to check temps. I've just recovered from another Corrupt Disk 'bashing' (second in 5 hours) with a CHKDSK report of nearly three A4 pages and an Event Log of over 150 errors (and thats after checking the memory and moving pagefile.sys to its own partition). So the system temperature (this is a possibility as my system has always run warmer than I would like, but nowhere near the limits) is all that I can think apart from a problem with NTFS or of course (says he belatedly), a bad ISO image of the Vista Beta 2 setup DVD. I can't see that though with everything working so well.
Have posted a 'bug' report to MS (with all the damning evidence), but won't hold my breath for a response.
GeoffP

"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).

You aren't the only one. I've seen corruption on the odd occasion as well, in fact I posted a few weeks ago that a critical system file was corrupt. On that occasion, checking the disk in XP resulted in quite a few corrupt files and tables being reported.
Jon

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

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

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

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?eventid=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

I am certainly not an expert here, but I would probably try removing the other controller and try running the system without it for a while. If the errors stop, then you know what might be upsetting the system. If you don't want to remove it, maybe moving it to another PCI slot.
Clark
"GeoffP" wrote in message

Sorry - Current config:
Seagate (120Gb) - IDE Master to motherboard controller (XP on partition 0/FAT 32, Vista Beta 2 on partition 1/NTFS) + two other partitions (FAT32)
Maxtor (200Gb) - IDE Silicon Image 0680 PCI ATA133 Controller (Driver installed ok) as Master (all partitions FAT 32)
GeoffP
"Clark" wrote in message 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 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

--- avast! Antivirus: Inbound message clean. Virus Database (VPS): 0626-2, 28/06/2006 Tested on: 29/06/2006 14:56:09 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0626-2, 28/06/2006 Tested on: 29/06/2006 15:00:47 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

Thanks - that's what I thought (and was told), but something in my setup must be causing this and its frustrating having a fully 'working' Beta, which seems to be causing major corruptions to the Visa partition and thus can't be 'trusted' to use and test properly
Any other ideas what could be causing it, there's no problems whatsoever with the FAT32 partitions just the NTFS partition.
GeoffP
"Jimmy Brush" wrote in message

NTFS does not mess with FAT32 and vice versa.
They are seperated cleanly at a very, very low level in Windows.
- JB
--- avast! Antivirus: Inbound message clean. Virus Database (VPS): 0626-2, 28/06/2006 Tested on: 29/06/2006 14:19:26 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

Sorry - Current config:
Seagate (120Gb) - IDE Master to motherboard controller (XP on partition 0/FAT 32, Vista Beta 2 on partition 1/NTFS) + two other partitions (FAT32)
Maxtor (200Gb) - IDE Silicon Image 0680 PCI ATA133 Controller (Driver installed ok) as Master (all partitions FAT 32)
GeoffP
"Clark" wrote in message

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 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

--- avast! Antivirus: Inbound message clean. Virus Database (VPS): 0626-2, 28/06/2006 Tested on: 29/06/2006 14:56:09 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

I was getting exactly the same problem, three installs on different drives, different partitions etc. using both x86 and x64 installs. Every time the same thing happened - getting the Event 55 errors and needing to run chkdsk, pretty much the same.
I tried a last time, but this time spent more time cleaning down the drive I was going to install to. I created a new primary partition under XP and made sure I formatted as NTFS using XP - not using Acronis Disk Director I had been using to format with. I then booted using the Vista x86 DVD and when selecting the partition I did another format from the install process (for good luck). This install has been fine for a few days now with many updates made - so far so good.

It's changed in 5456. Setting the time zone no longer changes the time.
"GeoffP" wrote in message

"Jimmy Brush" wrote in message I still can't figure out how it managed to get changed during the install as it definitely wasn't at the setting date and time stage.
Actually ... it probably was.
There's a bug in Vista where when you select your timezone during install, it changes your time.
- JB
Hmm wasn't aware of that one - thanks.
Incidentally this Corrupt Disk problem appears to be deteriorating fast, was up to the early hours sorting out last night's problems, booted straight into Vista this morning and 'Corrupt Disk' messages all over the place and hadn't done a thing. I think I might try downloading another copy of the ISO file and doing yet another re-instal as having eliminated hardware problems it is beginning to look as if it is a Vista 'problem' and as it is isolated to NTFS it may just may be the result of a bad download.
GeoffP

--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0626-2, 28/06/2006 Tested on: 29/06/2006 11:58:58 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

"Colin Barnhorst" wrote in message

It's changed in 5456. Setting the time zone no longer changes the time.

Having run out of ideas, I intend to download a new ISO tonight just in case the original was corrupt. From what I've seen on the group 5456 is only available for 'techies' so presumably will be stuck with 5384.
GeoffP

--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 29/06/2006 17:46:54 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

Thanks for the 'heads up', it sounds as if we have followed exactly procedures *including* the use of Acronis (a common denominator at last), which does make me wonder if that is the cause of my problems. I'll give it one more try this evening, before I download a fresh ISO, without using Acronis and see what happens.
GeoffP
"Cobblers" wrote in message

I was getting exactly the same problem, three installs on different drives, different partitions etc. using both x86 and x64 installs. Every time the same thing happened - getting the Event 55 errors and needing to run chkdsk, pretty much the same.
I tried a last time, but this time spent more time cleaning down the drive I was going to install to. I created a new primary partition under XP and made sure I formatted as NTFS using XP - not using Acronis Disk Director I had been using to format with. I then booted using the Vista x86 DVD and when selecting the partition I did another format from the install process (for good luck). This install has been fine for a few days now with many updates made - so far so good.
--- avast! Antivirus: Inbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 29/06/2006 17:39:34 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

No problems at all with the installation, only one driver (an additional PCI Parallel Port) caused any problems and that was soon solved by removing the card. Apart from this one problem Vista itself has been fine with everything working as it should.
Initially Vista was on a partition on the Maxtor 200Gb drive (with the SiI0680 controller - 48bit), it ran perfectly but when the 'corrupt disk' started appearing put it down to the XP Driver not being fully compatible so moved first to an old Seagate 60Gb drive and then on the third instal to a partition on the Seagate 120 Gb drive.
Hopefully from an earlier thread I may have found the culprit in Acronis Disk Director, which I had been using for all the partitioning and formatting through XP (sheer idleness on my part) but in light of the experiences of Cobblers it looks like its back to basics on fresh instal this evening.
GeoffP
"Michael Dodimead" wrote in message

Are you installing by starting the machine and booting from the Vista DVD, or starting your normal Windows version, and running the setup program on the Vista DVD. I had two installs fail booting from the DVD, but running setup from Windows work correctly first time. If you do install from Windows, accept the option to download updates while you still have a working net connection.
On your very first post you say you have installed on different partitions/hard disks. My failed installs were caused because setup running from the DVD was not identifying my Maxtor 200GB drive correctly and trying to use 36bit addressing. This doesn't however explain why you can't get a working copy on the Seagate drive, as this is less than 137GB and doesn't require 48bit addressing like the Maxtor.
Regards Mike

Correct. It is not so much techies as professionals.
"GeoffP" wrote in message

"Colin Barnhorst" wrote in message It's changed in 5456. Setting the time zone no longer changes the time.
Having run out of ideas, I intend to download a new ISO tonight just in case the original was corrupt. From what I've seen on the group 5456 is only available for 'techies' so presumably will be stuck with 5384.
GeoffP

--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 29/06/2006 17:46:54 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

Well it's looking good. Dumping Acronis Disk Director and formatting, partitioning, and Chkdsk'ing the old fashioned way seems to have done the trick. I won't count my chickens and will give it a couple of days of testing but I feel a lot more confidence in Vista that I've had for the past two weeks. Thanks again on the heads up regarding Acronis, it might work Ok with XP but it does seem to cause problems in setting up partitions/disks for Vista.
GeoffP

Acronis says their software does not support Vista.
--
Yesterday is a canceled check; tomorrow is a promissory note; today is the only cash you have. Spend it wisely.

"GeoffP" wrote in message

Well it's looking good. Dumping Acronis Disk Director and formatting, partitioning, and Chkdsk'ing the old fashioned way seems to have done the trick. I won't count my chickens and will give it a couple of days of testing but I feel a lot more confidence in Vista that I've had for the past two weeks. Thanks again on the heads up regarding Acronis, it might work Ok with XP but it does seem to cause problems in setting up partitions/disks for Vista.
GeoffP

It wasn't installed or used on Vista but on XP Pro and used to partition, format and check the partition prior to installing Vista. I've been using it for some time on XP without any problems (mainly on FAT32 partitions) but Vista appears not to like the NTFS partitions created by the Acronis Disk Director.
GeoffP
"Leo" wrote in message

Acronis says their software does not support Vista.
--
Yesterday is a canceled check; tomorrow is a promissory note; today is the only cash you have. Spend it wisely.

"GeoffP" wrote in message Well it's looking good. Dumping Acronis Disk Director and formatting, partitioning, and Chkdsk'ing the old fashioned way seems to have done the trick. I won't count my chickens and will give it a couple of days of testing but I feel a lot more confidence in Vista that I've had for the past two weeks. Thanks again on the heads up regarding Acronis, it might work Ok with XP but it does seem to cause problems in setting up partitions/disks for Vista.
GeoffP

--- avast! Antivirus: Inbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 30/06/2006 23:41:48 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

Now appears to be sorted and everything working as it should with no corruption errors for three days. Nice to know it wasn't Vista, Hardware or Drivers but down to use of a third party Disk Manager to set up the initial partitions/drives. Thanks to one and all for their very valuable help and advice hope I will be able to reciprocate at some time in the future.
GeoffP

--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 02/07/2006 11:26:29 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

Just so we don't make the same error, Geoff, what was the name of the third-party Disk Manager that you suspect caused this grief?
"GeoffP" wrote in message Now appears to be sorted and everything working as it should with no corruption errors for three days. Nice to know it wasn't Vista, Hardware or Drivers but down to use of a third party Disk Manager to set up the initial partitions/drives. Thanks to one and all for their very valuable help and advice hope I will be able to reciprocate at some time in the future.
GeoffP

--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 02/07/2006 11:26:29 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

Acronis Disk Director Suite (v10.0 build 2.089). Have emailed their support with the offer of output etc., but doubt whether I will hear anything back. No problems with it doing routine stuff with FAT32 on XP (and until recently Win98SE) just the prep, formatting & disk checking for the Vista partition, which appears to have caused the problems. Being of the 'old school' I should know better and stick to doing things properly and not using third party software to speed things up. It takes longer initially but in the long term it doesn't pay.
One thing I would say is that I have been away from the microsoft newsgroups since the early days of Win95 & Win98 and nothing has changed, still the 'silly' questions, but nearly all answered (generally :) )in a very sympathetic, helpful and professional way. It is appreciated by some of us.
GeoffP
"Mark D. VandenBerg" wrote in message

Just so we don't make the same error, Geoff, what was the name of the third-party Disk Manager that you suspect caused this grief?
"GeoffP" wrote in message Now appears to be sorted and everything working as it should with no corruption errors for three days. Nice to know it wasn't Vista, Hardware or Drivers but down to use of a third party Disk Manager to set up the initial partitions/drives. Thanks to one and all for their very valuable help and advice hope I will be able to reciprocate at some time in the future.
GeoffP

--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 02/07/2006 11:26:29 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

--- avast! Antivirus: Inbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 02/07/2006 16:45:59 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

I'm glad you figured it out :)
Will have to remember that one when Microsoft changes NTFS again in the next, next version of Windows.
- JB

Everyone snickers when I say that I use PartitionMagic and Ghost, but I don't ever seem to have these problems.
"GeoffP" wrote in message Acronis Disk Director Suite (v10.0 build 2.089). Have emailed their support with the offer of output etc., but doubt whether I will hear anything back. No problems with it doing routine stuff with FAT32 on XP (and until recently Win98SE) just the prep, formatting & disk checking for the Vista partition, which appears to have caused the problems. Being of the 'old school' I should know better and stick to doing things properly and not using third party software to speed things up. It takes longer initially but in the long term it doesn't pay.
One thing I would say is that I have been away from the microsoft newsgroups since the early days of Win95 & Win98 and nothing has changed, still the 'silly' questions, but nearly all answered (generally :) )in a very sympathetic, helpful and professional way. It is appreciated by some of us.
GeoffP
"Mark D. VandenBerg" wrote in message

Just so we don't make the same error, Geoff, what was the name of the third-party Disk Manager that you suspect caused this grief?
"GeoffP" wrote in message Now appears to be sorted and everything working as it should with no corruption errors for three days. Nice to know it wasn't Vista, Hardware or Drivers but down to use of a third party Disk Manager to set up the initial partitions/drives. Thanks to one and all for their very valuable help and advice hope I will be able to reciprocate at some time in the future.
GeoffP

--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 02/07/2006 11:26:29 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

--- avast! Antivirus: Inbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 02/07/2006 16:45:59 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

But they don't install on Vista, at least my versions don't - didn't install on x64, but worked fine on XP, at least until Ghost decided I had a problem on my partition table that nothing else could find. Finally had to adjust the size of my drive every time I went to back it up. Got one backup then the next time it failed again, always reading the last block of data. Increase one time, decrease the next.
"Mark D. VandenBerg" wrote in message

Everyone snickers when I say that I use PartitionMagic and Ghost, but I don't ever seem to have these problems.
"GeoffP" wrote in message Acronis Disk Director Suite (v10.0 build 2.089). Have emailed their support with the offer of output etc., but doubt whether I will hear anything back. No problems with it doing routine stuff with FAT32 on XP (and until recently Win98SE) just the prep, formatting & disk checking for the Vista partition, which appears to have caused the problems. Being of the 'old school' I should know better and stick to doing things properly and not using third party software to speed things up. It takes longer initially but in the long term it doesn't pay.
One thing I would say is that I have been away from the microsoft newsgroups since the early days of Win95 & Win98 and nothing has changed, still the 'silly' questions, but nearly all answered (generally :) )in a very sympathetic, helpful and professional way. It is appreciated by some of us.
GeoffP
"Mark D. VandenBerg" wrote in message Just so we don't make the same error, Geoff, what was the name of the third-party Disk Manager that you suspect caused this grief?
"GeoffP" wrote in message Now appears to be sorted and everything working as it should with no corruption errors for three days. Nice to know it wasn't Vista, Hardware or Drivers but down to use of a third party Disk Manager to set up the initial partitions/drives. Thanks to one and all for their very valuable help and advice hope I will be able to reciprocate at some time in the future.
GeoffP

--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 02/07/2006 11:26:29 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

--- avast! Antivirus: Inbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 02/07/2006 16:45:59 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0626-3, 29/06/2006 Tested on: 02/07/2006 17:00:24 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com

"John Barnes" wrote in message But they don't install on Vista, at least my versions don't - didn't install on x64, but worked fine on XP, at least until Ghost decided I had a problem on my partition table that nothing else could find. Finally had to adjust the size of my drive every time I went to back it up. Got one backup then the next time it failed again, always reading the last block of data. Increase one time, decrease the next.

To be honest I have not attempted to install any Norton/Symantec products in Vista. Too many horror stories already and I don't need to add to them. For testing, MS Backup and System Restore are fine, since I don't care about any documents, and I can always boot from PM and adjust sizes as I need. Actually, MS Backup is pretty well featured, under Vista. Good improvement, although it won't let you do a system backup to anything but an NTFS drive.
I do want to play a little with MS Disc Management, as I understand that under Vista it is alleged to be fault-tolerant, but call me skeptical (okay, paranoid) if I take a wait-and-see approach to that one.
Strange behavior of Ghost, I've not had an issue and I use it to back-up multiple partitions on multiple, networked computers to a central storage drive.

I tried to install most of my previous programs whether I used them or not to see how it went. Not very successful (maybe 20% installed and ran). At least for me if you install using the compatibility wizard you cannot uninstall the program, period (manually, but who has time for that). Only difference I found in the Vista DM is it is more descriptive and it does allow you to adjust partition sizes up and down, which is handy unless you have to do it to install Vista, then catch-22. When I checked System Restore, I didn't have any restore points, so I manually created one. May test that sometime later. I was glad to see Vista just set only its own drive up to automatically do restore points. In other systems, my experience, was that restore points across systems would kill restore points on other systems if you changed systems often. I found it worked best like Vista. Restore points only on drives any OS uses. I will probably use another backup program recommended in the x64 newsgroup. Acronis True Image.
"Mark D. VandenBerg" wrote in message

"John Barnes" wrote in message But they don't install on Vista, at least my versions don't - didn't install on x64, but worked fine on XP, at least until Ghost decided I had a problem on my partition table that nothing else could find. Finally had to adjust the size of my drive every time I went to back it up. Got one backup then the next time it failed again, always reading the last block of data. Increase one time, decrease the next.

To be honest I have not attempted to install any Norton/Symantec products in Vista. Too many horror stories already and I don't need to add to them. For testing, MS Backup and System Restore are fine, since I don't care about any documents, and I can always boot from PM and adjust sizes as I need. Actually, MS Backup is pretty well featured, under Vista. Good improvement, although it won't let you do a system backup to anything but an NTFS drive.
I do want to play a little with MS Disc Management, as I understand that under Vista it is alleged to be fault-tolerant, but call me skeptical (okay, paranoid) if I take a wait-and-see approach to that one.
Strange behavior of Ghost, I've not had an issue and I use it to back-up multiple partitions on multiple, networked computers to a central storage drive.

One quick thing about the restore points that MICHAEL mentioned and Collin explained: if you are dual-booting but don't have the Vista drive hidden from the XP drive or the Vista drive encrypted with BitLocker, XP will delete the Vista restore points. I don't remember the exact reason, but I did duplicate it.
"John Barnes" wrote in message I tried to install most of my previous programs whether I used them or not to see how it went. Not very successful (maybe 20% installed and ran). At least for me if you install using the compatibility wizard you cannot uninstall the program, period (manually, but who has time for that). Only difference I found in the Vista DM is it is more descriptive and it does allow you to adjust partition sizes up and down, which is handy unless you have to do it to install Vista, then catch-22. When I checked System Restore, I didn't have any restore points, so I manually created one. May test that sometime later. I was glad to see Vista just set only its own drive up to automatically do restore points. In other systems, my experience, was that restore points across systems would kill restore points on other systems if you changed systems often. I found it worked best like Vista. Restore points only on drives any OS uses. I will probably use another backup program recommended in the x64 newsgroup. Acronis True Image.

I will check but that may be related to the fact that XP defaults to every drive included in restore points by default. Since I have my Vista drive turned off, I will boot there and see if it deletes the drives. I really don't want to have to hide the Vista drive on XP since that is the C drive and makes installing nVidia drivers a pain along with other programs. It is also now the system drive so I can't quickly change the drive letter. Thanks for the heads up.
"Mark D. VandenBerg" wrote in message

One quick thing about the restore points that MICHAEL mentioned and Collin explained: if you are dual-booting but don't have the Vista drive hidden from the XP drive or the Vista drive encrypted with BitLocker, XP will delete the Vista restore points. I don't remember the exact reason, but I did duplicate it.
"John Barnes" wrote in message I tried to install most of my previous programs whether I used them or not to see how it went. Not very successful (maybe 20% installed and ran). At least for me if you install using the compatibility wizard you cannot uninstall the program, period (manually, but who has time for that). Only difference I found in the Vista DM is it is more descriptive and it does allow you to adjust partition sizes up and down, which is handy unless you have to do it to install Vista, then catch-22. When I checked System Restore, I didn't have any restore points, so I manually created one. May test that sometime later. I was glad to see Vista just set only its own drive up to automatically do restore points. In other systems, my experience, was that restore points across systems would kill restore points on other systems if you changed systems often. I found it worked best like Vista. Restore points only on drives any OS uses. I will probably use another backup program recommended in the x64 newsgroup. Acronis True Image.

No. It is an incompatibility between volsnap.sys in XP vs volsnap.sys in Vista. SR uses volsnap.sys to capture data for its restore points and then SR does the rest. Volsnap.sys is the Volume Shadowcopy Service driver. It is not a part of SR but is used by it. When XP starts up VSS detects what it thinks are corrupted SR points on the Vista volume and deletes them thinking to protect the user from trying to restore from a corrupt data file. That's why turning off SR on XP still doesn't save the Vista restore points. SR isn't doing the checking. MS has stated that they will not do what it would take to backport the Vista volsnap.sys to XP because the changes to XP would be too extensive.
"John Barnes" wrote in message

I will check but that may be related to the fact that XP defaults to every drive included in restore points by default. Since I have my Vista drive turned off, I will boot there and see if it deletes the drives. I really don't want to have to hide the Vista drive on XP since that is the C drive and makes installing nVidia drivers a pain along with other programs. It is also now the system drive so I can't quickly change the drive letter. Thanks for the heads up.
"Mark D. VandenBerg" wrote in message One quick thing about the restore points that MICHAEL mentioned and Collin explained: if you are dual-booting but don't have the Vista drive hidden from the XP drive or the Vista drive encrypted with BitLocker, XP will delete the Vista restore points. I don't remember the exact reason, but I did duplicate it.
"John Barnes" wrote in message I tried to install most of my previous programs whether I used them or not to see how it went. Not very successful (maybe 20% installed and ran). At least for me if you install using the compatibility wizard you cannot uninstall the program, period (manually, but who has time for that). Only difference I found in the Vista DM is it is more descriptive and it does allow you to adjust partition sizes up and down, which is handy unless you have to do it to install Vista, then catch-22. When I checked System Restore, I didn't have any restore points, so I manually created one. May test that sometime later. I was glad to see Vista just set only its own drive up to automatically do restore points. In other systems, my experience, was that restore points across systems would kill restore points on other systems if you changed systems often. I found it worked best like Vista. Restore points only on drives any OS uses. I will probably use another backup program recommended in the x64 newsgroup. Acronis True Image.

Thanks Collin. I could remember the scenario but not the actual file.
And John, when I use BootMagic to load either O/S, both of them show up as "C:\" as the system drive (well, not at the same time of course) when they are running. Could solve the driver loading issue?
"Colin Barnhorst" wrote in message No. It is an incompatibility between volsnap.sys in XP vs volsnap.sys in Vista. SR uses volsnap.sys to capture data for its restore points and then SR does the rest. Volsnap.sys is the Volume Shadowcopy Service driver. It is not a part of SR but is used by it. When XP starts up VSS detects what it thinks are corrupted SR points on the Vista volume and deletes them thinking to protect the user from trying to restore from a corrupt data file. That's why turning off SR on XP still doesn't save the Vista restore points. SR isn't doing the checking. MS has stated that they will not do what it would take to backport the Vista volsnap.sys to XP because the changes to XP would be too extensive.
"John Barnes" wrote in message

I will check but that may be related to the fact that XP defaults to every drive included in restore points by default. Since I have my Vista drive turned off, I will boot there and see if it deletes the drives. I really don't want to have to hide the Vista drive on XP since that is the C drive and makes installing nVidia drivers a pain along with other programs. It is also now the system drive so I can't quickly change the drive letter. Thanks for the heads up.
"Mark D. VandenBerg" wrote in message One quick thing about the restore points that MICHAEL mentioned and Collin explained: if you are dual-booting but don't have the Vista drive hidden from the XP drive or the Vista drive encrypted with BitLocker, XP will delete the Vista restore points. I don't remember the exact reason, but I did duplicate it.
"John Barnes" wrote in message I tried to install most of my previous programs whether I used them or not to see how it went. Not very successful (maybe 20% installed and ran). At least for me if you install using the compatibility wizard you cannot uninstall the program, period (manually, but who has time for that). Only difference I found in the Vista DM is it is more descriptive and it does allow you to adjust partition sizes up and down, which is handy unless you have to do it to install Vista, then catch-22. When I checked System Restore, I didn't have any restore points, so I manually created one. May test that sometime later. I was glad to see Vista just set only its own drive up to automatically do restore points. In other systems, my experience, was that restore points across systems would kill restore points on other systems if you changed systems often. I found it worked best like Vista. Restore points only on drives any OS uses. I will probably use another backup program recommended in the x64 newsgroup. Acronis True Image.

Unfortunately the first time you boot an os the drive lettering is set in the Registry for that os and takes a highly recommended against registry modification to change it. I can change the C drive to another letter if I change to another drive as system drive temporarily, but not worth the effort at this point. System Restore points on a test system don't matter much and I can just image the file for now so I don't have to start from scratch. Have done most of my testing in Vista for now i think.
Thanks Colin for the great information. "Mark D. VandenBerg" wrote in message

Thanks Collin. I could remember the scenario but not the actual file.
And John, when I use BootMagic to load either O/S, both of them show up as "C:\" as the system drive (well, not at the same time of course) when they are running. Could solve the driver loading issue?
"Colin Barnhorst" wrote in message No. It is an incompatibility between volsnap.sys in XP vs volsnap.sys in Vista. SR uses volsnap.sys to capture data for its restore points and then SR does the rest. Volsnap.sys is the Volume Shadowcopy Service driver. It is not a part of SR but is used by it. When XP starts up VSS detects what it thinks are corrupted SR points on the Vista volume and deletes them thinking to protect the user from trying to restore from a corrupt data file. That's why turning off SR on XP still doesn't save the Vista restore points. SR isn't doing the checking. MS has stated that they will not do what it would take to backport the Vista volsnap.sys to XP because the changes to XP would be too extensive.
"John Barnes" wrote in message I will check but that may be related to the fact that XP defaults to every drive included in restore points by default. Since I have my Vista drive turned off, I will boot there and see if it deletes the drives. I really don't want to have to hide the Vista drive on XP since that is the C drive and makes installing nVidia drivers a pain along with other programs. It is also now the system drive so I can't quickly change the drive letter. Thanks for the heads up.
"Mark D. VandenBerg" wrote in message One quick thing about the restore points that MICHAEL mentioned and Collin explained: if you are dual-booting but don't have the Vista drive hidden from the XP drive or the Vista drive encrypted with BitLocker, XP will delete the Vista restore points. I don't remember the exact reason, but I did duplicate it.
"John Barnes" wrote in message I tried to install most of my previous programs whether I used them or not to see how it went. Not very successful (maybe 20% installed and ran). At least for me if you install using the compatibility wizard you cannot uninstall the program, period (manually, but who has time for that). Only difference I found in the Vista DM is it is more descriptive and it does allow you to adjust partition sizes up and down, which is handy unless you have to do it to install Vista, then catch-22. When I checked System Restore, I didn't have any restore points, so I manually created one. May test that sometime later. I was glad to see Vista just set only its own drive up to automatically do restore points. In other systems, my experience, was that restore points across systems would kill restore points on other systems if you changed systems often. I found it worked best like Vista. Restore points only on drives any OS uses. I will probably use another backup program recommended in the x64 newsgroup. Acronis True Image.

Thanks Colin for the great information.
"Colin Barnhorst" wrote in message

No. It is an incompatibility between volsnap.sys in XP vs volsnap.sys in Vista. SR uses volsnap.sys to capture data for its restore points and then SR does the rest. Volsnap.sys is the Volume Shadowcopy Service driver. It is not a part of SR but is used by it. When XP starts up VSS detects what it thinks are corrupted SR points on the Vista volume and deletes them thinking to protect the user from trying to restore from a corrupt data file. That's why turning off SR on XP still doesn't save the Vista restore points. SR isn't doing the checking. MS has stated that they will not do what it would take to backport the Vista volsnap.sys to XP because the changes to XP would be too extensive.
"John Barnes" wrote in message I will check but that may be related to the fact that XP defaults to every drive included in restore points by default. Since I have my Vista drive turned off, I will boot there and see if it deletes the drives. I really don't want to have to hide the Vista drive on XP since that is the C drive and makes installing nVidia drivers a pain along with other programs. It is also now the system drive so I can't quickly change the drive letter. Thanks for the heads up.
"Mark D. VandenBerg" wrote in message One quick thing about the restore points that MICHAEL mentioned and Collin explained: if you are dual-booting but don't have the Vista drive hidden from the XP drive or the Vista drive encrypted with BitLocker, XP will delete the Vista restore points. I don't remember the exact reason, but I did duplicate it.
"John Barnes" wrote in message I tried to install most of my previous programs whether I used them or not to see how it went. Not very successful (maybe 20% installed and ran). At least for me if you install using the compatibility wizard you cannot uninstall the program, period (manually, but who has time for that). Only difference I found in the Vista DM is it is more descriptive and it does allow you to adjust partition sizes up and down, which is handy unless you have to do it to install Vista, then catch-22. When I checked System Restore, I didn't have any restore points, so I manually created one. May test that sometime later. I was glad to see Vista just set only its own drive up to automatically do restore points. In other systems, my experience, was that restore points across systems would kill restore points on other systems if you changed systems often. I found it worked best like Vista. Restore points only on drives any OS uses. I will probably use another backup program recommended in the x64 newsgroup. Acronis True Image.

I have had the same problems, and I hope I have fixed the problems. The symptoms are corrupted disk and chkdsk found bad indexes and a bad MFT. The MFT could not often repair and I must start chkdsk from XP. Both partition with XP and VISTA were corrupted.
How I have fixed the problems...
I have two disks. The first is for the Systems with two partitions, everyone with a size of 75GB. The second is for the dates which I have for years and will not lost. There is the outlook datafile, pictures, music and so on.
After some days with hanging system, (I used Acronis for dual booting) I tried another way..
On C: Disk0,Part1 I installed XP SP2 with all needfull things. (Format it before install, and don't forget to rescue all needfull thinks like outlook.pst) This is my backupsystem.
On D: Disk1,Part0 are all my datas, I do nothing
On E: Disk0,Part2 I installed Vista. (Before installing, I format E:). At first I started XP and in XP I started to install VISTA. I use the possibility to install on E:. When you do so you have the Multi Boot System from Vista (for more information look under BCDEdit.exe). I have no more Acronis or other third party "Bootmanager". The bootmanager from Vista works well.
Very important. Only install VISTA-compatible driver. Perhabs some other can be installed, but they could corrupt your system. After you have a running clean VISTA you can try some other driver. The best way, is test only one old driver / software for one moment.
Now I have a clean system and it is running since 48hours.....
I have learned, that Terratec-drivers are not really compatible.
-- AMD Athlon(tm) XP 2400+ 1,00 GB RAM RADEON 9600 MS WDDM Brother DCP 340CW Cinergy Hybrid T USB XS

Since a few days, since Sunday I have a working VISTA without the problem of corrupted disk. How it was before? Every time I use a program I got the message that the file system was corrupted. I used very often chkdsk and there problems with the indexes and the MFT. Not every time chkdsk could fix the problems by the first run. I have two systems (XP and Vista) on the computer. So I run chkdsk from XP even chkdsk from Vista could not fix the problem. The MFT per example could not repair, because there were not enough memory. There was a problems in the file system on partition from XP. Infected from the partition vista? Through the boot system? I don't know. I had a third party boot manager. The boot manger manipulated the system files and the drive letter. So it was in conflict of the boot manager of Vista and his secure file system.
What is in my Computer? Hard drive 1 with two partitions, 75GB and 75GB for the Operation Systems. Hard drive 2 with one partitions, 160GB. ATI 9600 Radeon AMD Athlon XP 2400+ VIA-Chips on the Mainboard. Netgear WG311 Terratec Cinergy Hybrid T USB XS (works till now not with Vista, but with XP)
What have I done? At first I have saved the important files like outlook.pst. Then I have deleted the partitions, both. Next I formatted C: (Disk0,Part1) and install XP inclusive SP2 and all the needful things I need. After XP is running with the newest updates I install Vista from XP. I use the possibility in the install menu to install on E: (Disk0,Part2). It's do a little time, because the partition was formatted by Vista. The whole time I was connected to the internet and so I get the updates during installation. Warning! Don't install a driver. Vista will do it. You have only to wait ( and wait…).
Now you have a clean Vista with Vista drivers.
The first driver, I install myself was for the graphic. Under ATI, there is a vista driver only the driver, not the manager) and the system works well.
The next driver was for WLAN. This was not explicit for Vista, but it runs till now. There a some Problems when I hide the SSID. But no corrupted hard disk. Today runs the Office 2007 and I used often outlook and word and there are no problems with the file system. The next one will be Visual Studio Express 2005. Conclusion: At first try to build a clean Vista and then in a second step test software. Test only on software in a moment. Some driver can be installed, and worked a little, but corrupted the disk. Don't use a third party boot manger, the one from Vista is enough. (For more information google for bcdedit. This is the editor for the new boot manager.)
-- AMD Athlon(tm) XP 2400+ 1,00 GB RAM RADEON 9600 MS WDDM Brother DCP 340CW Cinergy Hybrid T USB XS

Thanks but looks like the problems were down to Acronis Disk Director suite creating a NTFS partition that Vista did not like. Did a manual partition, format and checked the disk without the third party disk manager and no problems whatsoever for 5 days.
Don't know all the techie details, but Vista does write to all available partitions (NTFS and FAT32), certainly the XP Boot Disk is written to (the boot manager etc.,) and Vista 'recycle' bins are stored on each partition ($RECYCLE) and possibly Vista restore points, which have been the subject of a number of threads but the latter is a bit over

thee clean re instals still one major need s

Windows Vista

Thee clean re-instals and still one major problem ... need s