From: valley@gsbsun.uchicago.edu (Doug Dougherty)
Subject: Some DV/X questions  (Or, my adventures with QOS offhours support)
Summary: Really, I won't...
Organization: University of Chicago Computing Organizations
Date: Thu, 16 Apr 1992 13:19:43 GMT

Here are my questions about DV/X:

	1) How to do 10x7 on my monitor/card (Trident 8900C) ?
	2) How to do MS Windows full-screen inside a (not full-screen)
	   X window?
	3) How to make Windows come up automatically not full-screen?
	   (I.e., when I launch Windows, it takes up my entire X/Windows
	   screen, and the first thing I do is resize it down so that I
	   have room onscreen for other DV/X apps.  I would like this to
	   happen automatically.)  Actually, I suppose I could do it
	   with a script, now there's an idea... (I just thought of that
	   as I write this)
	4) Having just installed Windows 3.1, when I run an application
	   that I wrote in Actor (a Windows development
	   language/environment), I get a "Not Present Fault" and it
	   aborts the entire Windows window.  This does not happen with
	   any other combination besides Win 3.1, Actor, and DV/X.
	   Whose [of the 3 mentioned] fault [so to speak] is this?
	5) I have Windows (i.e., WINX.DVP) set to Allow Close = No.
	   Yet, Close still shows up on the menu (with a C) and you can
	   exit DV/X while WX is still active.  Note: The first, having
	   C available on the menu is a sometimes yes/sometimes no
	   thing, but the second (being able to exit DV/X) is 100%.
	   Note: When I exit DV/X w/o having closed WX, the machine
	   always crashes shortly thereafter.
	6) How much memory does the DV/X system take?  I.e., I start DV/X,
	   and open MS (Memory Status), it says 4.5M free (expanded mem).
	   This is on a 8 Meg system, with a 1M disk cache installed.
	   Is this reasonable?  (I.e., the system seems to take about
	   2 to 2.5 megs.
	7) Why do Windows & Memstat share MS.DXS?
	   That is, I did some Customize Menu in Windows and then
	   selected Save Scripts.  I accepted the default filename of
	   MS.DXS, and found that my changes then affected both WINX and
	   Memstat.  Further, inspection of WINX.DVP shows that its
	   default script name is (or should be) WINX.DXS.  Yet, it is
	   clearly using MS.DXS

My adventures with QOS off-hours (I should say, off-shore) support:

	1) I called QOS's Santa Monica number [(310) 392-9701] at 6:30
	   this morning (Chicago Time) and was duly forwarded to their
	   Ireland office.
	2) The guy I talked sounded like he has just gotten the job,
	   although to be fair, it did seem like they were all just being
	   briefed on DV/X, it being such a new product and all...
	   Really, I won't make any ethnic slurs here, although given my
	   own background, I would be entitled...
	3) We did establish that they don't support the Trident 8900 as
	   of this writing.  That takes care of #1 and #2 above,
	   although I had a Dickens of a time explaining what I meant in #2.
	   I hope it is reasonably clear.  He kept thinking I wanted
	   something to do with the scalable fonts and I kept explaining
	   that I didn't think scalable fonts were applicable to
	   Windows, it being a graphical app and all...
	4) #3 was equally confusing to him.  He thought I could do it
	   with Change a Program, but I am pretty sure that the settings
	   there only affect how the program runs as a DOS text app,
	   not how it behaves graphically.
	5) We never did get to 5, 6, or 7.

Anyway, any help/answers would be appreciated.  Postings preferred, but
email will be considered at least superficially.

I think I will print this out and FAX it to QOS, then call them and see
if the domestic support is any better than the imported.
****************************************************************************
The Slug		valley@gsbsun.uchicago.edu

"Can I shake your hand or would I be violating about 15 federal laws ?"

(THis [sic] message should be assumed to have been smiley captioned for the
humor impaired)
Newsgroups: comp.os.msdos.desqview