Spybot Problem - A Workaround

[Guest Nigel Stapley]

Some of you may be finding that the latest versions of Spybot S&D (1.5.1

and above) won't run on 98, giving the following error:

 

"Exception EAccessViolation in module SPYBOTSD.EXE at 002E 6098. Access

violation at address 006E 609B in module 'SPYBOTSD.EXE'. Read of address

FFFFFFFF."

 

Someone on the Spybot forums has come up with a workaround, namely that

you start Dr Watson first, *then* run Spybot.

 

It seems to work. Safer-Networking claim that the problem is caused by

Windows memory management, but I'm not convinced.

 

Hope this helps.

 

--

Regards

 

Nigel Stapley

 

http://www.judgemental.plus.com

 

<reply-to will bounce>

[Guest AlmostBob]

Re: Spybot Problem - A Workaround

 

repaired in 1.5.2

 

update to a current version

 

--

-- -- -- -- --

Adaware http://www.lavasoft.de

spybot http://www.safer-networking.org

AVG free antivirus http://free.grisoft.com/

Etrust/Vet/CA.online Antivirus scan

http://www3.ca.com/securityadvisor/virusinfo/scan.aspx

Super Antispyware http://www.superantispyware.com/

Panda online AntiVirus scan http://www.activescan.com

Panda online AntiSpyware Scan

http://www.pandasoftware.com/virus_info/spyware/test/

Catalog of removal tools (1)

http://www.pandasoftware.com/download/utilities/

Catalog of removal tools (2)

http://www3.ca.com/securityadvisor/newsinfo/collateral.aspx?CID=40387

Trouble Shooting guide to Windows http://mvps.org/winhelp2002/

Blocking Unwanted Parasites with a Hosts file

http://mvps.org/winhelp2002/hosts.htm

links provided as a courtesy, read all instructions on the pages before

use

Grateful thanks to the authors/webmasters

_

"Nigel Stapley" <unet@judgemental.plus.com> wrote in message

news:13s3d10qgi1toc4@corp.supernews.com...

> Some of you may be finding that the latest versions of Spybot S&D (1.5.1

> and above) won't run on 98, giving the following error:

>

> "Exception EAccessViolation in module SPYBOTSD.EXE at 002E 6098. Access

> violation at address 006E 609B in module 'SPYBOTSD.EXE'. Read of address

> FFFFFFFF."

>

> Someone on the Spybot forums has come up with a workaround, namely that

> you start Dr Watson first, *then* run Spybot.

>

> It seems to work. Safer-Networking claim that the problem is caused by

> Windows memory management, but I'm not convinced.

>

> Hope this helps.

>

> --

> Regards

>

> Nigel Stapley

>

> http://www.judgemental.plus.com

>

> <reply-to will bounce>

[Guest Nigel Stapley]

Re: Spybot Problem - A Workaround

 

AlmostBob wrote:

> repaired in 1.5.2

>

 

No it isn't.

> update to a current version

>

 

See above.

 

--

Regards

 

Nigel Stapley

 

http://www.judgemental.plus.com

 

<reply-to will bounce>

[Guest bobster]

Re: Spybot Problem - A Workaround

 

I have version 1.5.2.20 and Windows 98SE and have no problem.

=====================================================

"Nigel Stapley" <unet@judgemental.plus.com> wrote in message

news:13s5c453e1he71d@corp.supernews.com...

AlmostBob wrote:

> repaired in 1.5.2

>

 

No it isn't.

> update to a current version

>

 

See above.

 

--

Regards

 

Nigel Stapley

 

http://www.judgemental.plus.com

 

<reply-to will bounce>

[Guest MEB]

Re: Spybot Problem - A Workaround

 

 

 

"Nigel Stapley" <unet@judgemental.plus.com> wrote in message

news:13s3d10qgi1toc4@corp.supernews.com...

| Some of you may be finding that the latest versions of SpyBot S&D (1.5.1

| and above) won't run on 98, giving the following error:

|

| "Exception EAccessViolation in module SPYBOTSD.EXE at 002E 6098. Access

| violation at address 006E 609B in module 'SPYBOTSD.EXE'. Read of address

| FFFFFFFF."

|

| Someone on the Spybot forums has come up with a workaround, namely that

| you start Dr Watson first, *then* run Spybot.

|

| It seems to work. Safer-Networking claim that the problem is caused by

| Windows memory management, but I'm not convinced.

|

| Hope this helps.

|

| --

| Regards

|

| Nigel Stapley

|

| http://www.judgemental.plus.com

|

| <reply-to will bounce>

 

Along those lines: monitoring several other forums which have and or are

discussing these same types of issues, it would appear that these issues

might be cropping up on boards designed for newer OSs [OSs with increased

addressing space and chipsets which require that space] running 9X and newer

AGP cards and other hardware [and extended addressing requirements]. Nothing

concrete here, but it seems that these are the systems running into these

issues more often than the older computer configurations, that are NOT

having issues with the below.

 

Another potential seems to be the amount of already running programs, such

as one of the Anti-V or firewall programs which load several other on-access

servers/applications for SpyWare, phishing, Spam, etc... The 9X systems are

running out of static memory addressing space..

 

Glad someone came up with a temporary work-around.

 

--

 

MEB

http://peoplescounsel.orgfree.com

_________

[Guest Franc Zabkar]

Re: Spybot Problem - A Workaround

 

On Sun, 24 Feb 2008 18:15:06 +0000, Nigel Stapley

<unet@judgemental.plus.com> put finger to keyboard and composed:

>Some of you may be finding that the latest versions of Spybot S&D (1.5.1

>and above) won't run on 98, giving the following error:

>

>"Exception EAccessViolation in module SPYBOTSD.EXE at 002E 6098. Access

>violation at address 006E 609B in module 'SPYBOTSD.EXE'. Read of address

>FFFFFFFF."

>

>Someone on the Spybot forums has come up with a workaround, namely that

>you start Dr Watson first, *then* run Spybot.

>

>It seems to work. Safer-Networking claim that the problem is caused by

>Windows memory management, but I'm not convinced.

>

>Hope this helps.

 

I've never seen that problem with version 1.4 and I don't see it after

upgrading directly from 1.4 to 1.5.2.

 

What I *do* notice is that Spybot is a voracious resource hog.

 

This is how Resource Meter reports my resource usage:

 

System User GDI (% resources)

-----------------------------------------------------

85 85 85 - no apps loaded

36 77 36 - Spybot only (main menu)

15 72 15 - Spybot (update menu)

 

Perhaps it's a resource issue ???

 

- Franc Zabkar

--

Please remove one 'i' from my address when replying by email.

[Guest bobster]

Re: Spybot Problem - A Workaround

 

Franc

 

SpyBot truly is a resource hog! My System, User and GDI resource numbers

agree with yours almost exactly.

 

In addition, it uses about 96% of my anemic 300 MHz CPU capability when it

is running a scan.

 

I make sure that I scan when I don't plan on using my computer for any other

function -- usually late at night. It takes over an hour to do a full scan

with my slow machine.

 

All that being said, I believe it is well worth the effort as it seems to

catch things that SpywareBlaster and Ad-Aware sometimes miss.

 

=========================================================================

"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message

news:f786s3l75mhie9s0uobjvhjmqba621a3pf@4ax.com...

On Sun, 24 Feb 2008 18:15:06 +0000, Nigel Stapley

<unet@judgemental.plus.com> put finger to keyboard and composed:

>Some of you may be finding that the latest versions of Spybot S&D (1.5.1

>and above) won't run on 98, giving the following error:

>

>"Exception EAccessViolation in module SPYBOTSD.EXE at 002E 6098. Access

>violation at address 006E 609B in module 'SPYBOTSD.EXE'. Read of address

>FFFFFFFF."

>

>Someone on the Spybot forums has come up with a workaround, namely that

>you start Dr Watson first, *then* run Spybot.

>

>It seems to work. Safer-Networking claim that the problem is caused by

>Windows memory management, but I'm not convinced.

>

>Hope this helps.

 

I've never seen that problem with version 1.4 and I don't see it after

upgrading directly from 1.4 to 1.5.2.

 

What I *do* notice is that Spybot is a voracious resource hog.

 

This is how Resource Meter reports my resource usage:

 

System User GDI (% resources)

-----------------------------------------------------

85 85 85 - no apps loaded

36 77 36 - Spybot only (main menu)

15 72 15 - Spybot (update menu)

 

Perhaps it's a resource issue ???

 

- Franc Zabkar

--

Please remove one 'i' from my address when replying by email.

[Guest lb]

Re: Spybot Problem - A Workaround

 

 

 

bobster wrote:

> Franc

>

> SpyBot truly is a resource hog! My System, User and GDI resource numbers

> agree with yours almost exactly.

>

> In addition, it uses about 96% of my anemic 300 MHz CPU capability when it

> is running a scan.

>

> I make sure that I scan when I don't plan on using my computer for any other

> function -- usually late at night. It takes over an hour to do a full scan

> with my slow machine.

>

> All that being said, I believe it is well worth the effort as it seems to

> catch things that SpywareBlaster and Ad-Aware sometimes miss.

>

 

SpywareBlaster is not a scanning engine, but it is a program that

installs killbits for the various places that spyware likes to install

itself. After updating SpywareBlaster, you need to enable protection

for all items. This takes up registry spae. SpyBot also has an

innoculating feature but I have read that one should avoid using this

and use only the SpywareBlaster innoculating feature. When I undid

all of the SpyBot immunizations, my registry shrunk over a megabyte.

> =========================================================================

> "Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message

> news:f786s3l75mhie9s0uobjvhjmqba621a3pf@4ax.com...

> On Sun, 24 Feb 2008 18:15:06 +0000, Nigel Stapley

> <unet@judgemental.plus.com> put finger to keyboard and composed:

>

> >Some of you may be finding that the latest versions of Spybot S&D (1.5.1

> >and above) won't run on 98, giving the following error:

> >

> >"Exception EAccessViolation in module SPYBOTSD.EXE at 002E 6098. Access

> >violation at address 006E 609B in module 'SPYBOTSD.EXE'. Read of address

> >FFFFFFFF."

> >

> >Someone on the Spybot forums has come up with a workaround, namely that

> >you start Dr Watson first, *then* run Spybot.

> >

> >It seems to work. Safer-Networking claim that the problem is caused by

> >Windows memory management, but I'm not convinced.

> >

> >Hope this helps.

>

> I've never seen that problem with version 1.4 and I don't see it after

> upgrading directly from 1.4 to 1.5.2.

>

> What I *do* notice is that Spybot is a voracious resource hog.

>

> This is how Resource Meter reports my resource usage:

>

> System User GDI (% resources)

> -----------------------------------------------------

> 85 85 85 - no apps loaded

> 36 77 36 - Spybot only (main menu)

> 15 72 15 - Spybot (update menu)

>

> Perhaps it's a resource issue ???

>

> - Franc Zabkar

> --

> Please remove one 'i' from my address when replying by email.