Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!math.fu-berlin.de!unido!rwthinf!slcdec!hippo!f1.n6000.z2.fidonet.org!f50.n347.z1.fidonet.org!Kent_Stewart
From: Kent_Stewart@f50.n347.z1.fidonet.org (Kent Stewart)
Newsgroups: comp.windows.ms.programmer
Subject: Best setup with SDK and MSC 6.0a
Message-ID: <1602679066@f50.n347.z1.fidonet.org>
Date: 31 May 91 06:02:00 GMT
References: <7149@p1.f6.n242.z2.fidonet.org>
Reply-To: Kent_Stewart%f50.n347.z1@hippo.dfv.rwth-aachen.de (Kent Stewart)
Organization: The Traveler's Mail BBS Richland, WA.
Lines: 24
Comment-To: Malzor@f1.n6000.z2.fidonet.org (Malzor)


 > From: MXP122@psuvm.psu.edu (Malzor)
 >
 > I am new to windows programming, I have MSC 6.0a and
 > the SDK 3.0, and I was
 > having trouble with the MAKE files and stuff for a
 > while but I have it
 > straightened out now (more or less, I have to select
 > the MAKE file (non-
 > standard) everytime I load PWB).  I was really

The context information is saved if you save the environment. However, I found 
using PWB to be so slow that I switched to bc++. There are rules on using bcx 
in a standard window but far superior to using pwb.  I found that you can have 
either pwb or bc++ in a dos window and toggle between them using the alt+tab.

If I hadn't started carrying both c's along time ago, I would have stuck it out 
using 6.0.  In order for the mouse to work you have to use either full screen. 
Doing anthing else cripples the editing features.  Using pwb, running enh386 
and toggling worked well for me.  From appearances neither work as well as tpw 
and I don't expect visual basic have problems either.

Kent