From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_02BF_01C47EFB.1A9A2FE0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Did you look for a spyware keyboard logger?

Rich

  "Frank Haber"  wrote in message =
news:41192ca4{at}w3.nls.net...
  Here's a loverly one.

  Knowledgable friend lost both kb and mouse on one of his old machines. =
 He
  couldn't get to base one, so I said, "Sure, bring it over."  Now I =
have egg on
  my face, too.

  It's a junker Cel466 Dell desktop, Intel 810 integrated video, 256MB, =
XP
  Home - a relative's machine.  The kb and mouse PS/2 checked out fine =
at the
  DOS level with two diags.  But he was right - under XP, no kb, and the =
mouse
  dies when you hit the first key.  The kb shows the yellow bang =
("cannot load
  driver, code 39)

  o delete both drivers, detect, reinstall - no joy.
  o safe mode delete no joy.
  o attach Chicony USB kb, detected properly, no joy!  Same errmsg!
  o Do same with several combos of various mice, kbs, and safe mode.  =
Joyless.
  o Restore to last week, before he installed a new Kingston USB mouse, =
no joy.
  There's no evidence of anything Kingston on the machine.
  o Popped in the retail XP Home disk, do overlay install. Kb fails at =
the
  serial number entry point, 34 minutes to go, the infamous PCI/hwcompat =
"point
  of horror."  It's an upgrade install over 98, what do I expect.
  o Slap in test HD, everything comes up roses.

  Now the better part of valor is obviously to reformat, or throw the =
machine
  out, which will happen.  I'm curious, though. Anybody hit anything =
like this
  with the critical system drivers before?

  --=20

  -Frank

------=_NextPart_000_02BF_01C47EFB.1A9A2FE0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Did you
look for a spyware =
keyboard=20
logger?
 
Rich
 

  "Frank Haber" <frhaber{at}N0SPMrcn.com>">mailto:frhaber{at}N0SPMrcn.com">frhaber{at}N0SPMrcn.com>
=
wrote in=20
  message news:41192ca4{at}w3.nls.net...He=
re's a=20
  loverly one.Knowledgable friend lost both kb and mouse on one =
of his=20
  old machines.  Hecouldn't get to base one, so I said,
"Sure, =
bring it=20
  over."  Now I have egg onmy face,
too.It's a junker =
Cel466=20
  Dell desktop, Intel 810 integrated video, 256MB, XPHome - a =
relative's=20
  machine.  The kb and mouse PS/2 checked out fine at theDOS =
level with=20
  two diags.  But he was right - under XP, no kb, and the =
mousedies=20
  when you hit the first key.  The kb shows the yellow bang =
("cannot=20
  loaddriver, code 39)o delete both drivers, detect, =
reinstall - no=20
  joy.o safe mode delete no joy.o attach Chicony USB kb, =
detected=20
  properly, no joy!  Same errmsg!o Do same with several combos =
of=20
  various mice, kbs, and safe mode.  Joyless.o Restore to last =
week,=20
  before he installed a new Kingston USB mouse, no joy.There's no =
evidence=20
  of anything Kingston on the machine.o Popped in the retail XP Home =
disk,=20
  do overlay install. Kb fails at theserial number entry point, 34 =
minutes=20
  to go, the infamous PCI/hwcompat "pointof
horror."  It's an =
upgrade=20
  install over 98, what do I expect.o Slap in test HD, everything =
comes up=20
  roses.Now the better part of valor is obviously to reformat, =
or throw=20
  the machineout, which will happen.  I'm curious, though. =
Anybody hit=20
  anything like thiswith the critical system drivers =
before?--=20
  -Frank

------=_NextPart_000_02BF_01C47EFB.1A9A2FE0--

--- BBBS/NT v4.01 Flag-5