Just to update with my Skype problem/reinstall.
(Skype stopped working and the install appeared to fail when being installed)
I decided to try and find out where/what was actually causing the problem, which probably was a good job, because if I had gone for a reinstall the chances are I would also have re-introduced the Skype problem when installing all the software that I would have put on each of the partitions, which would have been my dual-boot XP/Win7 on the laptop and Win7 starter on the NetBook, obviously I would have been checking, but it might have been easy to get beyond myself and miss the problem until after installing a few of the programs which obviously would have then caused confusion.
So after giving it some thought what with the same problem on all 3 partitions, so spent all weekend and most of Monday on the problem and managed to discovered the problem was being caused by 'NetLimiter v1.3' yes I know it's a old program but it did the job and I never needed anything else for what I required and there was never a problem until a few months ago when Skype updated away from v5.1.
To double/triple check, I even 're-introduced' the problem using a ghost image and know the problem is resolved, which fortunately only meant un-installing NetLimiter. (yep, a 5 minute job)
(The problem with the cursor jumping when typing in a post has not been resolved, but I can live with that as it's just a case of turning off the touchpad with the Fn key which I never use anyway and also the Belkin Bluetooth software which again is very rarely used)
So in a way, although it wasn't the last program to be installed, it probably was the last program to get updated that caused the problem.
Sorry for waffling on, but thought it might be good for anyone to know if they come across this thread.
So that's it, now back to topic............ what was the topic?
************************
Edit:
Since finding my original problem was with NetLimiter 1.3 I have now installed 'NetLimiter 2.0.10.1 x86' and everything is working properly, so just more confirmation that it was the older NetLimiter 1.3 program that caused the problem and not necessarily all of the NetLimiter programs.
.