Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-spam!sri-unix!hplabs!decwrl!pyramid!amdahl!dlb!auspyr!sci!phil
From: phil@sci.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Desqview installation problem
Message-ID: <1312@sci.UUCP>
Date: Fri, 30-Jan-87 16:57:22 EST
Article-I.D.: sci.1312
Posted: Fri Jan 30 16:57:22 1987
Date-Received: Sun, 1-Feb-87 16:15:20 EST
References: <2110@batcomputer.tn.cornell.edu>
Organization: Silicon Compilers Inc., San Jose, Calif.
Lines: 21
Keywords: desqview
Summary: deskview comments

In article <2110@batcomputer.tn.cornell.edu>, prove@batcomputer.tn.cornell.edu (Roger Ove) writes:
> 
> 	A few months ago I bought an AST Premium pack eems card
> that came with a copy of desqview.  There was a serious problem with
> the installation of desqview that others contemplating a similar
> ...The result of this 2nd installation was a trashed hard disk.  About 20
> files were cross-linked.  


Most program install scripts have nasty problems if not done in a plain vanilla
environment. it is always best to try and avoid them.

re comment on use of CED, and similar programs, with Desqview: CED works fine
even if the dos window is sawpped or put in background IF you invoke CED in
EACH dos window rather than just once before starting up DV (once before
startup couses no problems inside DV and multiple invokations seems
to cause no problem). I put CED and other similar stuff that would otherwise
be in AUTOEXEC.BAT in a script that runs whenever a DOS window is invoked.

One think DV can't seem to do is pass the ENVIRONMENT variables that you have
set (other that PATH etc) to a DOS window. Anyone know how to work around this?