David H. Lipman said:
Remeber this...
If you do slave a hard disk then when the scanner scans the
Registry and other OS files it will make corrections to the
surrogate and NOT the OS and Registry of the slaved hard disk.
It will only remove the file(s) on the slaved hard disk.
True.
But once any nasty files have been put out of action (or removed) from
the slaved drive, you can then put the drive back in the original
computer and run some basic registry integrity tools (norton) or AV
software that should find and delete any offending registry entries
(which have been rendered useless because of the prior removal of the
viral executables).
When slaving a second hard drive to a trusted (master) computer, note
the following:
1) the trusted (master) computer should be running the same
operating system as is on the slave drive. If they are not
the same, then the operating system on the master must be
more recent (chronologically) than what exists on the slave.
2) if slaving an NT4 drive to a Win-2K system, or if slaving a
win-2K drive to a Win-XP system, note that the particular
version of NTFS on the slave drive will be changed to match
the version of NTFS on the master. This change is
irreversable. This may (or will) result in the non-
functionality of system tools (such as chkdsk) on the slave
once it is returned to it's native computer. If the slave
drive has not been formatted as an NTFS drive (ie if it is
a FAT or FAT-32 drive) or if the slave drive is a Windows-9x
(or ME?) operating system then this issue is not applicable.
3) the best way to connect the slave drive to the master
system is to connect the slave to the secondary IDE
connector or channel, and configure it as the master
(and only) drive connected to that channel. That will
usually mean un-plugging the optical (CD/DVD) drive on
the master computer and connecting the slave drive to
that same connector. When performing such a temporary
connection, do not rest the slave drive directly on the
metal chasis or frame of the open case of the master
system (you could short it out). Place something like a
magazine or at least a few pieces of paper between the
slave drive and what-ever it is resting on.
4) if the master computer is running XP, note that you may
invalidate your installation of XP by simply starting
the master without it's native CD or DVD drive being
connected to it. This situation may exist if you have
changed several hardware components of the master system
since XP was installed on it originally (such as the
amount of installed memory, the CPU model, the graphics
card, or the network adapter). This is known as "Windows
Product Activation" (wpa). Obtain and run a program called
"XPINFO.EXE" to check if the XP installation on the master
system will invalidate itself if it is started without
it's CD/DVD drive connected to the system.
