I may or may not be having trouble installing software from a CD onto an
XP Acer Netbook without a CD drive. I copied all the files to a
flashdrive and I think once I installed from the flashdrive and for sure
once I copied from the flashdrive to the HDD and installed from that.

I get one .dll that does not "register" (error messages below**)
whatever that means. (And the first time

I don't know if this is the fault of the software, the XP installation,
or the fact that I'm going from the flashdrive and not a CD. I didn't
suspect the last possibility until someone else on Amazon thought it was
his problem. Is copying to a thumb drive and installing from that ever
a problem?

Somewhere I have a USB CD drive that the ebay seller of the netbook
included, and I can find it if it would increase my chance for success.

If not that, then what can I do to resolve the error messages at the
bottom**?

Background:
I bought a new used car, 2005 Toyota Solara, and it has the check engine
light and codes 0171 and 0174, meaning a lean mixture. I've done the
easy repairs, cleaning the MAF sensor, replacing the PCV valve (which
was not leaking), and adding fuel injection cleaner (only 50 miles ago,
so I don't think it could have worked yet). The next step is to
*replace* the MAF sensor for $85, doing it myself. And after that,
likely parts are $140 and $150 dollars and $50, and I might need all
three and might need installation of one or two of them for another
$200. I hate to just replace parts without knowing which part is bad.
I was hoping to use this tool with its software to get more info about
the problem, from which "an experienced knowledgable mechanic could
easily diagnose" the problem, another webpage unrelated to this item
says.

It will probably take me hours to read about it and look at test
results, and even then I wont' know the answer, but I want to try. I've
already learned how the air/fuel ratio and 02 sensors work, pretty much,
including trim, but since I don't know what short term or long term trim
I have been having, or my fuel pressure (which most cars didn't report 5
or 10 years ago (I don't know if it has increased.) understanding things
doesn't help. I need the data. For example an inadequate fuel pump or
a clogged fuel filter can cause a lean mixture, although since the car
goes 80 without a problem, my primitive mind doubts that that is the
problem.

I have a year before the car is due for emissions inspection (its
schedule is independent of who owns it), but a) I don't want to pollute
or waste gas so I'd like to fix it asap, b) there are still some warm
days this fall.

**Installation error messages. Despite these messages, the program
started, and ran without crashing or error messages but didn't behave as
expected:

10 or 15 of these for different files, but only the first time I
installed it. How come they didn't recur the second time?:
"CRC error: The file C:\Program Files\... AHB)_1`2PF_P4.ddb doesn't
match the file in the setup's .cab file. The medium from which you are
running the setup may be corrupted; contact your software vendor."

How can the file not match the .cab file? Isn't it extracted from
the .cab file in the first place? If not, what is the .cab file for?


This one only occurred once, or conceivably it was the other one that
only occurred once and this one 10 to 15 times***.
"Error 1904, Module C:\Windows\system32\msxml4.dll failed to
register. HRESULT -2147023782. Contact your support personnel" AFAIC,
you guys are my support personnel.

What does registering entail? Can I register the file by hand. (It
sounds like it's installed, just not registered. But if it's not even
installed, maybe I can extract it by hand and move it to system 32? Or
maybe even find a copy online?

***From two days ago, I thought it was reversed but the errors are
listed in this order where I saved them.


I found and dl'd another copy of the software and installed it again and
this time I got one installation error message and then a fatal runtime
error message"
"This application has failed to start because tiswebapi.dll was not
found. Re-installing the application may fix this problem."