I thought because Sprint did not provide software to tether my blackberry to my mac, I would not be able to use it as a modem. Well, it's not exactly real easy like most things on the mac, but not terribly difficult either. What follows is instructions on how to make this happen w/ a Sprint Blackberry 8830. [ Update: These steps work for Leopard and Snow Leopard ] [Before you begin, make sure you're Sprint account is enabled for data tethering, there is usually an extra charge for this service] What follows are some instructions to get this to work in Leopard (OSX 10.5.x): Click the Apple icon and select preferences. Next, click the bluetooth icon. Now click the plus (+) button. A setup wizard should start. Follow the wizard's instructions to pair your phone. Make sure your blackberry is in discovery mode so the mac can see it when it searches for it Once you've paired your blackberry, you should see it in your bluetooth preferences like picture below. Highlight your
Popular posts from this blog
Summary: Long story short, Fire TV Stick (2nd Generation) doesn't allow you to calibrate the screen, software wise, forcing you to use your TV settings (if available) to fit the screens content within it's borders. Super annoying for some apps, but you can fix this dumb issue as I was able to. If your TV allows you to adjust its settings, then you'd be fine as well, but the Vizio I have, has no such setting. Solution: Get the Amazon Fire TV instead. It's only slightly more expensive, but doesn't suffer the problems the Fire Stick does. Workaround: First you have to enable ADB debugging ( step 1 here ) on your fire stick. Next you'll need the ADB provided w/ Android Studio , or you can install w/ brew on the Mac . I prefer brew cause it's easier, keep following steps described by Amazon page if you are using Windows. Open Terminal brew cask install android-platform-tools Next find the IP address of your Firestick Settings --&
Summary: Unable to connect to ESXi/vCenter server with Connect-VIserver cmdlet, get the following error: "The SSL connection could not be established, see inner exception." Be sure to "Set-PowerCLIConfiguration -InvalidCertificateAction:Ignore" if you plan to connect to an ESXi/vCenter that does not have trusted certificate. Interestingly, something must've changed recently because the PowerCLI module actually would output a more descriptive message about setting your PowerCLIConfiguration. This appears to be the case w/ Powershell Core 6.1. I'm actually unsure when this behavior started happening and whether is module or powershell related. Regardless, figured I'd post this since I was initially confused myself when running some things on another system.