Return of the 50ms asio - problem - X-Fi/

Question

I'm using winxp x64, the 2.07.0004 - drivers (web update 2) with the X-FI Fatalty fps and commonly using sonar 5 x86
I've read through this forum for a solution to my problem, which is that I set ASIO-latency at 4ms in sonar (lowest I can go without large projects just stopping), but upon reboot the latency-setting reverts to 50 ms.
I read that this was a problem back in like 2003, but it seemed that it was fixed with some driver update suggesting that the current x-fi x64-drivers are either based on the wrong x86-build or some other messed up error.
Is there a workaround or some file that I can substitute, or do I have to wait for a technical response and some new drivers?
Anyway, I hope I have alerted you to the fact that this problem still exists (at least for me) in 2006

Answer 1

I seem to have narrowed down to what is the direct reason for the default 50ms-setting, but not what causes it.
You're correct, jutapa, in that the settings are stored two places due to wow64 and regular x64 behavior, and sonar x64 wrote the settings to
HKCR\CLSID\{48653F8-8A2E-D3-9EF0-00C0F02DD390}
, whereas 32-bit apps running on WOW64 would make creative asio panel write to
HKCR\Wow6432Node\CLSID\{48653F8-8A2E-D3-9EF0-00C0F02DD390}
And upon editing the latency in sonar x86 or B4 . the setting of dword:00000004 would be written to the registry, but upon reboot THAT SETTING WAS DELETED from the registry again by some process, (most probably upon bootup, since I even tried by hard-resetting after editing the registry), thus forcing the panel to revert to the "default" setting for lack of better instructions.
The "normal" x64-setting direct in HKCR\CLSID was correctly saved between reboots.
I'll try to fiddle a bit to see what process causes this behavior, although I suspect the startup-process CTASIO to be the culprit.
EDIT: removing the entry CTASIO from the startup-session caused the problem to disappear. The entry invoked regsvr32.exe /s ctasio.dll, all running from the %systemroot\SYSWOW64 -directories, and probably rewriting/resetting the registry entries for wow64 only.
Playback doesn't seem to suffer from me having removed this startup-process, so is it harmful to ahve removed it, or was this just meant to be a single.time process for wow64 that for some reason was set to start everytime?Message Edited by Dispater on 03-06-200602: PM