🚀 go-pugleaf

In <1992Dec28.074914.7584@microsoft.com> jenk@microsoft.com (Jen Kilmer) writes:

>A not-very-common windows 3.0 setup problem is caused by the windows original
>disks being infected with a virus (microsoft is very careful about the
>"health" of the master diskettes and even duplicates disks on machines
>running xenix, so even if the duplicator gets infected it can't affect the
>MS-DOS-based or Macintosh-based software on the disks).  Each case we know
>about, the software had been installed previously on an infected system
>(and sometimes returned, re-shrinkwrapped, and re-sold). No such problem is
>known about windows 3.1. Windows 3.0 shipped on writable disks; windows 3.1
>(and the ms-dos 5 upgrade, and most new products being released) are shipped
>on "permanently" write-protected disks.  

>From a support standpoint, this is seriously cool (unless the user cut
>a notch in a set of 5.25"s, no viruses, no accidently-deleted-the-file-we
>-need, etc :)

There is also one other thing that this does that I like.  It
eliminates those annoying 'guilt screen' registrations that want to
write back to your original disks with your name, etc.  I routinely
write-protect the original disks for any software I buy, and it's
incredibly annoying to have to make a copy of disk #1 in order to
reinstall Word for Windows or Excel on my machine (because I most
definitely will not let the thing write to the originals).

-- 
"Insisting on perfect safety is for people who don't have the balls to live
 in the real world."   -- Mary Shafer, NASA Ames Dryden
------------------------------------------------------------------------------
Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.