Turner Morgan

I have O&O Defrag which has a defragger as a screensaver. I can run the
defragger on my computer (Athlon 64 X2, Asus Crosshair main board, 4Gb RAM,
WD Raptor X for OS and programs, WD Caviar for data, Windows Vista Ultimate
64-bit) in the usual way as with any other program. The screensaver is in
C:\Windows\System32 as ooscrsav.scr and it shows up in Windows Explorer and
in the selection for screensavers in the desktop Properties dailog.

However, when I set the O&O Defrag screensaver to run when the computer is
idle, an error message shows up on the display ("Initializing connection. .
.. An attempt was made to access a socket in a way forbidden by its access
permissions. (0)"). Moving the mouse to cancel the screen saver shows the
OneCare firewall blocker dialog, I reply to allow the connection, the UAC
pops up (I'm gettin' to hate that thing!), again I say this is OK, then the
OneCare firewall blocker pops up for the second time to which I reply allow
the connection again.

If you allow something through the firewall, shouldn't OneCare remember that
and not ask *every* time the program tries to run? It remembers other
programs.

Even more mysterious, I have tried to change the firewall settings to force
the firewall to allow ooscrsav.scr. When you click on "Add" you are
presented with a dialog box for you to select the program via a Windows
Explorer-like interface. Well, I drill down to C:\Windows\System32 and
*there is NO ooscrsav.scr file to be found*!!! Yet it shows up in
Explorer!!!! What the hey is going on here? Does this mean OneCare
recognizes only Microsoft products?

There is a firewall listing for OO Defrag Container (x64). Don't know what
that does although I do have the 64-bit version of the defragger.

I have notified the vendor of the above, but have not heard from them yet
(of course, I usually do these stupid things on Friday evening or on the
weekend when no one is at work so I have to wait until the next working day
before I get a response!).

Maybe this is just something to add to the list of OneCare bugs. . .

Regards,

Turner