Print

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

[cc999]

   I have to say that the 1.30 firmware is excellent! My A3 has been running for 24 hrs now
perfectly. No reboots, No lag, streaming video is much improved. I do NOT use any b protocol
so no loss for me. I am so happy I snagged it while it was availiable. I will not look back!

   If anyone wants me to post a d/l link let me know.....

Charlie

[summerstormpictures]

I have also been using 1.30 without a hitch...knock on wood. What I'd like to get is the Shareport utility for Mac that was supposedly up for download and then wasn't.

[cc999]

Can someone post a link to that shareport utility? I will trade links.........

[davevt31]

Mac Sharepoint Link can be found here:

http://www.dlink.com/products/support.asp?pid=530&sec=1#firmware

[Justus]

I have also been using 1.30 without a hitch...knock on wood. What I'd like to get is the Shareport utility for Mac that was supposedly up for download and then wasn't.

A3 as well?

[summerstormpictures]

A3 as well?

A3 as well. Still running fine. I also am N-only.

What I'm having trouble figuring out is how the heck to install the Shareport 1.01 for Mac. I unzip the file after downloading and there's no package installer or any sort of instructions. The manual for separate download is Windows only. I'm a fairly advanced Mac user but have no clue.

[arod]

Open sharport folder and go to SHAREPORTutility > SHAREPORTutility  The pkg files should be listed there.

[summerstormpictures]

Open sharport folder and go to SHAREPORTutility > SHAREPORTutility  The pkg files should be listed there.

Which one should I run? Where's a ''read me'' file to at least give me some clue before just arbitrarily running something?

Who is running the shop at D-Link software development? It only takes a couple minutes to rustle up a simple text file--probably from a boilerplate template--add in one simple line: ''To install...''

In perusing the latest posts concerning this 1.30 (suddenly re-packaged as ''beta''), I can see I'm one of the ''lucky ones'' who has not had a complete fiasco with the 1.30 firmware update, however, I can understand completely the anger from D-Link DIR-655 owners who have had their routers turned into bricks. You'd think I'd be happy and/or thankful, but if anything, I'm frustrated beyond all belief. I feel like I dodged a bullet out of sheer blind luck.

I read the ''disclaimer'' about not installing if one wanted to back-install to an earlier firmware. I also read the part about wireless ''B'' no longer being supported. I was fine with all that. Nowhere did I read the words ''beta.'' That I am not fine with. If I had read this, I would have stopped cold and waited. I didn't--but I was lucky...very lucky

Honestly, you all really need to get your act together. There's a complete communication breakdown and a broken system of development--maybe more.

You all at D-Link have fumbled once too often in the last months and there's a point when even the most patient lose that virtue and then something you cannot control at all happens: word of mouth--and not good word of mouth either. I expect Tekzilla and/or GeekBrief and/or CNET's Buzz Report will soon be featuring D-Link in their commentary. I already found out that I was not the only one to email them over all this.

Suffice it to say, when my D-Link router expires at some point in the future, I can say with 100-percent certainty that I will buy anything other than D-Link, including the Brooklyn Bridge.

Lastly, I feel guilty in an earlier post I made where I compared the development team at D-Link to the Three Stooges. That was unfair. I'm sorry Moe, Larry and Curley.

Sorry to crescendo so harshly, but you guys are in desperate need of a wake-up call.

[avsfan77]

After looking in the Cosetup.app files, I saw that it is supposed to call SharePortUtility_10_2 or SharePortUtility_10_4.  So, I ran SharePortUtility_10_4 and the install worked.

That was the good news.

The bad news is that the SharePort utility doesn't actually work for me.  I had to disable my firewall (took a while to figure out that one) to see my printer in the SharePort app.  Apparently, the Mac firewall blocks SharePort, but there are no warning messages (like most apps display).

Once I could see the printer, I could connect to it.  For about two seconds.  It would automatically disconnect with no warning or error messages to be found.  If I tried to connect and immediately disconnect, I got a warning that I can't disconnect because the device was not actually connected.

The printer is a HP PSC 2410xi all-in-one, if that matters.

That's my experience...  I hope it works better for others.

[summerstormpictures]

After looking in the Cosetup.app files, I saw that it is supposed to call SharePortUtility_10_2 or SharePortUtility_10_4.  So, I ran SharePortUtility_10_4 and the install worked.

That was the good news.

The bad news is that the SharePort utility doesn't actually work for me.  I had to disable my firewall (took a while to figure out that one) to see my printer in the SharePort app.  Apparently, the Mac firewall blocks SharePort, but there are no warning messages (like most apps display).

Once I could see the printer, I could connect to it.  For about two seconds.  It would automatically disconnect with no warning or error messages to be found.  If I tried to connect and immediately disconnect, I got a warning that I can't disconnect because the device was not actually connected.

The printer is a HP PSC 2410xi all-in-one, if that matters.

That's my experience...  I hope it works better for others.

Basically took a chance and did the 10.4 install as well. Same basic problem you have. No warning messages even after I allowed the specific application unlimited access.

Again, with nothing to go on from the D-Link people, waste of time--as usual.

[tipstir]

Besides the word beta. Should I upgrade it to Beta from NA? Now since you can't revert back and stuck in one way trip?

[Lycan]

Which one should I run? Where's a ''read me'' file to at least give me some clue before just arbitrarily running something?

Who is running the shop at D-Link software development? It only takes a couple minutes to rustle up a simple text file--probably from a boilerplate template--add in one simple line: ''To install...''

In perusing the latest posts concerning this 1.30 (suddenly re-packaged as ''beta''), I can see I'm one of the ''lucky ones'' who has not had a complete fiasco with the 1.30 firmware update, however, I can understand completely the anger from D-Link DIR-655 owners who have had their routers turned into bricks. You'd think I'd be happy and/or thankful, but if anything, I'm frustrated beyond all belief. I feel like I dodged a bullet out of sheer blind luck.

I read the ''disclaimer'' about not installing if one wanted to back-install to an earlier firmware. I also read the part about wireless ''B'' no longer being supported. I was fine with all that. Nowhere did I read the words ''beta.'' That I am not fine with. If I had read this, I would have stopped cold and waited. I didn't--but I was lucky...very lucky

Honestly, you all really need to get your act together. There's a complete communication breakdown and a broken system of development--maybe more.

You all at D-Link have fumbled once too often in the last months and there's a point when even the most patient lose that virtue and then something you cannot control at all happens: word of mouth--and not good word of mouth either. I expect Tekzilla and/or GeekBrief and/or CNET's Buzz Report will soon be featuring D-Link in their commentary. I already found out that I was not the only one to email them over all this.

Suffice it to say, when my D-Link router expires at some point in the future, I can say with 100-percent certainty that I will buy anything other than D-Link, including the Brooklyn Bridge.

Lastly, I feel guilty in an earlier post I made where I compared the development team at D-Link to the Three Stooges. That was unfair. I'm sorry Moe, Larry and Curley.

Sorry to crescendo so harshly, but you guys are in desperate need of a wake-up call.

Lets try to regain focus.
1) it doesn't brick your router by any means.
2) There was a publishing mistake made with the firmware. We failed to make the notifications large enough to bring these changes to your attention. That being said a small failure has yeilded huge issues. We are working to correct it. To my knowledge there will be a code released that will re-add the B support for those customers that lost it and want it back.  I do not have an ETA, so please don't ask. As soon as I have it and it passes basic inspection I'll make it available.

We understand your frustrations and want to correct this over sight asap. Please be pateint while we do so.

[arod]

Besides the word beta. Should I upgrade it to Beta from NA? Now since you can't revert back and stuck in one way trip?

If you don't mind the fact that 802.11B is removed go for it.. The firmware works it just can't be downgraded and removes B. However we are pushing to put B back in 1.31 firmware.

[FrostyMelon]

Besides the word beta. Should I upgrade it to Beta from NA? Now since you can't revert back and stuck in one way trip?

It's the same firmware...

[EddieZ]

And it's a one way trip