Re: Why don't Registry edits "stick"?
 

msh441, if you can't test this for me can you at least tell me how you were able to shut down the Guardian service with FDc?

I have installed the program and can see that Guardian is running or is at least listed in the services tab of FDc, so did you shut this down permanently by setting it to manual via that tabs menu?

If so could you tell me that to indeed continue to make this permanent, do you have to run FDc at startup and leave it running in the background for this to stay that way?

Thanks

Re: Why don't Registry edits "stick"?
 

You might also check to see whether or not CM Guardian is in your start up folder.

Re: Why don't Registry edits "stick"?
 

Create a blank txt document and rename it HTC_CM_Guardian.exe or whatever the equivalent file name is on your phone under windows. Then copy to windows directory using something like total commander. You then have a 0 byte file in it place.

Re: Why don't Registry edits "stick"?
 

Yeah currently CM Gaurdian is not there nor do I think it ever was I as I think I remember looking there before an have never seen it and I have just tried a file called HTC CM killer which re-wrote the file HTC_CM_Guardian.exe to a 0kb file but it still shows up on the services running list.

Now I don't know if that list means its running or just part of a list of all that could be run but the one thing I do see if I tap and hold on the Guardian service is that with the option view in the registry, it goes to HKLM\Services\CMGuardian and the only file listed there is CM_Guardian_Services.dll although were that is I don't know but I am assuming that if indeed it is being run as it is showing up in the services list, that it must be getting run via that .dll an not the .exe file in the windows folder.

But don't quote me on this as I really don't know for sure.

Re: Why don't Registry edits "stick"?
 

I have overwritten both files (dll and .exe) with blank files. This does not fix the resproxy issue. Try my fix posted above for what I have found to be permanent resproxy fix.

Re: Why don't Registry edits "stick"?
 

Yeah basically that is what the HTC_CM_Killer app that I used that you could get here http://forum.ppcgeeks.com/showthread.php?t=88014, did and it does work in that respect but again and I don't know if or what this means, it still shows up under the services list of FDc and in that list it refers to a file called CM_Guardian_Services.dll not a .exe so if indeed this means its running, it maybe running via that .dll an not the .exe file in the windows root folder.

Note: I just read a post at Howard Forms where someone deleted all the info in their CM_Guardian_Services.dll and zeroed out the file and that let them play with their connections without restoring the default one.

Not that I’m suggesting that unless you want to try it but it suggests that it is using this .dll instead of the .exe.

Re: Why don't Registry edits "stick"?
 

For those having disconnect issues, below are 2 reg edits you can use:
1. To auto disconect data after 1 min. of being idle:
HKLM\Comm\ConnMgr\Planner\Settings\
Set "SuspendResume" to 58 00 00 00 33 00 99 00 88 00 39 00 58 00 39 00 29
Set "CacheTime" to 60
This is found on this site somewhere in cab format, by straa.

2. Disconnect button:
KKEY_LOCAL_MACHINE\Control Panel\Phone
"Flags2"=dword:16 (decimal)

Re: Why don't Registry edits "stick"?
 

I need help with this aspect also. I found a reg setting under HKLM/software/OEM/Wmodem. The reg setting that TP2 won't let you delete or change is "Connected = 0". I want to either delete it or change to 1. But everytime I delete or change it, after I reset, it's back to exactly what it was. I have a feeling that this is preventing Wmodem from working like it used to.

I do have this reg setting
HKLM\Services\CMGuardian
Flags = 4

and it does not help in preventing the change to HKLM/software/OEM/Wmodem "Connected = 0" from being revert back every time a reset is done

Much appreciated if anyone knows how to make some of these reg setting changes stick.Thankx

P.S. A big F.U. to both HTC and Sprint to making our life more miserable with their new ploy to prevent registry changes. It wasn't like this with Mogul or even TP1

Re: Why don't Registry edits "stick"?
 

maybe write a mortscript that makes these changes as part of your tethering run??? that way it runs the script each time you tether so it doesn't matter if it resets later.

Re: Why don't Registry edits "stick"?
 

sure, but i am also wondering if this value needs to be there at boot time rather than just there before the start of wmodem for things to work properly.

I am also wondering if there's any other reg values that might also need to be changed or is now protected.... I think these protected ones are the ones that definitely related to services which they don't want us to use. I recall that ICS tethering supposely needs the Flags = 4 to stop CM Guardian from changing a reg key back. This however still didn't allow the change to "connected = 0" under the HKLM/software/oem/wmodem. I actually have a feeeling that there could be more to it but this is just a start

It's frustrating that we have not been able to pinpoint down the exact mechanism of registry protection going on. Looks like HTC and the carriers are really stepping it up...