Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to [GNG] Gated, Filtered alt.comp.a...  <--  <--- Return to Home Page
   Networked Database  [GNG] Gated, Filtered alt.comp.a...   [625 / 759] RSS
 From   To   Subject   Date/Time 
Message   mark_t    All   Re: Anti-virus software needed for old AMD processor   February 25, 2019
 1:19 AM *  

From: mark_t@phffft.com

On Mon, 25 Feb 2019 18:26:28 -0000, "Flyi±g ╤u± 2░19 + on netbook"
<flyingnun@tiscali.co.uk> wrote:

>Flyi±g ╤u± 2░╣9 + on desktop wrote:
>> CRNG wrote:
>>> Take a look at https://www.malwarebytes.com/premium/  I think they
>>> may still support Wxp.
>>>
>>>
>>> On Mon, 25 Feb 2019 11:38:16 -0000, "Flyi±g ╤u± 2░╣9 + on desktop"
>>> <flyingnun@tiscali.co.uk> wrote in <gdi2d5Fm9esU1@mid.individual.net>
>>>
>>>> Until earlier in the year I have successfully been running an old
>>>> computer with Windows XP Home Edition and a AMD processor (x86
>>>> Family 6 Model 8 Stepping 1 AuthenticAMD~1833 MHz),  whatever all
>>>> that means.  I have been running Avast Premium Internet Security for
>>>> several years.  To all intents and purposes it seems to be running
>>>> well but I noticed a couple of days ago that the firewall was
>>>> switched off and despite my efforts it just refused to be switched
>>>> on,  giving a curt error message "Firewall cannot be switched on.
>>>> During by unsuccessful efforts I also spotted that,  although the
>>>> latest virus definitions update was dated as 02/02/2019 it refused
>>>> to update but told me that I still had the current update.  I tried
>>>> to install the current Avast free as a back up until the problem was
>>>> sorted out and but as I tried to run it I immediately got the error
>>>> message:    "We are sorry but Avast Antivirus cannot run on your
>>>> computer because your processor does not support SSE2 instruction
>>>> set." So I presumed that this was probably the reason that my
>>>>    Premium installation had stopped working.  :( All I can think of
>>>> is to use Clamwin which does in fact run and updates it's virus
>>>> definitions daily,  but this doesn't offer as much protection as
>>>>    the Avast or AVG offer. Has anyone in this Newsgroup any ideas
>>>> as to how I can improve my security.  Please don't suggest chucking
>>>> the archaic computer in the skip! Thanks.  :
>;)
>>
>> Thank you CRNG I'll take a butcher's at it.
>>
>>
>Unfortunately I'm afraid one of their hardware requirements is:
>80MHz CPU or faster, with SSE2 technogy.   :(
>
>
Why don't you use a sandbox and forget about AVs?


--- NewsGate v1.0 gamma 2
 * Origin: News Gate @ Net396 -Huntsville, AL - USA (1:396/4)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to [GNG] Gated, Filtered alt.comp.a...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0856 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_told9r4fg98iu7a50qjj283bi4, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_told9r4fg98iu7a50qjj283bi4, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_told9r4fg98iu7a50qjj283bi4, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0