Obama Defines "Change".

"Change"

http://yro.slashdot.org/article.pl?sid=09/04/07/1330229

Not that I have a problem with this policy. I just think it's funny how the mass of Obama supporters assumed that this was what "Change" meant. In reality, the only Change in store is more government control over you.

Palm Pre Goodness

I've been drooling over this device since it was announced in January. Now that ads are actually starting to show up, the only thing left to see is a release date.

UPDATE: Adding new commercial clips as they come out.

PROC Machine Chk processor sensor transitioned to non-recoverable

Just making a quick post to help out any Googler's out there looking for the solution to this problem. I had a Dell SC1425 pizza box server with an error/alarm light on it's face recently. The alarm showed up when the server had been rebooted after a full lockup. I downloaded the Dell DSET utility and ran a report, which found this error:

PROC Machine Chk processor sensor transitioned to non-recoverable

Basically this means that the mainboard detected that the processor stopped responding (i.e., locked up), which of course we already knew.

To get rid of the alarm light, just run DSET again and tell it to clear the log. After you do so, your server lights should once again be a calming, cool blue.

Resolving a Persistent spoolsv.exe Error/Crash

Today I was troubleshooting a couple of network printers. One of them, I believed, had an incompatibility with "Standard TCP/IP" printing, via RAW communications. I tired other printer port options, including the HP TCP/IP port. I found out later on that the printer itself (a multifunction copier actually) did not have printing capability enabled. In the process of installing a printer driver later in the day, I ran into this error:

The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "written".

The error wouldn't go away. Reboots did nothing. Clearing out all registry references of the printers and drivers that I had been troubleshooting did nothing. Deleting my printer drivers folder only made things worse (as you'll read later) Even a reverting to an earlier System Restore point failed. Finally, after finding tidbits of information online here and there, nothing with a complete solution, I tried removing this key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\HP Standard TCP IP port

I then restarted "Print Spooler" in the Services control panel (services.msc), and my Printer control panel finally displayed properly, without crash. Unfortunately for me, I then had to delete all my printers, as I had deleted all of my printer drivers and none of the installed printers were functional.

So if you run into this error, try deleting the key above before attempting anything else.

Obama Yuks It Up Over the Collapsing Economy

Now, I'm no fan of the American auto industry either, but for much different reasons than Obama. Obama sees the auto industry as a whole as evil greedy capitalist pollution profiteers, and clearly takes joy in overseeing their demise. He sees the collapse of the American auto industry as a success of his ideals.

I, on the other hand, dislike what the American automobile makers have allowed to have happen to their once prosperous industry. One has to ask the question: Why are the foreign owned, yet locally manufactured, automobiles doing just fine in today's economy, yet the American manufacturers are struggling? The answer: Unions. The successful auto makers never bowed to union pressure. Foreign companies realized the hazard of giving up control of their own companies to socialist union thugs, pushing unsustainable pension plans and benefits. If the American auto industry had the spine to kick them out years ago, they'd be much better off now.

MuchTall.com: In With WordPress, Out With PHPNuke

I'm finally taking the plunge into WordPress. I've moved all of the accounts (minus passwords), categories, stories, and comments over from the old PHPNuke site. I have yet to pretty up the theme, but I just couldn't wait any longer. PHPNuke was just too difficult to maintain, and worse, was prone to spamming from bot-created accounts.

More changes to come.