Mail Archives: opendos/1997/01/18/02:23:14
At 01:56 AM 1/18/97 +0100, Mark Habersack wrote:
>Once upon a time (on 16 Jan 97 at 22:03) Gene Buckle said:
>
>
>> I'll look into newgrouping these:
>>
>> comp.os.opendos.advocacy
>> comp.os.opendos.bugs
>> comp.os.opendos.developer
>> comp.os.opendos.gui
>> comp.os.opendos.misc
>> comp.os.opendos.programming.djgpp
>> comp.os.opendos.programming.drivers
>> comp.os.opendos.programming.multitasking
>
>comp.os.opendos.programming.customapi /* For API specific for OpenDOS */
>comp.os.opendos.compatibility
>
Ok. It may be easier to place them in the alt.os.* heirarchy so we don't
need to do an RFD to get them newgroup'd under the comp. heirarchy. Thoughts?
>>
>> No changes need to be made at all for djgpp. I've even been able to use
>> Allegro with it. *chuckle* (Hey! Maybe all the problems those folks are
>> having is because they're not running the _Right_ operating system! :) )
>;-)Maybe... Speaking of Allegro. Do the examples that use timers run OK
under
>OpenDOS multitasker? They cause Windoze to choke.
>
If memory serves, there should be no problem. I can't easily test right
now because I'm waiting for another machine to built so I can dedicate the
one I'm on now to OpenDOS.
>>
>> There is no documentation available right now. I'm hoping to get a
>> pre-release draft of the EMM386 API docs soon, so people can start working
>> magic once OpenDOS is released next week.
>Excellent! I hope the sources will be well-documented - that will be
>sufficient to do anything with OpenDOS
>
I just went digging through the EMM386 sources and they seem very well
documented. It's 100% assembly, so you better start brushing up. ;)
DPMS is version 1 as well as VCPI. (from notes in the code)
g.
- Raw text -