Thursday, 24 October 2013

As Predicted, Some BT Routers Won't Download Maverick

Well, last night I disconnected my trusty 2-Wire 2700HGV BT Business Hub and replaced it with a simple Draytek Vigor 120 broadband modem. Other than the appalling download speed here in the depths of rural Wiltshire (actually, according to the Highways Agency, our corner of this green and pleasant land is actually a vibrant metropolis) , the download worked. It only took 11 hours to download all 5.31 GB of OS X Mavericks.

So if you've got a similar hub, you are going to have issues. I'm now trying to download an iPhoto update of 1.44GB and am wondering if that too is going to stall. At the moment, only 7.2Mb downloaded. Hang on though, 30 minutes ago it was at 900Mb and counting. Here we go again!

UPDATE:

An Anonymous respondent advised that the issue with large file downloads may be caused by Content Filtering in
v6.3 firmwares. v6.3.9.41 has a known 2GB file limit issue. v6.3.9.63
'might' have a 4GB file size limit.

The same person provided the following link that might be of use to folks who don't have the luxury of being able to swap out their router.

http://bt2700hgv.tripod.com/161.htm

I should add that I haven't tried this "fix" myself, but I have hacked earlier versions of this router firmware using instruction from this same site and they all worked. I'm currently using firmware version 6.3.9.63-plus.tm (Look on the Settings>System Info>Summary page to check yours. For my own part, it takes me a matter of a minute or two to swap out the routers when needed. It would take much longer to alter the settings on the 2-Wire - which for me would need to be reset again at the end of the process.But nice to have an alternative nevertheless.

3 comments:

Anonymous
said...

The issue with large file downloads may be caused by Content Filtering in v6.3 firmwares. v6.3.9.41 has a known 2GB file limit issue. v6.3.9.63 'might' have a 4GB file size limit. Have you tried the workaround for 2GB file downloads described here which was known to fix the problem for v6.3.9.41.