🚀 go-pugleaf

So, on the eve before my computer architecture mid-term, I decided to do the
obvious - play with my new BC++. This leads to:

a) Is there any way to get turbo debug to work with stuff generated by MSC?
   I have a windows program written in MSC 6.00a, and would like to keep using
   MSC. However, I would like to try out TDW. Yes, I read the manual best I
   could so I did the following:
     a) ran TDCONVRT on my .exe file which has codeview info (ie, I can debug
        using codeview for windows). I also ran tdmap using
        tdmap -w xxx.map xxx.exe. I could find no docs on tdmap in the manuals.
     b) I ran TDW, but it displays my stuff in assembly. I did set the
        Languages option to C and even set the source directory. But it insists
        on displaying my code in assembly.
   Is it possible, then, to do source level debugging using MSC 6.00a and
   TDW?
b) I used TDW in two monitor mode, with TDW running on the mono. I can type go
   on my MSC executable, it runs fine etc. When I quit my app, and then quit 
   TDW, my mouse cursor has mysteriously disappeared. To be honest, though, I
   am running Windows in 800x600x16 mode. However, after quiting TDW, 
   everything, *including the mouse*, works fine; its just the mouse cursor
   that has vanished. I know the mouse works because I can click on my desktop
   and bring backmenu up.
c) Lastly, am I doing something wrong, or is the whitewater resource toolkit
   a model memory hogger and slower than Dan Quayle? It takes about 10 secs to
   even draw its first window when I run it (on a 386-20, 64K cache, 8Meg, 17ms
   harddrive, pc-cache disk caching program). Next, I opened its own executable
   up (ie, opened up wrt.exe) and modified one of its cursors. When I tried to
   save the file, it kept going for about 10 secs before declaring out of 
   memory). Windows otherwise shows 24 Meg free.

d) One more thing: can anyone review *real quickly* what was covered in comp.
   architecture in the past two weeks? ;-)

Thanks!

Milan