From: bodoh@xraylith.wisc.edu (Daniel J. Bodoh)
Subject: Received my DV/X
Summary: Wow! 
Organization: Center for X-ray Lithography, UW-Madison
Date: Sat, 11 Apr 92 01:15:21 GMT


Wow! Wow! Wow!  Windows, eat your heart out.  DV/X even has a better
title screen!

Some things to watch out for in the installation:
It went pretty easily for me, but took about 1/2 hour...  First thing
you have to do is fill in your name & serial number.  I think the
install program wrote that info to the originals, so you may want to make
copies of your originals and install from them.

It's a disk hog -- get at least 10 megs free before installing.  Supposedly
you can trim that down.

And it's a memory hog -- 4 megs is going to be like maybe 1.5 megs in
DV classic.  I had to disable my 1 meg disk cache to do anything useful.
The X server requires 222K, and the Window Manager takes another 142K.
I haven't figured out what the kernel takes, but I have a feeling that its
more than DV Classic.  It looks like you can configure the server to use
more/less memory and let it use disk space for virtual memory.  It'll
take a little tuning.  On the subject of tuning, all the good stuff
on ticks, etc. in the Tune Performance menu is gone.  It doesn't really
Tune Performance any more, it just gives you a Copyright screen and a
screen refresh option.

I just managed to crash DV/X by starting up the old version of Manifest...

Just noticed another bug -- the Switch Windows number must be re-assigned
by the server.  The number reported by the API call and the number
on the window border are 2 different numbers.

I don't know about other video cards, but it doesn't handle 1024x768 on
an ATI VGA Wonder Plus.  I'm going to try to find out if it supports
user-written drivers.  And on the subject of video, I configured it for
800x600, but it doesn't seem to be using my whole screen.  I'm not sure
if that's the monitor shrinking it, or if DV/X doesn't want to use the whole
thing.  Anyone else have any problems?  Also, virtualized windows on
my 386SX/20 are SLOW!  I'm writing this in a virtualized Kermit window
and scrolling is pretty painful.  But I LOVE this tiny font!

You may want to take DV.COM out of AUTOEXEC.BAT before starting.  If you
don't you'll be starting the old DV during Optimize for QEMM.  Also,
Optimize managed to lock my system up and give my printer fits.  But
it nicely restored the original CONFIG/AUTOEXEC before dying...

They are also stepping into DVSI territory -- including is a system
monitor, which gives some of the DVSI PS info.  There is also a real
PS & KILL provided.  The DV/X Ps doesn't do much; it just tells you
the current process state -- it should be easy to reverse-engineer
and add to the DVSI PS.  There's also a whole print spooler.  And
there is a RUN.COM which only lets you run .DVPs, but it also allows
you to run things remotely.  And there is some hacked-in TSR support
for the Unix "&".  I think the QOS guys are finally figuring out what
a real op sys can do...

Well, back to playing.
-- 
Daniel J. Bodoh - bodoh@xraylith.wisc.edu or via Fidonet Daniel Bodoh 1:121/99
    "I'll be back!  You can't keep the Democrats out of office forever!"
 - Sideshow Bob, as he was being led to jail for attempted murder of Aunt Selma
Newsgroups: comp.os.msdos.desqview