3
We are starting to see a problem with some Windows XP machines. These XP machines are running unpatched, vanilla installations of XP. They are not connected to the internet and so haven't downloaded any updates, no software is being updated. Our application runs fine when the system is first used but over time the performance of the XP machine is slowing down. By 'over time' I mean the PC itself is running for weeks without a power cycle and the application we've built runs for days at a time. We have only just noticed this slow down because the XP machine has a life-sign protocol with the rest of the system which is not being triggered because the load on the XP machine is too high, failing this life-sign halts the system (if you've read some of my other questions you'll know the system counts cash and so it's important that records are kept of how much cash has been through the system, which is what the Windows XP machine does).
So, does anyone have any ideas why the XP machine is slowing down? Is it the system event log, an unnecessary service or something else. Any ideas how to identify the source of the slow down?
Edit: If it were up to me, I would update with the latest patches. Unfortunately, these PCs are in banks based in other countries and they really don't like the machines being updated, let alone being connected to the internet. I have two options for investigating the problem: 1. Ask a field service engineer to get information from the machine and 2. flying out to the machines and seeing what's happening first hand. Option 2 would make the banks suspicious, which would be bad (we have a work-around at the moment, but we still need to work out why it's happening and whether or not the fix will last).
Finally, the people using the machines do not have access to the explorer shell, there is no start menu, alt-tab and ctrl-alt-del are disabled (again, the banks don't want anyone having access to the data/software).
We've asked w service engineer to get some data from task manager and do some defragging (although I'm not sure a defrag will do much).
If you say "unpatched, vanilla installations of XP", I would suggest to reinstall and install the service packs which might improve stability. – schnaader – 2009-11-27T14:51:36.273
1is it 'OS Rot' week at SU? :) i think this is the 3rd time i see this topic coming in the last few days. – None – 2009-11-27T15:44:09.657
1@schnaader This is likely a corporate machine with a critical, narrowly-defined role that would require a change request and sign-off from the application team before any changes could be made. In these situations, the platform is left alone as even seemingly benign or otherwise advisable changes like service packs could have unexplained and undesired consequences. – Lunatik – 2009-11-27T15:45:42.260
@Lunatik: I understand such situations, but I can't agree with them. It's like "Hey - we could make this power plant secure, but we don't like the paperwork - What was that noise?"... – schnaader – 2009-11-27T17:00:58.113
1@schnaader: it's not the paperwork, rather, all the testing that is required to verify the updates don't change the behaviour of the system, and in large systems the number of interdependancies makes test complex. "We upgraded the power plant control's OS - what do you mean it's stopped working?" – Skizz – 2009-11-27T20:03:04.843