O2 online help to enable users to find the answers they need. ZTE MF100; Mobile Broadband support. Currently there is no firmware update for this dongle.

If after installing your MBRN3000 router and 3G+ USB modem, you get the message '3G USB modem is not supported', but you see your USB Modem and ISP listed on this page, then please follow the steps below to UPGRADE your ROUTER software. • Go to and select the Downloads tab. • Click on the latest firmware version based on your region and follow the upgrade instructions. If you removed your 3G USB modem from the router, reinsert it. Then, return to your Installation Guide and follow the steps to connect to the Internet and complete 'Configuring Your Router's Internet Connection.' ISP USB Model No.

GearHead Support for Home Users GearHead Support is a technical support service for NETGEAR devices and all other connected devices in your home. Advanced remote support tools are used to fix issues on any of your devices. The service includes support for the following: • Desktop and Notebook PCs, Wired and Wireless Routers, Modems, Printers, Scanners, Fax Machines, USB devices and Sound Cards • Windows Operating Systems (2000, XP or Vista), MS Word, Excel, PowerPoint, Outlook and Adobe Acrobat • Anti-virus and Anti-Spyware: McAfee, Norton, AVG, eTrust and BitDefender. Katalog kovanih elementov dlya sozdanie chertezhej.

Hi there, I'm not sure if my experience is typical, but i recently bought an MF100 o2 PAYG modem from Argos and tried it out on three different MacBookPros (running MacOSX 10.6, 10.5.8 and 10.5.1 respectively), and in each case the modem was not recognised, nor did any window come up offering software installation of the MobileConnect app or drivers or any such thing. The lights on the modem went from red to green, but the device was simply not at all recognised, in any way, by any of the computers.

It just didn't show up anywhere (as either a modem or a USB hard drive), including when I opened DiskUtility and Network Prefs. After long conversations (and being passed from pillar to post) with o2 Support (I was eventually put through to a knowledgeable Mr Ahmed Balal, who was very helpful, and who provided me with a software download link when other support staff had previously told me no such link existed) I tried downloading and using the OsX10.6 Mobile Partner app from here ---- and still no luck. After I went back to Argos and had the unit replaced for another identical one, but the same problem persisted. The MF100 simply doesn't do anything on any of the three MacBookPros on which I've tried it. However the o2 PAYG SIM which was supplied with the unit *does* work when I put it in a Vodafone India dongle that I'd bought in India (model HUAWEI K3565) using the standard Vodafone Mobile Broadband app (which the dongle also offers to install for me every time I plug it into any Mac).

It surprised me that two successive o2 MF100 units failed in this very same way, unless this is a recognised issue. Alas I'm going to have to return the unit to Argos now, as i've given up. Long calls to o2 Support were unable to solve this.

.knowledgeable Mr Ahmed Balal, who was very helpful, and who provided me with a software download link when other support staff had previously told me no such link existed) I tried downloading and using the OsX10.6 Mobile Partner app from here ---- and still no luck. The previous staff that told you no link existed were technically correct as that link is for the updated Mac client for the Huawei modems that O2 offer, it doesn't have the ZTE drivers. Would be interesting to see what experience others are having on Macs. FYI I just checked with a Mac running 10.5.8 and it worked fine first time, so there must be something else in play here. The previous staff that told you no link existed were technically correct as that link is for the updated Mac client for the Huawei modems that O2 offer, it doesn't have the ZTE drivers. Would be interesting to see what experience others are having on Macs. FYI I just checked with a Mac running 10.5.8 and it worked fine first time, so there must be something else in play here.