windows xp corrupted on few years

[jjcimon]

then  before re-installing the OS I would (by experience) suggest to change memory, just to try

an other cause could be the cpu overheating, try to get the cpu Temp from ......

did you check if the cpu fan is working properly? 

[gnunesjr]

I'm with Joe.  In my experience, XP is a self-corrupting operating system.  After a year or two, you need to scrape down the hard drive and start over.

[Graziano]

---

gnunesjr wrote:
I'm with Joe.  In my experience, XP is a self-corrupting operating system.  After a year or two, you need to scrape down the hard drive and start over.

---

   It can be, but the strange thing is that this problem is on many PCs, not connected to internet... uhm, this is strange, I'd think about a RAM overload (due to large data which increases slightly over time) or, as many gurus suggested, disk fragmentation. 

   A simple memory profile, and/or scandisk/defrag would help.  At least, they're quite compulsory to check application and system performance and for system maintenance!

graziano 

[tst]

XP is not "self corrupting". I have seen several XP installs (including my home machine) which ran for years with no trouble and no major performance degredation. That should prove that point.

I'm not saying that this doesn't happen (my current laptop isn't as snappy as it was 18 months ago when nothing was installed on it), just that it isn't necessarily caused by the OS. Ray mentioned COTS as opposed to home grown code. This obviously isn't really a valid point, since COTS is code just as well. It might be better designed and tested, but there is no guarantee for it. After all, XP itself is COTS and if you can blame it, you can certainly blame anything running on it (potentiallly including parts of the OS as well).

As an example, I often try to shutdown my laptop and find that it won't because LV 7.0 didn't fully shut down. The fact that it won't shut down is undesired behavior from the OS (although not necessarily a bug), but my point here is about LV not closing. Who's to blame? NI? MS? Maybe it's a third party DLL or driver?

[Jorge_Amaral]

thanks for all the replies.

Till this moment the conclusion it's:

 - There's no conclusion -

Some people have the luck of receiving the bugfree version of XP.

[Mathan]

---

Jorge Amaral wrote:

Till this moment the conclusion it's:

 - There's no conclusion -

---

Lol

Am using XP for the past 5 years and found no problems. Specifically my friends (win 2k) used to say when having both LabVIEW and internet connection in the same system will slow down the operation and they are very upset about that. After my suggestion, they are also now updated to XP. This is upto my knowledge.

Mathan

[Ben]

---

tst wrote:

...

As an example, I often try to shutdown my laptop and find that it won't because LV 7.0 didn't fully shut down. The fact that it won't shut down is undesired behavior from the OS (although not necessarily a bug), but my point here is about LV not closing. Who's to blame? NI? MS? Maybe it's a third party DLL or driver?

---

Mine does that also!

I think it started after I loaded one of the LV 8.X versions.

Back on topic.

I alos should mention that a bad hard drive will show strange issues since virtual memory relies heavily on the hard-drive functioning properly. The drivers will automatically retry the I/O so you can't really see the error until the drive is gone beyond recovery.

Disk technology is constantly moving upward and the latest and greatest hard-drives may not be all they are supposed to be.

Ben

(Ex-Large Disk Specialist - Specializing in all disk drives that are 67Mb or larger circa 1983  )

[Ray.R]

I'm not disagreeing with tst or those who support windoze...  I'm just stating my personal experience. 

I saw the latest MAC commercial last night, which is very funny and to the point.  These "adds" started with xp which was a troublesome OS.. 

One more experience...  My business PC, which ran Win-2K and had ms-office 2000 plus Quickbooks ran flawlessly for 3 years.  Installed xp and immediately had problems..  Of course, it was when it was first released and got attacked with the trojan which caused reboots every minute.  Returned to Win-2K no problems.  SP1 came out.  Re-installed xp....  (sigh)  It was a very flaky experience..  Replaced Win-2K on that machine (which still runs on the same installation of 2K since then without problems).   Bought a new machine.  Installed xp & SP2 (fool) on the new machine.  Installed ms-office 2000 and Quickbooks on this new PC.  Good thing I had a HD image of the drive because I had to redo the machine twice.  😠  When reverting to the image, the PC is back to "normal" / fast speed.

Speaking of degraded performance, anyone installed office 2007?  They did that at one customer..  Everybody is complaining about how slow the machines have become...  

On the other hand, since I had bought office 2003 and refused to cause further caos on my machine, I decided to install it on my wife's cheaper PC version (still respectable machine nonetheless) which also runs xp pro...  For some strange reason, her PC works well.. (euh... very well, actually).  It was a different vintage of xp (more recent).. 

SO:  Did they improve the OS as time went by?  Possibly..  Her's included SP2, whereas the one I have on my business machine is the original to which you have to install the service packs...  Also, I gave up installing all the interim patches....  which may have an influence over the functionality of the OS..

The two new machines run a similar vintage, which was a release that came with SP1.  SP2 was also installed, but no other patches, since they are not on the network and the automatic upgrades is turned OFF (obviously).  The two new machines do not have office.

Which leads to this question:  Do you have all the SP's and patches installed?

[Graziano]

Hi!

   To support what JoeLabView says, I can say that Windows XP, SP2 is a very stable system. I didn't install SP3, simply, I don't have extreme gaming needs, and about security, it seems to me that SP2 is ok.

    The problems with XP come when you start installing - uninstalling many drivers, applications, freeware, and so on, say, for test purposes.  This can corrupt OS, but I think this is reasonable (in MS world!).  That's why, I keep a Virtual machine with another windows XP inside, for all the tests.

   BTW, your applications do some registry access stuffs? Just to know...

graziano