Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!uokmax!d.cs.okstate.edu!ong
From: ong@d.cs.okstate.edu (ONG ENG TENG)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Prodigy Rip-Off?!?
Message-ID: <1991May1.184727.22850@d.cs.okstate.edu>
Date: 1 May 91 18:47:27 GMT
References: <1991May1.161749.25807@agate.berkeley.edu>
Organization: Oklahoma State University
Lines: 21

From article <1991May1.161749.25807@agate.berkeley.edu>, by raymond@math.berkeley.edu (Raymond Chen):
> Interested readers should follow the discussion in comp.risks.
> 
> One theory is that the information enters the Prodigy files purely
> by accident when the Prodigy software requests disk buffers from DOS
> and doesn't bother to zero them out.  So whatever leftover junk was
> in the disk buffer makes its way into your Prodigy file.
> 
> `Don't attribute to maliciousness what can easily be explained by stupidity.'

First I like to say that I ran a small test and find the
above to be true.  But... 

What if Prodigy knows of this "problem" with DOS and delibrately use
it to upload the "junk" to their main computer for evaluation for
whatever purpose, knowing full well that they could blame it on DOS
if things should go to court.

Can someone with Prodigy and some software savy debug the Prodigy 
software to see if the STAGE.DAT file is somehow uploaded to their
main computer?