Wednesday, January 31, 2018

Latest Autonomous Vehicle Stats

Well, it looks like the California DMV has posted the results for 2017's autonomous vehicle testing. Very interesting results, with GM Cruise catching up to Waymo. Unfortunately, it looks like Waymo may have hit a wall in development. Not much improvement from them over the past year, unfortunately.

Thursday, April 22, 2010

Looking For Older iPhone SDK?

I'm starting to get into iPhone dev, but needed an older iPhone SDK that works with OSX 10.5 (Leopard). Of course, Apple makes it darn near impossible to find older SDK's, with their website only pointing to SDK 3.2 and SDK 4.0Beta, both of which require OSX 10.6 (Snow Leopard), which would be a $30 upgrade. This seems quite silly; since I can compile Microsoft .NET executables for Windows from within Linux, why can't I use the new iPhone SDK in a 6-month-old version of OSX?

The old SDK is still on Apple's server, it's just really hard to find. You still need to sign up as a developer with Apple, but a list of old SDK's can be found at http://iphonesdkdev.blogspot.com/2010/04/old-versions-of-iphone-sdk.html

Happy hacking!

Tuesday, March 09, 2010

Shaw Forcing Upgrade To DOCSIS

When my family first switched from dialup to Shaw Cable for internet some 10 years ago, we got a Terayon TeraPro TCM200 as part of the package. We have used that modem up until today. Unfortunately, this modem does not support the newer DOCSIS standard for cable modem communication. For a while now, I don't know exactly how long, Shaw has been giving new customers DOCSIS compatible modems, but pre-existing customers have been using whatever they were given originally. It looks like Shaw is finally going full DOCSIS because today they sent us a new Motorola SB5102 in the mail, and are asking us to send the Terayon back to them. This modem is DOCSIS 2.0, which is sufficient for anyone using less than the Nitro package (the fastest residential package from Shaw). DOCSIS 3.0 would've been nice, since there is better support for IPv6, but Shaw just isn't ready for that yet. I decided I would do some bandwidth tests to see if the new modem will affect my speeds (we have the second-slowest internet package, so I wasn't expecting any boost at all).

All values in Mbps (I don't think these are very accurate, so Mib vs. Mb is probably pointless)
Apologies for the extra space before tables. I think my hand-written html is compliant...
Old modem:









ServerDown SpeedUp SpeedPing
Speakeasy Seattle3.520.48null
BandwidthPlace.com2.680.474null
Speedtest.net Vancouver3.790.47116
Speedtest.net Burnaby3.80.477126
dslreports Toronto2.480.47798
dslreports Los Angeles3.0350.48299


Now for the new modem:








ServerDown SpeedUp SpeedPing
Speakeasy Seattle7.150.25null
BandwidthPlace.com6.1350.189null
Speedtest.net Vancouver5.190.4752
Speedtest.net Burnaby8.110.2846
dslreports Toronto6.2850.264141
dslreports Los Angeles4.7440.23955


Not very scientific. I only did one test at each server. No statistical analysis, but we can see a bit of a trend. Unfortunate about the upload speeds dropping a bit, but download looks nice. The two modems were tested within 30 minutes of each other, so time of day has no effect here. I'm sure my brother will appreciate it :)

Wednesday, May 06, 2009

Hurray for Microsoft

Today I tried installing Service Pack 3 for Windows XP on my parent's computer. The computer no longer boots. Three cheers for Microsoft!

Edit: Booting into safe mode and uninstalling various hotfixes seems to have remedied the issue. I swear I will never install Windows ever again, so if this goes kaput, then my parents and brother will be forced into learning Ubuntu.

Saturday, January 03, 2009

HP Fail

I tried helping a neighbour install his new Hewlett Packard print/fax/scan/copy machine today, but it did not go well. The person who set up Windows for this neighbour (not me, I swear) decided to letter the root drive as E: instead of the regular standard of C:. The HP drivers didn't quite like this, and refused to install on drive E:, meaning my neighbour has now gone out to return the HP and buy a Canon machine. It's surprising that HP can't write software that allows one to install their software on any old drive. It's not like it came up with a box saying "where is Windows? Perhaps we can recover from this...", instead it plain old failed, and decided to uninstall everything it had done up to that point. Quite unfortunate, seeing as how I've had pretty good support for HP on my Linux box. Of course, changing the drive lettering is out of the question, since that will just mess up every other program on the system.

Lesson 1: Use the industry standard of installing Windows to drive C:, and don't invent your own standard.

Lesson 2: Don't assume that the customer's computer will be exactly like your own. Allow your software to be installed to any place possible. It's okay to have C:/Program Files/... as a default, but forcing that on users is a bad idea.

Update (2009/01/07): HP responded, with the following excerpt:
"I would like to inform you that the HP Software is designed to install in C: drive by default. It will look for the C: drive automatically during the installation and we will not be able to install the software to any other drive. So in order to resolve the issue I request you to change drive letter on your computer to C: drive."
Thank you HP. Thanks a lot.

Monday, December 22, 2008

Threading is Fun?

Not at the moment...

Monday, September 01, 2008

Dual Screens with Nvidia 5200

According to the official specs, my video card cannot output video to two monitors at the same time. There have been many times where I would have liked to set up this feature, but could not. Over the summer I have had one monitor hooked up to my computer, while another monitor was hooked up to my brothers computer. Today is the day that I move into Vancouver, so I was messing around with the monitors to get my X.org settings ready for some monitor switching, and what do I discover? I can output to both monitors at the same time. This must have been a new feature of a recent Nvidia driver, or maybe it's doing it in error, and my video card is going to overheat and burnout. I now have about one hour to play around with Twinview, et cetera, before I have to pack up the computer and leave. Why couldn't I have discovered this at the *start* of the summer?