ASUS Eee PC (model 1005HA maybe more)
WEP wireless networking doesn't work
This is by design! The wireless networking driver supplied with the Eee PCs is designed to work in open environments and secure wireless networking environments. The WEP security protocol was a good idea when wireless networking first started but these days it can be circumvented in minutes.
An open environment is one that is a public "WiFi" access point. Two good examples are McDonald's and Starbucks. Both companies have committed to allowing anybody to reach the Internet from their dining areas but to do that, no security has been implemented on their network.
Secure networks now use WPA or WPA2. In addition, these protocols allow two different types of encryption: TKIP and AES. Of the two, vulnerabilities have been uncovered in AES and exploits have been found that allow a malicious intruder to use the protocol to monitor private traffic on the network. When possible configure your access point to use WPA with TKIP. Your 1005HA will work with it out of the box with no special configuration required.
Nemesis Of The Roman Empire
The screen is inverted when the game is launched.
This is known to happen on Intel motherboards using the integrated video driver. First, upgrade your video driver. If that doesn't correct the problem, take a look at the graphics properties. On the more recent motherboards, there is an option to enable rotation. Disable this and save the settings. Once done, the game will launch correctly.
PCLaw JR
PLXML32 - Microsoft XML v3 or v4 could not be found. Call Alumni Computer Group for technial support.
This indicates the PCLaw JR software was not able to find the dll called msxml4.dll. To fix the problem: start->run; regsrvr32 msxml4.dll; click OK. This problem will arise after the installation of .Net v2.0, .Net v3.0, and some of the .Net / XML security updates that are automatically installed onto workstations.
QuickBooks
Error 15270 During Update
An update file is missing from Quickbooks. This generic error applies to almost all versions of Quickbooks. To fix it.... Help->Update QuickBooks; Select Update Now; Click Reset Update; Click the Get Update button. There will be a warning that the next update could take a considerable amount of time because the entire update will be downloaded again.
Error 2755 During Installation
The most likely problem is an attempt to install the QuickBooks product from a cd-rom on another system. Always make sure you have one license for each copy of QuickBooks you are installing and then install it locally. Intuit tracks all licenses used as they are activated and will always know if you have exceeded your license limit. Either purchase additional licenses through the QuickBooks product, contact a QuickBooks Pro Advisor, or call Intuit to purchase any licenses you need.
SeaTools
Drive Over Temp - XXX
This indicates the drive has exceeded its maximum operating temperature. When exposed to excessive temperatures, the platters and other internal components can become irrevocably damaged. If your drive is reported as exceeding the maximum temperature, immediately backup your data and seek the advice of a professional for migrating to a new hard disk so your existing Windows operating system, programs, and data will not be lost.
Windows Blue Screen
"inaccessible_boot_device" with error code 0x0000007B
Get thee to a disk recovery professional! Asking "my cousin's husband's friend" to fix the problem can result in a catastrophic loss of data. While there are several ways to fix the problem the recommended solution by Microsoft consists of starting up from the same disk that has the problem and running the last known good configuration. Because there are executables actively using the partition that will be repaired, the possibility exists that additional damage will be incurred. The best way to fix this problem is to use the repair console. If you don't know what this is, stop and get to somebody who clearly does.
With most home systems, this problem can be fixed by a professional very quickly. For systems utilizing RAID software, this problem is substantially more difficult to solve and is usually beyond the capabilities of most people.
Why did I get this error?
- Corrupted partition journal file
- Corrupted partition log file
- Corrupted partition tables
- Cache failure on the disk drive
- Defective block(s) on the disk caused one of the top three reasons to occur
If you can get to the recovery console, always use the /r option to fix this error. If files are lost or bad blocks are found, you should seek the advice of a professional for migrating to a new hard disk so your existing Windows operating system, programs, and data will not be lost.
If you have a tool such as seatools, always scan the disk for errors after this error. If errors are found, you should seek the advice of a professional for migrating to a new hard disk so your existing Windows operating system, programs, and data will not be lost.
If you are able to get the drive operating again, immediately backup your data. If you don't have a backup unit, there are many units to choose from on the market today. Try to find one that backs up your files, creates an image backup of the entire disk, and provides a recovery cd-rom in the event you need to recover to a new disk.
Windows XP Service Pack 2 Halts on "Checking Product Key"
If Service Pack 2 stops responding when it displays "Checking product key", the solution can be very simple.
- Start > Run
- Enter CMD and click the OK button
- Type cd /d %windir%\inf and press the Enter key
- Type ren oem*.inf oem*.old-fixmysp2 and press the Enter key
- Type ren oem*.pnf oem*.oldpnf-fixmysp2 and press the Enter key
- Type ren INFCACHE.1 INFCACHE.1-fixmysp2 and press the Enter key
- Close all of you open windows and shutdown the computer.
- Start the computer and press the F8 button once per second as soon as it starts until you see a menu.
- Select Safe Mode and press the Enter key
- Log into your computer and start the installation of Service Pack 2 again.
- After the Service Pack has been installed be sure to restart your computer.