Hi All,
I have built many PCs and configured many laptops... I still run winXP on various "mission critical" machines (used for test equipment, no internet access, so please don't say winXP is trash, vulnerable, etc
).
I have found, repeatedly, that winXP trashes SSDs in around 1 year of 24/7 operation. They seem to hard-fail, with errors like NTLDR not found, so obviously something seriously wrong with the boot process.
I don't know the detail (I am an embedded systems developer, hardware & software, assembler and C) but I understood that all drives nowadays, HD and SSD, have auto sector remapping in the event of a hard sector defect. Yet this seems to fail on SSDs under winXP.
Separately, in another context, I found that win2k and winXP writes to the registry around once per second, all the time. This was found to block auto shutdown on SCSI drives... but how did they implement auto shutdown on XP laptops?? Was it a special OEM version of XP? A 1/sec write of a few 4k sectors works out at quite a few GB a year and with typical FLASH write endurance of 10k writes per block could explain the short life of SSDs even with remapping. There is a calculation for SSD life with remapping of each block written 10k times, and it is a lot less than most would think - of the order of tens of TB for a 100GB SSD, to completely trash it.
Anyway, I am looking to moving some machines with SSDs to win7-32 and wonder whether this works OK with SSDs.
I recall reading something about the TRIM command... not sure why that should be relevant to sector remapping.
The reason for win7-32 is that it maintains compatibility with some old software we have. Win7-64 doesn't work because it enforces additional Program Data v. Program Files separation rules, relative to win7-32 (relevant to old apps which keep data in Program Files, like they all used to in the bad old days 😉 ).
I would appreciate any views on win7-32 and SSD operation. The SSDs in question are Intel ones but nothing new (year 2012 or so); they are in existing machines under winXP.
I have built many PCs and configured many laptops... I still run winXP on various "mission critical" machines (used for test equipment, no internet access, so please don't say winXP is trash, vulnerable, etc
).I have found, repeatedly, that winXP trashes SSDs in around 1 year of 24/7 operation. They seem to hard-fail, with errors like NTLDR not found, so obviously something seriously wrong with the boot process.
I don't know the detail (I am an embedded systems developer, hardware & software, assembler and C) but I understood that all drives nowadays, HD and SSD, have auto sector remapping in the event of a hard sector defect. Yet this seems to fail on SSDs under winXP.
Separately, in another context, I found that win2k and winXP writes to the registry around once per second, all the time. This was found to block auto shutdown on SCSI drives... but how did they implement auto shutdown on XP laptops?? Was it a special OEM version of XP? A 1/sec write of a few 4k sectors works out at quite a few GB a year and with typical FLASH write endurance of 10k writes per block could explain the short life of SSDs even with remapping. There is a calculation for SSD life with remapping of each block written 10k times, and it is a lot less than most would think - of the order of tens of TB for a 100GB SSD, to completely trash it.
Anyway, I am looking to moving some machines with SSDs to win7-32 and wonder whether this works OK with SSDs.
I recall reading something about the TRIM command... not sure why that should be relevant to sector remapping.
The reason for win7-32 is that it maintains compatibility with some old software we have. Win7-64 doesn't work because it enforces additional Program Data v. Program Files separation rules, relative to win7-32 (relevant to old apps which keep data in Program Files, like they all used to in the bad old days 😉 ).
I would appreciate any views on win7-32 and SSD operation. The SSDs in question are Intel ones but nothing new (year 2012 or so); they are in existing machines under winXP.
Facebook
Twitter
Instagram