Print

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

[Lycan]

That can't happen.
Because the update functionality is based on a .xml we control. It's not automatic. we handle it.

[camattin]

I installed 1.22 today and it's working much better for me than 1.21 did (1.21 was bad enough for connecting to my company's VPN that I had to revert back to 1.20).

So far so good (note: I do have DNS relay disabled).  Haven't tested out everything yet... but first impressions are good.

[summerstormpictures]

Here's a little insight.

Version numbers are for TRACKING of versions. That being said if we come out with a firmware version 1.22b01 and a 1.22b02 and the b02 gets posted, but is found to have a flaw we'll post the working b01 until we can either fix the flaw (1.22b03) or get a new firmware 1.23.

Please do not ask me what constitutes a new firmware or a build change, they NEVER tell me.
(I'm guessing it has to do with how far in to the code they have to go to effect the fix/change.)

We can NOT just change the numbers as that would skew our tracking process and also disrupt error reporting to our software people.

Hope this shed's some light on the situation for you guys and helps you to be less confused.

I was right with you up until the part where you started talking.

[lotacus]

Would still like to request the ability to have client "ALIAS" in the wirless client information page.


As well, that feature for detecting new firmware has NEVER worked on my 655 here in canada.

[Evildust]

I tried to update my DIR655 A2 (1.21) with the 2 1.22 firmwares versions out this week but each time, the updating is ok but my router write it's the 1.21 firmware again I can't change the date inside.
 

[EddieZ]

Just leave 1.22 alone for now.
D-link has put it on the site too early, which I can understand because there has been a lot of impatience, and retracted it.

[booglehead]

Here's a little insight.

Version numbers are for TRACKING of versions. That being said if we come out with a firmware version 1.22b01 and a 1.22b02 and the b02 gets posted, but is found to have a flaw we'll post the working b01 until we can either fix the flaw (1.22b03) or get a new firmware 1.23.

Please do not ask me what constitutes a new firmware or a build change, they NEVER tell me.
(I'm guessing it has to do with how far in to the code they have to go to effect the fix/change.)

We can NOT just change the numbers as that would skew our tracking process and also disrupt error reporting to our software people.

Hope this shed's some light on the situation for you guys and helps you to be less confused.

That might be a fair statement for internal operations but when I visit the support site to download the latest firmware I would suspect the binary to work without the need to pull it!

It just so happens that I downloaded the 1.22 [1/13/2009] version the other day and was going to install this weekend, its only because I had missplaced my download did I come back to the support site to download again only to find that the latest 1.22 is missing.

I do not believe I've seen firmwares treated this way by other vendors, please take note.

[EddieZ]

That might be a fair statement for internal operations but when I visit the support site to download the latest firmware I would suspect the binary to work without the need to pull it!

It just so happens that I downloaded the 1.22 [1/13/2009] version the other day and was going to install this weekend, its only because I had missplaced my download did I come back to the support site to download again only to find that the latest 1.22 is missing.

I do not believe I've seen firmwares treated this way by other vendors, please take note.

Lycan,
From I professional point of view I do not have great admiration for your Tech dpt.'s versioning process or release management. Please get them to read a book on it or something because their practices look kind of amateuristic. I would gladly help you guys out (free of charge).

[Toilet-Duck]

Hey Eddie have you any idea when version 1.22 will be re-released again?

[EddieZ]

Nope, no idea. Shouldn't take too long, but the 1.21 is quite workable when tuned correctly.
Would like to do some testing for them before they put it out there. Haven't been able to convince them yet I guess 

Your alias could need a nice avatar:

[Toilet-Duck]

Aww I cant see the image lol 

[davevt31]

Aww I cant see the image lol 

http://www.sevensheaven.nl/images/producten/cartoon-spotprent_wc-eend-duck.jpg

[summerstormpictures]

Not to add to any discord over the ongoing fiasco over the 1.22 release, but from someone who actively sought out the DIR-655 from ''rave reviews'' by several sources as the best all around router for the money, and as someone who returned a freshly purchased and overpriced Apple Airport Extreme base station in exchange for it because the Apple unit was more expensive and was unreliable, I am a bit disillusioned that things have been so ''clunky'' thus far with my DIR-655.

The rather clumsy way that the 1.21 and 1.22 releases have gone remind me a bit of the MobileMe fiasco at Apple. There seems to be a relaxation in quality control, and when someone tries to point it out on the forums here, instead of understanding, they get the defensive attitude.

As for myself, after a heck of a lot of research and tinkering on my part post-1.21 firmware update, I managed to get it to work at least 90% of spec on a mixed Apple-Windows network--however--one should not have to ''hamstring'' something to get it to perform properly using less than optimal settings.

When the latest firmware update to 1.22 (the first posting) was reported I updated. There was no overt difference with when my 1.21 settings were kept. Then I was advised by a tech that there was an ''updated update'' of 1.22, so I then re-updated. Again, generally with my ''tinkered settings'' from 1.21, things seemed to be status-quo.

Thinking that 1.22 was a success, I decided to return the ''tinkered settings'' to what should be ''normal'' and optimal settings. Like many have noticed, not a good idea. I immediately re-imported my backed up 1.21 ''tinkered settings'' and to make this long story short -- 1.22 is a vapor update. Nothing better and nothing worse as far as I can see so far.

To use an analogy, if this was an automobile, yeah, sure it could drive, but it definitely would not pass state inspection.

Please guys in development, I know this is a down economy and perhaps your staff has been cut--and if this is the case, you have understanding and compassion--however, this might also be an opportunity for the ''proud few'' to shine and surprise us with a stellar firmware update that fixes everything and shows a ''can-do'' attitude.

A friendly nudge of encouragement.

[EddieZ]

http://www.sevensheaven.nl/images/producten/cartoon-spotprent_wc-eend-duck.jpg

They seem to be strict on cross linking. Therefore the solution:

[Toilet-Duck]

Ohh Love it lol!

Everyone look at my new avatar!