Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!uwvax!astroatc!nicmad!madnix!aaron
From: aaron@madnix.UUCP (Aaron Avery)
Newsgroups: comp.sys.amiga.tech
Subject: Re: What does this guru mean?
Message-ID: <1431@madnix.UUCP>
Date: 28 Jul 90 09:48:46 GMT
References: <32034@cup.portal.com>
Reply-To: aaron@madnix.UUCP (Aaron Avery)
Distribution: usa
Organization: ASDG Incorporated
Lines: 24

In article <32034@cup.portal.com> DrBob@cup.portal.com (Robert A Rethemeyer) writes:
>I can't figure out what I'm doing wrong.  Perhaps if I knew more about
>what dos thinks is an "unexpected packet" during Write(), and how I could
>be creating that situation, I might know where to look.  Is there anything

Well, basically, you're doing something which is not allowed. It's not well
documented, but it's a no-no to call DOS functions from a DOS handler.

The problem is that Write() is using the same message port that the handler
uses for its input and output. When the packets get inter-mingled, bad things
can happen. If you _really_ want to use DOS I/O from your handler, you'll
need to create a new message port with a new signal bit and do all of the I/O
by packets, all the while handling the incoming packets meant for you.

The best low-level debugging option is still a terminal (or computer) hanging
off the serial port and kprintf().

- Aaron

-- 
Aaron Avery, ASDG Inc.         "A mime is a terrible thing to waste."
                                                             -- Robin Williams
ARPA: madnix!aaron@cs.wisc.edu   {uunet|ncoast}!marque!
UUCP:   {harvard|rutgers|ucbvax}!uwvax!astroatc!nicmad!madnix!aaron