JDBP>DS>
    >  > JdeBP> There's a note in your Information folder about CodeView, in 
th
    >  >      > Application Considerations book.  Have you tried what it 
sugges
    >  >      > What happened ?
    >  >
    >  > I reviewed the "Using the Operating System, 2.1" book, and assuming 
th
    >  > the info there is the same as on-line info (I don't have that book)
    >  > there wasn't anything for me to try, since I am using DOS MASM/CV.
    >DS>
JDBP>  Did you not try deleting PWBHLP.PXT, as it suggests ?
                                ^^^^^^^^^^
I had scanned both drives for this file, and it wasn't there.  Maybe,
because I was never crazy about the PWB in the first place, I may not
have loaded it, or may have subsequently, in the past, deleted it.
Since that last time (a couple(?) of years ago) that I ran CV
successfully, I have recently upgraded to an Intel 486DX4-66, from an
Intel 486DX33, and added 16 meg-o-ram, for a total of 20meg, on a clone
ISA system.
I had been running the F16 Falcon simulator in both native-DOS and a VDM
until the upgrade.  The simulator stops after the opening screen and
some music: the whole system is hung, as it is w/ CV.  I believe I
tested the simulator w/ the '66, and it worked fine, so it may be after
the memory increase that the program stopped.  I double checked the
motherboard book as to the BIOS settings for the new '66 and memory
increase, and they are correct.  I finally deleted the simulator since I
rarely played it, and it released many megs of disk space.
Obviously I am casting about for the common thread as to what is
happening w/ CV.  WIN-OS2 works fine, and BC++3.1 (except the existing
link problem) and the games, etc w/in Windoze are all okay.  My VDM
programs such as DOS shells, Telemate, OLX, etc, are also okay.  BC++1.0
hasn't shown any problems, either.
A couple of days ago I was tweaking the autoexec.bat file and something
that I did caused OLX to fail to unpack the .qwk files (no info was
given).  I went to a totally vanilla "general.bat" file in the
DOS-settings and OLX was happy again.  So now I am concentrating on that
area: perhaps there is something in the overall VDM environment that CV
doesn't like.  Every test is a power off/on cycle, however.
[scratch scratch scratch].
___
 X OLX 1.53 X DOS: Venerable     WIN: Vulnerable    OS2: Viable
--- Maximus/2 3.01
---------------