D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: dns-323 on November 05, 2008, 12:27:37 PM
-
???
-
There isn't one - it hasn't been released yet.
-
Can't wait! My Xbox 360 is waiting impatiently to stream some movies & music. ;)
-
And my 1.5 tb HD's are sitting like lame ducks... :-[
-
Why not just release the latest 1.06 build labelled as a BETA?
-
Why not just release the latest 1.06 build labelled as a BETA?
We like to release firmware that doesn't have critical issues risking your data.
-
Please test this out :)... Is there any way that you can ask the new XBL update users/Microsoft to test it with firmware 1.6.
-
Please test this out :)... Is there any way that you can ask the new XBL update users/Microsoft to test it with firmware 1.6.
I'm one of those NXE Users. I'd be happy to try out the 1.6 for Dlink. :)
-
Can we get some sort of rough date for this firmware release??
DNS-323 Firmware 1.06 is nearing final stages of beta and no further additions of features will be added.
This statement was made over two weeks ago...
...and like others, I have two 1.5tb drives sitting here useless...
-
Feel your pain ... with all of the activity on the forums of late, I wouldn't be surprised to see them skip to 1.7 ;)
Either way, I suspect it's going to be at least a few more weeks while D-Link Engineering reviews the feedback from their BETA customers.
Cheers,
-
I wouldnt expect the firmware before x-mas, not to mention this rls looks like a b-fix rls (no majorly huge new features).
On another note, i have personally found that hounding the mods/devs NEVER makes a rls come earlier.
It comes when it comes
Take care.
-
I would happy that if 1.6 support USB hard disk!
-
Why is it that the DNS 343 has support for the features + the driver that we are about to get when 323 has been out longer.... I understand that the DNS 343 has 128 meg's while the DNS 323 has 64 meg's of storage memory that is the difference...
-
A question regarding 1.5TB support. What happens if 1.5TB drive(s) are installled in a DNS-323 with 1.05 firmware? Will they work at all? Seems that some people are using them. Will some advanced features not work? I just received my DNS-323 yesterday, and I an not sure whether I should order 1TB drives which are supported, try 1.5TB drives and see what happens, or wait until 1.06 is released. I've see some horror stories about the Seagate 1.5TB model, so I am leaning towards to 1TB Hitachi. Any advice or suggestions are appreciated. Thank you.
-
The 1.5TB drives will work as standard drives fine. RAID will not format on these drives with 1.05 fw.
-
The intention was not hound mods/devs but to get an estimated release date. If I am told to wait till christmas for the release, I have no problems logging into this forum on the announced day to look for firmware. I am sure the dev team would have setup somekind o***oal to release the fmware.
What I do not like is to get to this forum every morning to see if the firmware has been released today. Just, don't leave people hanging by leaving messages like.. release could be in weeks if not next week.
>:(
I wouldnt expect the firmware before x-mas, not to mention this rls looks like a b-fix rls (no majorly huge new features).
On another note, i have personally found that hounding the mods/devs NEVER makes a rls come earlier.
It comes when it comes
Take care.
-
There was another post on this forum which indicated the release would be this week or next. Seeing the performance issue with the Seagate 1.5 tb drive is being addressed with a firmware fix, I ordered two of the drives this afternoon. I am hoping the drives, the firmware update from D-Link and the firware fix from Seagate all arrive around the same time. I need something to do over the long Thanksgiving weekend.
-
Whats the firmware fix from Seagate that you mentioned? Is that fix for their 1 TB drives from the same family as the 1.5 TB?
I've never upgraded firmware to a harddrive. Didn't even know they did that.
Can you post a link to info and instructions?
Thanks
-
It's only for the 1.5TB firmware.
Here's the link to the "official" announcement on the Seagate forum.
http://forums.seagate.com/stx/board/message?board.id=ata_drives&view=by_date_ascending&message.id=3116#M3116
-
I can't get them do work wit 1.05 even. probably need to format them in a PC first?
-
I'm very disappointed so far with the extended wait for 1.06. A month ago the Beta was almost finished. Two weeks ago it was supposed to be released in a week. I'm really tired of the UPnP server bug on the 4 GB file size limitation. At this time, the unit is virtually worthless for the intent I bought it for.
Can D-Link not commit to a date for this firmware? This units have been selling for some time with these issues, some of them major. It would be nice to have them fixed so this unit can do everything that D-Link advertised it could.
-
i totally agree with divesheik
If i knew about this issue, i wouldnt of bought it yet. I paid 180 CAD for this and now its gone down to 139 CAD. dats kinda dumb.
-
It doesn't look like Dlink is in the business of making money and keeping their customers happy otherwise they would be keeping us uptodate with respect to the firmware update. I know Intel would never let things like this slip through their fingers so I my just have to spend the extra money to buy a better product and customer service.
A.
-
i dont know why people keep complaining about the firmware realease date. they've already said that it would be comming out soon, they didn't promise an official date. just let them finish the dang testing so that we don't get some firmware with a bunch of bugs in it. complaining isn't going to make it better or come out faster, testing these things take time so stop being so impatient.
besides their implementing new functionallity and asking us what we them to add to for functionallity, so don't be so hard on them. if you think you can do a better job and why not apply for a job a dlink and show them how its done.
-
Hi I'm a loyal D-Link Customer (I purchase all D-Link networking products for my home based business).
I Purchased the DNS-323 because it was cheap and said it supports the xbox360 "soon".
I just wanted to let D-Link know I'm awaiting the 1.06 firmware update just like many of other customers.
Thanks
-
i dont know why people keep complaining about the firmware realease date. they've already said that it would be comming out soon, they didn't promise an official date. just let them finish the dang testing so that we don't get some firmware with a bunch of bugs in it. complaining isn't going to make it better or come out faster, testing these things take time so stop being so impatient.
besides their implementing new functionallity and asking us what we them to add to for functionallity, so don't be so hard on them. if you think you can do a better job and why not apply for a job a dlink and show them how its done.
Because the 1.5TB fix is a walk in the park, no joke.. its about 5 to 10 lines of code to fix on the web interface which doesn't not require them to test it for weeks on end, unless of course Dlink has scaled it operations back to 1 developer and 2 testers for all their products in light of the recent market changes :)
A.
-
Because the 1.5TB fix is a walk in the park, no joke.. its about 5 to 10 lines of code to fix on the web interface which doesn't not require them to test it for weeks on end, unless of course Dlink has scaled it operations back to 1 developer and 2 testers for all their products in light of the recent market changes :)
A.
How about I give YOU a link to the 1.05 code and YOU add those 5 to 10 lines - isn't the the "raison d'etre" of opensource - giving YOU the code so YOU can make the changes that YOU need?
-
How about I give YOU a link to the 1.05 code and YOU add those 5 to 10 lines - isn't the the "raison d'etre" of opensource - giving YOU the code so YOU can make the changes that YOU need?
if he did and then we applied the "patch" wouldn't that void our warranty?
-
if he did and then we applied the "patch" wouldn't that void our warranty?
Let me answer your question with one of my own.
If I told you no - this would not void your warranty, and offered you a patched version of the firmware that would fix the problem - would you load it?
Would you load a piece of software or firmware - provided to you by a total stranger - because it supposedly resolves a problem you are having?
Do you have any idea what that piece of software will actually do?
-
Let me answer your question with one of my own.
If I told you no - this would not void your warranty, and offered you a patched version of the firmware that would fix the problem - would you load it?
Would you load a piece of software or firmware - provided to you by a total stranger - because it supposedly resolves a problem you are having?
Do you have any idea what that piece of software will actually do?
That really is the beauty of GPL/open source code, its open to examination by everyone in the community. I seriously doubt that many of the people using the Funplug "patches" know the developers. However, I believe one of the D-link mods have advised that using that code does in fact void the warranty.
-
That's an interesting response - given the original question - let me ask another one
does an opensource afficionado really care about the warranty or has he/she gone past that and wants to hack the device, to fix a perceived problem, to add new functionality
and another one
What percentage of the open source community would you guess, have the skill to actually examine the code?
and yet one more - this time getting to the crux of the matter and the reason for my comment.
do you feel an opensource developer would be so naive as to think 5~10 lines of code inserted into the "web interface" would fix the problem and not require testing?
Watching someone else run a few commands through a CLI to fix a problem is a far cry from developing a script that automates the process - one that can provide the logic required to analyze the problem and then issue the few commands required to fix it - we're discussing scripts that partition and format disks, do you really want to change those scripts and not test them thoroughly?
-
Bought myself a Dell Vostro for 160 EUR (new), ripped out the 80GB disk
swapped in two Seagates, Ubunto 8.04 - and voila a nice storage area with
1gb mem + 2ghz 64 bit dualcore.
I even got a Vista basic licence to use on some of the childrens computers :-)
-
That's an interesting response - given the original question - let me ask another one
does an opensource afficionado really care about the warranty or has he/she gone past that and wants to hack the device, to fix a perceived problem, to add new functionality
good point!
and another one
What percentage of the open source community would you guess, have the skill to actually examine the code?
relevance? it only takes one
and yet one more - this time getting to the crux of the matter and the reason for my comment.
do you feel an opensource developer would be so naive as to think 5~10 lines of code inserted into the "web interface" would fix the problem and not require testing?
Watching someone else run a few commands through a CLI to fix a problem is a far cry from developing a script that automates the process - one that can provide the logic required to analyze the problem and then issue the few commands required to fix it - we're discussing scripts that partition and format disks, do you really want to change those scripts and not test them thoroughly?
again relevance? i would be happy to beta test...most companies at least give the option of using the beta product with full disclosure/release of liability
-
Read leathal's other posts and hopefully the relevance should become obvious
-
I just wanted to say that I am excitied about the new firmware. I am currently using a Windows Home Server to handle a lot of my network storage needs which I think is overkill.
My only concern though is that there is a way to perform off-unit backups via the USB port to an external hard drive. I am sure that the topic of USB port use has been beat to death so I am not going to go into it.
Again thanks for the fine product and so far good support.
-
In reply to lethals post. there is alot more to fw 1.06 then just supporting 1.5TB hard drives. if your unhappy that your drives are supported then maybe next time you should look at the list of supported drives of check the forum to see if anyone else is using the drive.
-
In reply to lethals post. there is alot more to fw 1.06 then just supporting 1.5TB hard drives. if your unhappy that your drives are supported then maybe next time you should look at the list of supported drives of check the forum to see if anyone else is using the drive.
not that I agree with leathal's posts but d-link's website does say under "Supported Hard Drive Type" in the specs page:
• SATA –Any Capacity
• 3.5” Internal
http://www.dlink.ca/products/resource.asp?pid=509&rid=1951&sec=0
with no disclaimer, qualifier or footnote.
The responsibility is clearly with D-Link to uphold or revise that statement, not for the consumer to disprove it.
-
That statement was made over two years ago - before there were 750GB drives - and when I bought my DNS-323, the firmware available at that time did not support 750 GB drives, the current firmware does.
My point here is that development is ongoing - both in drive capacity and in the firmware's ability to support them - a little patience is all that is required.
And one more thing - D-Link does make beta product available to users for testing - I have no idea what the basis is for selection of beta testers, but I know that they do it.
-
not being a ****** might be a pre-req for that.
-
That statement was made over two years ago - before there were 750GB drives - and when I bought my DNS-323, the firmware available at that time did not support 750 GB drives, the current firmware does.
My point here is that development is ongoing - both in drive capacity and in the firmware's ability to support them - a little patience is all that is required.
And one more thing - D-Link does make beta product available to users for testing - I have no idea what the basis is for selection of beta testers, but I know that they do it.
I understand why they are not able to support hardware that doesn't exist when the firmware was originally released, but any reasonable person would have to agree that claiming to support "any capacity" without a qualifying footnote is misleading.
Don't get me wrong, I use/sell a lot of D-Link products but when a mod/engineer says the firmware will be out soon on Nov 10th:
I am very sorry but we do not have a mailing list for firmware releases. Please just keep posted on the forums or check the support site frequently. It should be here soon.
then next week on Nov 14th:
I would go with weeks if not next week
then next week on the 25th:
I would not expect it until probably next week if all testing has been finalized since this is such a short week for most people.
you kind of have to wonder how many revisions of the eta before there is a revision of the firmware.
-
Somehow your earlier posts gave me the impression that you had some familiarity with opensource and the whole process of software development - this last post makes me wonder.
There are two approaches to software patches (be it OS or application) - the fast & nasty and the slow & thorough - the first is the approach often adopted by neophytes, we have a problem, so we throw a few lines of code at it, give it a quick test and push it out the door - quite often those few lines of code fixed the first problem and introduced half a dozen others. The second is the reverse, we spend a little more time looking at how the few lines of code will impact the whole and then test a little more thoroughly.
The first approach is what leads to the wild accusations of insecurity that we have seen - a planned feature (http access to files) was pulled and someone simply removed the web page links that led to it, but left the code that allowed access.
The second approach is what leads to threads like this.
If you were the manufacturer, which road would you choose - the one that jepoardized the users data for a quick fix or the one that allowed you a better shot at releasing a quality product?
What would you as a user choose - a manufacturer who made firmware updates on a weekly basis (which by the way suggests either a seriously flawed code base - or - a product that was rushed to market before it was ready) and whose product you can't trust with your data, or one who took a little longer and a little more care?
-
not suggesting `the fast & nasty`just suggesting more accurate eta or better communication. If there is a problem be honest.
-
I used feed43.com (http://feed43.com) to make an RSS feed for DNS-323 firmware updates (http://feed43.com/3074286271661073.xml).
It scrapes the firmware page using &origin=1 (USA). It should update when then 1.06 firmware is posted to that page if they don't change the page format too much.
Yo, D-LINK forum moderator. If its within your power, please tell the D-LINK website people that ATOM or RSS feeds for pages that update (like firmware on product support pages) is very nice. Even better would be a 1.07 feature for an option for the DNS-323 to ping home every week and see if its firmware is out of date and email me to update it.
-
Yo, D-LINK forum moderator. If its within your power, please tell the D-LINK website people that ATOM or RSS feeds for pages that update (like firmware on product support pages) is very nice. Even better would be a 1.07 feature for an option for the DNS-323 to ping home every week and see if its firmware is out of date and email me to update it.
Just a passing comment - several of the Netgear products do this - and over on the Netgear forums, there is a thread, right now, with people upset that their <whatever device> "phones home" without their knowledge.
-
Just a passing comment - several of the Netgear products do this - and over on the Netgear forums, there is a thread, right now, with people upset that their <whatever device> "phones home" without their knowledge.
Yeah. It needs to be optional and off by default.
-
I used feed43.com (http://feed43.com) to make an RSS feed for DNS-323 firmware updates (http://feed43.com/3074286271661073.xml).
It scrapes the firmware page using &origin=1 (USA). It should update when then 1.06 firmware is posted to that page if they don't change the page format too much.
Yo, D-LINK forum moderator. If its within your power, please tell the D-LINK website people that ATOM or RSS feeds for pages that update (like firmware on product support pages) is very nice. Even better would be a 1.07 feature for an option for the DNS-323 to ping home every week and see if its firmware is out of date and email me to update it.
Thanks for the feed. Adding it to google reader :)
-
Thanks for the feed. Adding it to google reader :)
Same here...added it to my outlook. Thanks!
-
not suggesting `the fast & nasty`just suggesting more accurate eta or better communication. If there is a problem be honest.
It's not that there is a lack of communication, the communication is here. The problem is we are trying to make a stable release so that we can start implementing new feature sets into our products without having to worry about critical bug fixes along the way. Each time that statement was made we were qualifying a new build and it was in the hopes that the new build would pass QA however we have found some bugs which we are resolving before going public with the firmware. We would love to give you a date set in stone but it doesn't work that way.
-
I would classify myself as someone who doesn't have much patience when waiting for the long awaited Xbox 360 support for the 323, but I would much rather have a solid build come out rather than something that doesn't work or creates other problems.
Take your time...but not too long....
-
The problem is we are trying to make a stable release so that we can start implementing new feature sets into our products without having to worry about critical bug fixes along the way. Each time that statement was made we were qualifying a new build and it was in the hopes that the new build would pass QA however we have found some bugs which we are resolving before going public with the firmware. We would love to give you a date set in stone but it doesn't work that way.
this is the kind of info i was looking for...not looking for a date set in stone, just an update regarding delays.
thanks
-
It's not that there is a lack of communication, the communication is here. The problem is we are trying to make a stable release so that we can start implementing new feature sets into our products without having to worry about critical bug fixes along the way. Each time that statement was made we were qualifying a new build and it was in the hopes that the new build would pass QA however we have found some bugs which we are resolving before going public with the firmware. We would love to give you a date set in stone but it doesn't work that way.
Thank you for all the QA. :) I'd rather wait a year than install something with a known bug that could corrupt data or axe a partition/RAID. When you're dealing with routers and the like I don't mind beta stuff. Hardware is replaceable. Data is not. Something that is directly interacting with my information should be as perfect as it can be.
-
I would classify myself as someone who doesn't have much patience when waiting for the long awaited Xbox 360 support for the 323, but I would much rather have a solid build come out rather than something that doesn't work or creates other problems.
Take your time...but not too long....
Install Twonky, its free for 30 days, but if you "happen" to reboot you NAS, the 30 day period resets itself. I'm not suggesting you use it illegally, but you can certainly evaluate it until the new firmware is released :0)
Twonky will allow you to stream your music and videos to the 360.
Here is a full guide on how to install it:-
http://wiki.dns323.info/howto:twonkyupnpserver
-
I am glad that D-Link is fixing the bugs. Hopefully with DNS 343 and 323 next time the release dates won't be that long apart when it comes to releasing and updated firmware and they are released at the same time not within 2 - 4 months apart since they are both NAS devices and 323 was out before 343.
-
With over 4000 views on this topic I would think the message is clear. I am tired of waiting and i'll never buy dlink again because of this, and never will recommend.
on the DNS 323 page you advertise "SATA Drive Support" and make no mention of no support for 1.5tb.
this post will probably be deleted because its what you don't want to hear, but its the truth.
It's been said this firmware is within a week away, but that was month ago. i'm tired of this bs.
-
Holy.... why don't people stop being such big babies and treaten dlink and theyre not going to buy their products. obviously you dont value a quality product, because you just want it and you want it now. have you ever thought that maybe 1.5 TB drive didn't exist until recently so maybe dlink couldn't have possibly tested them when the DNS323 was released.
development takes time. especially good development, and from what i can see thats what dlink has in mind. theyre not just making a quick fix, they are testing everything inside and out, and theyre not just fixing stuff but theyre also adding funcitonnality.
so if all of you babies that cant stop wining need a place to cry. do it in you pillow at night not on the this forum. im tiered you people complain, how about trying to add constuctive critisim or comments.
-
Wow!
Whilst I agree with your sentiments - a rant isn't exactly the best way to get the message across - but - you go man!!
-
yeah there is some ranting, maybe if someone explained how this is a difficult thing to implement? any other product that takes sata (motherboards, other nas products, anything that supports sata etc...) can take a 1.5tb without problem, yet this cant. that is my question.
-
this isn't the first time that there have been limits with harddrive. throughout history as drive reach new limits BIOS's or opperating systems had to catch up to be able to deal with them. i believe there use to be a 32GB or 64GB (can't exactly remember) max partition size in Win95or 98. if your drive was bigger, then you had to have multiple partitions to deal with this.
this is the same type of senario pretty much. the DNS323 is based on an older linux kernel. from what i understand its a few years old. i'm going to assume that this kernel doesn't have support for this size drive. and since you cant exactly partition drive or control partitions with the DNS323 that this doesn't work. the problem isn't the hardware its the software, which is why they are able to fix it with the new firmware once it is released.
For an interesting read of the issues with hard drive size limitation as technology advances check this out http://www.dewassoc.com/kbase/hard_drives/hard_drive_size_barriers.htm (http://www.dewassoc.com/kbase/hard_drives/hard_drive_size_barriers.htm)
-
1.5TB drives work as single drives, but not RAID, so I don't think it's the
Linux kernel.
EDIT - Someone in the DNS-321 group http://forums.dlink.com/index.php?topic=2543.msg13856#msg13856
managed to get their 1.5TB drives formatted at RAID using a 'Javascript' hack.
-
Btw. sorry about the little rant i just couldn't help it. It seems like more and more people keep posting complaints, like i'm not going to buy this, or if i was your boss i'd fire you and silly things like that. I just couldn't handle it anymore... someone had to tell them eventually. The only things that are worth anything are the things that are worth taking the time to do properly. Quality = time so just have a little patience, the firmware will come out when Dlink deems it as Stable. i'm also eagerly awaiting it, but i don't go around complaning about it, i'm happy that they continue to support it, fix it and add to it. Man, they even ask us what we want them to add to it. thats pretty awesome in my oppinion, you don't see all manufacturers doing that.
keep up the good work dlink
-
keep in mind that not all raid is hardware raid, there is also software based raid, which i assume is used in this case. i'm no linux expert, so maybe it isn't in the kernel, but i'm pretty sure that its software based, otherwise they wouldn't be able to fix it.
-
The RAID on the DNS-323 is software RAID.
-
So back to the original topic, the 1.06 release is still not available.
The advertised features that I purchased the product for does not work (iTunes and UPNP).
It's time D-Link either offer a free upgrade to a box that did work, offered to buy back the product at the original purchase price, or fix the problems (I'm personally hoping that they fix the problem).
Fixing the problem would be a nice Christmas present from D-Link to its loyal customers. Lets hope D-Link gets into the giving spirit in time for Christmas (I'm not willing to wait much longer).
-
I also hope improved firmware is released soon. But be careful what you ask for!
Dlink! Please don't release the firmware until it is READY. My NAS is just about the WORST electronic product in my house to have a bug. I don't want any unstable, buggy, or otherwise messed up firmware that could endanger my data.
So please make 1.06 rock solid!
-
Isn't 1.06 released already? I have both the dns-321 and dns-323. I just installed 2 1.5T seagate drives on my dns-321 and they are recognized. Before I upgraded the firmware their capacity was 0 so I couldn't do anything with them. I just happened to look on their download list and 1.06 is out, correct me if I am wrong.
Also, what's the difference between manual and auto rebuild? I'm being asked that. What should I select?
Thanks,
Gary
-
The download list on this page: http://support.dlink.com/products/view.asp?productid=DNS%2D323 (http://support.dlink.com/products/view.asp?productid=DNS%2D323) still only has 1.05?
Steve
-
I definately saw it on a different site (I searched for 5-10 mins after I saw your post but I can't find it). The filename was 1.06beta or something like that. I'll check again..
-
I definately saw it on a different site (I searched for 5-10 mins after I saw your post but I can't find it). The filename was 1.06beta or something like that. I'll check again..
If the word beta was a part of the file name wouldn't that tell you something? Perhaps that it's not a final release and so it's "released already"?
Now - this is just my opinion - but I've never seen D-Link release a firmware with the word beta in the name (even a beta release) so I'm guessing the website you saw it on was not a D-Link site.
-
I have actually seen beta firmware on some of the other dlink sites, not US though, i believe its was the german site, and possibly others, but definetly not on the US or Canadian site (which i think are the same anyway)
-
I have actually seen beta firmware on some of the other dlink sites, not US though, i believe its was the german site, and possibly others, but definetly not on the US or Canadian site (which i think are the same anyway)
Did it include the word beta in the file name? I'm not disputing that D-Link makes beta software available - just commenting that I've never seen them use the word beta in the file name.
-
Did it include the word beta in the file name? I'm not disputing that D-Link makes beta software available - just commenting that I've never seen them use the word beta in the file name.
the one I saw was titled Version 1.06b60 beta but the filename was DNS232.1.06b60.exe so whoever put it out there(obviously not d-link) has packaged/named it however they like.
Apparently that is at least 2 builds behind what they are currenty working on.
-
good point the ones that ive seen have always shown the build and not said beta, in the filename
-
Did it include the word beta in the file name? I'm not disputing that D-Link makes beta software available - just commenting that I've never seen them use the word beta in the file name.
Hi fordem
I know a lot of your postings in different boards. Most of them are really good an excelent, but also some, sorry, but are wrong. Like this one.
D-Link released since years a lot of firmwares and drivers on their public servers labled with "beta" in their filenames.
Like those as an example:
ftp://ftp.dlink.com/Gateway/dir655/Firmware/dir655_CA_firmware_121B09_BETA.zip
ftp://ftp.dlink.com/Gateway/dir655/Firmware/dir655_firmware_121b05_beta_nosecurespot.zip
ftp://ftp.dlink.com/Gateway/dir855/Firmware/dir855_Firmware_112B01_BETA.zip
ftp://ftp.dlink.com/Wireless/dwlg810/Firmware/dwlg810_BETAfirmware_213.bin
...
And there are hundreds more beta versions on the D-Link custumers public servers.
Search here ftp://ftp.dlink.com/ and you will find a lot of Beta named versions. Only in USA. Worldwide you will find thousands files on all D-Link servers labled beta in the filenames!
I use the DNS-323 firmware version 1.06b65 since 4 days and this one is working perfect without a special email alert mail account setting problem. I can´t and i will not test everything, because this is the job from D-Link employers and not my. ;)
-
Thanks for bringing that to my attention Tilly - all I said was I'd never seen it before.
-
Thanks for bringing that to my attention Tilly - all I said was I'd never seen it before.
Now this is really a storm in a tea cup, because it no way changes the point I was making, quite simply that the fact that a firmware with the word beta in the name is available should not be considered to mean that the firmware has been released.
A beta version is exactly that - a beta (or test version) and not a final release.
-
Thanks for bringing that to my attention Tilly - all I said was I'd never seen it before.
No problem fordem - but please open your´e eyes before you write things you did before!
-
Now this is really a storm in a tea cup, because it no way changes the point I was making, quite simply that the fact that a firmware with the word beta in the name is available should not be considered to mean that the firmware has been released.
A beta version is exactly that - a beta (or test version) and not a final release.
Hi Fordem
When there is a new D-Link firmware offen D-Link named this in the file with "beta". But when D-Link is released this same version D-Link is cut off "beta" from the filename.
You get it now?
-
throughout history as drive reach new limits BIOS's or opperating systems had to catch up to be able to deal with them. i believe there use to be a 32GB or 64GB (can't exactly remember) max partition size in Win95or 98. if your drive was bigger, then you had to have multiple partitions to deal with this.
True. But but the DNS-323 uses SATA drives which should at least be addressed in 48bit LBA. In theory, the device should be able to access drives up to 128 Petabytes in size.
Being that EXT2 file system is limited to a 32 Terabyte volume size, the limitation here is software and not LBA addressing.
So the real million dollar question is this. Why does the DNS-323 have such trouble mounting large SATA drives? Is it a bug in the firmware, or a hardware limitation of the chipset it uses?
-
are you saying that 1.5TB won't work with the DNS 323 fw?
i'm not able to see the size of the 2 1.5TB disks when i'm trying to set the DNS to RAID 1 (the value in the table is "0" for each hard disk) :-( (after pressing on the "set RAID Type and re-format" button .
please advice?
will 1.06 solve this issue?????? when is it coming out?
does it mean that i cant use DNS-323 with my 2 1.5B hard disks? i dont want to serial them and then to RAID 1 them (thats mean i'll need to format it again....
Heeeelp help
Guy
-
does it mean that i cant use DNS-323 with my 2 1.5B hard disks? i dont want to serial them and then to RAID 1 them (thats mean i'll need to format it again....
Heeeelp help
Guy
just do as i have done, install and use only one drive to begin with(because when you are done setting up the RAID you will still only have 1.5tb)
when you install the second drive only it will be formatted and the RAID will be configured
-
are you saying that 1.5TB won't work with the DNS 323 fw?
i'm not able to see the size of the 2 1.5TB disks when i'm trying to set the DNS to RAID 1 (the value in the table is "0" for each hard disk) :-( (after pressing on the "set RAID Type and re-format" button .
please advice?
will 1.06 solve this issue?????? when is it coming out?
does it mean that i cant use DNS-323 with my 2 1.5B hard disks? i dont want to serial them and then to RAID 1 them (thats mean i'll need to format it again....
Heeeelp help
Guy
Guy,
I have a DNS-323 and DNS-321. Last night I tried installing two seagate 1.5T drives in my dns-321. The 321 reported the drives as having a size of "0" for both in a raid 1 configuration. I upgraded my firmware to 1.01 and now I'm running dual seagate 1.5T on my dns-321. So you (and I) have to wait for the firmware update for the dns-323 to get the 1.5T drives working in RAID 1. It's working great on the dns-321 (knock on wood).
Gary
-
If the word beta was a part of the file name wouldn't that tell you something? Perhaps that it's not a final release and so it's "released already"?
Now - this is just my opinion - but I've never seen D-Link release a firmware with the word beta in the name (even a beta release) so I'm guessing the website you saw it on was not a D-Link site.
Yeah, it tells me 1.6 Beta was released. I know you're not trying to be smart, but it came off that way. Yes, 1.6 is out there, but it's beta. I never said it wasn't :).
-
Hi Fordem
When there is a new D-Link firmware offen D-Link named this in the file with "beta". But when D-Link is released this same version D-Link is cut off "beta" from the filename.
You get it now?
Tilly
Let's just say that not all D-Link beta code includes the word beta in the file name and leave it at that.
-
Yeah, it tells me 1.6 Beta was released. I know you're not trying to be smart, but it came off that way. Yes, 1.6 is out there, but it's beta. I never said it wasn't :).
Gary - to me if it's out in beta - it's not yet released, it's still being tested - when testing is complete, only then will it be released - it's that simple.
There are several 1.06 builds available to beta testers, some of which have been leaked, at some point one of these builds (or maybe one not yet completed) will be considered final and released, but until the time that happens 1.06 should not be considered "released".
-
Tilly
Let's just say that not all D-Link beta code includes the word beta in the file name and leave it at that.
Fordem
In the other way also D-Link released to their customers until today a lot of firmwares in whose filenames no "beta" contained. So these firmwares should not be beta versions. But because too many previous D-Link firmwares are filled with o lot of bugs that they are never be tested professionally. Those are still beta versions.
-
Gary - to me if it's out in beta - it's not yet released, it's still being tested - when testing is complete, only then will it be released - it's that simple.
There are several 1.06 builds available to beta testers, some of which have been leaked, at some point one of these builds (or maybe one not yet completed) will be considered final and released, but until the time that happens 1.06 should not be considered "released".
Fordem
When it´s so simple for you, than my questions:
For Netherland D-Link released until tody for their Netherland customer the old buggy version 1.02b114.
Latest upgrades: 1.02b114
http://www.dlink.nl/?go=gNTyP9CnptFMIC4AStFCF834mptYIe5XTNvhLPG3yV3oV412galtbNlwaaRp7ytsRWm5kC9PiO52eLCGv9yUQC5gx5/IbIC0H9q/8zMK
In UK D-Link released until today for their UK customer the version 1.05.
Latest upgrades: 1.05
http://www.dlink.co.uk/?go=jN7uAYLx/oIJaWVdDbgYU93ygJVYLelXSNvhLPG3yV3oV415g6ltbNlwaaRp7jksEz2onGQTo48EE5+3n/K9K0MQs/yZPsXnQNexqmNU0dsPTbhHNpfFqQfX/iaAfZWqa6gw7k4pr54S7CoTft2giSykx3YFsmbbcGUQCHErnwHl11qiNI5DcdhLLv4n1cvw
Is than (for you) the version 1.05 from UK for the Netherland DNS-323 owner a beta version because D-Link doesn´t released yet the version 1.05 in Netherland?
What is the different between a Dutch and a UK DNS-323 owner without their country languages?
-
There appears to be a beta of 1.06 here: http://www.station-drivers.com/page/dlink.htm (http://www.station-drivers.com/page/dlink.htm).
I've installed it and everything is fine.
Steve
-
Fordem
When it´s so simple for you, than my questions:
Tilly
Perhaps we need to define what beta software is ...
Here's (http://en.wikipedia.org/wiki/Beta_version#Beta) what Wikipedia has to say.
The difference between beta code and final code is that the manufacturer of the particular code states that one is beta and the other is not, and a particular piece of code can be deemed beta on a particular day, and then deemed a final release on a later day with absolutely no changes to the code itself.
In a nutshell, D-Link is going to be the one who decides if a particular piece of code is a beta test version and at some point when a particular piece of code passes it's quality assurance testing, it will be released as a final version.
To answer your question - if D-Link in the Netherlands chooses not to release one or more versions on the firmware for whatever reason and those versions have been released for use in other countries, it does not make those final versions, beta versions for the Netherlands - however, if D-Link in the Netherlands chooses to call one of them a beta and release it for testing, at that point it will become a beta version for the Netherlands.
Is this likely to happen? I doubt it, but, that's just my guess.
Unless I am mistaken D-Link in the Netherlands would probably consider anything later than what has been released on their support site as an unsupported versions, as I believe you already know.
-
Fordem
In the other way also D-Link released to their customers until today a lot of firmwares in whose filenames no "beta" contained. So these firmwares should not be beta versions. But because too many previous D-Link firmwares are filled with o lot of bugs that they are never be tested professionally. Those are still beta versions.
See my previous reply for a definition of beta - you're free to call it what you want - but strictly speaking only D-Link can define whether a particular piece of code is beta - bugs or no bugs, it is the manufacturer's decision to release it.
By the way - consider this my final answer.
-
There appears to be a beta of 1.06 here: http://www.station-drivers.com/page/dlink.htm (http://www.station-drivers.com/page/dlink.htm).
I've installed it and everything is fine.
Steve
Even if there it´s not the version 1.06b56, so I am pleased for you as for many others as well.
-
See my previous reply for a definition of beta - you're free to call it what you want - but strictly speaking only D-Link can define whether a particular piece of code is beta - bugs or no bugs, it is the manufacturer's decision to release it.
I guess now you don´t want to understand the point. Maybe there is a reason for this?
Yes, "only D-Link". When, like only D-Link Australia released a firmware then everybody worldwide can use this version. And it doesn´t matter if this version called or called not beta, is beta or is not beta!
D-Link firmwares are not made in single D-Link countries. They are produced by D-Link central. Most of them by D-Link in Taiwan or by the equipment manufacturers like Alpha Networks for the D-Link DNS devices. If every D-Link country is doing their own quality testing, then there are, there must be significant differences in the quality of testing.
By the way - consider this my final answer.
I understand this now very well. Merry Christmas. ;)
-
Tilly. Fordem is correct.
It does seem odd that their software status is not globally unified, but I’m sure it has 100% to do with internal technical support for their customers. I’m guessing D-Link USA doesn’t have their customer support staff trained for 1.06 yet. For all we know, their shelving certification for economic and not technical reasons.
The bottom line is this. Run beta software all you want, but at your own peril. If you want to retain warranty and technical support with D-Link, stay with official released software only. It’s all about understanding the rules of what is and is not covered between you and the company you wish to do business with. Like it or not. :-\
-
Merry Christmas. ;)
Merry Christmas
-
Today!!
-
Awesome! Thanks
http://www.dlink.com/products/support.asp?pid=509
It's live!
-
EDIT Moved to new topic. Where are the UPS settings in the new firmware v1.06 GUI?
-
Props to D-Link for updating this great product.
I look forward to D-Link's continued support, thanks!
(1.06 flashed and working great so far!)
TK
-
For all you early adopters, can I assume an uneventful upgrade from 1.05? Hard drive reformat not needed? :)
BTW, I have hardware revision A1, single drive in the right bay, standard mode. All important data is of course already backed up...somewhere...