Quote:
Originally Posted by ebmorgan
I would explain this and get input before suggesting an unknown reg hack so we don't have another one to debunk.
Also, is this a hack simply to solve the error 67, or is this also something you suspect might have something to do with tethering detection?
|
Perhaps you're not familiar with my post history on this site, so I'll forgive you that mis-step, but you can rest assured that I don't post anything that needs debunking. I had a look in rilphone.dll with a hexeditor and saw the tethering detection logic. You're welcome to do the same.
Making this registry change will prevent Sprint from knowing you're tethering. I don't have the time nor the patience to explain it to you, other than to say that the Internet Sharing app is microsoft code, and does not have tethering detection built into it. It is extensible, however, but any of that code is not microsoft code. The link between the MS code and the 3rd party code is that registry entry. Without it, the internet sharing app will function just as it would on any other device--which is just straight IP NAT.