Comments on: Resurrecting DWL-2100AP http://www.digdice.com/2007/05/29/resurrecting-dwl-2100ap/ diy wifi antennas and designs, wireless tutorials and other things ... Sat, 05 Jul 2008 10:43:47 +0000 http://wordpress.org/?v=2.5.1 By: Borlam http://www.digdice.com/2007/05/29/resurrecting-dwl-2100ap/#comment-2325 Borlam Wed, 16 Apr 2008 16:38:41 +0000 http://www.digdice.com/?p=23#comment-2325 After Attaching to TFFS... done. don't load the vxWorks image from "/tffs0", and I don't know where is the problem After Attaching to TFFS… done.
don’t load the vxWorks image from “/tffs0″, and I don’t know where is the problem

]]> By: estqwerty http://www.digdice.com/2007/05/29/resurrecting-dwl-2100ap/#comment-15 estqwerty Fri, 31 Aug 2007 13:55:01 +0000 http://www.digdice.com/?p=23#comment-15 I am happy that this helped to You. My surecom is still somehow cant remember his firmware - after 30 min it begin to reboot again - I thing that the flash memory chip is death. I am happy that this helped to You.
My surecom is still somehow cant remember his firmware - after 30 min it begin to reboot again - I thing that the flash memory chip is death.

]]> By: Crom http://www.digdice.com/2007/05/29/resurrecting-dwl-2100ap/#comment-14 Crom Wed, 29 Aug 2007 07:16:51 +0000 http://www.digdice.com/?p=23#comment-14 Thank You very much for posting this information. I've just followed your procedure and successfully resurrected 2 DWL-2100ap Access Points. They were suffering from exactly the same symptoms you describe! My access points went into a reboot loop when I attempted to use the web interface to configure them for WPA. Perhaps there is a bug in the firmware revision I was using - (ie: v220eu_r486). Thanks again :-) Crom Thank You very much for posting this information. I’ve just followed your procedure and successfully resurrected 2 DWL-2100ap Access Points. They were suffering from exactly the same symptoms you describe! My access points went into a reboot loop when I attempted to use the web interface to configure them for WPA. Perhaps there is a bug in the firmware revision I was using - (ie: v220eu_r486).

Thanks again :-)
Crom

]]>