Question and Request for added feature to LRC

Asked by zak k on 2011-03-01

Hi Nick,

I notice that a lot of people are having 'not responding' problems with LRC when the number of registry errors goes above a certain amount (say 600). For me this happens when I am scanning the ActiveX/COM and I usually get 1000 or so errors. I have to let the computer sit for 20 minutes or so, so that LRC does its thing. I was wondering if you could add a 'pause and fix' option to the scan so that for example one can pause the scan once 300 errors are found and do a fix and then continue the scan for the next 300 errors and so on ( I hope that makes sense). This way the computer should be able to handle the fixes much more efficiently specially when not enough RAM is available. Looking forward to hearing back from you.

ZAK

Question information

Language:
English Edit question
Status:
Answered
For:
Little Registry Cleaner Edit question
Assignee:
No assignee Edit question
Last query:
2011-03-01
Last reply:
2011-03-22
Nick (ub3rst4r) said : #1

Hi, once I get some time ill try and work on it. Thanks

On 1 Mar 2011 12:42, "zak k" <email address hidden> wrote:

New question #147424 on Little Registry Cleaner:
https://answers.launchpad.net/lilregcleaner/+question/147424

Hi Nick,

I notice that a lot of people are having 'not responding' problems with LRC
when the number of registry errors goes above a certain amount (say 600).
For me this happens when I am scanning the ActiveX/COM and I usually get
1000 or so errors. I have to let the computer sit for 20 minutes or so, so
that LRC does its thing. I was wondering if you could add a 'pause and fix'
option to the scan so that for example one can pause the scan once 300
errors are found and do a fix and then continue the scan for the next 300
errors and so on ( I hope that makes sense). This way the computer should be
able to handle the fixes much more efficiently specially when not enough RAM
is available. Looking forward to hearing back from you.

ZAK

--
You received this question notification because you are an answer
contact for Little Registry Cleaner.

LAN (xfire) said : #2

This problem is much more pronounced on lower end systems. My computer is quite a few years old, and I don't normally do registry cleaning. LRC finds around 2572-2575 problems, then leading to the CPU maxing out as it tries to generate the list. However, I let LRC run for over a hour without any other programs running, and the list never came up. Whenever is most convenient, would it be possible if there be a minor patch that could ease this problem until a full fix can be implemented?

Nick (ub3rst4r) said : #3

Hi LAN, Please understand that I am very busy right now and that I am the only one maintaining this project. In the meantime, can you please tell me the specs for your computer (ie: cpu speed, ram, & operating system). Thanks!

LAN (xfire) said : #4

I did not mean to be rude. I am sorry it came off as such. Anyway, here is an overview of my specs:

<<< System Summary >>>
  > Manufacturer : eMachines
  > Mainboard : Unspecified Unspecified
  > Chipset : Intel i845G
  > Processor : Intel Celeron D 330 @ 2666 MHz
  > Physical Memory : 512 MB (1 x 512 DDR-SDRAM )
  > Video Card : Intel Corporation 82845G/GL/GV/GE/PE Integrated Graphics Device
  > Hard Disk : MAXTOR (320 GB)
  > Hard Disk : WDC (80 GB)
  > DVD-Rom Drive : JLMS XJ-HD166S
  > CD-Rom Drive : HL-DT-ST CD-RW GCE-8483B
  > DVD-Rom Drive : MagicISO Virtual DVD-ROM0000
  > Monitor Type : eView 17f3 - 16 inches
  > Network Card : Marvell Semiconductor (Was: Galileo Technology Ltd) W8300 802.11 Adapter
  > Network Card : Intel Corporation 82801DB/DBL (ICH4/ICH4-L) PRO/100 VE Network Connection
  > Operating System : Microsoft Windows XP Home Edition 5.01.2600 Service Pack 3
  > DirectX : Version 9.0c (April 2009)

Can you help with this problem?

Provide an answer of your own, or ask zak k for more information if necessary.

To post a message you must log in.