Quote:
|
Originally Posted by sfaure03
helmi_c 
Not so much. Its actually worse in that now if I access the connection settings in any way, the ppc locks up complety.
However for the first time on 3.5 I know see that if I plug in the USB cable the XP-laptop actually tries to get an ip address for an active sync connection.
However at that time it ALSO locks up the PPC, so no address is given out.
So. This is the right area. We were having significant problems w/ the Bluetooth screens not working right, and having very long delays and then unsuccessful attempts to enable / disable.
However from a practical point of view, its not so good. snicker. You think maybe the registry entries need adjusting?
By the way I used a build straight from IMCokeman here, no mods whatsoever from what he has on our ftp site. just a build, hard reset. hard reset again for "good measure", install cab. Soft reset (forced by the cab install).
then attempt usb, or bluenet adjustments. Either of which fail.
By the way another "interesting" side effect is that whereas the wireless today plugin was showing "sprintpcs" before installing the cab, after the cab, it only shows "Home Service". Seems that maybe some function call is returning "wierd" to the pluggin |
hmm... thats because, I included the ms2_usbfn.dll registry in platformxxx.reg... thats for testing...
btw the two file wavedev.dll & mfcce300.dll should fix the bt issue because I've learn the rom core, there was a conflict in ram address, see below:
Wavedev conflicted with intshare at ram address
Ram Address: 01290000
Ram Address: 01291000
Ram Address: 01292000
Ram Address: 01293000
Ram Address: 01294000
Ram Address: 01295000
Ram Address: 01296000
and for mfcce300.dll is conflicted with bthuart.dll at ram address
Ram Address: 01C80000
Ram Address: 01C81000
Ram Address: 01C82000
Ram Address: 01C83000
Ram Address: 01C84000
so theorytically speaking, the two files should fixed some issue with BT and internetsharing if the both function is been use for the same time, since they overlap each other ram memory, sound & Internetsharing or Bluetooth with any app that use mfcce300.dll, or generaly make the system unstable in some function...
the two files it self will fix that, not the registry value that I added to platformxxx.reg for ms2_usbfn.dll... so u might extract the two files from the cab, or remove the platformxxx.reg from the cab.
hmm... I think we need to patch other device driver (ms2_usbfn.dll) hopes that will fix the problem...