From: marcov@stack.nl
On 2005-12-21, Jyrki Lahtonen wrote:
> Alas, running these programs in the command prompt window (full-screen)
> of winXP immediately hangs the system. The programs that only use
> my modeX graphics unit run ok - it is the ones that use my mouse unit
> that won't run. Consultation with a local guru gave me the impression
> that meddling with the timer interrupt is a no-no under XP. A lengthy
> lecture on interrupt tables under protected mode ensued (over my head,
> I'm afraid)...
In general the dossupport in the NT systems is much more limited.
> Any ideas? Should I just redraw the mouse cursor by callinig a
> refresh routine within the loop from the module that wants to
> get some input from the mouse? That would be ugly, but if it works...
> Will updated mouose drivers handle modeX?
Maybe. Moreover, in dosboxes, windows provides the dosdriver. Another
possibility would be to not directly try to access the timer hardware,
but to study the interrupt list if there is some timing support in "dos",
that is emulated by XP. You could also try to mess with the settings of the
dosbox ("set win98 emulation mode or so").
> I'm still running this stuff at home on an original 60Mhz Pentium
> (a real collector's item, FDIV bug and everything:), but the countdown
> to a hardware upgrade will begin any time (missus permitting). At work
> I get to try things out with a newer PC with winXP that won't let
> me do anything (why do they want to take "Personal" out of "PC"?)
Because it was a recipe for system instability. The XP/NT series of windows
is way better than the 9x. Unfortunately, the legacy support is worse, and a
fact that one can't escape in the long run. I wouldn't personally invest any
time in 16-bit or dos programs anymore.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
