From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,28db79a4b238c104 X-Google-Attributes: gid103376,public From: jerry@jvdsys.stuyts.nl (Jerry van Dijk) Subject: Re: What's wrong with this simple Ada w/ assembly code? Date: 1999/03/17 Message-ID: #1/1 X-Deja-AN: 456234037 References: <36ddb9aa.0@silver.truman.edu> <36ec237f.0@silver.truman.edu> <36ef2175.4732984@news.pacbell.net> Organization: * JerryWare *, Leiden, Holland Newsgroups: comp.lang.ada Date: 1999-03-17T00:00:00+00:00 List-Id: Tom Moran (tmoran@bix.com) wrote: : >No, there are _no_ interrupts in Windows. : 16 bit DOS apps that use Int 10, for instance, run just fine in a : Windows 95 DOS window, at least on my machine. It's been a while : since I wrote, or used, a 32 bit "Extended DOS" program, but don't : they also do what's necessary to handle such interrupts, IO, etc, : while running under Windows? Yes, on Win9X (and to a lesser extend NT) you can run DOS programs that use interrupts. What I tried to point out was: -> If you want to write DOS programs, use a DOS compiler. GNAT/NT generates code for Win32, not DOS. [The confusion here is that, contrary to for example OS/2, there is only one type of console window in Win9x, which is called the MS-DOS window. In reality it is a Win32 console with the ability to recognize DOS excutables and running them in a emulated DOS environment] -- -- Jerry van Dijk | Leiden, Holland -- Team Ada | jdijk@acm.org -- see http://stad.dsl.nl/~jvandyk