Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!uxc.cso.uiuc.edu!uxc.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!mms00786
From: mms00786@uxa.cso.uiuc.edu
Newsgroups: comp.windows.ms
Subject: Codeview for Windows problem.
Message-ID: <246400026@uxa.cso.uiuc.edu>
Date: 18 Sep 89 02:13:00 GMT
Lines: 24
Nf-ID: #N:uxa.cso.uiuc.edu:246400026:000:949
Nf-From: uxa.cso.uiuc.edu!mms00786    Sep 17 21:13:00 1989


Hello.          

I got such a good response from my last posting, I thought I'd venture another
question. I am trying to get codeview for windows to work on my 386. First of
all, do I still need another monitor for that, or can it work within a 
"virtual" dos machine set up by win386? The documentation seems to indicate
the latter. Well, I installed the debugging version of Windows/386, and started
up cvw as specified in the documentation. All I got was a blinking cursor.
However, codeview seems to be up and running, because I can still type in 
commands and it does as told. For example, I can type "G" and hit enter, and it
brings up windows as it should.

So the only problem is that codeview can't seem to write to my primary display.

I am using version 2.1 of win386 and the SDK. I have a Mylex motherboard, AMI
bios, 4Megs of RAM. I also have a Paradise VGA+/16 card and a NEC 3D.

Any response will be appreciated,

Thanks,

Milan
.