Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

DPMILD32 issues - spawn trouble: solution found ??? (DOSX)

posted by jaybur Homepage E-mail, UK, 22.02.2008, 01:49

> > Just what does "to some extent" mean exactly.
>
> "to some extent" means: "to a certain extent" (sorry for my bad English
> :-D )

It's not bad English, just ambiguous.:-P

> Thread priorities aren't supported, but "SetThreadPriority()" isn't a
> no-op, because changing a thread's priority to "real-time" will have
> "some" impact - IIRC.

Ok. :-(

> > How does it handle file I/O and other DOS calls?
>
> It calls int 21h with register AX set "properly".
>
> When the "indos" flag is set, no thread switching is done.

Right, so DOS calls are effectively serialized.

> > What is the timeslice, and can it be changed?
>
> it is 20 ms and it can be changed in the source.

But not programatically. :-(

> > Does a complete timeslice have to have elapsed before a context-switch
> can occur?
>
> "Usually" yes. :-D

:-(

> > What timer does it use - the PIT#0 or the RTC interrupt?
>
> The RTC - "usually" (that is, it can optionally be changed to use the PIT
> timer).

Ok.

> > Can an application reprogram PIT#0 without it screwing up the task
> > scheduler?
>
> The scheduler might not be worried too much. But why should a Win32
> program come to think that it can "reprogram" the hardware?

Why would a DOS program think it can't?

Is it your only goal to [partially] emulate Windows, or does HX aspire to be capable of being used for some things that Windows can't?

 

Complete thread:

Back to the forum
Board view  Mix view
22632 Postings in 2109 Threads, 402 registered users, 366 users online (0 registered, 366 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum