Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!spool.mu.edu!snorkelwacker.mit.edu!primerd!primerd!eriador!mguyott From: mguyott@eriador.prime.com Newsgroups: comp.windows.ms.programmer Subject: Questions about CVW ... Message-ID: <149000012@eriador> Date: 7 Mar 91 00:06:20 GMT Lines: 37 Nf-ID: #N:eriador:149000012:000:1779 Nf-From: eriador.prime.com!mguyott Mar 6 16:44:00 1991 I have begun using CVW for the first time and all in all it seems to be a really nice debugging environment. But I am experiencing some problems and have a few comments. If anyone knows how to fix the problems I am experiencing I would appreciate hearing from them. 1. The /L flag does not appear to be working. I invoke cvw from the run command off of the progman's file menu. If I specify the /L flag with any values (user, user.exe, c:\windows\system\user.exe) the program manager returns and never starts up codeview. If I just enter "cvw c:\path\myapp" things start up fine. Or almost fine ... 2. When I first enter cvw I am greeted by the following message: CV0013 Warning: Access denied What file is cvw attempting to access that is causing this message? 3. The helpfiles: entry in the tools.ini file appears to be ignored. I had my HELPFILES path variable set to c:\msc\help\*.hlp and I wanted to get the cvw.hlp file from c:\sdk\cvw.hlp so I add the line: helpfiles:c:\sdk\cvw.hlp to my tools.ini file but it did not do any good. In order to get the cvw help I had to change the HELPFILES variable in my autoexec.bat file to c:\sdk\*.hlp and reboot. So I guess that's about it for the moment. Other then these minor problems cvw seems to be working really well and I think it's a great tool. Marc ---- Two of the worst things we teach our children are that a knowledge of science is nice but not necessary, and a knowledge of sex is necessary but not nice. Marc Guyott Constellation Software, Inc. (508) 620-2800 Framingham, Mass. 01701 USA Ext. 3135 mguyott@primerd.prime.com ...!{uunet, decwrl}!primerd.prime.com!mguyott