chryses@xurilka.UUCP (Phong Co) (05/29/91)
I just downloaded cvw305.zip from cica, and got it up and running... sort of. I can get to the Codeview display and muck around there OK. The problem is when I switch back to Windows, with either the F4 or F5 key. The screen becomes pattern of vertical stripes, and the mouse shows up only as movement of these stripes. The only way to quit is to click where my winexit icon should be. I've tried using the vcv.386 driver in my system.ini, but the results are the same. Any one tried it with similar/different results, who may know what's going on? I'm using a 25MHz 80386 with 4MB of extended memory, and a Hercules Graphics Station in standard VGA mode. Thanks for any info. Phong. -- ========================================================================= Phong T. Co | chryses@xurilka.UUCP | Nice girls don't explode. dada Indugu Inc. | -- Dave Sim (Cerebus #110) Montreal, CANADA |
bert@helix.nih.gov (Bert Tyler) (05/30/91)
> I just downloaded cvw305.zip from cica, and got it up and running... > sort of. I can get to the Codeview display and muck around there OK. > The problem is when I switch back to Windows, with either the F4 or > F5 key. The screen becomes pattern of vertical stripes, and the > mouse shows up only as movement of these stripes. The only way to > quit is to click where my winexit icon should be. Phong, I grabbed that same file, and am happy (no, I'm ecstatic!) to report that I don't have any of those problems on my XGA-equipped PS/2 model 80. Windows is definitely using the XGA driver - the first thing I tried was to run a debugging session on WINFRACT while it was color-cycling. All I did was to copy 'vcv.386' to my '\windows\system' directory, add a 'driver=vcv.386' line to the '[386enh]' section of SYSTEM.INI (the 'device=windebug.386' line was already there), copy CVW.EXE and CV.HLP to my '\windev\ directory (after squirreling away the older versions of those files in a safe place), and edit the 'codeview' startup parameters to remove all the old '/' options leftover from the days when I was using an 8514/A adapter and two monitors. Assuming that you've done similar steps, my guess is that there's a problem with the interaction between CVW and your Hercules Graphics station driver somehow. Maybe you could (temporarily) use the SETUP program to switch to the stock VGA video driver and see if CVW still has problems there... Bert Tyler bert@helix.nih.gov tub@cu.nih.gov
press@venice.SEDD.TRW.COM (Barry Press) (05/31/91)
In article <1543@nih-csl.nih.gov> bert@helix.nih.gov (Bert Tyler) writes: >Phong, I grabbed that same file, and am happy (no, I'm ecstatic!) to > ... >color-cycling. All I did was to copy 'vcv.386' to my '\windows\system' >directory, add a 'driver=vcv.386' line to the '[386enh]' section of >SYSTEM.INI (the 'device=windebug.386' line was already there), copy >CVW.EXE and CV.HLP to my '\windev\ directory (after squirreling I had much the same result, but noticed the following. I have an Orchid Prodesigner II (1MB) running 1024x768x256, and cvw refused to recognize it as a VGA. I suppose if I went back to stock VGA operation it would, but that costs a lot of pixels. After installing the vcv driver, cvw runs single screen, but F4 doesn't work, the cv display is only 25 lines, and even though F4 doesn't work, each time I do a STEP, the screen goes black for about 5-8 seconds (as if it's switching) although the Windows screen is never visible. The single-screen debugging is something I've wanted for a long time, more so since I got the VGA card (which slows down 2x due to the mono screen forcing it to 8 bits). Does anyone have info that would let the new cvw recognize a super-vga as being a vga and enable the rest of the nifty features? -- Barry Press Internet: press@venice.sedd.trw.com