Newsgroups: comp.os.msdos.desqview
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!stanford.edu!leland.Stanford.EDU!portia!stanton
From: stanton@lurch.stanford.edu (Scott Stanton)
Subject: Re: Desqview Not Running Programs
In-Reply-To: jf@spocom.guild.org's message of 7 Jun 91 15:08:28 GMT
Message-ID: <STANTON.91Jun11111502@lurch.stanford.edu>
Sender: news@leland.Stanford.EDU (Mr News)
Organization: Stanford University
References: <TwF732w164w@spocom.guild.org>
Distribution: comp.os.msdos.desqview
Date: 11 Jun 91 11:15:02
Lines: 24

In article <TwF732w164w@spocom.guild.org> jf@spocom.guild.org (Jason Bassford) writes:

           It seems to me that a lot of these problems must be do to the 
   fact that many of us (myself included) are using IBM clones.  Quite 
   possibly there could be a glitch in the hardware of these computers which 
   results in these many and inconsistent problems.  Because if it's not the 
   software, what else could it be.  Anybody out there, if you have a 
   program which simply REFUSES to work with DV and/or Qemm ask yourself 
   this question.  Are you using an IBM or are you using a clone?  I would
   be interested in knowing the answer to this.

                   Jason Bassford.

It is more likely to be BIOS problems rather than actual hardware
glitches.  You might compare notes with other people who have had
problems and see if you are all running unusual BIOS's.  In
particular, compare your BIOS to the machine that you got your setup
to work on.  You might be able to switch BIOS's and solve your problem
if this turns out to be the culprit.


--
--Scott Stanton     (stanton@cs.stanford.edu)   
--
