Skip to main content

Posts

Showing posts from August, 2009

Farewell, D430... It's Been Real

Well, in spite of all the headaches and issues I went through with my old D430, it's been sad to see it go... Today, I imaged it for a co-worker and put WinXP back on it. I felt bad. It's kind of like reclaiming land, building some futuristic development on it, and then clearing it again to turn it into a waste dump. The machine was INSTANTLY 30% slower and I'm sure it will just go downhill from here. Bummer. Farewell D430. I wish I could say you were going to a better place...
Post a Comment
Read more

D630 System Up and Running on 9.04

Gotta love Ubuntu. Just one day later and I'm fully up and running. Bluetooth is working great (send-recieve from phone, check. bluetooth audio for headset, check.), nvidia graphics working great (after installing proprietary driver version 180), wireless working great (Broadcom B43 Wireless proprietary driver and updated OS). Yep, everything working great! I've updated my Bluetooth Headset post to include more accurate information on how I got it working this time around. Just do a search or click here .
Post a Comment
Read more

"New" Test Subject

I won't go into how (sad story), but I was just given a Latitude D630 to possibly switch out my D430. I've been VERY happy running Ubuntu 8.10 on my D430 but am now interested to see how 9.04 works on the D630. With the NVidia card, faster CPU, and other goodies, it ought to be a slightly better, albeit heavier, experience. I'll post some of my findings here in the next few days.
Post a Comment
Read more

Exposing .NET as COM (Windows)

Below didn't work for me, so I'm trying these links instead: http://www.codeproject.com/KB/COM/VS2005ComDllWalkThru.aspx http://www.codeproject.com/KB/COM/VS2005RegisteringComDLL.aspx Sorry, real world problem here - need to write it down: (Ripped shamelessly from Experts-Exchange ) Ok, to make a VB Component COM callable, follow the instructions below: 1) Open up the Visual Studio . NET command prompt, and change to your project directory (where your .sln file is located). Whenever I refer to the command prompt, I mean the VS.NET command prompt. To open it, go to Start->Program Files ->Microsoft Visual Studio . NET ->Visual Studio . NET Tools->Visual Studio . NET Command Prompt. You may want to put a link to it on your quickbar. In the command prompt, while in your project directory, type: sn -k key.snk This will create a strong name RSA key file with a public and private key. There are security implications if you create any components that are distrib
Post a Comment
Read more