Print

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

[DLP]

MTV generation. Haha.

I'm a software developer / consultant. I don't even want to think about the talk I'd have had with my employer or client if I'd dropped the ball like this. It wasn't beta when I installed it, it was a production firmware.

If someone wasn't reamed for breaking a flagship product, then they should have been. I know I'd have been hacking code all day and night to fix the error if I'd done this.

All this talk of inspiring D-Link to do better and not making a fuss is insane.

[Kneo]

Any updates when we can expect the F/W? Will it be today?

[iconeater]

MTV generation. Haha.

I'm a software developer / consultant. I don't even want to think about the talk I'd have had with my employer or client if I'd dropped the ball like this. It wasn't beta when I installed it, it was a production firmware.

If someone wasn't reamed for breaking a flagship product, then they should have been. I know I'd have been hacking code all day and night to fix the error if I'd done this.

All this talk of inspiring D-Link to do better and not making a fuss is insane.

Here here! Right on Brother!

[DLP]

 

Digging the Raoul Duke picture, BTW. I'm feeling some F & L in this thread, for sure!

[iconeater]

Boing Boing Gadgets Posted our Story!!!


http://gadgets.boingboing.net/2009/06/12/hey-d-link-youve-got.html

Special Thanks To Cindy Brady who Inspired me to be a Tattletale.

HEEEE YAAAAAAA!

[DLP]

Did we ever get so much as an apology for this fiasco?

I think the guys over at hardforum.com might be interested too. Think I'll pay them a little visit.

Edit: Done.

Also submitted a story to Slashdot.

[iconeater]

Did we ever get so much as an apology for this fiasco?

I think the guys over at hardforum.com might be interested too. Think I'll pay them a little visit.

Edit: Done.

Also submitted a story to Slashdot.

good call forgot about those guys.

[arod]

For those looking for a beta firmware I have it. Going to test before I post here as Beta.

[Kneo]

For those looking for a beta firmware I have it. Going to test before I post here as Beta.

Thank you for letting us know. I will be looking forward to trying it out when I get home.

[DLP]

For those looking for a beta firmware I have it. Going to test before I post here as Beta.

Do you happen to have a changelog? Any sort of description of the cause/resolution?

Thanks.

[Xender]

OK, I admit my use of the word 'inspire' was wrong and really does not represent my true feelings.  I do not go to forums to 'inspire' companies to fix my product and agree we should not need to 'inspire' them to do whats right.  I use forums to find answers to problems and questions.  I find it useful to find out if others are having the same problems I'm having or if my deserves a RMA.  I also find them useful to find out if investing in a piece of hardware is going to function as described.  Admittedly if I was looking at purchasing this router now knowing it was shipping with the 1.15 or 1.20 firmware I would definitely hold off.  

As a IT Manager I am lucky enough to be able to purchase and work with a wide variety of equipment.  Its a freedom that I truly enjoy but it can also be very frustrating.  My experience has been that least 40% of everything I buy will probably have a problem.  This includes modems, routers, managed switches, firewalls, PC, and laptops.  Its to the point where if something works right out of the box as expected or advertised I'm surprised.   As a hobby I like to build my own gaming PCs for fun, certainly not because its cheaper.  Motherboard firmware has always been an issue and a struggle.  One of the things I've learned is that I never install beta firmware and adopt a wait and see attitude toward a production release.  I broke my own rule when I upgraded from 1.02 to 1.15 because I got all happy about using Shareport and will admit that I had a high level of trust for D-Link.  I have kicked myself many times for that but consider myself lucky I didn't go to 1.20.  The problems I'm having are nothing compared to the problems you guys are having.

The above does not make me any better, smarter than anyone else in this forum, truth be told you have no reason to believe anything I've written.  In fact I'm thankful and impressed by some of the helpful, informational posts here because that is what is needed to assist developers in resolving the problems.  While it is beneficial to complain/report an issue with hardware, I am of the opinion that it is counterproductive to consistently complain about the same thing using different wording.  My worry is that Ru-Fi-Oh's frustration will cause a breakdown in communication which is why I made the comment about 'trashing'.

I am also aware that my opinion smells no better than anyone else.

I hope this next firmware release will make everyone happy.  If it turns out to be no better than the current 1.20 I would like to see them release 2 firmware updates that will allow us to either take the firmware back to 1.02 (my preference) or 1.15 if desired.  I see no reason why that could not happen.  I feel for the users that are using 1.20 as the router appears to be pretty much useless at this point.  If D-link can't fix it in a timely manner at least take take us back to a usable product.

Thanks for listening,
Xender

[iconeater]

Do you happen to have a changelog? Any sort of description of the cause/resolution?

Thanks.

I also, would like to say thank you and request a change log.

[Fearreality]

People expect a lot for their cash nowadays.  Welcome to the instant on, MTV, I want it now generation.  They want it fast and accurate, without conceding both ideals may directly impact each other.  Loading a beta firmware? Caveat emptor.

We never said anything about wanting it fast. We are talking about products that were already on the shelves (with broken firmware). We def want it to be accurate and if it is not, then the company that made it should make it so. However i do agree that loading Beta is at our own risk.

How does this sound. I was in the market for a shovel to dig a hole, so I went to the shovel shop and browsed the different brands. I assumed they all could dig a hole so I looked at the features. Some came with nice cushy handles while some had large foot stomps. I picked one up that looked nice and sturdy and fit me well. I took it home and got about 10 percent into the hole when all of a sudden I went to pick up a load of dirt to throw and the head was gone. I reach down to pick up the head and took both pieces to the store I bought it. I show the gentleman behind the couter and he looks at me and says, "you piled too much dirt on it". Dumbfounded I look at him and ask for the specs and he proceeds to tell me he doesn't know exactly how much it is meant to hold but he can assure me I used it wrong. He says normally he can’t refund the money but the company has an upgraded shovel head so that this won't happen again. I will be able to continue to dig my hole but I can only use it to 50 percent of its potential and i will have to wait a year for development.

Now on a maybe more helpful note. There have been talks on the www that the latest uPnP build for linux has some bugs in it. Maybe the developers can look into the version they are using and see if that might be a cause. Also I have read that Windows XP causes a lot of issues with a couple of the newer uPnP builds. There is a MickySoft article for turning off the uPnP feature in XP http://support.microsoft.com/kb/821980/en-us . It seems Windows 7 and Vista cause little to no effect on uPnP. I am going to disable uPnP on all of my Windows XP machines and see if this helps our router slow downs and/or uPnP fails.

I would like to say this in all honesty. The D-link routers are attractive because the developers are trying to add things that the other companies do not have. I know that is the reason I have stayed with them this long. My point is we like what the developers are trying to do for us the consumers and the fact they have some board administrators that are on top of our issues makes it bearable for us.  So thank you to everyone involved and thank you to us for testing.

Now everyone get back to work.

[jscoleman]

Ive been having serious issues with this router since I bought it.  I have 1.20 and all of the issues posted before me.  I read the other day there would be a beta posted a day or 2 ago, I haven't seen that yet and still dont see one.  I plan on returning my 4500 tomorrow if I cant get it working right, this router is a premium product and its being handled like a second grade nothing.  I prefer to keep it but I'm done waiting for fixes which should inherently work on all routers these days.

[Routers]

Any ETA on when the beta will be posted so we can download?