You can reboot from ftp. I think your environment was probably so fragmented that it got trashed (not the first time that something like that would happen). So the bootloader created a fresh default environment - but one that is not sufficient to make the router boot up. Just as well that you had a backup of the environment with the RUC output.
Yeah good thing I did have a backup
but for good measure I reflashed the modem's firmware using an exe I found on the D-link support pages for my modem. Modem works fine and is booting up without a hitch. However, the modem again fails to enable the wireless radio.
I went with the earlier command you requested
echo "NVS_TFTP_LOAD 0" > /proc/ticfg/env
via telnet, and the modem took a very long time to reboot (14 minutes with only the power light lit), but when that was done, the status light, the lan lights lit up as usual, modem is able to connect to the internet via ADSL2+ and I used it to get online and post this reply.
Again however, the Wifi light is not lit, and none of my devices can see the wireless access point, regardless of the settings i set in the modem's configuration page.
I went onwards to use the RouterTech Firmware Tool v0.97b to check the router and was thrown a very nice message, a copy of the message is below:
You seem to have a wireless router, BUT no wireless driver! Enable your wireless AP, and start again. Otherwise, you are on your own!
I attempted to go to the 1350A Wireless TAB and select "Get Details from router", I was thrown with the following message
I cannot find the TNETW ID. Perhaps your wireless is okay (or not enabled)?
Is there anything else i can do from here?
Thanks again Chief