You said config.xml, a non existing file. msbombs gave a demo URL but didn't say what to change in that URL (that has way more than one input field).

Come on, I meant where in the output of this program do I look for "can my modem be upgraded to your firmware via web interface"?

Yes, but I meant "the firmware's" as in the ZIP file (docs\faq.html).

I mean when upgrading the manufactor's firmware to yours. I see no config.xml file (the ZIP for 600E). So what do I need to change exactly in order to be back with 10.0.0.138?

Thanks!

Where do I look?

The one in that file gives a 404 error while the one here works.

Why don't you put this URL instead of the obsolete one in your firmware's faq.html#demo?

If I want to move from my router's manufactor's filmware to yours, can I still use web upgrade and just upload your firmware as if it was meant for the original firmware? If not, what should I do?

Thanks!

For example, making it 10.0.0.138 like it used to before the upgrade. I have static devices that use 10.0.0.*.

Better yet, can I do it so the upgrade would be to 10.0.0.138 to begin with?

Like the OP mentioned, it's not available there: DSL600E(C) Firmware v108.6.2b upgrade from v108.6.2a This is the closest they have. But as you can see it's not even a standalone firmware. When I tried to run it anyway (from the older version which komer83 had and I have) the modem got bricked (not ...

Wow. In that case, how do I back up my current firmware that - for this modem - is not "found either on their CD or on their website"? This modem's "Firmware Upgrade" page only offers to download the current configuration (which RUC does anyway).

If something goes wrong, will I be able to use this modem's reset button to get back my original firmware (your FAQ doesn't state if "factory defaults" also stand for "original firmware")?

If komer83's upgrade went fine, you should add this modem straight into https://www.routertech.org/faq/firmware/compatible-routers/ (which currently has similar modems but not this one specifically). With that said, I have the same firmware as komer83 had originally. When I try to enable UPNP, it ju...

Great tool, but please don't touch the registry and make it truly portable. It creates HKEY_CURRENT_USER\Software\Microsoft\Visual Basic even though it doesn't even actually put anything in it. Update: I've confirmed you indeed fixed it in newer versions, thanks! Speaking of portability, are there a...