For your fingerprint reader - if your system is set to logon via FP, how are you getting in if the reader isn't appearing? Did you reset the BIOS or have a separate password set up? Open your Task Manager and see if you have DPAgent.exe running (Processes) and the DpHost Service (Services) running, and if you have the Digital Persona FP Icon in the System Tray. If the processes aren't running your FP won't work.
Try holding the Shift key down and running your finger over the scanner - if the processes are working you should automatically get a "Create Fingerprint Logon" window.
You can check your current system's serial number (label under the remote on the left side) against the original invoice from when you purchased it to see if it's the same unit. If they've roughed it up I'd like to know - making a list of issues to send to some HP friends. If it's different, it's always possible they gave you a system that was sent in and refurbished, but wasn't entirely fixed. Such is the state of HP's Support these days.
It would also help to know your system's Product # (on the label under the left side - PRODUCT, not Model # - usually ends with a #ABA) so we know which HDX you're talking about, and your OS Edition and type (32 or 64). Also, are you running any update processes in automatic?
Your original problem sounds like it was caused by a file transferred from your desktop. Since you haven't put down your system configuration or your desktop's, it's hard to say, but if your desktop is an XP system and you didn't use a cable specifically for XP - Vista transfers it could've caused the kind of problems you were seeing.
As far as your current problem with QL button possession, as someone else has pointed out, there have been problems with HDX assembly of the QL button component not being fully attached at certain points - you can disassemble it to find out, and it's not that hard to do. The manuals are easy to access, but you might want to download it before you go back.
One thing I've noticed is that you haven't said anything about whether or not you've run all of the Windows and HP Update programs to update your system to the latest software and driver configuration, or if you have updated anything, where you got the updates from and how you installed them.
No one should ever assume that the configuration you receive your system in will work perfectly after your order changes the baseline configuration. In today's world, nothing could be further from the truth, as people just don't understand how systems are manufactured, configured and delivered, and how support works (or doesn't) when they receive your system.
Remember that these things are being made by the hundreds and thousands. All PC's, be it notebook or desktop, have a model series base configuration - the template for all others in the series to go by. Those systems are configured & loaded with applicable software and custom vendor (HP) changes, then set aside. As orders are placed, the customer's desired configuration is assembled by changing / adding to the base configuration, then it's sent for a final check then shipped.
What's important to note is that the OS install and the drivers for the base configuration are usually installed weeks or months prior to you ever even ordering it, and of course changes (driver updates, Windows updates, etc) are to be expected during that time frame. Engineering issues may have come up with a certain component, something may not work properly, any number of things, as well as anything that may arise from any custom configuration components in your order. The 'net, while changing the way we live, has unfortunately given businesses a way to slack off of Quality and Product Assurance. System or Game not ready? No Problem!!! Ship it out so we can get $$ rolling in. If there's a problem, the customer can update their system with an update via the 'net.
And therein lies the problem - the vendor expects the user to update their system to the latest drivers and software configurations available, but the majority of users don't know how to correctly update their systems. Instead of using the system to do it for them, they try to do it manually, and in some cases wind up installing a driver that didn't need to be updated. Updating a driver just because there's a newer version is just plain stupid - sorry to everyone else, but frankly you should only be replacing a driver if there's a good reason, and just because it's newer isn't one of them. If it ain't broke, don't fix it - or even try to.
There's other things you can check as well:
First - click on Pearl (start icon in Vista) then All Programs, then click on the Maintenance folder. When it opens, click on the "View Problem History". If you're having intermittent problems there's likely a record of it that'll give you a clue as to either the process responsible, or whether it's likely a hardware problem rather than software/firmware.
Another question to also ask is that even though you're in the big sandbox, are you using your system in environmentally stable conditions or is it exposed to desert thermal fluctuations on a regular basis? Also, are you running it on AC or DC, and if you're switching between both, does it occur on both power options, and are you using an AVR UPS for your AC power?
(Yes, I know that the AC is converted to DC via the transformer for anyone thinking I don't know that. The reason for asking is that system power is more stable when the AC adapter is used rather than just battery power alone - unstable voltage can cause more than one problem and will appear to be intermittent faults. If you've never experienced this, let your battery fall to critical levels with several programs running and watch what happens.)
One way you can check for a thermal intermittent is to download and install HWMonitor (CPUID.com), then note the thermal conditions when it happens to see if there's a specific thermal condition that triggers it.
The reason I'm focusing on a hardware intermittent is because of what HP found, or in this case didn't find. The reason they just replaced / re-installed the OS is that they couldn't find an actual problem using in-house diagnostics, nor could they recreate or find the problem. In those kinds of cases they have limited options, so realistically unless you have a hard fault you can point to, you're just wasting time by sending it to them. And don't take it personal that they didn't pay attention to what you told them - I'm guessing that they're taught to ignore anything the customer says, which if you think about how many thousands of idiots there are that they must deal with, probably isn't a bad idea. Remember as techs ourselves we're used to providing much more personal service than HP and other vendors do these days. Also, you've got to remember that dealing with anyone who lives in a country where they would rather worship a cow and starve to death rather than eat it ain't playing with a full deck anyway. Just an observation......
If you're using the system exposed to the extreme thermal variants of the sandbox, constant board expansion due to thermal changes can cause any borderline SMT component connections to fail, and any such problem wouldn't be seen unless it was a clean failure or the system was tested at all thermal conditions the unit was exposed to when the problem occurred. HP techs these days aren't smart enough to figure that out unfortunately. Of course if you're using it in a conditioned, stable environment that's different, but given the situation there I can't believe that you're enjoying constant air-conditioned comfort on a regular basis.
Keep in mind also that it doesn't take much pressure either on or near the QL buttons to initiate the process. You can start a process just by getting your hand or finger close enough to the QL buttons while pressing one of the number or F keys. Even a microfiber cloth sitting on top of them will trigger them.
A way you can narrow down a QL button fault is to use its Sound function. Go to your Control Panel, then open up Quick Touch and click on the Sound option. You'll get a window with 3 Sound options with checkboxes - #1 is silent, 2 is a beep and 3 is something best left to your imagination as to what it is.
Check either #2 or #3 - if your problem is in the sensors itself, you should hear the sound the next time you get an unintended start.
As far as the QL button LED's going on and off, you do know that the theatre mode button turns those LED's off right? The reason I mention it is that if the problems are connected, that'd be the first place to look. Also, if you touch it intentionally or unintentionally and aren't aware of what it does, it could appear to be a problem when it isn't. The theatre mode button has the projector icon on it, in between the QuickPlay and DVD buttons.
Even though your audio problems sound more like a corrupted driver or Windows file, the audio problems you describe could be caused by any number of things, including ITunes (HP systems have had problems with ITunes), even the audio files you're playing or how they were recorded. Does it do the same thing with hard-copy files (DVD or CD based) rather than MP3's or other files downloaded into your system? If you haven't checked, see if you get the same problem.
Let us know more info about your system and what you've done to it as far as updates - it'll be easier with more specific information.
Click to expand...
Problems? See this thread at archive.org.
