Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[booglehead]

ADD WIRELESS 802.11B BACK TO ROUTER

--OR

LET ME DOWNGRADE

[EddieZ]

tried downgrading?

[lotacus]

LOL I would like to see what happens if someone tries to downgrade teh 1.3 firmware.

[EddieZ]

Me too, before I upgrade 

[AWDL]

The 1.30 Firmware has been taken down from the support site. It may do a little too much at once.
Removing 802.11b is not a bad thing for most people.
Conditions that make a firmware unable to be downgraded are not always avoidable.
Distributing a firmware that removed 802.11b and also will not allow the end-user to downgrade said firmware, could result in customer service or RMA issues neither the customer, seller, or manufacture desire.

Granted from what I have seen, people are reading the release notes and the warnings about the firmware, but I am looking to be on the safe side as the user base with access to the code made change (not read).

It may go back up because the benefits to the majority are to great, but for now we just need too take a closer look at the release.

[EddieZ]

The 1.30 Firmware has been taken down from the support site. It may do a little too much at once.
Removing 802.11b is not a bad thing for most people.
Conditions that make a firmware unable to be downgraded are not always avoidable.
Distributing a firmware that removed 802.11b and also will not allow the end-user to downgrade said firmware, could result in customer service or RMA issues neither the customer, seller, or manufacture desire.

Granted from what I have seen, people are reading the release notes and the warnings about the firmware, but I am looking to be on the safe side as the user base with access to the code made change (not read).

It may go back up because the benefits to the majority are to great, but for now we just need too take a closer look at the release.

Non-downgradeable firmware would suggest that the code base has radically changed. But still, regular firmware update routines clear out the whole memory space, so it is not impossible to create a downgrade path. Also because theoretically there is plenty of memory to address for such a feature. Will take some effort to add, but you will minimize the user discontent.

I agree with the b removal, but I can imagine the impact is great. And people should be aware of the releaslog, but we all know you only read them afterwards 

[booglehead]

yes, exactly what I did when my wife's laptop stopped working, checked the settings and read the release notes. I nice big FAT warning during the upgrade would of avoided this.

So how can I recover? I tried to downgrade but a message comes up like this:

[EddieZ]

There is no recovery possible...

I think it would be a wise thing Dlink came up with a statement of some sort...
Just applying the basic rules of customer satisfaction and damage control.

[summerstormpictures]

There is no recovery possible...

I think it would be a wise thing Dlink came up with a statement of some sort...
Just applying the basic rules of customer satisfaction and damage control.

Who at D-Link should make this statement? Curly, Larry or Moe?

[EddieZ]

Who at D-Link should make this statement? Curly, Larry or Moe?

That's probably one of the other issues, next to release management, test management and quality management