Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!crdgw1!uunet!panews!rchland.ibm.com!seurer+ From: seurer+@rchland.ibm.com (Bill Seurer) Newsgroups: comp.org.eff.talk Subject: Re: Prodigy charged with invading users' privacy Message-ID: Date: 30 Apr 91 21:20:43 GMT References: <1991Apr20.022809.10259@svc.portal.com> <1991Apr30.143000.17493@cbnewse.att.com> <1991Apr30.184714.4675@mnemosyne.cs.du.edu>, <1991Apr30.185752.4913@mnemosyne.cs.du.edu> Organization: IBM Rochester, Mn Lines: 18 In-Reply-To: <1991Apr30.185752.4913@mnemosyne.cs.du.edu> I plan on running a little test tonight to see if this is true. 1) De-install Prodigy. (Erase all the Prodigy-installed files) 2) Run CLEANDSK (or equivalent) to overwrite all unused disk space with 0's. 3) Run CLEANEND (or equivalent) to overwrite the unused ends of files with 0's. 4) Modify CONFIG.SYS and/or AUTOEXEC.BAT to have 0 DOS buffers and remove any disk caching TSRs. 5) Defragment the harddisk. 6) Power PC off and then on to remove any DOS buffers and other resident stuff. 7) Re-install Prodigy. (Use a large STAGE.DAT) 8) Power PC off and then on to remove any DOS buffers and other resident stuff. 9) Immediately sign on Prodigy, poke around a bit, then sign off. 10) Dump STAGE.DAT and see what's inside. Does that sound reasonable? Can anyone think of other steps to take? - Bill Seurer IBM: seurer+@rchland Prodigy: CNSX71A Rochester, MN Internet: seurer+@rchland.vnet.ibm.com