Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

why can't i open rtsp source although i have edited aout:config appropriately

  • 3 ŋuɖoɖowo
  • 1 masɔmasɔ sia le esi
  • 2 views
  • Nuɖoɖo mlɔetɔ anmaelo

more options

i used to be able to open an rtps-stream source following the instructions after editing the config information as before like this: network.protocol-handler.external.rtps;false

then i had reset Firefox for some reason and repeated the edit in the config. after this i haven't been able to open rtps-sources anymore. why doesn't it work anymore. what have i done wrong. i read somewhere that other people have also experienced this problem (but not everyone). i also found out that the problem appeared after some update in Firefox. i checked that my Firefox is up-to-date. i have Windows 7, and i think that you know my plug-in's much better than i do. ;)

how can i fix this?

i used to be able to open an rtps-stream source following the instructions after editing the config information as before like this: network.protocol-handler.external.rtps;false then i had reset Firefox for some reason and repeated the edit in the config. after this i haven't been able to open rtps-sources anymore. why doesn't it work anymore. what have i done wrong. i read somewhere that other people have also experienced this problem (but not everyone). i also found out that the problem appeared after some update in Firefox. i checked that my Firefox is up-to-date. i have Windows 7, and i think that you know my plug-in's much better than i do. ;) how can i fix this?

All Replies (3)

more options

Hi, any luck if you change to false the network.protocol-handler.expose.rtps also ?

thank you

more options

On Windows a protocol needs to be registered by the application that supports it and that creates the correct registry keys. See:

more options

cor-el said

On Windows a protocol needs to be registered by the application that supports it and that creates the correct registry keys. See:

so...? what should i do? - but i don't think that anything that i could do here would help. the problem appeared suddenly after i had had my pc with the W7 and Firefox working well with my VLC for a long time. the only change was an update in Firefox. that was many months ago.

the first answer didn't help either. i tried it. thank you for your trials.