Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


pointertovoid

Reduce the size of the registry?

Recommended Posts

Hello everybody!

I had recently again the already known "C\Win\Sys32\Config\System missing or corrupt" error preventing W2k booting.

This was solved by reverting Ntldr+Ntdetect from 5.1 to 5.0 and at the same time pasting a 2 week older System hive.

But I'm looking for other solutions.

- In a 2k-Xp dual-boot scheme, having Ntldr+Ntdetect v5.1 is much easier!

http://www.msfn.org/board/please-help-w-du...ml&t=127900

- The same error is known to exist with Ntldr+Ntdetect v5.0 and even v4.0

http://support.microsoft.com/kb/306038/en-us

So I would like to reduce efficiently the size of the registry, which at first glance looks like a more elegant solution, and might accelerate Win startup as well.

I used RegClean, RegCompact, NtRegOpt with disappointing results. Only the Software hive shrank by just 4%, with no effect on boot time. Hives now weigh:

Software 20MB, System 6MB, my NtUser >3MB, others smaller

So are there more efficient ways? Maybe, repair W2k using a more recently HfSlipped Cd?

-----

Just for fun: this failure to boot appeared shortly after I installed a mouse driver - yes sir - that added 1700 files - yes sir again. I wanted to scroll windows without clicking in them (like my stone-old 4dmain v1.0 from Aidem does) but all this new driver brought to me were help files to use the Control Panel settings by Microsoft, and buttons to download an even newer version of this wonderful driver, all needing an added task.

-----

Thanks!

Share this post


Link to post
Share on other sites

Nothing beats good old manual slashing. :DThis might help. :hello:

GL

Share this post


Link to post
Share on other sites
But I'm looking for other solutions.

NO you are not. ;)

ANother solution has been given in the thread you referenced.

You are looking for a way to perform the Registry shrink solution.

I agree that slimming down the Registry is a better and more elegant way, but you cannot slim it down if not up to a certain limit.

I would try RegSeeker, but do not expect miracles:

http://www.hoverdesk.net/freeware.htm

The sizes you report do not seem to me "abnormal". :unsure:

Something you may want to explore would be to reduce the ControlSet002 to the bare minimum, but you are effectively losing (at least partially) an "escape pod" in case of troubles.

You sure you have just ControlSet001 and ControlSet002, I had a 2K machines where in time I had as much as 5 ControlSets.

Using the nirsoft tool that GrofLuigi suggested, this usually results as a "problematic" area:

http://www.pctools.com/guides/registry/detail/1238/

jaclaz

Share this post


Link to post
Share on other sites
...So I would like to reduce efficiently the size of the registry, which at first glance looks like a more elegant solution, and might accelerate Win startup as well.

...

create a new user account with administrator rights, and then copy all previous documents back into the new user folder, except ntuser.*. keep it safe just in case you need the customization as well as the corrupted data.

Share this post


Link to post
Share on other sites

Thanks everybody!

- NtRegOpt had brought very little reduction in size;

- Yes I like W2k, but not only. I also have W95b which is good. Future will tell us about Seven.

- A new user account? Nice idea! I didn't try because I expect this reduces only Ntuser, though my Software hive is big. Or does it?

- ControlSet003: I had one too many, it saved some room.

- I also used Nirsoft's tool and slashed a help file that was integrated in two languages in the registry, don't ask me why. Saved a bit as well.

And then I had gained very few %, which means that the worry would reappear soon on this computer used by a granny who couldn't fix it. So I decided to revert to Ntldr and Ntdetect v5.0, alas.

Share this post


Link to post
Share on other sites

Is this a bug of NtDetect 5.1 or of Ntldr 5.1, when double-booting with W2k?

And why the heck was this never fixed? Sp4 for W2k was issued 2 years after Xp, so Xp could have been fixed!

Or would there be a non-official fix?

Share this post


Link to post
Share on other sites

This message is usually a sign that the hard disk is on the way out. Run chkdsk from safe mode for a start.

If ye get messages about corrupt $i30 sector, just get a new hard disk.

Share this post


Link to post
Share on other sites

[...]I wanted to scroll windows without clicking in them (like my stone-old 4dmain v1.0 from Aidem does) but all this new driver brought to me were help files to use the Control Panel settings by Microsoft, and buttons to download an even newer version of this wonderful driver, all needing an added task.

Thanks!

For any one wanting to scroll windows without clicking in them, and a lot more as well, I thought I would add in this smart little tool I have in every windows install, I cant do without it now.

http://pitaschio.ara3.net/

Also a lifeHacker page about it can be found at...

http://lifehacker.com/software/featured-windows-download/make-minor-windows-tweaks-with-pitaschio-260608.php

Share this post


Link to post
Share on other sites

Thanks Lenny_Nero! Tried Pitaschio, looks interesting, started an other topic about it.

os2fan2: nothing to do with the hard disk, as the beginning of the thread shows.

Share this post


Link to post
Share on other sites

if youre registry keeps getting corrupt the problem is not the size, some 3rd party program thats not compatible with win2k is causing the problem. The system hive stores settings for HKLM and for services, its very likely some 3rd party service borked things up.

Share this post


Link to post
Share on other sites

It is precisely a matter of size of the registry.

The registry isn't corrupt.

The worry is exactly linked with Xp's Ntldr and its known limitation.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...