From: dg AT dcs DOT st-and DOT ac DOT uk Message-Id: <18053.9703092358@pulteney.dcs.st-andrews.ac.uk> To: opendos AT mail DOT tacoma DOT net Subject: Re: [opendos] Multitasker API and a demo program In-Reply-To: chambersb@juno.com's message of Sun, 09 Mar 97 17:32:25 -0500. <19970309 DOT 143603 DOT 4943 DOT 4 DOT chambersb AT juno DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Mar 97 23:58:44 +0000 Sender: owner-opendos AT mail DOT tacoma DOT net Precedence: bulk >On Sat, 08 Mar 97 02:56:38 +0000 dg AT dcs DOT st-and DOT ac DOT uk writes: >>(BTW, is there an easier way of getting at the 32-bit registers from >>Borland >>than using inline assembler and `db 0x66' in front of instructions? >>That makes >>my skin crawl... luckily, I found an API that didn't need it.) >Sure, use TASM and link in the object file. (I had to do this with bpc). > BTW, do you _have_ to use Borland to compile programs for the API, or >was it just the one you picked? I vaguely recall I tried TASM and it didn't understand the 32-bit instructions either (though I could be wrong). Besides, doing it stand-alone with TASM means that I'd have to find out about the C calling conventions. Having just spent the day struggling with Alpha assembly code and gcc's C calling conventions (run screaming!) I didn't feel like doing the same for Borland. (Odd though this may seem I wrote PS to wind down.) Why Borland? It's small (v3.1), easy to use (*great* IDE) and is perfectly suited for the task. -- ------------------- http://www-hons-cs.cs.st-and.ac.uk/~dg -------------------- If you're up against someone more intelligent than you are, do something totally insane and let him think himself to death. --- Pyanfar Chanur ---------------- Sun-Earther David Daton Given of Lochcarron ------------------