Guest amdzero Posted June 20, 2010 Report Share Posted June 20, 2010 just thought I'd add my fix the the list of fixes. I know that Ninja posted a fix, but it didn't work for me as I'm using 6.5.5 So here is the reg edit that worked for me, I've cabbed it up so you can use it. This will probably be temporary, as the chefs now have working fixes for MMS Receive. Just thought I'd make a new post for future reference. "Those who do not remember the past are condemned to repeat it" AMDZero_AMDZero_mms_fix.cab also for those that want to edit their registry instead: [HKEY_LOCAL_MACHINE\Security\PushRouter\Registrations\ByGenericId\80724304BD56BF01] "GenId"="80724304BD56BF01" "ContentTypes"="application/vnd.wap.mms-message" "AppId"="" "Path"="\\windows\\MMSListener.exe" "Params"="/mms" "RefCount"=dword:1 "Trust"=dword:2 Link to comment Share on other sites More sharing options...
Guest Ninja4Hire Posted June 20, 2010 Report Share Posted June 20, 2010 (edited) [HKEY_LOCAL_MACHINE\Security\PushRouter\Registrations\ByGenericId\80724304BD56BF01] "GenId"="80724304BD56BF01" "ContentTypes"="application/vnd.wap.mms-message" "AppId"="" "Path"="\\windows\\MMSListener.exe" "Params"="/mms" "RefCount"=dword:1 "Trust"=dword:2 That is weird because that is what I already have in my registry. So all I had to do what change the "ByCTAndAppId" to point to it. I wonder if it is different for 6.5.5. Edited June 20, 2010 by Ninja4Hire Link to comment Share on other sites More sharing options...
Guest kdkinc Posted June 20, 2010 Report Share Posted June 20, 2010 (edited) If I didn't repeat the past I'd have nothing to DO .. ;) Thanks AMD for what you do.. :( :) Edited June 20, 2010 by kdkinc Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now