fredch@starlite.hf.intel.com (09/28/90)
Has anyone else had these problems? Know any resolutions?
1. Since PWB seems to remember every file it's ever seen (well, almost 8-)
the file menu quickly fills up and spills over into the secondary file
list. To try and control the name space, I have tried to reduce things
by closing a bunch of files (one at a time). Numerous times PWB has
hung on me, forcing a reboot and even an occasional reset.
2. PWB is aware of assembler files and will even figure out dependencies
as well as invoke masm. However, none of the menus permit me to set
flags for the assembler. My kludge has been to set the flags directly
in the projects .sts file, but this is clearly less than satisfactory.
3. The editor handles tabs very poorly. If I am adding new text, tabs behave
correctly, but if I am inserting a tab into an existing line, I do not
get a tab, just a space. Ditto if I use the mouse to select a textual
portion and then retype.
4. All too often, I get this message: Out of virtual memory space - unable
to recover. I exit the session and then reinvoke PWB. Same msg. I can
only restart by rebooting.
5. Browser intermediate files are created if there are just warnings.
However, nmake refuses to build the .bsc (required to browse within PWB)
unless there are no warnings whatsoever (let alone errors, which I could
understand). Workaround was to use the menu extender/customizer facility
to invoke nmake and specify the .bsc target.
6. PWB remembers all these files but does not remember the .mak it last used
so I have to specify it every time I re-invoke PWB. Strange!
----------
Fred Christiansen, Intel, JF1-67 503-696-4214 | fredch@starlite.hf.intel.com
5200 NE Elam Young Prkwy, Hillsboro, OR 97124 | uunet!intelhf!starlite!fredch
Children spell love this way: t-i-m-e. "Quality time" must be in quantity.bank@lea.ncsu.edu (Dave The DM) (09/29/90)
I have MS C 6.0 (in fact, I'll shortly be Posting a question about
MS C myself) but I don't use PWB. The problems you cite are one reason.
However, I have a pretty good idea as to how to workaround your
problem with setting flags on MASM when compiling inside PWB. What
Microsoft usually does is look for environment variables. As an
example, you can set the command-line parameters for CL (the
compiler) just by typing "CL=/AL /FPi" at your DOS prompt. In this case,
I've instructed the compiler to use the large memory model and to use
the floating-point library that supports both the 80x87 and emulation.
Now I don't have to specify those things when I compile (altho if I DO
specify command-line parameters when I compile, they override and
conflicting ones present in the environment variable).
What the name of the environment variable is for MASM I haven't
the faintest idea. Try checking the docs. But I do know that this
feature is pretty consistent thru the MS line of compilers -- I
have a FORTRAN compiler of theirs that does things the same way.
Dave the DMerikt@cs.umu.se (Erik T{rnvik) (10/01/90)
In article <834@intelhf.hf.intel.com> fredch@starlite.hf.intel.com () writes: >Has anyone else had these problems? Know any resolutions? > >3. The editor handles tabs very poorly. If I am adding new text, tabs behave > correctly, but if I am inserting a tab into an existing line, I do not > get a tab, just a space. Ditto if I use the mouse to select a textual > portion and then retype. I've fixed this by redefining the tab key. > >6. PWB remembers all these files but does not remember the .mak it last used > so I have to specify it every time I re-invoke PWB. Strange! This is really annoying. I've tried to fix it. No luck yet. -- Erik Tarnvik University of Umea erikt@cs.umu.se Dept. of Computing Science TEL:+46-90166583 S-90187 Umea, SWEDEN "audentes fortuna juvat"
browns@iccgcc.decnet.ab.com (Stan Brown, Oak Road Systems) (10/02/90)
In article <1990Sep29.060422.7362@ncsuvx.ncsu.edu>, bank@lea.ncsu.edu (Dave The DM) writes: > you can set the command-line parameters for CL (the > compiler) just by typing "CL=/AL /FPi" at your DOS prompt. ^^^^^^^^^^^ This should be "SET CL= ..." The above is my own opinion and, though very true, is not attributable to any other person or organization. email: browns@iccgcc.decnet.ab.com Stan Brown, Oak Road Systems, Cleveland, Ohio, U.S.A. (216) 371-0043
mkelson@microsoft.UUCP (Michael KELSON) (10/03/90)
|>From: erikt@cs.umu.se (Erik T{rnvik) |Newsgroups: comp.os.msdos.programmer |Subject: Re: MSC 6.0 / PWB quirks |Date: 1 Oct 90 13:25:44 GMT |Organization: Dep. of Info.Proc, Umea Univ., Sweden | |> |>6. PWB remembers all these files but does not remember the .mak it last used |> so I have to specify it every time I re-invoke PWB. Strange! | |This is really annoying. I've tried to fix it. No luck yet. | In your "tools.ini" file there is a DEFLANG switch you can set which will cause PWB to automatically search your directory for ".MAK" files. In the [PWB] section of your "TOOLS.INI", add the switch DEFLANG:C When you start PWB with a file argument, (ie "pwb foo.c"), if a make file exists PWB will ask if you would like your program list set to it ("FOO.MAK"). | |-- |Erik Tarnvik University of Umea |erikt@cs.umu.se Dept. of Computing Science |TEL:+46-90166583 S-90187 Umea, SWEDEN "audentes fortuna juvat" | Michael Kelson