News
Follow Us on Twitter
Like Us on Facebook
Subscribe on Youtube
Rouli, on Jul 31 2009, 05:58, said:
It's August. You ever get any answers from badmfmike or ArizonaLoco about the version of SRS they're using? I've got version 1.2.10.0 from freewarePPC.com that I have NOT installed yet. I'm running a BJII with WM 6.1. I understand that 1.2.10.0 is an old version. I don't mind as long as it works.
If not, I guess I'll have to go with the registry entries.
Ok, these are the registry entries for wavedev and A2DP (not BtA2dpSnd):
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\wavedev]
"R2VS Target Model"="SGH-i617"
"R2VS Driver Version"="2.0.3 (2007.08.21)"
"OutputDevice"="wavedev.dll"
"DeviceAttenMax"=dword:00000014
"StreamAttenMax"=dword:0000002C
"IClass"="{A32942B7-920C-486b-B0E6-92A702A99B35}"
"MemLen"=dword:00000400
"MemBase"=dword:FFFB3000
"Order"=dword:00000010
"Index"=dword:00000001
"Flags"=dword:00010000
"Dll"="R2VS_ARM_WM6_STD_Driver.dll"
"Prefix"="WAV"
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\wavedev\R2VS]
"Power"=dword:00000000
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\A2DP]
"SamplingFreq"=dword:0000AC44
"Order"=dword:0000000A
"Keep"=dword:00000001
"Prefix"="A2D"
"Index"=dword:00000000
"Dll"="A2DP.dll"
I think one of the first q's I have is: Does SRS-WOW replace wavedev.dll (as OutputDevice) or R2VS_ARM_WM6_STD_Driver.dll (as Dll)? Based on this, I can't see anyone getting SRS-WOW to work on WM 6.1 BJII's even with the registry edits described in this thread, let alone "out the box". Next: A2DP makes more sense than BtA2dpSnd. The only instance of A2DP that I can think of in a WM registry (or computer environment in general) is that concerning Bluetooth, and A2DP is a one way profile (no Rcv). The Bt and Snd in BtA2dpSnd are redundant. Is there a way to can misinformation here or do we all need to keep a big grain of salt in front of our monitors.
If not, I guess I'll have to go with the registry entries.
Ok, these are the registry entries for wavedev and A2DP (not BtA2dpSnd):
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\wavedev]
"R2VS Target Model"="SGH-i617"
"R2VS Driver Version"="2.0.3 (2007.08.21)"
"OutputDevice"="wavedev.dll"
"DeviceAttenMax"=dword:00000014
"StreamAttenMax"=dword:0000002C
"IClass"="{A32942B7-920C-486b-B0E6-92A702A99B35}"
"MemLen"=dword:00000400
"MemBase"=dword:FFFB3000
"Order"=dword:00000010
"Index"=dword:00000001
"Flags"=dword:00010000
"Dll"="R2VS_ARM_WM6_STD_Driver.dll"
"Prefix"="WAV"
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\wavedev\R2VS]
"Power"=dword:00000000
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\A2DP]
"SamplingFreq"=dword:0000AC44
"Order"=dword:0000000A
"Keep"=dword:00000001
"Prefix"="A2D"
"Index"=dword:00000000
"Dll"="A2DP.dll"
I think one of the first q's I have is: Does SRS-WOW replace wavedev.dll (as OutputDevice) or R2VS_ARM_WM6_STD_Driver.dll (as Dll)? Based on this, I can't see anyone getting SRS-WOW to work on WM 6.1 BJII's even with the registry edits described in this thread, let alone "out the box". Next: A2DP makes more sense than BtA2dpSnd. The only instance of A2DP that I can think of in a WM registry (or computer environment in general) is that concerning Bluetooth, and A2DP is a one way profile (no Rcv). The Bt and Snd in BtA2dpSnd are redundant. Is there a way to can misinformation here or do we all need to keep a big grain of salt in front of our monitors.
Trying Rouli's reg settings above to restore sound on BJII WM6.1 as like a dumb@## I tried to load SRS WOW last night was getting the infamous driver error then lost all audio and was getting that wmp could not play file. Any advice would be great will let you know if settings above work
Promote to Article
