Monday, April 16, 2007
I obviously have a serious lack of judgement...
Having purchased two of the nominees for Engadget's Worst Gadget of 2006 (my MacBook and Motorola Q) I obviously have questionable, at best, judgment. Moments after reading this poll (and voting for the Q as the worst of the worst) the Motorola just rebooted itself without warning in my hand. It is obviously punishing me for my lack of faith in it.
Tuesday, April 10, 2007
Problems connecting Mac with Bluetooth Motorola Q Modem
O.K., I went and bought a Mac. As someone who makes his living off of Microsoft technologies it may seem like an odd decision. I ended up deciding to go with the new MacBook due to iLife's nicely integrated suite of applications that allowed me to easily edit my old family slides and Super-8mm movies into a nicely polished DVD for the rest of the family to view.
Anyway, that part worked great and everyone was impressed with the quality of the results.
It didn't take me long to want to connect to the Internet through my Motorola Q. I have been wanting to do this for years, and I am finally doing it. I won't go into all of the details of how to do this (there are loads of great sites--Tharmsen's post was probably my favorite).
They all have one thing in common--the assertion of "follow these steps and it will work". However, I had problems and I will explain them here.
It worked briefly yesterday, but then stopped working. It would start to connect, then immediately go to "Disconnecting" where it would hang indefinitely. Very frustrating. It helped to go to the terminal window and navigate to:
/var/log
tail +40 ppp.log
This showed me the following problem:
Tue Apr 10 16:05:02 2007 : Starting Apple Verizon Support CCL
Tue Apr 10 16:05:02 2007 : CCLWrite : AT\13
Tue Apr 10 16:05:06 2007 : CCLWrite : AT\13
Tue Apr 10 16:05:09 2007 : CCLWrite : AT\13
Tue Apr 10 16:05:12 2007 : Connect script failed
A search on this problem turned up no definitive solutions and whatever I did (changing the connect script/modem, setting the PPP settings, etc.) didn't affect the behavior.
The solution turned out to be pretty simple. I just unpaired my phone and computer then re-paired and it worked. I can't remember for sure, but I think the first time I paired the DUN option wasn't available (just the Address Book was there). This time DUN was an option, I selected it, entered the login information and I was connected. Sweet!
A quick trip tohttp://www.dslreports.com/speedtest?flash=1 turned up a download rate of 230 kbps and an upload of right at 100 kbps. Not too shabby considering I can connect from just about anywhere here in Denver for only an extra $15 per month on my Verizon bill.
[A Note: Since I discovered this "fix" I've had to re-do this a couple of times as the behavior will re-appear. Oh well, it's not too difficult or time consuming, though sometimes I arrive at my train station about the time I get fully connected. Still, being connected to a remote desktop session with my office while sitting on the train is pretty cool. ]
Anyway, that part worked great and everyone was impressed with the quality of the results.
It didn't take me long to want to connect to the Internet through my Motorola Q. I have been wanting to do this for years, and I am finally doing it. I won't go into all of the details of how to do this (there are loads of great sites--Tharmsen's post was probably my favorite).
They all have one thing in common--the assertion of "follow these steps and it will work". However, I had problems and I will explain them here.
It worked briefly yesterday, but then stopped working. It would start to connect, then immediately go to "Disconnecting" where it would hang indefinitely. Very frustrating. It helped to go to the terminal window and navigate to:
/var/log
tail +40 ppp.log
This showed me the following problem:
Tue Apr 10 16:05:02 2007 : Starting Apple Verizon Support CCL
Tue Apr 10 16:05:02 2007 : CCLWrite : AT\13
Tue Apr 10 16:05:06 2007 : CCLWrite : AT\13
Tue Apr 10 16:05:09 2007 : CCLWrite : AT\13
Tue Apr 10 16:05:12 2007 : Connect script failed
A search on this problem turned up no definitive solutions and whatever I did (changing the connect script/modem, setting the PPP settings, etc.) didn't affect the behavior.
The solution turned out to be pretty simple. I just unpaired my phone and computer then re-paired and it worked. I can't remember for sure, but I think the first time I paired the DUN option wasn't available (just the Address Book was there). This time DUN was an option, I selected it, entered the login information and I was connected. Sweet!
A quick trip tohttp://www.dslreports.com/speedtest?flash=1 turned up a download rate of 230 kbps and an upload of right at 100 kbps. Not too shabby considering I can connect from just about anywhere here in Denver for only an extra $15 per month on my Verizon bill.
[A Note: Since I discovered this "fix" I've had to re-do this a couple of times as the behavior will re-appear. Oh well, it's not too difficult or time consuming, though sometimes I arrive at my train station about the time I get fully connected. Still, being connected to a remote desktop session with my office while sitting on the train is pretty cool. ]
Subscribe to:
Posts (Atom)