Bugs in 1.5.2rc1

[martin.leese]

Just installed spybotsd152rc1 under Windows 95. There were a couple of bugs.

The first is that the bug reported on October 7, 2007 here:
http://forums.spybot.info/showthread.php?t=18806

has not been fixed. Instead of Spybot-SD Resident taking 13 minutes to fire up, it now takes 20 minutes. This is a shame because this bug was my sole reason for upgrading from the Helloween Edition. The bug is annoying because, until Spybot-SD Resident fires up, clicking on a file in Explorer doesn't fire up the relevant program but, instead, hangs. That is to say, clicking on file.doc doesn't fire up MS Word until Spybot-SD Resident has started running. (The work around is to start MS Word and then use File => Open.)

I checked a couple of things:
Advanced mode => Tools => System Startup lists only Tea Timer under SpybotSD.
Advanced mode => Tools => Resident shows a tick only by Resident "SDHelper" active.

The second bug was a minor problem during installation. On the File Download screen, the Speed: is shown as " KB/s" (ie, no actual speed). Also, the Current File: and Overall Progress: bars worked fine, but the text on the right was gibberish. It looked like "___KB of ___ KB (___%)" except that the underscores were nonsense that looked like Inuit syllabics.

Please fix these bugs before release.

[PepiMK]

The second bug is known, see for example here (http://forums.spybot.info/showthread.php?t=1180). There are two versions of the download part of the installer available; the older one 5.1.0 is compatible with Windows 95, the newest one 5.1.5 has this GUI bug fixed.
I've created a feature request for Win95 compatibility on the authors SourceForge page (http://sourceforge.net/tracker/index.php?func=detail&aid=1876429&group_id=206943&atid=999625), maybe we'll get Win95 support back, in which case we could have both bugs fixed.

As for the first one, I just started TeaTimer in my Windows 95c virtual machine, and it came up in 20 seconds. Granted, the host machine is for times as fast as 500 Mhz, but virtualization takes its toll, and with 64 MB, it's even smaller than your 128.
All in all, I still suspect that your machine just hasn't got enough RAM left, and that it is slow because it's doing a lot of memory swapping to be able to run AV and AS parallel to each other. Maybe you could use the System Monitor that comes with Win95 to monitor the free memory (and possibly also page faults, which are not "faults" in the classical error sense) while TeaTimer loads?

[martin.leese]

The second bug is known, see for example here (http://forums.spybot.info/showthread.php?t=1180). There are two versions of the download part of the installer available; the older one 5.1.0 is compatible with Windows 95, the newest one 5.1.5 has this GUI bug fixed.
I've created a feature request for Win95 compatibility on the authors SourceForge page (http://sourceforge.net/tracker/index.php?func=detail&aid=1876429&group_id=206943&atid=999625), maybe we'll get Win95 support back, in which case we could have both bugs fixed.

Many thanks for this. The install still works fine, so this is a minor bug.


As for the first one, I just started TeaTimer in my Windows 95c virtual machine, and it came up in 20 seconds. Granted, the host machine is for times as fast as 500 Mhz, but virtualization takes its toll, and with 64 MB, it's even smaller than your 128.
All in all, I still suspect that your machine just hasn't got enough RAM left, and that it is slow because it's doing a lot of memory swapping to be able to run AV and AS parallel to each other. Maybe you could use the System Monitor that comes with Win95 to monitor the free memory (and possibly also page faults, which are not "faults" in the classical error sense) while TeaTimer loads?

Booting with nothing else running (except System Monitor), Spybot-S&D Resident took 25 minutes 20 seconds to come up. AVG 7.5 (anti-virus) Resident came up after 1 minute 16 seconds (and I immediately Quit it).

During this 25 minutes, the Memory Manager: Free Memory started out at 20 M and very, very gradually reduced to zero. The Memory Manager: Page Faults started out at 25, quickly went up to 218, but then settled after 2 minutes at around 12 with occasional leaps above. The Kernel: Processor Usage was stuck at 100%. The Kernel: Threads stayed between 36 and 38.

I keep remembering the similar problem with Spybot itself (issue 85) described here:
http://forums.spybot.info/project.php?issueid=85

Are you sure this isn't just the same thing, but in Tea Timer?