v1.5.2 Problems on Win2k

[geoapps]

Had some serious problems upgrading some 1.4 installations to 1.5.2 on Windows 2000 tonight.

First, the HOSTS file immunization is missing. These machines have Windows in C:\WINNT and it appears that SSD can't deal with this.

Second, and most serious, is that I am getting the following error on multiple machines:


After this error shows up, the immunization stops. On one machine I increased the RegistrySizeLimit to 0xfffffff as per Microsoft's KB article on this, rebooted, but got the same error on reboot. Once I uninstall SSDv1.5.2 from these Win2k systems the "max registry size" errors go away so it's pretty clear it's related to SSD.

[PepiMK]

As for the Hosts file immunization, that's a feature, not a bug
See Hosts file immunization and Windows 2000
Hosts file immunization on Windows 2000 causes the system to go to full load regularly unless you deactivate the DNS Client service.

As for the registry, uninstalling Spybot-S&D actually shouldn't change a thing (neither should installing it). Granted, the immunization adds a few KB to the registry file, but uninstalling Spybot-S&D wouldn't undo the immunization.

After uninstalling Spybot-S&D, TeaTimer will no longer be active, which is about the only thing that could cause this in boot. Not because I would knew about anything in there that could cause it, but because it's the only thing that runs on startup and could cause that message. The only registry-related part it uses is an officially documented "notify me on changes of that registry key" handler, which shouldn't cause any size problems at all.

[geoapps]

As for the Hosts file immunization, that's a feature, not a bug

now where have I heard that before [g,d,rlh]

See Hosts file immunization and Windows 2000
Hosts file immunization on Windows 2000 causes the system to go to full load regularly unless you deactivate the DNS Client service.

Thanks for the warning ...

As for the registry, uninstalling Spybot-S&D actually shouldn't change a thing (neither should installing it). Granted, the immunization adds a few KB to the registry file, but uninstalling Spybot-S&D wouldn't undo the immunization.

After uninstalling Spybot-S&D, TeaTimer will no longer be active, which is about the only thing that could cause this in boot. Not because I would knew about anything in there that could cause it, but because it's the only thing that runs on startup and could cause that message. The only registry-related part it uses is an officially documented "notify me on changes of that registry key" handler, which shouldn't cause any size problems at all.

Well, all I know is that removed SSDv1.4 from two Win2kSP4 machines, installed SSDv1.5.2, and both were throwing the above error. Uninstalling SSD and rebooting cleared both up.