Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!msuinfo!sharkey!teemc!fmeed1!cage
From: cage@fmeed1.UUCP (Russ Cage)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Why doesn't this work?
Summary: Check for proper exit from the program!
Message-ID: <8302@fmeed1.UUCP>
Date: 6 Oct 90 19:24:17 GMT
References: <1939.2709b45f@spacm1.uucp> <34517@cup.portal.com> <OTTO.90Oct4103609@tukki.jyu.fi> <4153@altos86.Altos.COM>
Reply-To: russ@m-net.ann-arbor.mi.us (Russ Cage)
Organization: Ford Motor Co., Electronics Div., Dearborn, MI
Lines: 29

In article <4153@altos86.Altos.COM> rcollins@altos86.UUCP (Robert Collins) writes:
>>[why doesn't this work ?]
>>   >> DEBUG<SOURCE.DBG>SOURCE.LST

>Does the file SOURCE.DBG look like this:
>a  	; for ASSEMBLE
>SOURCE CODE
><ENTER> ; to exit ASSEMBLE MODE
>RCX     ; file size
>RBX     ; File size
>W	; Write file
>Q	; QUIT (this is as important as "A" for assemble)

WHATEVER you do, do NOT forget the "Q"uit command to DEBUG.

I have done procedures such as the above hundreds of times (literally).
If you forget the "Q" command, DEBUG does not recognize the EOF condition
on stdin as it should, and it infinite loops, locking up the machine.
The only way to exit then is to reboot.

If you construct your SOURCE.DBG file correctly, your script will
work.  If not, you will chase the bug for a long time, especially if
you are re-directing the output to a file which is lost when you
reboot.
-- 
Russ Cage	Ford Powertrain Engineering Development Department
Work:  itivax.iti.org!cfctech!fmeed1!cage   (Business only, NO CHATTY MAIL PLS)
Home:  russ@m-net.ann-arbor.mi.us  (Everything else)
I speak for the companies I own, not for the ones I don't.