XXHighEnd

Some errors generated during the use of XXHE versions 09t-0 and 09t-2.
Playing unattended

Peter,

The error with Spooler/Hostproces is here too...

Also I like to say that invert checked and  Q1 at -3 playing is impossible... Cracks come up very often.... sliding the Q1 a bit up solves the problem.

Grtz

Hi Johan,

Do these errors also occur with both priorities to Normal (or better : "Nothing" after a reboot) ?

Peter,

I like to say that setting both priorities to nothing, that until this moment i have had no errors. Spooler/Host

 :)

Thank you Gerard.

Johan ?

Hello Peter,

First of all happy new year! Great job You've done in 2007!

Indeed after changing the priorities to Nothing, the errors where gone. After changing the ThreadPrio to normal the first system errors appeared again.

After installing version 09t-4 with the default priorities all seems to be working well. After changing this morning the Treadpriority to Realtime and a reboot i had again systemerrors.

Regards, Johan

Ok, this implies that anyone receiving these errors and can't live with them (the reasons can be various), should not mangle with the priorities, or should find a setting which does not harm.
Please note that the Processor Schemes will be related, and generally spoken "No Appointment" is the best setting for mangling the priorities.

All 'n all it comes down to
a. what sounds best, but
b. what your system can cope with.

Note that IMO a normally "lean" setup PC should be able to cope with all combinations offered. However, the drivers used (disk, soundcard) may influence a lot, and if e.g. a soundcard driver needs many resources (or needs them in critical situations) there's not much to do about it.
Whether indeed drivers take a lot of resources can be determined ... maybe, but I never bothered to research it.

I think it is fair to say/state, that those having these problems since "a" version of XXHighEnd, will be having these problems since the Processor Appointment was introduced, together with the system-wide priority settings. It might be (too) confusing in finding out since exactly which version this happened, because either (Appointment / Priorities) took a few versions before all worked as intended (like system wide priorities should work with a certain version, but they didn't).

Lastly, for SQ for *your* system it shouldn't matter compared to the earlier versions, were or the priorities weren't working system wide, and/or the Core Appointment wasn't there.
If there ever has been a version which allowed a lower Q1 than right now, you *must* be able to find a setting which allows for that again. You would need (to find) this when you recognize that Q1 on itself is more important for SQ than Prio settings or Corte Appointment.

:wacko:
Peter