LoneLurker
2008-02-18, 22:21
This is to inform you I have removed the RunAlyzr program, as it seems to run even when it is not running. What I mean by that is the Drive Light is very active or flashes very brightly and very often, after the removal the light is not shown very much. Have had a problem with my system re-booting when starting up, some times it will allow me to login then it re-boots. Before learning of the 'Last Good Configuration' it would re-boot several times if allowed to just run. The only way to get in is to do the F8 thingy and select the 'Last Good Configuration" then I can get in and check what has occurred.
In the Registry under HK_L_M\System\ there are usually four 'ControlSetxxx', 'ControlSetDefault' or 'CurrentControlSet' with 'LastGoodControlSet' this last one ususally will have NO entry. One time when it was re-booting 'ContolSet001' looked just fine, but; 'ContolSet002' under the 'Control' KEY was very short. The problem I have with RunAlyzr is it was listing 'ContolSet001,' 'ContolSet003,' 'ContolSet004,' 'CurrentControlSet' with 'ContolSet003,' shown as 'FAILED' the others were supposed to be good. That was before the re-boot with 'CS002' still shown in the registry. I later did a re-boot and the ControlSet002 was gone from the registry and the same 'ControlSetxxx' were still listed, but; all were shown as good. The automatic re-boot has occurred for the last five days. I feel this problem, automatic re-boot, is caused by RunAlyzr as it started with that installation. I have removed it this day and will report if the automatic re-boot is still occurring or not, later.
I like the features of RunAlyzr except for the length of time it takes to run a full scan to collect all of the data before any actions or even examinations can take place. Maybe set it to have those tabs selectable for whatever we need or want to examine along with a count UP timer in GREEN so when it is run again the times can be compared and we know how long it will take the next time it is run. I know this will be adding much to the program, maybe not have it take over our systems to the MAX, reduce it's share of the processor so we may do other things. Mine takes about 1.5 to 1.75 hours to run. My O/S and system are in my sig.
If you have any questions on this please ask them and as a user I will attempt to answer,
In the Registry under HK_L_M\System\ there are usually four 'ControlSetxxx', 'ControlSetDefault' or 'CurrentControlSet' with 'LastGoodControlSet' this last one ususally will have NO entry. One time when it was re-booting 'ContolSet001' looked just fine, but; 'ContolSet002' under the 'Control' KEY was very short. The problem I have with RunAlyzr is it was listing 'ContolSet001,' 'ContolSet003,' 'ContolSet004,' 'CurrentControlSet' with 'ContolSet003,' shown as 'FAILED' the others were supposed to be good. That was before the re-boot with 'CS002' still shown in the registry. I later did a re-boot and the ControlSet002 was gone from the registry and the same 'ControlSetxxx' were still listed, but; all were shown as good. The automatic re-boot has occurred for the last five days. I feel this problem, automatic re-boot, is caused by RunAlyzr as it started with that installation. I have removed it this day and will report if the automatic re-boot is still occurring or not, later.
I like the features of RunAlyzr except for the length of time it takes to run a full scan to collect all of the data before any actions or even examinations can take place. Maybe set it to have those tabs selectable for whatever we need or want to examine along with a count UP timer in GREEN so when it is run again the times can be compared and we know how long it will take the next time it is run. I know this will be adding much to the program, maybe not have it take over our systems to the MAX, reduce it's share of the processor so we may do other things. Mine takes about 1.5 to 1.75 hours to run. My O/S and system are in my sig.
If you have any questions on this please ask them and as a user I will attempt to answer,