🚀 go-pugleaf

In article <1992Apr1.210913.17019@access.digex.com>, terryfry@access.digex.com (Terry Fry) writes:
> In article <1992Mar31.211155.3189@ux1.cso.uiuc.edu> ffujita@s.psych.uiuc.edu (Frank Fujita) writes:
>>timb@ecst.csuchico.edu (Timothy Berger) writes:
>>>>Until an employee can be *fully* up and adminstering it in a
>>>>couple hours it won't sell here.
>>>Training doesn't have to be all at once.
>>
>>How about this for a first session.
>>     1) This is how you open a DOS box.
>>     2) Now do what you always did.
>>     3) If you want to learn more, fine, if not, that's fine too.
>>
>>Why does an employee need to be '*fully*' up in a couple of hours?
>>Frank Fujita
>>
>>
> 
>       4) Determine why DOS won't run, why the Windows session crashed, or
> what the hell a HIMEM.sys is
> 
> More accurate?

	Cept for the windows session crashing, theses sound more like problems
that you would have with windows not os/2.  I haven't seen a single ref. to
himem.sys under os/2.  Dos emulation is much more likely to fail under Windows
than OS/2.  As to windows session crashing...who knows(maybe UAE), but in most
cases, unlike a UAE in wondows, you'll only lose what was in that session
instead of the entire OS.

btw, from what little I've heard on win3.1 it sounds like what it does in the
case of a uae is it just re-checks it's internal data to see if it's been
corrupted if it detects a memory access violation...really high-tech there. 
Oh, feel free to correct me if I'm wring:)

						John Stewart