Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!jarthur!nntp-server.caltech.edu!rknop From: rknop@nntp-server.caltech.edu (Robert Andrew Knop) Newsgroups: comp.sys.cbm Subject: Re: GEOS Companion Disk Keywords: Problems... Message-ID: <1991Feb18.012622.25064@nntp-server.caltech.edu> Date: 18 Feb 91 01:26:22 GMT References: <1991Feb17.024528.17465@nntp-server.caltech.edu> <1991Feb17.202800.29061@evax.arl.utexas.edu> Organization: California Institute of Technology, Pasadena Lines: 15 cs4344af@evax.arl.utexas.edu (Fuzzy Fox) writes: >Perhaps the best course of action is to contact GeoRep Jim and find out >why his boot disk is succeptible to this Berkeley Trojan? You'd think >that he would have discovered this problem while building the program. I actually did this; I don't remember the response in detail, but I think that he tried to deal with this, but wasn't able to fully get rid of it. As it is, almost everything will work allright- you can copy files to/from the boot disk and so forth; however, there are some things you can do, like move a file from a page to the desktop, and to another page, which causes the Trojan Horse to kick in and delete your boot files. So if you avoid this, you are OK. -Rob Knop rknop@tybalt.caltech.edu