From: "Alexei A. Frounze" Newsgroups: comp.os.msdos.djgpp Subject: Re: 3rd Try: Maybe an asm problem? (Problems linking) Date: Tue, 02 May 2000 00:18:03 +0400 Organization: MTU-Intel ISP Lines: 21 Message-ID: <390DE67B.5F9387B8@mtu-net.ru> References: <390D472E DOT 34491066 AT mtu-net DOT ru> NNTP-Posting-Host: ppp103-25.dialup.mtu-net.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Trace: gavrilo.mtu.ru 957212293 62988 212.188.103.25 (1 May 2000 20:18:13 GMT) X-Complaints-To: usenet-abuse AT mtu DOT ru NNTP-Posting-Date: 1 May 2000 20:18:13 GMT X-Mailer: Mozilla 4.72 [en] (Win95; I) X-Accept-Language: en,ru To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Damian Yerrick wrote: > >Actually, most of them do, especially if they use RHIDE, Emacs, Less, > >Info, and other programs. 2Fh/1680h is the function called by the > >library function __dpmi_yield; most interactive programs call that > >function inside their idle loop (or if they don't, they should). > > Oh, BTW, how often should __dpmi_yield() be called, to balance time > between drawing an app's graphics and giving time to other apps? Don't share any time with other programs. Especially, if your program is time-critical such as gfx stuff, 3d engine, etc. Btw, is there something about "release timeslice" in Allegro? Or a programmer must take care about that himself? bye. Alexei A. Frounze ----------------------------------------- Homepage: http://alexfru.chat.ru Mirror: http://members.xoom.com/alexfru