Hi grurndles,

Have a prob for all you geeks.

Last week my PC started to run slowly (on boot, on app open etc).

Today it failed to boot! First attempt I was presented with a blank 
screen after the POST. Second attempt I got the flashing cursor, the 
Windoze countdown bars along the bottom of the screen, and then an error 
message WHICH I FAILED TO WRITE DOWN !!!!!!!!!!!!!!!!!!!!!!! (I 
know...my only excuse was that I worked a 14 hour shift last night).

All I remember of the error was something like

Corrupt file  (here's where the memory goes a bit virtual)
C:\Windows\System32\Config\System

At least I think that's the path.

It points to a file called 'system' which has no file extention, is 
about 6Mb in size and, I assume, was created on install (Nov 06) because 
I can find no equivalent file on my Win CD (not in the dirs or the 
cabinet files, all of which have a creation date of March 03).

Now...can any of you kinds souls tell me whether I have to reinstall 
Windoze complete, or whether I can rebuild this file somehow.

I have just checked event viewer and there are shitloads of system error 
notifications. A few examples are (NB: indent numbers are mine);

1) The HTTP service failed to start due to the following error:
The specified procedure could not be found. (Event #7000)

2) The SSDP Discovery Service service depends on the HTTP service which 
failed to start because of the following error:
The specified procedure could not be found. (Event #7001)

3) The following boot-start or system-start driver(s) failed to load:
FltMgr
OMCI (Event #7026)

I guess the HTTP prob may be caused by Norton buggering with ports 80 or 
443 but I would have thought the protocol would have started anyway.

The events go back to at least 11/02/07, and are all produced by the 
Service Control Manager.

One other piece of info that may be relevant. About a week ago I managed 
to log on to the net with no AV or IntSec running!!!! (I had been 
running a game and always switch off all user services to make it run a 
bit faster - trouble is the icons were still showing in the SysTray.

Any ideas?
-- 
Loretta
A smile, a song, and a bucket of lard.

Loretta wrote:
> Hi grurndles,
> 
> Have a prob for all you geeks.
> 
> Last week my PC started to run slowly (on boot, on app open etc).

> Any ideas?
open the case and vacuum the shit out.

N

Loretta wrote:
> Hi grurndles,
> 
> Have a prob for all you geeks.
> 
> Last week my PC started to run slowly (on boot, on app open etc).

That could be congestion in your registry. This gets bigger and bigger 
as time goes on and can cause slow running.

> Today it failed to boot! First attempt I was presented with a blank 
> screen after the POST. Second attempt I got the flashing cursor, the 
> Windoze countdown bars along the bottom of the screen, and then an error 
> message WHICH I FAILED TO WRITE DOWN !!!!!!!!!!!!!!!!!!!!!!! (I 
> know...my only excuse was that I worked a 14 hour shift last night).
> 
> All I remember of the error was something like
> 
> Corrupt file  (here's where the memory goes a bit virtual)
> C:\Windows\System32\Config\System
> 
> At least I think that's the path.
> 
> It points to a file called 'system' which has no file extention, is 
> about 6Mb in size and, I assume, was created on install (Nov 06) because 
> I can find no equivalent file on my Win CD (not in the dirs or the 
> cabinet files, all of which have a creation date of March 03).
> 
> Now...can any of you kinds souls tell me whether I have to reinstall 
> Windoze complete, or whether I can rebuild this file somehow.

You might be able to get away with a system repair using the recovery 
disk you probably got instead of an OS disk when you bought the PC. 
Didn't work for me but then all PCs are different. (Thats one reason I'm 
running Linux these days!)

> I have just checked event viewer and there are shitloads of system error 
> notifications. A few examples are (NB: indent numbers are mine);
> 
> 1) The HTTP service failed to start due to the following error:
> The specified procedure could not be found. (Event #7000)
> 
> 2) The SSDP Discovery Service service depends on the HTTP service which 
> failed to start because of the following error:
> The specified procedure could not be found. (Event #7001)
> 
> 3) The following boot-start or system-start driver(s) failed to load:
> FltMgr
> OMCI (Event #7026)
> 
> I guess the HTTP prob may be caused by Norton buggering with ports 80 or 
> 443 but I would have thought the protocol would have started anyway.
> 
> The events go back to at least 11/02/07, and are all produced by the 
> Service Control Manager.
> 
> One other piece of info that may be relevant. About a week ago I managed 
> to log on to the net with no AV or IntSec running!!!! (I had been 
> running a game and always switch off all user services to make it run a 
> bit faster - trouble is the icons were still showing in the SysTray.
> 
> Any ideas?

In message <evdut0$6vv$1@news.freedom2surf.net>, John Wright 
 writes
>Loretta wrote:
>> Hi grurndles,
>>  Have a prob for all you geeks.
>>  Last week my PC started to run slowly (on boot, on app open etc).
>
>That could be congestion in your registry. This gets bigger and bigger 
>as time goes on and can cause slow running.
>
Good idea but I reinstalled Windoze about 10 months ago. The slow 
running is *very* noticeable, and fairly sudden. I think this is more a 
case of corruption rather than overweight.
>
>You might be able to get away with a system repair using the recovery 
>disk you probably got instead of an OS disk when you bought the PC. 
>Didn't work for me but then all PCs are different. (Thats one reason 
>I'm running Linux these days!)
>
I don't use OEM disks, only full install versions (so I can migrate when 
I need to). Prob is the file I think is corrupt is only created on 
install, which is a bit of a bugger.

Many thanks for the comments anyway.
-- 
Loretta
A smile, a song, and a bucket of lard.

In message <evdup4$ra2$1@aioe.org>, Nev Young 
 writes
>Loretta wrote:
>> Hi grurndles,
>>  Have a prob for all you geeks.
>>  Last week my PC started to run slowly (on boot, on app open etc).
>
>> Any ideas?
>open the case and vacuum the shit out.
>
I did that 3 months ago...just as I do every 3 months, and reseat all 
cards, memory, and cables. I also reseat the CPU every 9 months or so ( 
and put icky gunge on).

Temp probe from my multimeter shows CPU running within tolerance and the 
BIOS temp monitor shows it to be OK.

Thanks for the idea though.
-- 
Loretta
A smile, a song, and a bucket of lard.

Loretta wrote:
> In message <evdup4$ra2$1@aioe.org>, Nev Young 
>  writes
>> Loretta wrote:
>>> Hi grurndles,
>>>  Have a prob for all you geeks.
>>>  Last week my PC started to run slowly (on boot, on app open etc).
>>
>>> Any ideas?
>> open the case and vacuum the shit out.
>>
> I did that 3 months ago...just as I do every 3 months, and reseat all 
> cards, memory, and cables. I also reseat the CPU every 9 months or so ( 
> and put icky gunge on).
> 
Well I just filled my Dyson[tm] with the contents of a cooked peecee.
My next suggestion is enable, if not already done, the s.m.a.r.t. on the 
HDD and see if it's failing. (look for a program called "speedfan" to 
read smart stats). If HDD is failing then change it.

OR

if you have a spare HDD try it.

Nev

"Loretta"  wrote in message 
news:v26MyYB8JnGGFwFD@trawley.demon.co.uk...
> Hi grurndles,
>
> Have a prob for all you geeks.
>
> Last week my PC started to run slowly (on boot, on app open etc).
>
> Today it failed to boot! First attempt I was presented with a blank screen 
> after the POST. Second attempt I got the flashing cursor, the Windoze 
> countdown bars along the bottom of the screen, and then an error message 
> WHICH I FAILED TO WRITE DOWN !!!!!!!!!!!!!!!!!!!!!!! (I know...my only 
> excuse was that I worked a 14 hour shift last night).
>
> All I remember of the error was something like
>
> Corrupt file  (here's where the memory goes a bit virtual)
> C:\Windows\System32\Config\System
>
> At least I think that's the path.
>
> It points to a file called 'system' which has no file extention, is about 
> 6Mb in size and, I assume, was created on install (Nov 06) because I can 
> find no equivalent file on my Win CD (not in the dirs or the cabinet 
> files, all of which have a creation date of March 03).
>
> Now...can any of you kinds souls tell me whether I have to reinstall 
> Windoze complete, or whether I can rebuild this file somehow.
>
> I have just checked event viewer and there are shitloads of system error 
> notifications. A few examples are (NB: indent numbers are mine);
>
> 1) The HTTP service failed to start due to the following error:
> The specified procedure could not be found. (Event #7000)
>
> 2) The SSDP Discovery Service service depends on the HTTP service which 
> failed to start because of the following error:
> The specified procedure could not be found. (Event #7001)
>
> 3) The following boot-start or system-start driver(s) failed to load:
> FltMgr
> OMCI (Event #7026)
>
> I guess the HTTP prob may be caused by Norton buggering with ports 80 or 
> 443 but I would have thought the protocol would have started anyway.
>
> The events go back to at least 11/02/07, and are all produced by the 
> Service Control Manager.
>
> One other piece of info that may be relevant. About a week ago I managed 
> to log on to the net with no AV or IntSec running!!!! (I had been running 
> a game and always switch off all user services to make it run a bit 
> faster - trouble is the icons were still showing in the SysTray.
>
> Any ideas?

I've seen similar when i was running an internet cafe, in each case it was 
the hard drive getting ready to fail because of a boot sector virus. 
Reformatting and reinstalling worked for a little while but it always 
screwed the pooch again quicker and quicker until the drive died completely.

Loretta wrote:
> In message <evdut0$6vv$1@news.freedom2surf.net>, John Wright 
>  writes
>> Loretta wrote:
>>> Hi grurndles,
>>>  Have a prob for all you geeks.
>>>  Last week my PC started to run slowly (on boot, on app open etc).
>>
>> That could be congestion in your registry. This gets bigger and bigger 
>> as time goes on and can cause slow running.
>>
> Good idea but I reinstalled Windoze about 10 months ago. The slow 
> running is *very* noticeable, and fairly sudden. I think this is more a 
> case of corruption rather than overweight.
>>
>> You might be able to get away with a system repair using the recovery 
>> disk you probably got instead of an OS disk when you bought the PC. 
>> Didn't work for me but then all PCs are different. (Thats one reason 
>> I'm running Linux these days!)
>>
> I don't use OEM disks, only full install versions (so I can migrate when 
> I need to). Prob is the file I think is corrupt is only created on 
> install, which is a bit of a bugger.

Indeed, more than one Windoze guru round here says that recovery disks 
are the bane of life. However if you only ever use full install ones, 
(unless you get pirate ones from ebay or wherever) doesn't that mean 
you're paying Bill Gates through the nose)

-- 
John Wright

In message <evgqbj$us2$1@news.freedom2surf.net>, John Wright 
 writes
>Loretta wrote:
>> In message <evdut0$6vv$1@news.freedom2surf.net>, John Wright 
>> writes
>>> Loretta wrote:
>>>> Hi grurndles,
>>>>  Have a prob for all you geeks.
>>>>  Last week my PC started to run slowly (on boot, on app open etc).
>>>
>>> That could be congestion in your registry. This gets bigger and 
>>>bigger as time goes on and can cause slow running.
>>>
>> Good idea but I reinstalled Windoze about 10 months ago. The slow 
>>running is *very* noticeable, and fairly sudden. I think this is more 
>>a case of corruption rather than overweight.
>>>
>>> You might be able to get away with a system repair using the 
>>>recovery  disk you probably got instead of an OS disk when you bought 
>>>the PC.  Didn't work for me but then all PCs are different. (Thats 
>>>one reason  I'm running Linux these days!)
>>>
>> I don't use OEM disks, only full install versions (so I can migrate 
>>when I need to). Prob is the file I think is corrupt is only created 
>>on  install, which is a bit of a bugger.
>
>Indeed, more than one Windoze guru round here says that recovery disks 
>are the bane of life. However if you only ever use full install ones, 
>(unless you get pirate ones from ebay or wherever) doesn't that mean 
>you're paying Bill Gates through the nose)
>
Indeedy...but then an OEM version already installed can only be used on 
the PC it was intended for, and that costs enough already.

I may be a mug, but I'm a legal mug.
-- 
Loretta
A smile, a song, and a bucket of lard.

Loretta wrote:
> In message <evgqbj$us2$1@news.freedom2surf.net>, John Wright 
>  writes
>> Loretta wrote:
>>> In message <evdut0$6vv$1@news.freedom2surf.net>, John Wright 
>>>  writes
>>>> Loretta wrote:
>>>>> Hi grurndles,
>>>>>  Have a prob for all you geeks.
>>>>>  Last week my PC started to run slowly (on boot, on app open etc).
>>>>
>>>> That could be congestion in your registry. This gets bigger and 
>>>> bigger as time goes on and can cause slow running.
>>>>
>>> Good idea but I reinstalled Windoze about 10 months ago. The slow 
>>> running is *very* noticeable, and fairly sudden. I think this is more 
>>> a case of corruption rather than overweight.
>>>>
>>>> You might be able to get away with a system repair using the 
>>>> recovery  disk you probably got instead of an OS disk when you 
>>>> bought the PC.  Didn't work for me but then all PCs are different. 
>>>> (Thats one reason  I'm running Linux these days!)
>>>>
>>> I don't use OEM disks, only full install versions (so I can migrate 
>>> when I need to). Prob is the file I think is corrupt is only created 
>>> on  install, which is a bit of a bugger.
>>
>> Indeed, more than one Windoze guru round here says that recovery disks 
>> are the bane of life. However if you only ever use full install ones, 
>> (unless you get pirate ones from ebay or wherever) doesn't that mean 
>> you're paying Bill Gates through the nose)
>>
> Indeedy...but then an OEM version already installed can only be used on 
> the PC it was intended for, and that costs enough already.
> 
> I may be a mug, but I'm a legal mug.

Or simply being paid too much :-) the nice thing about Linux is its free.

-- 

John Wright

On Wed, 11 Apr 2007 22:33:31 +0100, John Wright wrote:

> Loretta wrote:
>> In message <evgqbj$us2$1@news.freedom2surf.net>, John Wright 
>>  writes
>>> Loretta wrote:
>>>> In message <evdut0$6vv$1@news.freedom2surf.net>, John Wright 
>>>>  writes
>>>>> Loretta wrote:
>>>>>> Hi grurndles,
>>>>>>  Have a prob for all you geeks.
>>>>>>  Last week my PC started to run slowly (on boot, on app open etc).
>>>>>
>>>>> That could be congestion in your registry. This gets bigger and 
>>>>> bigger as time goes on and can cause slow running.
>>>>>
>>>> Good idea but I reinstalled Windoze about 10 months ago. The slow 
>>>> running is *very* noticeable, and fairly sudden. I think this is more 
>>>> a case of corruption rather than overweight.
>>>>>
>>>>> You might be able to get away with a system repair using the 
>>>>> recovery  disk you probably got instead of an OS disk when you 
>>>>> bought the PC.  Didn't work for me but then all PCs are different. 
>>>>> (Thats one reason  I'm running Linux these days!)
>>>>>
>>>> I don't use OEM disks, only full install versions (so I can migrate 
>>>> when I need to). Prob is the file I think is corrupt is only created 
>>>> on  install, which is a bit of a bugger.
>>>
>>> Indeed, more than one Windoze guru round here says that recovery disks 
>>> are the bane of life. However if you only ever use full install ones, 
>>> (unless you get pirate ones from ebay or wherever) doesn't that mean 
>>> you're paying Bill Gates through the nose)
>>>
>> Indeedy...but then an OEM version already installed can only be used on 
>> the PC it was intended for, and that costs enough already.
>> 
>> I may be a mug, but I'm a legal mug.
> 
> Or simply being paid too much :-) the nice thing about Linux is its free.

The asprins are'nt.

Loretta wrote:
> Hi grurndles,
> 
> Have a prob for all you geeks.
> 
> Last week my PC started to run slowly (on boot, on app open etc).

> Any ideas?
open the case and vacuum the shit out.

N

Loretta wrote:
> Hi grurndles,
> 
> Have a prob for all you geeks.
> 
> Last week my PC started to run slowly (on boot, on app open etc).

That could be congestion in your registry. This gets bigger and bigger 
as time goes on and can cause slow running.

> Today it failed to boot! First attempt I was presented with a blank 
> screen after the POST. Second attempt I got the flashing cursor, the 
> Windoze countdown bars along the bottom of the screen, and then an error 
> message WHICH I FAILED TO WRITE DOWN !!!!!!!!!!!!!!!!!!!!!!! (I 
> know...my only excuse was that I worked a 14 hour shift last night).
> 
> All I remember of the error was something like
> 
> Corrupt file  (here's where the memory goes a bit virtual)
> C:\Windows\System32\Config\System
> 
> At least I think that's the path.
> 
> It points to a file called 'system' which has no file extention, is 
> about 6Mb in size and, I assume, was created on install (Nov 06) because 
> I can find no equivalent file on my Win CD (not in the dirs or the 
> cabinet files, all of which have a creation date of March 03).
> 
> Now...can any of you kinds souls tell me whether I have to reinstall 
> Windoze complete, or whether I can rebuild this file somehow.

You might be able to get away with a system repair using the recovery 
disk you probably got instead of an OS disk when you bought the PC. 
Didn't work for me but then all PCs are different. (Thats one reason I'm 
running Linux these days!)

> I have just checked event viewer and there are shitloads of system error 
> notifications. A few examples are (NB: indent numbers are mine);
> 
> 1) The HTTP service failed to start due to the following error:
> The specified procedure could not be found. (Event #7000)
> 
> 2) The SSDP Discovery Service service depends on the HTTP service which 
> failed to start because of the following error:
> The specified procedure could not be found. (Event #7001)
> 
> 3) The following boot-start or system-start driver(s) failed to load:
> FltMgr
> OMCI (Event #7026)
> 
> I guess the HTTP prob may be caused by Norton buggering with ports 80 or 
> 443 but I would have thought the protocol would have started anyway.
> 
> The events go back to at least 11/02/07, and are all produced by the 
> Service Control Manager.
> 
> One other piece of info that may be relevant. About a week ago I managed 
> to log on to the net with no AV or IntSec running!!!! (I had been 
> running a game and always switch off all user services to make it run a 
> bit faster - trouble is the icons were still showing in the SysTray.
> 
> Any ideas?

In message <evdut0$6vv$1@news.freedom2surf.net>, John Wright 
 writes
>Loretta wrote:
>> Hi grurndles,
>>  Have a prob for all you geeks.
>>  Last week my PC started to run slowly (on boot, on app open etc).
>
>That could be congestion in your registry. This gets bigger and bigger 
>as time goes on and can cause slow running.
>
Good idea but I reinstalled Windoze about 10 months ago. The slow 
running is *very* noticeable, and fairly sudden. I think this is more a 
case of corruption rather than overweight.
>
>You might be able to get away with a system repair using the recovery 
>disk you probably got instead of an OS disk when you bought the PC. 
>Didn't work for me but then all PCs are different. (Thats one reason 
>I'm running Linux these days!)
>
I don't use OEM disks, only full install versions (so I can migrate when 
I need to). Prob is the file I think is corrupt is only created on 
install, which is a bit of a bugger.

Many thanks for the comments anyway.
-- 
Loretta
A smile, a song, and a bucket of lard.

In message <evdup4$ra2$1@aioe.org>, Nev Young 
 writes
>Loretta wrote:
>> Hi grurndles,
>>  Have a prob for all you geeks.
>>  Last week my PC started to run slowly (on boot, on app open etc).
>
>> Any ideas?
>open the case and vacuum the shit out.
>
I did that 3 months ago...just as I do every 3 months, and reseat all 
cards, memory, and cables. I also reseat the CPU every 9 months or so ( 
and put icky gunge on).

Temp probe from my multimeter shows CPU running within tolerance and the 
BIOS temp monitor shows it to be OK.

Thanks for the idea though.
-- 
Loretta
A smile, a song, and a bucket of lard.

Loretta wrote:
> In message <evdup4$ra2$1@aioe.org>, Nev Young 
>  writes
>> Loretta wrote:
>>> Hi grurndles,
>>>  Have a prob for all you geeks.
>>>  Last week my PC started to run slowly (on boot, on app open etc).
>>
>>> Any ideas?
>> open the case and vacuum the shit out.
>>
> I did that 3 months ago...just as I do every 3 months, and reseat all 
> cards, memory, and cables. I also reseat the CPU every 9 months or so ( 
> and put icky gunge on).
> 
Well I just filled my Dyson[tm] with the contents of a cooked peecee.
My next suggestion is enable, if not already done, the s.m.a.r.t. on the 
HDD and see if it's failing. (look for a program called "speedfan" to 
read smart stats). If HDD is failing then change it.

OR

if you have a spare HDD try it.

Nev

"Loretta"  wrote in message 
news:v26MyYB8JnGGFwFD@trawley.demon.co.uk...
> Hi grurndles,
>
> Have a prob for all you geeks.
>
> Last week my PC started to run slowly (on boot, on app open etc).
>
> Today it failed to boot! First attempt I was presented with a blank screen 
> after the POST. Second attempt I got the flashing cursor, the Windoze 
> countdown bars along the bottom of the screen, and then an error message 
> WHICH I FAILED TO WRITE DOWN !!!!!!!!!!!!!!!!!!!!!!! (I know...my only 
> excuse was that I worked a 14 hour shift last night).
>
> All I remember of the error was something like
>
> Corrupt file  (here's where the memory goes a bit virtual)
> C:\Windows\System32\Config\System
>
> At least I think that's the path.
>
> It points to a file called 'system' which has no file extention, is about 
> 6Mb in size and, I assume, was created on install (Nov 06) because I can 
> find no equivalent file on my Win CD (not in the dirs or the cabinet 
> files, all of which have a creation date of March 03).
>
> Now...can any of you kinds souls tell me whether I have to reinstall 
> Windoze complete, or whether I can rebuild this file somehow.
>
> I have just checked event viewer and there are shitloads of system error 
> notifications. A few examples are (NB: indent numbers are mine);
>
> 1) The HTTP service failed to start due to the following error:
> The specified procedure could not be found. (Event #7000)
>
> 2) The SSDP Discovery Service service depends on the HTTP service which 
> failed to start because of the following error:
> The specified procedure could not be found. (Event #7001)
>
> 3) The following boot-start or system-start driver(s) failed to load:
> FltMgr
> OMCI (Event #7026)
>
> I guess the HTTP prob may be caused by Norton buggering with ports 80 or 
> 443 but I would have thought the protocol would have started anyway.
>
> The events go back to at least 11/02/07, and are all produced by the 
> Service Control Manager.
>
> One other piece of info that may be relevant. About a week ago I managed 
> to log on to the net with no AV or IntSec running!!!! (I had been running 
> a game and always switch off all user services to make it run a bit 
> faster - trouble is the icons were still showing in the SysTray.
>
> Any ideas?

I've seen similar when i was running an internet cafe, in each case it was 
the hard drive getting ready to fail because of a boot sector virus. 
Reformatting and reinstalling worked for a little while but it always 
screwed the pooch again quicker and quicker until the drive died completely.

Loretta wrote:
> In message <evdut0$6vv$1@news.freedom2surf.net>, John Wright 
>  writes
>> Loretta wrote:
>>> Hi grurndles,
>>>  Have a prob for all you geeks.
>>>  Last week my PC started to run slowly (on boot, on app open etc).
>>
>> That could be congestion in your registry. This gets bigger and bigger 
>> as time goes on and can cause slow running.
>>
> Good idea but I reinstalled Windoze about 10 months ago. The slow 
> running is *very* noticeable, and fairly sudden. I think this is more a 
> case of corruption rather than overweight.
>>
>> You might be able to get away with a system repair using the recovery 
>> disk you probably got instead of an OS disk when you bought the PC. 
>> Didn't work for me but then all PCs are different. (Thats one reason 
>> I'm running Linux these days!)
>>
> I don't use OEM disks, only full install versions (so I can migrate when 
> I need to). Prob is the file I think is corrupt is only created on 
> install, which is a bit of a bugger.

Indeed, more than one Windoze guru round here says that recovery disks 
are the bane of life. However if you only ever use full install ones, 
(unless you get pirate ones from ebay or wherever) doesn't that mean 
you're paying Bill Gates through the nose)

-- 
John Wright

In message <evgqbj$us2$1@news.freedom2surf.net>, John Wright 
 writes
>Loretta wrote:
>> In message <evdut0$6vv$1@news.freedom2surf.net>, John Wright 
>> writes
>>> Loretta wrote:
>>>> Hi grurndles,
>>>>  Have a prob for all you geeks.
>>>>  Last week my PC started to run slowly (on boot, on app open etc).
>>>
>>> That could be congestion in your registry. This gets bigger and 
>>>bigger as time goes on and can cause slow running.
>>>
>> Good idea but I reinstalled Windoze about 10 months ago. The slow 
>>running is *very* noticeable, and fairly sudden. I think this is more 
>>a case of corruption rather than overweight.
>>>
>>> You might be able to get away with a system repair using the 
>>>recovery  disk you probably got instead of an OS disk when you bought 
>>>the PC.  Didn't work for me but then all PCs are different. (Thats 
>>>one reason  I'm running Linux these days!)
>>>
>> I don't use OEM disks, only full install versions (so I can migrate 
>>when I need to). Prob is the file I think is corrupt is only created 
>>on  install, which is a bit of a bugger.
>
>Indeed, more than one Windoze guru round here says that recovery disks 
>are the bane of life. However if you only ever use full install ones, 
>(unless you get pirate ones from ebay or wherever) doesn't that mean 
>you're paying Bill Gates through the nose)
>
Indeedy...but then an OEM version already installed can only be used on 
the PC it was intended for, and that costs enough already.

I may be a mug, but I'm a legal mug.
-- 
Loretta
A smile, a song, and a bucket of lard.

Loretta wrote:
> In message <evgqbj$us2$1@news.freedom2surf.net>, John Wright 
>  writes
>> Loretta wrote:
>>> In message <evdut0$6vv$1@news.freedom2surf.net>, John Wright 
>>>  writes
>>>> Loretta wrote:
>>>>> Hi grurndles,
>>>>>  Have a prob for all you geeks.
>>>>>  Last week my PC started to run slowly (on boot, on app open etc).
>>>>
>>>> That could be congestion in your registry. This gets bigger and 
>>>> bigger as time goes on and can cause slow running.
>>>>
>>> Good idea but I reinstalled Windoze about 10 months ago. The slow 
>>> running is *very* noticeable, and fairly sudden. I think this is more 
>>> a case of corruption rather than overweight.
>>>>
>>>> You might be able to get away with a system repair using the 
>>>> recovery  disk you probably got instead of an OS disk when you 
>>>> bought the PC.  Didn't work for me but then all PCs are different. 
>>>> (Thats one reason  I'm running Linux these days!)
>>>>
>>> I don't use OEM disks, only full install versions (so I can migrate 
>>> when I need to). Prob is the file I think is corrupt is only created 
>>> on  install, which is a bit of a bugger.
>>
>> Indeed, more than one Windoze guru round here says that recovery disks 
>> are the bane of life. However if you only ever use full install ones, 
>> (unless you get pirate ones from ebay or wherever) doesn't that mean 
>> you're paying Bill Gates through the nose)
>>
> Indeedy...but then an OEM version already installed can only be used on 
> the PC it was intended for, and that costs enough already.
> 
> I may be a mug, but I'm a legal mug.

Or simply being paid too much :-) the nice thing about Linux is its free.

-- 

John Wright

On Wed, 11 Apr 2007 22:33:31 +0100, John Wright wrote:

> Loretta wrote:
>> In message <evgqbj$us2$1@news.freedom2surf.net>, John Wright 
>>  writes
>>> Loretta wrote:
>>>> In message <evdut0$6vv$1@news.freedom2surf.net>, John Wright 
>>>>  writes
>>>>> Loretta wrote:
>>>>>> Hi grurndles,
>>>>>>  Have a prob for all you geeks.
>>>>>>  Last week my PC started to run slowly (on boot, on app open etc).
>>>>>
>>>>> That could be congestion in your registry. This gets bigger and 
>>>>> bigger as time goes on and can cause slow running.
>>>>>
>>>> Good idea but I reinstalled Windoze about 10 months ago. The slow 
>>>> running is *very* noticeable, and fairly sudden. I think this is more 
>>>> a case of corruption rather than overweight.
>>>>>
>>>>> You might be able to get away with a system repair using the 
>>>>> recovery  disk you probably got instead of an OS disk when you 
>>>>> bought the PC.  Didn't work for me but then all PCs are different. 
>>>>> (Thats one reason  I'm running Linux these days!)
>>>>>
>>>> I don't use OEM disks, only full install versions (so I can migrate 
>>>> when I need to). Prob is the file I think is corrupt is only created 
>>>> on  install, which is a bit of a bugger.
>>>
>>> Indeed, more than one Windoze guru round here says that recovery disks 
>>> are the bane of life. However if you only ever use full install ones, 
>>> (unless you get pirate ones from ebay or wherever) doesn't that mean 
>>> you're paying Bill Gates through the nose)
>>>
>> Indeedy...but then an OEM version already installed can only be used on 
>> the PC it was intended for, and that costs enough already.
>> 
>> I may be a mug, but I'm a legal mug.
> 
> Or simply being paid too much :-) the nice thing about Linux is its free.

The asprins are'nt.