HPET in XP ? yes, no, maybe ? :D

[leeperry]

so I got HPET enabled in my Gigabyte P31 mobo BIOS, and I run XP SP3.

it uses IRQ 0 & 8 in the device manager.

a friend of mine with pretty much the same mobo(giga P35) on XP SP2 doesn't have them.

he's got "system clock" on 0 and "CMOS realtime system clock" on 8.

so is m$ lying when they say that there's no HPET drivers for XP ? :D

I haven't found a way to check whether HPET was actually functional in XP :confused:

[James]

so I got HPET enabled in my Gigabyte P31 mobo BIOS, and I run XP SP3.

it uses IRQ 0 & 8 in the device manager.

a friend of mine with pretty much the same mobo(giga P35) on XP SP2 doesn't have them.

he's got "system clock" on 0 and "CMOS realtime system clock" on 8.

so is m$ lying when they say that there's no HPET drivers for XP ? :D

I haven't found a way to check whether HPET was actually functional in XP :confused:
You can check the clock frequencies in ReClock's logfile.

[leeperry]

well it says :

0.61s 000890 Getting reg key Wait = 154320.960000
0.61s 000890 Getting reg key WaitFactor = 2.572016
0.61s 000890 Getting reg key Freq = 3579535.500000
0.61s 000890 Getting reg key Ti = -1.369129
0.61s 000890 Getting reg key BaseFreq = 3579545

anyway it's clearly the timing source on my box...except if it runs in legacy mode ?

apparently you can check if HPET is active by using QueryPerformanceCounter/QueryPerformanceFrequency :
http://support.microsoft.com/default.aspx?scid=KB;en-us;Q172338

http://www.eggheadcafe.com/articles/20021111.asp

this might be interesting for Reclock maybe ?
http://www.codeguru.com/cpp/w-p/system/timers/article.php/c5759

[James]

well it says :

0.61s 000890 Getting reg key Wait = 154320.960000
0.61s 000890 Getting reg key WaitFactor = 2.572016
0.61s 000890 Getting reg key Freq = 3579535.500000
0.61s 000890 Getting reg key Ti = -1.369129
0.61s 000890 Getting reg key BaseFreq = 3579545

anyway it's clearly the timing source on my box...except if it runs in legacy mode ?

apparently you can check if HPET is active by using QueryPerformanceCounter/QueryPerformanceFrequency :
http://support.microsoft.com/default.aspx?scid=KB;en-us;Q172338

http://www.eggheadcafe.com/articles/20021111.asp

this might be interesting for Reclock maybe ?
http://www.codeguru.com/cpp/w-p/system/timers/article.php/c5759

No, I mean this:

0.01s 00075c Raw speed = 3579545 Hz
0.01s 00075c Used speed = 3579545 Hz


Above example is from PMTimer on XP.
"Raw Speed" is the value returned by QueryPerformanceFrequency.
ReClock's BaseFreq can be different (Used speed).

It is either 1.5MHz (PIT, Win2000), 3,5MHz (PMTimer), CPU Clock ( :bang: ) or HPT frequency (I believe around 15MHz)

[leeperry]

xp sp3 /NOEXECUTE=ALWAYSOFF /FASTDETECT /USEPMTIMER /NODEBUG /TIMERES=9766
0.00s 000890 Raw speed = 3579545 Hz
0.00s 000890 Used speed = 3579545 Hz

xp sp3 /NOEXECUTE=ALWAYSOFF /FASTDETECT /NODEBUG /TIMERES=9766
0.00s 000168 Raw speed = 3735070000 Hz
0.00s 000168 Used speed = 3647529 Hz

vista sp1
0.08s 0006ec Raw speed = 14318180 Hz
0.08s 0006ec Used speed = 3579545 Hz

you nailed it, thanks James :policeman:

[ashlar]

Meaning? From the above you have working HPET under XP SP3 or not?

Help us mere mortals :)

[leeperry]

well the "raw speed" on Vista is indeed 15MHz(HPET?), but the "Used speed" is the same as the PMTimer in XP....not sure why, maybe James knows ?

OTOH, even though I got 2 IRQ entries that say "HPET" on XP, the raw speed is not 15MHz :doh:

[James]

well the "raw speed" on Vista is indeed 15MHz(HPET?), but the "Used speed" is the same as the PMTimer in XP....not sure why, maybe James knows ?

Sure. ReClock divides the frequency by 4, which happens to be 3579545.

[ashlar]

Sure. ReClock divides the frequency by 4, which happens to be 3579545.And what do you make of his XP SP3 w/HPET results?

[leeperry]

And what do you make of his XP SP3 w/HPET results?
what results ?

anyway I don't recall ever having 2 HPET entries in the IRQ list..

and lately HR has been working amazingly well w/ the new betas + yesgrey's resampler on my box(starts at -8ms jitter and end up at -3ms 90' later on 23.976 MKV...great stuff!), so I thought it was sorta related :agree:

and to add more infos to the drifting jitter in HR(ÿaÿ :D ), Kazuya just told me that it also drifts with 23.976 xvid .AVI....but it doesn't happen with .TS or .VOB(this jitter renders VMR/HR/EVR unstable on XP)

so this is not a MKV-only problem....and might very well be a Reclock issue...or Directshow :confused:

[James]

And what do you make of his XP SP3 w/HPET results?

?????

Raw speed = 3579545 Hz

is not the frequency of the HPT

[leeperry]

all this stuff is rather confusing :D

coz I remember some guys having problems with glitches on their sound cards on HCFR had to increase its IRQ priority in the windows registry...then problems were gone.

so I found a link that said you should increase the IRQ8 priority(which is the CMOS realtime timer on XP SP1/SP2), and then I found another site that said that it was b/s :

http://www.wxpnews.com/archives/wxpnews-039-20020820.htm

The NT family of OSs don't even use the real-time clock (IRQ8 ) for timekeeping in the first place! They use programmable interval timer (8254, on IRQ0) for driving system timekeeping, CPU time accounting, and so on. IRQ8 is used for profiling, but profiling is almost never turned on except in very rare development environments.


on my XP SP3, IRQ0 & 8 are HPET....

I can remember that I read about a tool that increases IRQ priorities, I'll look into it :D

[leeperry]

ok so I could increase IRQ0 or 8 priority, I'll look into it :D

but a few weeks ago ashlar gave this link :
http://blogs.msdn.com/embedded/archive/2006/03/04/543141.aspx

they say that you wanna set it to 0x16, and I think it did increase the responsiveness of the system!

but if I go back to the windows setting, it says it's optimized for background processes ?!

and I've found a few interesting links :
http://forums.guru3d.com/showthread.php?p=1451631#post1451631
http://recoverymonkey.net/wordpress/?m=200708

the first link also says that /TIMERES=9766 is pointless, as any media player will set it to this value already...which is rather strange as w/o this I couldn't achieve 0.17ppm in Reclock when /USEPMTIMER was being used :doh:

the second link makes it even more complicated to know what to set for the damn win32priority reg entry :(