Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!portal!cup.portal.com!Sullivan
From: Sullivan@cup.portal.com (sullivan - segall)
Newsgroups: comp.sys.amiga
Subject: Re: Hardware Copy Device (how NIB works
Message-ID: <23051@cup.portal.com>
Date: 13 Oct 89 19:39:30 GMT
References: <758@nigel.udel.EDU> <1370@ultb.UUCP> <532@uncmed.med.unc.edu>
  <533@uncmed.med.unc.edu> <364@xrtll.UUCP>
Distribution: na
Organization: The Portal System (TM)
Lines: 18

In case anyone else was wondering, I've been experimenting some with
NIB.  From what I can tell it uses a special boot loader which intercepts
track read requests to a particular drive and track, and  replaces them
with the data expected.  This is a nifty little hack, but the program
isn't intelligent enough to know when the disk has been changed.  As a 
result, the same track data will be given to the program even if the disk
has been removed and replaced.  I'm curious how many programs this would work
for.  I also wonder where the author has managed to stuff the extra bytes
to make this scheme work.  (Funny, and FTL claimed right here that DM was
proof agains viruses.) 

...let the good times roll.
-ss  
Sullivan@cup.portal.com
sun!cup.portal.com!sullivan

The .signature file is currently Out of Order.
We apologise for any inconvenience.