Your right it will probably spoil you.  I tried my luck with the HC11
development tools
before this, and threw up my hands in disgust.  After countless hours
talking to
blank faced Motorola engineers ( who probably have it out for me), I
switched the
whole project to Microchip, and started from scratch.

It turns out the development environment is, press F10 and voila!... and
since I am
using an ANSI C compiler, all the stuff I learned in the last 8 years
writing test
software is not lost in this new frontier.

MPLAB was a bit quirky at first, but after solving these minor issues, I'm
quite happy.
I'm glad you find it to your liking too.

Craig


-----Original Message-----
From: bowman <bowman@montana.com>
To: Craig Lee <craiglee@TELUSPLANET.NET>
Date: Thursday, April 30, 1998 11:00 PM
Subject: Re: MPLAB under Windows 95


>
>: What I had to do was wait for the MPLAB timout message to come up, switch
>to
>: the dos box and quickly hit pause.  This suspended the dos box.  Then I
>set
>: it's
>: properties so that it didn't suspend the background, and I set the idle
>to
>: high.
>
>thanks! i had tried to change the properties with no joy. 3.11 let you mess
>with the pif, but i had had no reason to mess around with 95's DOS modes.
>caught the properties button on the window before it died, modified it, and
>it seem to work. don't know how it will be when i restart MPLAB.
>
>: I've seen the same thing when trying to include DOS tools under Borland
>C.
>: Perhaps
>: it's a Borland library issue.......
>
>may well be. i got burned by the OWL a few times. VC++ has its moments too,
>but has worked better for me. still don't know why they do that last getc()
>in MPASM. probably to let you see the results in DOS mode, but i think it
>would work better with MPLAB if they'd remove it.
>
>nice tool when i got it to work. probably spoil me for the primitive 8051
>setup i use.
>
>bob
>