Message-ID: <390DABE4.903187FC@maths.unine.ch> Date: Mon, 01 May 2000 18:08:03 +0200 From: Gautier Organization: Maths - Uni =?iso-8859-1?Q?Neuch=E2tel?= X-Mailer: Mozilla 4.72 (Macintosh; I; PPC) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.os.msdos.djgpp Subject: Re: 3rd Try: Maybe an asm problem? (Problems linking) References: <390D7DD9 DOT F55A5EF6 AT mtu-net DOT ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit NNTP-Posting-Host: mac13-32.unine.ch X-Trace: 1 May 2000 18:08:04 +0100, mac13-32.unine.ch Lines: 30 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com > > __dpmi_yield is not for task switching, it's for releasing the current > > time slice allotted by Windows (or any other multi-tasking scheduler). Alexei: > Just some kind of a synonym. :) Sorry to contradict, but the "task switching" jargon is for the user choosing manually and delibarately a task to be foreground of his/her display. It's rather an antonym! > Do you bother about that while you're programming? I.e. do you write a custom > keyboard read function that calls that thing? In an OO environment that provides events like Turbovision, it suffices to put a call to the "Release time slice" for the "idle event" case! > Or maybe we all develop applications for background that should work and be > invisible? I dboubt. :) Inexact: that "Release time slice" can act when your program is at foreground and visible. It helps the background tasks to run faster! > How about old DOS programs? Are you sure all they release timeslice? Surely that if you unassemble a commercial DOS app. (e.g. DOS interactive commands) you'll find plenty of them... _____________________________________________ Gautier -- http://members.xoom.com/gdemont/