Casey Tompkins wrote in a message to Patrick McCullough:
CT> Patrick McCullough wrote in a message to Dennis Faas:
PM>  Could be a memory problem with Win95.  Try setting the pif
PM> to "protect  conventional memory."
CT> Ahem.  Not "a problem with Win95", unless he messed about rather a
CT> bit with the default settings under '95. ;)
 Or the OS changed them itself.
 Look, I detect your impending OS snobbery, so don't even _start_
 down that road.  I happen to LIKE Win95.  But it's not perfect.
 Win95 ran Max, Squish, Bink, and everything else just fine on my
 system for more than six months, right up until it suddenly decided
 to change that one setting, quite all by itself, and break Squish
 among other things. 
 Oh sure, perhaps *I* screwed it up somehow... I could believe that
 if it hadn't happened to other people in exactly the same way,
 all by itself.  Ask Robby Dittmann about the time it did the same
 thing to him.  There's something Win95 just doesn't like about
 Squish.exe in particular.
 So since this has happened to other people, either something we
 do by accident causes it, or the OS does it all by itself for no
 obvious reason.
 Since the OS does _other_ things on its own and assumes changes are
 needed all by itself, and I know I changed nothing, that is MY
 interpretation of what happened.
 YMMV.
CT> The only change I ever needed to make was to not allow the window to
CT> be closed: Properties/Misc/Termination: check the box "Warn if still
 That's all?  What about Idle Sensitivity?
CT> active".  Aside from that, my Bink/Max system runs very well under
CT> the default MS-DOS icon settings.  FWIW, the default for MS-DOS icon
CT> under '95 is DPMI "Auto"... 
 Wait.
 It was like that here too, until it suddenly wasn't one morning.  :)
 Now it's working fine again.  How long that lasts is up the whims
 of the OS.  I know my configs are sound.
 Patrick
--- timEd 1.10
---------------