🚀 go-pugleaf

Hello, All:
I am using Windows 3.1 as an integrated programming environment
for a microcontroller. The MCU board communicates with the PC
through COM1. At one time I was able to use Kermit for DOS in its
own window along with a DOS command window. I would edit 
in Windows Write (not very good for programming), compile
in the DOS command, then see the results in my Kermit window - beautiful!

This is how I download to the MCU:
(Kermit is set for COM1)

1. In Kermit window, the MCU is put into load mode (it remains in Kermit)
2. In the Dos window, I type
	type myprog.s19 > com1

That used to work OK. One time I got a contention error message
from Windows for COM1, but I ignored it and eventually the problem
just vanished.  Then I noticed that line #2 above suddenly stopped
working after I run Procomm (set for COM3) in the DOS command window.
I would reset, restart Windows, and everything is fine again.

But today it won't do it at all. I still get a good DOS command window
and the Kermit window still talks to the MCU. But the DOS command
window can't talk to COM1 at all. I haven't changed any setting in
Windows throughout the whole time.

Does anyone have any ideas why this could be happenning?

thanks

-chito 
lapena@athena.cs.uga.edu