Creative Audigy 2 Value

M

Mike Warren

Hi Slobodan,
BTW why is your inf file name oem0.inf. Where did you find this file?
I guess in XPP windows\inf folder right? This is not a problem. But
I'm interested why you did not extract it from setup.exe?

The installation CD has 425MB of data on it and I wasn't sure which
files I needed so it seemed easier to get them from the XP Pro install.

I have now looked through the CD with a little more understanding
and found the correct INF file but using it made no difference.

It looks like I will have to let this problem remain a mystery to me for
a while until my knowledge of all this stuff gets better and I can revisit it.

I have a work-around (installing from the CD) which will get me out
of trouble for the moment.

Thanks again both of you for all your help.

-Mike
 
S

Slobodan Brcin \(eMVP\)

Hi Mike,

As you can see I guessed that you are using files from your XPP OS because of oem names. Nevertheless you should use the correct
file names from CD although like I said it is not a problem, just was interested in how did you get these files.

Reason for asking this was because I saw that you have told us that you were able to make it work trough manual work on runtime of
XPe. Which means that you have already all required XPe components present and I wanted to know for a fact whether you were able to
do this only by simply going to device manager and removing drivers and then reinstalling them by refresh or add new hardware
wizard.

If you can't make it wok in that way then setup.exe either bring some more files to your image so you should compare your pre
setup.exe and post setup.exe XPe image files. Or some registry entries are added by setup.exe which is uncommon but can be done of
course.

Also you can narrow down all files that you need and put them in one folder on XPe partition. So you will know minimum set of files
that you need, and then we can see why it is failing to work.

Regards,
Slobodan
 
M

Mike Warren

Hi Konstantin,
Off the topic but just to save you some dev time.

Install more RAM on your dev machine (the one that runs SQL Server
with XPe DB). Server will cahche most par tof the DB and on every
sequential Filter apply it will take less and less time.

I have 512MB. It's a Toshiba 2.8GHz notebook so upgrading will probably
be expensive. I'll look into it.
Also, on the www.xpefiles.com you will find XpeTools package
(Development Utilities/Main folder). If you use DependecyExplorer
component from there, it has a filtering feature that will take
seconds from you to serach in XPe DB for components that hold
particular: files, registry keys, registry entries.

I just downloaded it and will have a play.

Thanks.
-Mike
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top