UNSOLVED

pijai

updated

22 years ago

P

pijai

35 Posts

0

3225

October 29th, 2004 00:00

heads up ! (spy-bot)

heads  up !   (spy-bot)
this  posting  is  not  intended  to  warrant  resolution.
this  posting  is  intended  only  for  other's  reference  purposes . . .
 
on  10-25-2004 . . . spy-bot  offered  no  new  updates.
 
on  10-26-2004  spy-bot  offered  update / download :
     downloaded update Detection rules
          URL: http://www.spybotupdates.biz/updates/files/includes
     downloaded update English help for TeaTimer
          URL: http://www.spybotupdates.biz/updates/files/helpres.english
     downloaded update English language
          URL: http://www.spybotupdates.biz/updates/files/lang.english
 
on  10-27-2004  spy-bot  offered  update / download :
     downloaded update Advanced detection library
          URL: http://www.spybotupdates.biz/updates/files/advcheck
     downloaded update English language
          URL: http://www.spybotupdates.biz/updates/files/lang.english
 
spy_bot  sometimes  loads  "fixes"  via  the  update  feature . . . but  not  on  this  particular  event.
 
     Error during check!:
     New.Net (Datei C:\WINDOWS\wininit.ini kann nicht geöffnet werden.
     The process cannot access the file because it is being used by another process) ()
     Congratulations!: No immediate threats were found. ()
 
yes . . . i  realize  new.net  is  considered  to  be  a  threat.

on  10-26-2004 . . . i  downloaded  the  above  indicated  updates . . . 'n  did  a  scan . . . came  up  with  the  above-named  violation.  i  did  a  search  on  the  internet . . . using  the  above-named  New.Net (Datei  as  a  filter . . . nothin'  of  any  consequence  came  up.  searched  my  hard-drive . . . nothin'  came  up . . . even  the  administrative  "events_log"  didn't  reveal  anythin'  suspicious.
 
i  scanned  my  hard-drive  with  ad-aware  as  well  as  avg . . . finally  with  hijack-this.  started  thinkin'  the  issue  was,  inherently,  with  spy-bot . . . after  all,   dso_exploit  had  already  been  overcome (simple  registry  hack).  the  followin'  day,  sure  enough . . . spy-bot  came  up  with  a  second  update . . . two  updates  within  48  hours !  (it  should  be  noted . . . after  this  newest  update . . . the  questionable  issue  has  already  vanished.)
 
final  notation  before  i  close . . . if  you  will  notice  my  previous  postings,  in  regards  to  spy-bot . . . you  will  notice  spy-bot  is  becomin'  more  'n  more  suspicious . . . (specifically  with  her  highness  "new.net").
 
(edited)
( please  refer  to  my  previous  posting  on  08-22-2004  here )

Message Edited by pijai on 10-28-2004 08:04 PM

  • scoobydooby

    2 Intern

    •

    495 Posts

    315

    0

    Posted October 29th, 2004 01:00

    I tend to agree that Spybot appears to be more error prone than Ad-Aware.

    That's why I always scan first with Ad-Aware - if Spybot finds something not found by Ad-Aware - I will "google" it before I will fix it.

  • bionic747

    4 Posts

    315

    0

    Posted October 30th, 2004 02:00

    Get TuneUp 2004 (use google) and then find a keygen if you want (google).