Pappy said:
Thanks. I appreciate the reply. Misdirected as it is. There's an easy
solution to your dismay. Just don't answer my posts at all. If you read
the
original to begin with you would have seen that I started off with an
appology for not really knowing how to go about this and an offer to
accept
minimal help, not stupid answers. If you can't provide that much stop
wating
time. All anyone has to do is ask for more info. I'd be more than happy to
provide it but I just didn't and still don't see the need to clog up the
place with wasted words, probably pretty much like these. So Thanks again.
Nope, your blame shifting is not accepted. You really expect the car shop
to know what to fix when you simply state "it's broke"? You had an error.
You actually believe that asking vague questions which require someone else
to yank out more information is the correct manner to establish a thread
requesting help? When starting a discussion, provide enough context so the
reader knows what you are asking and provide enough details to let them
figure out how to reply. Newsgroups are not sitting down with your friends
or in chat rooms with endless rounds of minimal content in each post, or
like talking on a telephone. There is no immediacy of communication in
newsgroups. That's why I included the links for you to review on how to
better compose a post that help the users figure out enough to help you.
No, they are rigidly enforced rules but only to help you figure out how to
compose a post that can actually be answered. You were looking for an
answer, right? Consider how undetailed was your post, Joe matched with an
equivalently undetailed answer - because only YOU know *what* was the error
message on which to go do a search.
From the other subthread, you mention something of the error message (but
never do reveal the EXACT error message or WHEN it occurs). Does it occur
when you start Windows but before you login? Does it occur when you login?
Does it occur when you try to use your scanner's software, or software that
can use the scanner for input? Did you install the HP software *before*
connecting the USB-attached scanner?
Sounds like you installed the wrong version of the software. Did you
install it off the CD that came with the scanner? Did you download the
correct version of the scanner software? Will the HP software install in
Windows safe mode (to eliminate any conflicts with whatever else you are
loading on Windows startup)? You could also use msconfig.exe to disable all
startup items and reboot into normal mode to do the install. Have you used
msconfig.exe to see the startup items to note if any of the .dll files
mentioned in the errors are getting called by a command during startup? Did
you disable your anti-virus scanner and any anti-malware scanners during the
install?
If after a reinstall the errors reappear, use msconfig to see what are the
commands for loading programs on startup. I suppose it is possible that the
path to the .dll file being called by rundll32 is wrong and needs to be
fixed. After an install, what is the path to those .dll files? Did you
install under an admin-level account and then login under a normal account?
If so, did you check permissions on the install path for those .dll files
(if they aren't in a common path, like C:\Windows)?