Hi Mike,

 GVA>> But under OS/2 I get "strange results" I think is because
 GVA>> the kernel switch the process in the CPU (execute more than
 GVA>> a program), so the results are not the expected.

 MB> You get "strange" results because, under OS/2, your program is not
 MB> talking directly to any hardware.  Rather, OS/2 is using a protected
 MB> mode handler located in a virtual device driver (VDD) to trap your
 MB> attempts to access the timer hardware, and the timer is actually
 MB> emulated or "virtualized" in software by the VDD.  As you
can imagine,
 MB> this would more than explain why you are getting results which you
 MB> think are "strange."
Just wondering whether turning on HW_TIMER in the DOS settings would not do
the trick? (if his programme is a DOS programme that is)

Cheers,
        Neilen
[Sysop Jury-Rigged BBS AH]

... Windows UKD: Unexplained Keyboard Destructions
--- FMail 1.0g