The official blog of the Saved Content site

The aim of this blog is to collect and archive my selected thoughts, ideas, feelings, reactions, and opinions on subject matters that pique my interest. These entries represent initial drafts that may contain grammatical and spelling errors and whose substance and position could still change, and which, at some point, I could decide to put together into in-depth articles that will be posted on the main Saved Content and Poverty Sucks sites.

"God save us all from that evil Satanic Nazi, Paypal."

Transferring Windows XP to a New or Different Hardware Configuration

Moving Windows XP to a virtual machine or a physical machine (a PC or laptop) with a different hardware configuration can cause XP to experience a blue screen upon startup.  A BSOD with a Stop 0x0000007E error code means an incompatible CPU while an incompatible hard disk controller will result in BSOD with a Stop 0x0000007B error code .

Before moving Windows XP to a new or different hardware setup, rename amdppm.sys or intelppm.sys to a different filename so that the driver won't load and cause a BSOD.  Make sure to set the SATA type in the BIOS to Native IDE or Legacy IDE since XP doesn't have built-in drivers for SATA hard drive controllers.  Watch XP boot into the desktop on your different hardware setup.

Once in XP, go to HKLM\System\CurrentControlSet\Services\intelppm (or amdppm) and change the Start value to 4. Install the correct CPU or chipset drivers and then rename amdppm.sys or intelppm.sys back to their correct filenames.
 

TCP/IP Not Working and Missing Settings on LAN Interface

My Desktop/Storage PC went down during a power outage.  After power was restored, I found that I couldn't surf the Internet.  I checked the LAN interface in Network Connections and found that it didn't have any TCP/IP values.  Usually, they have at least 0.0.0.0 as its IP and Subnet Mask but in this case, it was just blank.

I tried disabling and repairing the LAN network connection but its TCP/IP values were still blank.  After I tried repairing the connection, I got this message - "Failed to query TCP/IP settings for the connection."  I also tried disabling and enabling the IPX/SPX and TCP/IP protocols and then tried removing them but all that didn't work.

After a bit of research, I uninstalled all my Network adapters in Device Manager and rebooted.  My network adapter was immediately detected again after startup.  This fixed my LAN network connection and I was able to surf again.

My 8-year Old USB Optical Mouse

Almost every improvement in mouse technology has rendered older generation mice obsolete. Eventually we stop using the older mice because the newer ones are so much better. That hasn't been the case with USB optical mice since there hasn't been any sign that a new mouse innovation is on its way to replace this older mouse technology.

I'm bringing up the history of advancements in mouse technology because I had a sudden realization that my 8 year old mouse didn't seem to be in any danger of becoming obsolete. Wireless mice haven't caught on because of their need for batteries and/or charging. This is why I feel that my 8 year old USB optical mouse is still relevant and will still be in use for a few years more.

Avacus, My Automatic Voltage Regulator (AVR) of Choice

The Automatic Voltage Regulators or AVRs that I use for my high-value personal electronic entertainment appliances are comparably highly priced and heavy. My reason for choosing Avacus AVRs is because of their simple good looks, slim design, their single 110v and multiple 220v outlets, and their quality which is evidenced by their heavy weight.