Good luck guys! Here's hoping AT&T sees this and works with Netgear to resolve. If successful, simply turn off any checking for updates and DO NOT accept any updates offered until we get confirmation from AT&T that another new version is out that doesn't break the modem in Yosemite. Install, Reboot, and check to see if the modem is now detected. This should start the Tru-Install process and present you again with the installer for the 10.0 version of AllAccess. One everything is removed, simply reboot, then re-insert the modem. It's also a good idea to check the root /Library/ and user ~/Library/ folders for remnants of AllAccess after running its uninstaller - In my case I still found a ".plist" file or two under /Preferences and some content under /Caches and /Saved Application State/ folders. Once these uninstallers are both run, if these folders still exist, it is OK to delete them. Library/Application Support/Sierra Wireless/ To remove them, you need to run the driver uninstallers from the following folders: Netgear's drivers are embedded in the AllAccess installer, but are not removed when uninstalling AllAccess from the uninstaller app included with the app. Here's how I uninstalled AllAccess and the numerous drivers included in the package: If I could uninstall the newer version and go back one, would it work? Then I realized that when installing the product, first the modem installs AllAccess 10.0 which prompts for an upgrade to 10.1 after first run. Everything works, particularly since updating all of my software and services to their latest "Yosemite Ready" versions, except that my AllAccess client, version 10.1, refused to see my inserted modem, the new AT&T Beam (Sierra/Netgear AC340U) - This all worked in Mavericks (OS X 10.9) but wasn't working now. I have a brand new MacBook Pro - Running OS X Yosemite 10.10 since it was released a few weeks ago. I searched all over the web and couldn't find this answer, so I wanted to write my experience down in the hopes of helping others, and getting some attention to the issue from AT&T's moderators, who can hopefully escalate this to a final fix.
0 kommentar(er)
