Andy's Technotes and commentary

Dell 6000 battery problems

admin — Fri, 20 Nov 2009 20:08:27 +0000

I purchased a battery for a Dell Inspiron 6000 from eBay seller WebExpress4u.
When installed into the Dell I got:

“Warning: The battery cannot be identified. The system will be unable to charge this battery. Press any key to continue.”

And true to the warning the battery would not charge.
I searched for a solution on the internet and flashed the BIOS to the latest rev and the problem remained.
I emailed the seller and got a form letter response about RMA-ing the battery back.l.
I sent the battery back and got a UPS delivery confirmation on 8/10/09.
After three weeks I emailed the seller. They claimed they had never received the battery.
Within a day or two they found the battery and sent me a new one that had the exact same problem on two different Inspiron 6000.
My best guess is the Dell BIOS checks the battery for authenticity and refuses to charge a non-Dell battery.
I asked the seller for a refund and got it within a couple days.
I am out the $7 to ship back to the seller but at least they have not asked me to return the unusable battery at my expense.

At least the seller did not require me to return the second incompatible batter, not that I would have anyway.

HP laptop dv2000 aka dv2500 dv2710us is not Windows 7 compatible. Coprocessor error.

admin — Fri, 20 Nov 2009 20:05:39 +0000

Tried Windows7 32 bit clean install on this notebook.
Loads and runs but device manager reports driver errors on Coprocessor and two “Base Devices”. The base devices are the card reader and the error goes away when you install the Vista card reader drivers from HP.
No chipset drivers available from HP or Nvidia for this model.
Tried HP Vista Nvidia graphics driver in “compatibility mode”. Installed but did no fix the error.
Coprocessor error is intractable.
Upgraded BIOS did not help

HP+Nvidia=crappy lappy in oh so many ways!

DNS won’t resolve following MCafee uninstall on Vista

admin — Fri, 13 Feb 2009 00:12:26 +0000

Symptom: user installed Mcafee on Vista Home. Internet connectivity lost. LAN and router ping OK. Tried opendns as static DNS server. Can PING OPENDNS by IP address.

Fix: from command line as administrator:

NETSH WINSOCK RESET

Reboot.

Problem solved.

AMD v Intel?

admin — Sun, 30 Nov 2008 20:12:43 +0000

How can you trust computer to a company that makes a heat sink and fan that is as awful as the stock fan included with retail boxed Intel socket 775 processors?
One flex of the motherboard (like when inserting a video card) or a jar of the computer and the heat sink comes loose. Awful.

Dot NET (.NET) cleanup tool

admin — Fri, 07 Nov 2008 20:15:03 +0000

System: HP M7480n.
Symptom: User can power on for a few seconds and the computer shuts itself off.
Problem: diagnosed and replaced power supply.
Visual inspection showed defective capacitor on AT X1600 video card. Replaced with ASUS 3450 ATI PCIe.
Catalyst Control Center software bundled with the new card requires .NET 2.0
All attempts to install .NET 2.0 failed, both in Windows Update and the using MSI redistributable.
I tried to research the problem in general by Google searchin .NET 2.0 install problems.
Aaron Stebner’s Web Log appears to be a good source for technical information about .NET.
I ran Aaron’s .Net Setup Verifier and it looked like .NET 1.1 was ok but 2.0 had partially installed.
The MSI redistributable produces better error messages so I looked at the System Event log and found a 25015 error which I cut and pasted into Google.
This lead me to the dotnetfx_cleanup_tool.exe which appeared to hang itself prior to completion.
I looked at the Task Manager and it saw SPYSWEEPER was causing the system to hang even though SpySweeper had been disabled through the UI.
I waiteded it out and eventually the cleanup tool finished successfully and cleaned out all the .NET installs.
Upon reboot I was able to install .NET.

There is a strong case to be made for uninstalling all the SpySweepers, Spyware Doctors, Zone Alarms and Internet Security Suites and even antivirus software when chasing down software problems. Even though the UI for these products says they are disabled….they arent. They impede the software troubleshooting process. One could even make the case that these security softwares cause as many problems as they prevent.

Error 619

admin — Wed, 06 Aug 2008 18:38:32 +0000

Error 619 result following a dial-up attempt is often caused by a bad or poor quality modem.

Wii interferes with WiFi

admin — Mon, 04 Aug 2008 20:03:17 +0000

Add the Nintendo Wii to the list of sources of WiFi 802.11x interference. The Wii shares the unregulated 2.4 ghz spectrum with such items as cordless phones, wireless keyboards, headphones, cell phones and older microwave ovens.

Consumer affection for expensive, slow and unreliable wireless networking is baffling to this blogger.

Ping: transmit failed, error code 65 fix

admin — Fri, 18 Jul 2008 18:22:28 +0000

This was caused here by a failed or partial uninstall of ZoneAlarm. Deleting the contents of the ZoneLabs folder under System32 and the contents of \Windows\InternetLogs fixed this problem.

Dell 3000 audio driver issue

admin — Fri, 18 Jul 2008 18:22:09 +0000

Analog Devices ADI 198x Integrated Audio driver A022 will not load on Dell Dimension 3000 and fails with “device object not present”

Use driver A021 instead.

More Vundo

admin — Sun, 11 May 2008 16:29:42 +0000

I ran yet another malware detector on the drive mentioned below.
Microsofts Live scanner:
http://onecare.live.com/site/en-au/default.htm?mkt=en-au

detected 8 more VUNDO infected files.

The Live Scanner is a nice tool.