🚀 go-pugleaf

In article <19626@mirror.TMC.COM> billc@prism.TMC.COM (Bill Callahan) writes:
>
>Well, it's time to get the ball rolling for this newsgroup, so I will start
>it with a question.
>
>What experiences have people had with installing and using CodeView under
>Windows?  I have heard much hype, but no word from someone who has done it.
>How did it go, and, what sort of machine and periperals did you use?
>
>---------------------------------------------

Everyone here who is woring on Windows apps has the following setup:

NCR 916 (16 mhz 80386)
4 meg. memory
EGA adapter and monitor (NCR's & NEC Multisync, some of each)
Mono adapter and monitor
Microsoft mouse
>= 70mb disk

Some general observations about CodeView with the 2.1 SDK:

1) For small apps is great!  I use it exclusively (since I got it)
   for little windows apps.

2) For our product(s) which consist of a set of relatively large
   windows apps (one of which managers the communications port, or
   a NetBIOS session) we have found CodeView too buggy to use.  
   Real bummer.  

3) We've also found that since we still need symdeb most of the time,
   we include both CodeView and sysmdeb information in the executables.
   Unfortunately, we can't include the source directory because mapsym
   can't handle it.  This means that when we use codeview, we have
   to enter the entire path for the source which gets to be a real
   pain.


I have a question:  does anyone out there have their development
machines LANed togther?  We're trying with Token Ring and Novell's
software, but there are still too many times when we have to reboot
to free up the valuable memory.

Rich Hume       rich@sandiego.NCR.COM