found something very interesting in Superantispyware

[Guest]

Robin and Dave,

Did either of you Allow (or Not Allow [or remove]) the " winlogon " setting
of SASW in the registry.

I have no idea what effect this might have. I do know that I block it every
time I update the SASW program as I see no use for it and the SASW people can
show me no value for it in the free version.

If Robin blocked it as well and Dave did not this could have an effect, No?
Mind you I'm just talking off the top of my head, but we are talking about
the behavior of SASW at boot time and this setting might affect the behavior
of the program. Just my 2 cents. I might be totally off base here.

?
Tim

 

[Dave M]

Nope Tim, not me anyway. I did find this additional reference in the SAS
Helpfile <g> while I was looking further though:

"After you select your desired Safe Mode option and scan your computer, you
MUST run BootSafe again and select the option to boot into Normal mode or
your computer will continue to boot into Safe Mode."
--

Regards, Dave

Robin and Dave,

Did either of you Allow (or Not Allow [or remove]) the " winlogon "
setting
of SASW in the registry.

I have no idea what effect this might have. I do know that I block it
every
time I update the SASW program as I see no use for it and the SASW people
can
show me no value for it in the free version.

If Robin blocked it as well and Dave did not this could have an effect,
No?
Mind you I'm just talking off the top of my head, but we are talking
about
the behavior of SASW at boot time and this setting might affect the
behavior
of the program. Just my 2 cents. I might be totally off base here.

?
Tim

:
OK, after a little experimentation on my XP system this is how it works
for
me after booting to SAFE using BootSafe then trying to go back to normal
boot:

Using msconfig and specifying normal puts me right back into SAFE
F8 specifying normal puts me back into SAFE
F8 specifying last known good config puts me back into SAFE

The only way to get back to normal boot that I can see is to run
BootSafe.exe again specifying normal from the SAFE mode initially
established by BootSafe. FWIW, net confirmation of this is here:
http://forum.zonelabs.org/zonelabs/board/message?board.id=Off-Topic&message.id=15987#M15987

So Robin, I have no idea of why your system would be that different and
allow or require you run msconfig to get back to normal boot mode, since
bootsafe apparently won't run for you in SAFE mode. Weird.

 

[Pat Willener]

That can be dangerous; you can end up in a terminal loop, and never get
out of Safe Mode again.

You should always use F8 to get the boot menu for Safe Mode.

 

[Alan]

Hi Alan D.

I think what many of us Yanks need is a "Help" file for understanding the
British sense of humor (okay, for you Alan D. and any other Brits or
Canadians reading this -- humour). :>

Alan

 

[Robinb]

yep it can- and i always use f8 for safe mode- i was just experimenting the
bootsafe exe in superantispware and those where the results i found.
robin