Newsgroups: comp.windows.ms
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cunixf.cc.columbia.edu!cunixb.cc.columbia.edu!mjf
From: mjf@cunixb.cc.columbia.edu (Michael J Flory)
Subject: Re: Strange memory errors in Windows?
Message-ID: <1991May30.025431.10744@cunixf.cc.columbia.edu>
Summary: Timing problems?
Sender: usenet@cunixf.cc.columbia.edu (The Network News)
Nntp-Posting-Host: cunixb.cc.columbia.edu
Reply-To: mjf@cunixb.cc.columbia.edu (Michael J Flory)
Organization: Columbia University
References: <1991May29.130902.17809@murdoch.acc.Virginia.EDU> <1991May29.175240.14589@cunixf.cc.columbia.edu> <1113@venice.SEDD.TRW.COM>
Date: Thu, 30 May 1991 02:54:31 GMT


Barry Press (press@venice.sedd.trw.com) suggested in reply to my reply
to Andrew Colfelt's suggestion re: DOS apps in Windows writing bad sectors
to floppies,

>>I think the problem occurred in full-screen DOS sessions as well as in a
>>window, so I don't *think* that what Andrew Colfelt suggested -- that I
>>might be losing time-slices in a windowed session -- is the answer. 

>I'm not convinced that the complete point of the fix he suggested got
>across.

>In particular, running full screen DOES NOT by itself ensure that your
>process does not get interrupted.  I can verify this by noting that a
>clock (a WinApp) I use that beeps on the hour still beeps when I have a
>full-screen DOS session going.

>The other point he mentioned was to turn on EXCLUSIVE, either in the pif
>or in the settings (Alt-space, settings, etc.).  While I haven't tested
>that, nor have I recently RTFM'd on it, I believe that it's purpose is
>to restrict the scheduler as he mentioned.

Thanks for the advice -- maybe I'm too wedded to my idea that this is
just a case of memory misallocation.  You're right, I never did run my
DOS apps in exclusive mode, and a lot of folk have suggested I should look
at timing/bitslicing problems.  I did a little more experimenting and 
now, of course, I can't replicate the problem!  (It was appearing quite
predictably -- the DISKCOPY problem, that is -- before...)  One of the
more DOSwise gurus on campus told me in no uncertain terms to get FASTOPEN
out of my Windows setup, too.

When I have some real time to put into this I will try to replicate the
problems I was having with DISKCOPY and make experimental changes to the
timesharing just to see what happens and I'll report.  There are just so
many variables in the system...  I did try MANY changes to my setup when
the problem first appeared, and only the adjustment of the .pif and
winmemsize values seemed to help, but I wasn't thinking in terms of the
timesharing...

Meanwhile, I'm on the waiting list for the OS/2 2.0 "Early Experience
Program."  :)

Michael Flory (mjf@cunixb.cc.columbia.edu)