Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 4396
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 1641
Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 4396
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 5531
Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 4396
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 5531
Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 4396
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 5531
Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 4396
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 5531
Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 4396
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 5531
Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 4396
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 5531
Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 4396
Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/system/lib-story.php on line 324
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 5531
Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 4396
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 5531
Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 4396
Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/system/lib-story.php on line 324
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 5531
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/www/nat.guyton.net/geeklog-1.4.0sr2/public_html/lib-common.php on line 1143 Nat's Geeklog - General News
It seems that even selecting a jury in Fort Bend county takes longer than can be done before lunch. I had a deceptively filling steak burrito at a local mexican place, and then decided to spend the remaining 60 of my 90 minute lunch walking around historic Richmond. I noticed an Italian place serving Osso Bucco! Darn, too bad I already ate. Now I almost want to be on the jury so I can go back there as well as another popular looking place or two.
I had the misfortune of walking into a gift shop with a confectionery, and thus walked out with two pieces of peanut butter fudge. Sitting on the bench in the cool afternoon tasting the peanutty treat with the sun on my face really made my day.
I got back to the courtroom with 30 minutes to spare, and I noticed that the jury chairs are nice, padded, blue leather chairs. Did I mention that they recline? I'm dead meat after lunch if I am on the jury!
I wonder if it's OK to have a margarita with lunch? Needless to say, I didn't get selected, so I won't get the opportunity... It's probably also not a good idea to do so during jury days, but having one on the jury selection day can't hurt! Just don't get sloshed. *wink wink*
Interesting note: they pay $40 / day if you are selected on the jury, but not for the jury selection. I guess that's sort of the consolation prize for those who have to return the next day.
Monday, September 04 2006 @ 12:28 AM CDT
Contributed by: nat
Views: 430
I noticed tonight that the baby channel (Noggin) that runs shows like Little Bear, Blues Clues, Barney, etc turns into Teen Soap Opera channel after 5. Wow.... Wife started watching one and didn't want me to switch to something else... and damn, I started following it, too.... There's been a "Degrassi" marathon on tonight that's been on while I've been computing on my laptop. I suppose it's interesting enough for a background show, but it's scary to think that I'd stop computing and do more watching... Like I said, teenage soap opera. More interesting that my wife's soap operas she used to watch, anyway. Is that a bad thing?
Sometimes you just can't win. Soon I am going on a 12 day trip where I will need my laptop, and I have three to choose from:
The first one is an HP that has a power cord that started fraying at the connection. If I adjust it just so and don't move, then I can get it to charge the battery and run the computer. Additionally, sometimes it overheats when I run a certain application (read: games) and just powers itself off hard.
The second one my wife used to use, but she dropped it out of her lap last summer and the headphone and microphone jacks got destroyed when the cords tugged on the unit. The power adapter is angled now as well, but at least it works.
The third one got its screen cracked, and I use it with an external monitor. Not good for trips, though.
I guess the best thing to do is go get a USB headphone with boom microphone that I can plug into the second one. Not the best solution (my wife has one and it is not very reliable), but short of getting another laptop, probably the right thing to do.
I don't want to get a new laptop until one comes with wireless-N as part of the package. Hence, I wait and play old games like Diablo 2 when I am not working.
Sunday, April 02 2006 @ 11:55 AM CDT
Contributed by: nat
Views: 447
Lately I have been making sure that all of the windows computers in the house are updated with the latest software. I guess this was brought about by all of the viruses and security vulnerabilities in Windows. Whatever the reason, read on for my list of apps... (I should note that ALL of these are 100% FREE!)
Browser:Firefox, of course. The single biggest hole in Windows is Internet Explorer. Firefox also runs on Windows, Linux, Mac, all of which I use.
Email:Thunderbird - there are plenty of mail programs out there, but I like this one. It also runs on Windows, Linux, and Mac.
AntiVirus:AVG Free Edition - I have talked about ClamWin elsewhere, but this antivirus package is a little more user friendly and polished. I run ClamWin on my laptop, and AVG everywhere else.
Office Productivity: Open Office - the latest version 2 has improved by leaps and bounds, and does most of what almost anyone would use MS Office for. Runs on Windows, Linux, Mac, Solaris, BSD, etc...
ZIP: 7-zip - Very broad, powerful zip program. Windows and Linux.
Instant Messaging:GAIM - this client speaks Yahoo, AOL, Microsoft, and other IM protocols, and you only have to run this one app. Runs on Windows and Linux.
Some other neat apps:
Spyware Removal: Spybot Search and Destroy - this only runs on demand, but is great for cleaning up a PC someone else has been using.
Windows License Key: Magical Jellybean's Keyfinder - this will find your registration key for MS windows and office. For my laptop that is about to die, I can save the key (license) so I can install XP Pro on another PC later when it dies. (Just have to get my hands on some install media) I hate how Microsoft was worked it so that you are buying a new copy of Windows with every PC. If your hardware dies, you should not have to repurchase the software!
Video Player: VLC media player - This plays a wide variety of formats and also runs on Linux, Mac, and Windows.
Remote Control: VNC - sure, windows remote desktop protocol is OK, but VNC runs on Mac, Windows, and Linux so I can display one desktop on any other OS.
Hardware: PC Wizard - detailed hardware and performance scans for Windows
Privacy: xp-AntiSpy - disble scan-and-report-to-microsoft features in XP.
Monday, January 09 2006 @ 10:33 AM CST
Contributed by: nat
Views: 522
Have you ever stayed up way too late and dreaded getting up in the morning? (Of course you have, that's a silly question) Every now and then, in my waking stupor I seem to get the idea that I have this amazing alarm clock.
This morning when it "woke" me, I automatically hit the snooze button in my sleep and wishful dreaming kicked in. Somehow I got the idea that my alarm clock would monitor the time and come up with just the right excuse for me to give my boss on why I missed work that day. But wait, there's more! Not only would it do the work of coming up with the right excuse, it also would communicate it to my boss via email as well! All official-sounding and stuff. Nothing more for me to do but sleep in. This turned out to be my dream's downfall, however, because I realized not that my clock didn't have the capability to come up with all of this, but that it did not have an internet connection and would not be able to send the email... nor had I configured an SMTP server for it. (dagnabbit! Why did I forget to do that!?)
Sometimes the basic points are the things to pay attention to, i guess. The funny thing is this is nowhere near the first time I've dreamed about my "special" alarm clock!
Did you know that the month of September got short-changed 11 days in the year 1752? Yep, you went to bed on Wednesday, September 2, and woke up on Thursday, September 14! This is because of reorganizing the Gregorian calendar or some such. Mindless trivia, I guess. It's neat to see that the computer relays it nicely:
August 1752 September 1752 October 1752
S M Tu W Th F S S M Tu W Th F S S M Tu W Th F S
1 1 2 14 15 16 1 2 3 4 5 6 7
2 3 4 5 6 7 8 17 18 19 20 21 22 23 8 9 10 11 12 13 14
9 10 11 12 13 14 15 24 25 26 27 28 29 30 15 16 17 18 19 20 21
16 17 18 19 20 21 22 22 23 24 25 26 27 28
23 24 25 26 27 28 29 29 30 31
30 31
I finally got my Linksys WRE54G wireless 802.11g repeater working with my WRT54G. This is nice because now I can use the laptop in the kitchen and study. It also forced me to do a firmware upgrade to my router, which seems to have fixed a few problems with losing connections. Happy surfing now!
But as I was saying, I finally got it working. The setup program was failing with a message: WRE54G cannot associate with this AP in repeater mode, so I put it in my closet for 6 months. This weekend I googled a bit, and found that the roundabout method works:
Reset the repeater
Set your wireless IP to 192.168.1.239, select the repeater network, and surf to http://192.168.1.240, login as admin.
In here you can set your SSID, frequency, security to match the current infrastructure. They should all be the same. (in the process of doing so, you may need to change your IP address back to whatever).
The tricky part for me was the MAC address: my AP has three: one for the WAN, one for internal wired, and one for internal wireless. I mistakenly gave it the WAN MAC address the first time, and while I was able to connect to my repeater, it could not talk to the AP. After I corrected it to the one for the wireless MAC address, the red light on the repeater turned blue. Hallelujah!
We went to Party City today to pick up a few things, and I passed through the wig section. Hilarious! Two of note: Enormous Afro and Deluxe Mullet. They also had "Comb-over" and a nerd 'do. Funny.
I got a cool plastic warhammer for $8, but it looks like Zachary owns it now...
My car that I got last December is going to have a Bluetooth module so I can use the car microphone and speakers and buttons on the steering wheel to talk to people while the phone is still in my pocket.
Well, the car module is not available yet, but I went ahead and got the Motorola V600...
The car module is still not available. I got tired of waiting, and just so I could play around with it, I got a USB Bluetooth module. It's cool! I can transfer pictures I take without having to email them to myself (thus incurring charges from T-Mobile), and I can put files ON the phone - now my background is a nice high quality photo of Zachary.
OK, now the coolest part is that I can use the cell phone as a modem for my laptop and dial out to an ISP. No wires, cell phone within 30 feet, just a bluetooth dongle and drivers installed on the computer. This is cool because now I can support remote sites from work, which pretty much blocks outbound shell access.
I don't have an ISP, but I want to get one of those thingies that can detect an incoming data vs fax vs voice call and route it appropriately. That way when I am on vacation I will still have dialup access anywhere I go. That's the plan, anyway.
I got a cool plastic warhammer for $8, but it looks like