...and I wanted to post our cadence (the clean one) for posterity. This is one my Dad (ex UDT/SEAL type) used to sing when running (again, this is the family oriented version but the original is close except at the end.)
C130 rollin down the strip
Airborne froggies gonna take a little trip
stand up hook up shuffle to the door
jump right out and count to four
if my chute don't open wide
i gotta another one by my side
and if that one should fail me too
I'll be on the ground before you
if i die in a combat zone
box me up and ship me home
put my fins up on my chest
and bury me in leanin' rest
Wednesday, October 29, 2008
...and I wanted to post our cadence (the clean one) for posterity. This is one my Dad (ex UDT/SEAL type) used to sing when running (again, this is the family oriented version but the original is close except at the end.)
Monday, September 29, 2008
Monday, July 28, 2008
Apologies for not having blogged in such a long time, I know Scrappy was about to remove me from her list of friends because of it, lol. Hold on Scrappy!
Anyhow, I thought I'd share some recent tribulation regarding setting up a flat panel television in your house (in my case, over the mantel of the fireplace.) Now, I wanted to have the "nothing to see here but the TV" kind of approach so that none of the components (Xbox 360, comcast HD DVR, VCR/DVR-R) would be visible as they were to reside in a cabinet built into the family room wall. This looks simple, sounds simple, but for me it was in reality a real pain in the a**. ;)
I'll avoid describing the annoying pain I went through learning how to run cable, what types of cable to run, what wall plates to get, the agonizing groan when I remembered that my remote(s) are IR and not RF and therefore do not penetrate wood cabinet doors (I know, I'm an idiot...) I'll simply put the steps I would take NOW to do this. I presume that you already have your components themselves. I also presume that you already have an electrical outlet above your mantle otherwise you'll need to hire an electrician to put one in for you Remember, if you don't feel competent performing these actions, don't blame me if you screw up your drywall/sheetrock/electrocute yourself, et cetera. America has become a land of litigation and I take no responsibility for your actions.
(1)Purchase TV, I recommend measuring the width of the area you wish to place it, in my case a Samsung PN58A550 (which fit perfectly between two areas of molding over the mantle.)
(2)Purchase installer service - you do NOT want to be doing this yourself unless your a professional handyman merely for the liability issues involved in a 120 pound television tearing out of the studs of your wall when there could be children near. I highly recommend searching your local area for home theater personnel to do this and skipping using services like Firedog (although I hear they're actually excellent) due to the expense. Companies like Firedog have package deals and won't simply "hang the mount and TV" because they'll charge you for wiring and everything else regardless of whether you have them wire it or not. BTW, they also charge an extra fee if the TV goes over a fireplace (which they don't mention but a friend mentioned this to me.) Anyhow, $400+ to properly bolt a TV mount to a wall and then hang the TV on it is just a little too much. The choice is yours.
(3)Go to radio shack or some other store which carries wall plates and buy two or 4 bull nose wall plates (depending upon how many cables you are going to run. I ran two HDMI and a set of component video and audio through a single bull nose and it barely fit - 7 cables in total.) Get an equal number of simple junction boxes as well.
(4)Depending upon the distance between your components and your TV you can use light HDMI cables (higher AWG means slimmer more flexible cables) instead of heavy ones and if the distance is short (15 feet or less) you can simply run the HDMI directly from the back of the component into the back of the TV - if longer I recommend getting two Beldin twisted pair HDMI cables (get all of your cables at www.bluejeancables.com by the way - the best quality and prices by far) and run those cables inside your walls and have them connecting to HDMI wall plates at either end. Then simply connect your component to the wall plate with a 1 foot flexible HDMI cable and connect your TV to the other wall plate via another 1 foot flexible HDMI cable. Don't try to connect your component directly to the TV with the heavier gage cables as this will affect your TV's tilt ability and possibly damage the inputs on the rear of the TV.
(5)Get an IR extender, I highly recommend the relatively inexpensive Hot Link Pro (http://www.hot-link.com) I was a little worried about it at first, but once I received it and installed it, it works great. No problems with plasma IR interference with the Samsung either (apparently this was an issue with earlier plasma televisions.) I highly recommend getting the extension cable for the IR 'eye' as well (there's a cheap one available on Amazon iirc) so that you can run that cable through the wall as well in order to put the IR extender's 'eye' just at the base of the TV itself so you only ever point your remote at the TV (not the TV and over to where the component rack/closet and 'eye' are) - the default cable that comes with the hot link pro is about 6 feet long.
(6)Beg/borrow/steal a wire guide/fishing tape. This is what you will use to run the cables through your walls. You can hack one of these together (like I did) but it's extremely unfun and it's always better to "use the right tool for the job" believe me.
(7)Beg/borrow/steal a drywall saw.
(8)Optional - Buy a Logitech Harmony One universal remote. OMG it was easy to setup, very nice, IS RECHARGABLE, and works very well (at least so far, hehe...)
Now, I would do the following once I'd accumulated all these things:
(1)If possible, test EACH cable you plan to run, I can imagine no greater disappointment than busting your butt running cables and then finding out that one or more of them don't work. This is highly unlikely to occur, but hey, running cables is not fun for me.
(2)Run your cables. Find a likely spot in your component cabinet that shares a common wall with the mantle/fireplace. Use a pencil and outline the junction box against where you'd like to place it. Use the drywall saw to cut this out. Do the same above the mantle in a spot that will be reasonably close to where the inputs on your TV will be when the TV is hung. Don't put in the junction boxes yet. Get a friend and a flashlight and start feeding your wire guide as close as you can toward the other hole in the drywall. Your friend should be looking through his/her drywall hold trying to catch a glimpse of your wire. Once they see it, they use the fishing tape to retrieve it. This is the hairiest part of the whole deal for me. Once you gotten a hold of that wire, it's all just regular old work. Once you do so, I HIGHLY recommend running some strong fishing line through with the wire guide. Use enough fishing line so that the line comes out the far drywall hole and can then be taped/tied to the other end of itself to make a circle. You want to do this so that you can attach your cables (a cable or two/three at a time) to it and simply pull on the fishing line to run these cables through the wall. I cannot stress enough the need to use strong fishing line, to securely attach your cables to it when running them, and to inspect the line every time you pull a cable, looking for abrasions and/or damage of any kind. If you see any damage, use it to run another line through before it breaks. Once you've run all the cables you want (make sure there's enough slack on each side of the drying holes), put in your junction boxes. You could do this before, but when I did I found that they interfered a bit with running the cables until I removed them again. Then put in your wall plates. You should know have a nice looking connection in your component cabinet with loose cables dangling out, and a similar connection above your mantle. I HIGHLY recommend that when you're done running cable you untie the fishing line from itself, tape one end of it securely on the mantle (where it will be covered by the TV) and roll up the slack and tape it under the top of your component cabinet so that you can run cable again in the future if you wish without having to fish for the wire guide (which seems like it would be tough if cables are already running through there.)
(3)Now you can have the installers come put up the TV mount (make sure you have purchased the correct mount for the type and size of your television, I used the x-large tilt mount.) Make sure the installers place the mount at the correct height you desire or your wife may yell at you (luckily mine expressed her displeasure before they permanently mounted it.)
(4)If the installers didn't connect the inputs, go ahead and do so now. Test the TV, get everything working from each component before moving on.
(5)Setup your universal remote (if you're going to use one), get everything working before moving on.
(6)Setup your IR extender. In my case this meant using the line I'd luckily kept to run my late arriving extension cable so that I could attach the IR extender's eye to the bottom of the TV behind a grill where you can't see it, then attaching little IR flashers to the IR sensitive spots on my components.
(7)Open a beer, sit down, and enjoy your new TV.
Wednesday, April 23, 2008
Friday, March 28, 2008
Monday, March 17, 2008
...as amateurish as a filename with a space in it breaking their tools (qmake) it makes you wonder.
Specifically, if you have a file name 'My Filename.cpp" and you run "qmake -project" you get a project file that has failed to wrap the filename in quotes which is required by "qmake -makefile" - ridiculous. You have to edit the *.pro file by hand.
You're probably thinking what I was thinking "there's a switch or option somewhere that he's missing" - nope.
So - If you find your attempt to produce a makefile resulting in weird errors where one filename becomes two, edit your *.pro and wrap those filenames with spaces in quotes yourself ;).
I found myself with some free time the other day and wanted to play with using Qt on Windows as I have been using it for fun on various Linux flavors for years. I even went so far, on Linux, as to write an 'intellisense' like autocompletion class that I put into my own little code editor (because I deal with a lot of APIs both in my day job and my own activities.)
This time though I wanted to use it with Visual Studio 2005 and let VS do the work for me. Some initial attempts at this (I am using the open source windows version which is available as of Qt4.x) failed miserably but I finally managed to get things going after checking a few blogs (most notably Bennet Smith's.)
The version of Qt I am using is Qt 4.3.4 (you should know this because qmake command line args change occasinally [as they have between 4.x versions already]) so this should work for you if you have installed and built Qt 4.3.4 on your Windows box and have Visual Studio installed correctly.
The general process, at least for me, is to create a new toolbar in VS and add two buttons to it for triggering "qmake -project" and "qmake -makefile", then to create a Visual C++ Makefile project and edit the nmake parameters of the project. After this you should be able to use both intellisense, debug, and build using your normal build methods without a hitch.
Let's get started!
Step 1 - create a new toolbar to contain your new Qt specific commands
We want to create 2 buttons, both run the 'qmake' command, the first one runs qmake to produce a *.pro (qmake project) file and the second one generates a makefile from that *.pro file.
(1)In VS select ToolsExternal Tools to bring up the external tools menu.
(2)Press the Add button, and fill in the following properties as below:
Title: qmake project
Initial Dir: $(ProjectDir)
(3)Press the Add button and fill in the following properties as below:
Title: qmake makefile
Arguments: -makefile -spec win32-msvc2005
Initial Dir: $(ProjectDir)
If you wish, you can also set the checkbox for "Use Output Window" for these buttons (I do in case there's a problem) You may also wish to add buttons to launch Qt Designer and Qt Assistant here as well (as I did.)
Now that you have new external tools configured, let's put them on a new toolbar to help us build Qt projects.
To add a new toolbar to VS go to ToolsCustomize and then select the Toolbars tab on the dialog and press the New button. Put in whatever you want for the toolbar name, because you may ultimately have more than one version of Qt installed I recommend putting something like "Qt 4.3.3" as the title.
To add the buttons we want to this new toolbar choose the Commands tab on the Customize dialog, then find the Tools entry in the categories listed and in that sub-category find the external commands.
You need to figure out which commands are your qmake commands because for some odd reason VS simply gives them numbers. For most people they will be the two last external tool entries by number but for others who have had other external tools installed and then uninstalled (such as myself) you may have to count the number of entries for external tools in the drop down menu on the main UI because in my case my qmake entries were #10 and #11 and I had external tool numbers all the way up to 23.
You can simply drag the entries from the sub category list onto the toolbar and the title should show up and tell you if you've selected the correct entry. If you just see 'external tool #
Step 2 - Create a VS project file for use with Qt
(2)Under Project Types, choose General
(3)Choose Makefile Project from the list of sub projects now showing
(4)Give it the location you desire
(5)Press the Ok button and when the application wizard pops up press the Finish button
Now that the project has been created, we need to edit some of its properties:
(1)Bring up the project's properties
(2)Choose Debug as the project type
(3)Choose Configuration Properties
(4)Choose NMake, and under the NMake properties on the right side:
(5)Set Build Command Line to: nmake debug-all
(6)Set Rebuild All Command Line to: nmake debug-clean debug-all
(7)Set Clean Command Line to: nmake debug-clean
(8)Set CLR Support to: No CLR support
(9)Add to Preprocessor Definitions: UNICODE; QT_LARGEFILE_SUPPORT; QT_DLL; QT_GUI_LIB; QT_CORE_LIB; QT_THREAD_SUPPORT
(10)Set Include Search Path to the corresponding locations of your Qt install:
(mine for example are: C:\Qt\4.3.4\include\Qt;C:\Qt\4.3.4\include\Qt3Support;C:\Qt\4.3.4\include\QtAssistant;C:\Qt\4.3.4\include\QtCore;C:\Qt\4.3.4\include\QtDBus;C:\Qt\4.3.4\include\QtDesigner;C:\Qt\4.3.4\include\QtGui;C:\Qt\4.3.4\include\QtNetwork;C:\Qt\4.3.4\include\QtOpenGL;C:\Qt\4.3.4\include\QtScript;C:\Qt\4.3.4\include\QtSql;C:\Qt\4.3.4\include\QtSvg;C:\Qt\4.3.4\include\QtTest;C:\Qt\4.3.4\include\QtUiTools;C:\Qt\4.3.4\include\QtXml)
(11)Set the project type to release and perform steps 5-10 replacing the word debug with release
Now, save everything, and before you do anything else, press the qmake project button on your toolbar (this should generate a *.pro file in the solution directory) and then press the qmake makefile button (this should result in a Makefile being placed in the project directory) and now you can simply choose "Build Solution" from the Build menu of VS and everything should be up and running.
Hope this helps someone out there :)
Wednesday, March 12, 2008
...try configuring X to avoid using the default detected S3 driver like below (other Linux distributions use other methods but below should work for OpenSuse flavors):
(1)Boot using "3" (without quotes) as an option to initiate a command shell
(2)Enter the command: "sax2 -m 0=vesa" (without quotes)
(3)Wait for the confirmation window and choose "Ok"
(4)Reboot and start as you would normally
...there's a 'quirk' with Virtual PC that can make it difficult for the installer (in my case OpenSuse 10.3) to detect your mouse/keyboard properly, to get around this try adding the installer boot option "i8042.noloop" (minus the quotes of course.)
Also, if you're mounting the install from an ISO, this can be problematic as well. If the install keeps asking you to put in CD1 (or any type of media it shouldn't be asking for), try burning the ISO to disk and asking Virtual PC to let the virtual machine grab the CD/DVD drive as this fixed some problems I was having as well.
I hear that you need to change the framebuffer's color depth to 16-bit (from the default of 24-bit) after install as well, but we'll see about that later...
Wednesday, February 6, 2008
Tuesday, February 5, 2008
|You Are 80% Boyish and 20% Girlish|
You have a tough exterior - and usually a tough interior to match it.
You're no nonsense, logical, and very assertive.
Sometimes you can't understand women at all, even if you're a woman yourself.
You see things rationally, and don't like to let your emotions get the best of you.
Sunday, February 3, 2008
That's right... I DO! Lol... I've 5 starred the first 28 songs on Expert now (on guitar) but the last few songs have been kicking my butt. I can beat the game on Expert, but getting four stars on some of these songs is tough (for me.)
I have a feeling some of the later songs like "Green grass and high tides" are going to be murder...
I was just happy to get past "Suffragette City" unscathed :). For some reason that song kicks my butt. Anyhow, eat your heart out Scrappy! (Reptilia took me a couple of times to 5 star it, the picture above is from my first attempt.)
Wednesday, January 30, 2008
Mein Rich undt mein self got muddy this past weekend. Rich got very slightly muddy. I got 'dug yourself out of your own grave' muddy. The best part was that I was fairly clean until we were coming back to the main parking area on the main trail and I went down a steep, muddy, slippery hill and at the bottom was a virtual bog o' mud. It was one of those mud bogs that makes you think "Damn, I'd sure hate to fall into that."
I make it down the slippery hill, and I need to explain that I'm tired by this point as the riding we were doing is very technical (tight trails, steep downslopes with large rocks, big slippery power hill climbs - but fun), I hit the bog knowing that I need to power through; unfortunately my front tire was in one underwater rut, and my back tire went into a different underwater rut and my back end threw out left. This had the interesting effect of catapulting me to the right and a bit over my handlebars and BLAM did I hit that mud with a spectacular splash. Rich tells me it was impressive from his vantage point.
Anyhow, here's a few pics that don't really do the mud justice (especially on the bike.) It took me hours to wash that thing off.
Tuesday, January 29, 2008
I recently tried out Eggbeaters for the first time and have to say that I was quite happy with them. I made a great omelette using the Southwestern variety.
The website is a little kitsch and oddly 80's (at least to me) but there's nothing wrong with the product itself.
The point of Eggbeaters is that Eggs are a great source of protein and relatively low in calorie; however, they are ridiculously high in cholesterol which is almost entirely found in the yolk and not the egg whites (hence all the 'egg white omelette' orders you've heard.) Of course, because God has a sense of humour, virtually all the vitamin benefits of eggs are also in that cholosteral filled yolk. Eggbeaters makes their product out of the white but adds vitamins to make up for those lost in removing the yolks. This results in cutting the calorie count in half, eliminating all the fat and cholesterol.
I had mistakenly assumed that they were some sort of facsimile or vegan analog to eggs when in fact they're just egg whites fortified with things like beta carotene. (Beta carotene gives the Eggbeaters a normal yellow color as well.)
They come in flavored varieties as well: Garden vegetable, Southwestern, Cheese & chive. The sodium content is a touch high in some of the flavoried varieties, but not bad if you don't throw salt on your food (which you shouldn't need to if you're making it anyhow.)
I ran into this years ago when adding network TCP/IP stream support for 3rd party clients and one of the companies wanted to use Flash to consume our AI and I couldn't understand why the damn thing couldn't receive responses (they were using XMLSocket in Actionscript) and there was zero information at the time because this was a new 'feature' of Flash. I only figured it out (luckily) when I noticed that n batched commands to the AI resulted in n-1 responses showing up in Flash. I figured we were missing a terminator. Why flash wouldn't need a terminator on multiple submissions but need one on a single submission is beyond me, anyhow, anybody out there understand the reasoning behind this? I'm consolidating some networking code and I really would like to eliminate this 'special case' in some fashion as I have two socket::send methods, one for normal properly behaving (imho) clients and one for flash that adds an extra zero byte explicitly into the TCP/IP stream. *** End Rant ***
Friday, January 25, 2008
Sunday, January 20, 2008
Friday, January 18, 2008
Just a note to anyone using gacutil on Vista, make sure you start the command prompt with administrative permissions prior to trying to uninstall an assembly, otherwise you get the oh so informative "The process cannot access the file because it is being used by another process" message.
Monday, January 14, 2008
I forgot to mention, when blogging about my new t-shirt from the boss, that a friend and previous co-worker had awarded me a 'Happy Bunny' to display on the door to my old office.
He mentioned that I left that out when talking about how sweet I am as a person, so in the interest of complete disclosure, there's my bunny :).
You need to be aware that some processes, such as internet explorer (iexplore.exe) will detect the privilege level at which they are launched and potentially relaunch themselves with different privileges (usually when a higher privileged process launches a process into the session of a user with lower default process privileges), therefore if you are tracking the created process id from the class I provided beware of this issue as the instance of (using iexplore.exe as an example) internet explorer you have created will self-terminate after launching another instance of itself.
When I get the chance I'll add a method to the class that overloads the current one for launching processes as a user which will accept an 'integrity level' in order to alleviate this issue. It isn't much of an issue currently; however, I'm not comfortable with processes running in user space with higher than default integrity levels. You would think this is a security issue but in actuality it appears to only effect iexplore.exe (I'm sure there must be something else that has this problem as well) because the DACLs and SACLs and process tokens security levels all match the user being impersonated so there's no apparent issue with a fear of security elevation (but you never know.)
I've been building (when I get the opportunity when not fixing some critical issue) a failover and replication support architecture for 3rd party applications that will allow someone to remotely monitor when a mission critical application crashes and how to handle the response (i.e. start it back up? E-mail someone about the problem and then start it back up? Reboot the machine? Restart some associated services and only then start it back up?) There are, of course, many ways to solve each of these individual problems but I wanted more of an all in one solution. I also wanted to be able to connect to the machine running these services and applications and ask them for their current state (memory usage, CPU usage, et cetera), I also wanted a plugin system (so I could later add an update system/deployment system), and finally I wanted it to run as a windows service so that I could make use of the operating system's service failover capabilities (sorry *nix, this one is just for Windoze.) I hope I'll get a chance to port the feature set to a comparable daemon on *nix because I really like using Qt (for the UI.) Anyhow, this one is written in C# using .NET 2.0. Now, all that aside, now that I've partially established why I'm using a windows service, there's only one blocking issue to doing all of this - Vista. Now, this is actually a good thing. Let me explain the problem. On previous Microsoft Operating Systems you could mark a windows service as being allowed to 'interact with the desktop' when running as the SYSTEM account. This made it very simple for people to write services which interacted with the logged in session. Services could run in multiple sessions and were not isolated from desktops (in the kernel sense), not really. This meant that you could write a service that started up applications and the UI would show up on the user's desktop. You can no longer do this in Vista. Vista has 'hardened' services in two ways (one of which is actually present in XP if you have fast user switching.) The first, and most important way, is that Vista runs ALL services in session id 0. Nothing else is allowed to run in session id 0. Services are not allowed to run in other session ids. The second way is that due issues regarding fast user switching, some new security issues, and the ability (in some XP installs and Vista) to have several people logged on under an interactive session simultaneously, the services subsystem would need to be careful about whose actual desktop to place the UI associated with a spawned application by the service. So, the Vista team decided to eliminate the 'interact with desktop' service configuration checkbox (although the UI component still exists and you can check it, it has no affect in Vista), and put services in its own dedicated session. Now, if you want your service to have a UI, that's fine and it can do so easily if you don't mind the UI only showing up on the session id 0 desktop. When that happens the Operating System will interrupt the user and announce that a 'service has a message' it wishes them to see and will let you switch to viewing the session id 0 desktop (usually a grey desktop with nothing on it but the UI from your service.) If the UI is only related to your service this is very likely an acceptable solution. Then you're in luck and don't have to do anything special; however, I can't do that. So... If you're still reading this diatribe, here's the meat and potatoes. I've encapsulated, in a C# class, all the little things you need to do in Vista (and it works on XP and 2003 Server) in order to have a windows service spawn an application's process so that its UI shows up on the currently active console's session (this means the user who is actually actively using the system, not just logged in.) I hope it saves you an enormous amount of time because I was googling my a** off and didn't find anything that actually worked on Vista.