Hi!
4-Май-2004 20:30 [EMAIL PROTECTED] (Paul Vojta) wrote to
[EMAIL PROTECTED]:
>> a
>> mov ah,4c
>> int 21
>> int 3
>>
>> g=100
>> g
PV> OK, I've tried it.
PV> Under MS-DOS 2.1 with native DEBUG and Win XP with native DEBUG, it
PV> drops you out of DEBUG and back into COMMAND.COM. In a way this makes
PV> sense, since the above code terminates a program and since you haven't
PV> loaded a program into DEBUG the only program that DOS (or XP) could
PV> possibly terminate is DEBUG itself.
1. Original letter says about LIST.COM which was ended by INT21/4C; your
test program was ended by INT20.
2. I was try INT21/4C manually (not through program file). Result: first
"g=100" silently returns to prompt ("-"), second "g" hangs my Windows
completely (I was forced to reboot machine).
PV> Under MS-DOS 2.1 with fd-debug, you're back at the DEBUG prompt.
MS-DOS 2.1? Where you find such anciency? :)
PV> Under dosemu 1.2.1 and FreeDOS (I don't know what FD version, sorry,
PV> but kernel.sys was dated 31 January 2004), I get "Unexpected single-step
PV> interrupt".
PV> So. Are you saying that the behavior under MS-DOS 2.1 is buggy?
Letter about "Unexpected single-step interrupt" was not from me.
Though, I myself report about extraneous message "Unexpected breakpoint
interrupt" after INT3 (do you seen my reports?).
PV> I strongly suspect that the buggy behavior under FreeDOS is either the
PV> problem of dosemu or freedos.
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_id│66&op=click
_______________________________________________
Freedos-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
