Well Ed,   
      
      
    EV> What I see is like this:   
      
    EV> 0  SyQuest drive   
    EV> 1   
    EV> 7  Adapter Card   
      
    EV> I see this extra device number show up once a    
    EV> week at least, when the   
    EV> xp box is turned on.   
      
    EV> I can't recall what name is shown along side #1.   
      
    EV> When I turned the XP box On this afternoon I saw the #1 entry appear   
    EV> between the #0 SyQuest SCSI Drive and the #7 SCSI Adapter Card lines   
    EV> when the Adapter was initializing.   
      
    EV> I used Hibernate when I turned the XP box Off last night.   
      
    EV> I pressed the Pause Key, the #1 entry had the words  Drive Not Ready .   
      
    EV> The SCSI wire goes from the Adapter Card to the SyQuest Drive.   
      
    EV> There isn't any other SCSI device between the Adapter and the Drive,   
    EV> and the other connector on the Drive is unused.   
      
    EV> That is why I get concerned when I see the extra entry showing up for   
    EV> a phantom drive.   
      
    EV> I looked in Device Settings for the SCSI Card Properties.   
      
    EV> It's called Advansys SCSI Host Adapter made by Advanced System Products   
      
    EV> Location: PCI Slot 3 (PCI bus 3, device 9, function 0)   
      
    EV> Have You or Any Others in this echo seen Drive Not Ready when a SCSI   
    EV> Adapter is starting up, when there isn't any device using that SCSI   
    EV> Device Number?   
      
    EV> Thanks!   
      
   MANY years ago I saw something similar to this on one of my OS/2 boxes.  It   
   was long before WIN XP was ever there but might be sort of related to things   
   here about Windows whatever.  The OS/2 system had nothing to do with the   
   Windows stuff.  It was simply put together with the at the time 'standard'   
   OS/2 installation.  I can't at this point recall the driver name but it is for   
   "(something) over TCP/IP" that the Windows stuff uses for hard disk operations   
   that OS/2 absolutely does not.  This box would jam up on SCSI operations at   
   times sort of like is discribed here and finally when I got around to running   
   a virus check on the system I found it!   
      
   The master Windows mess uses an Administrator mode to automatically update the   
   disk for 'Windows fixes' by doing the whole thing over the Internet and the   
   'user' can have no information or even any awareness that this or that has   
   been done.  Well guess how malware and virus stuff can totally be whopped on a   
   box?  What I found out was that when the box was connected to a contaminated   
   site on the Internet, 'Windows' was putting one or a hundred contaminated   
   actual files in one or many of the hard drive areas that were to be used for   
   malware or virus contamination of this OS/2 box!   
      
   No, the actual contamination wouldn't work the way it was designed in that the   
   operation was 'focused' on hidden operations that were often designed to be   
   interfaced to one or many other IT infected 'boss' sites and so on to steal   
   information from or use a box for a 'middle-man' operation.  The actual   
   operation wouldn't even run under OS/2.  Nor, since OS/2 would NOT use an   
   Administrator or Guest mode without a password more or less from a 'normally'   
   set up system and to install a new device driver you had to 'normally' hand   
   and use your own password do this to enable a device driver addition or   
   change, this file or these files that had been punched into an OS/2 hard disk   
   were just 'there' one never knew about.  But a good virus checking program for   
   OS/2 would spot.  This stunt could use a HUGE amount of disk space too!   
      
   Over and over again I'd have to go in and probe through a ton of these nasty   
   files and even strange new directories and erase them.  Machine would work   
   normally again!  Looking through all of this in a special way that I created   
   decades ago, I discovered that this device driver that operated all of this   
   over the Internet with TCP/IP protocol had no use in OS/2 unless one was   
   cross-operating Windows programs under OS/2, especially with a tool like   
   VMWARE; whatever.  I have worked closely with OS/2 even on their older design   
   team since even the mid-1970's.  I found out that this 'stunt' was hitting a   
   lot more than my box or boxes!  Yes, there are firewalls and so on.  Which I   
   do use.  However 'we', for security reasons fullowed my suggestion to remove   
   the OS/2 device driver for "(something) over TCP/IP" that was contaminating   
   the OS/2 system if you never were doing anything with 'windows' on the box.   
      
   I've actually seen MANY years ago an attempt to man-in-the-middle the OS/2   
   system for people with SCSI hard drives this way.  Plus now we have NSA and   
   what all else from where and who even as computer bolts is a cloud?   
      
      
   Sigh.   
      
      
   Mike Luther as N117C at 1:117/100   
      
      
      
   ---   
    * Origin: BV HUB CLL(979)696-3600 (1:117/100)