Need help on this, after I install winxp on my notebook and install ALL the drivers. I check on my device manager that there is still 1 unknown device left after that I test it on a desktop computer and its still the same I tried to remove some update pack but still its same. the preset that I use is the same preset I use on the previous version of nLite and I didnt encounter this kind of issue.

I hope you guys can help me...

Thanks!

I would be more worried about the PINK Start button!

Can you report what is under Details?

LOL!!!

on the details tab

drop down box
Device Instance ld

big textbox
ACPI\GENIUNEINTEL_-_X86_FAMILY_6_MODEL_15\_0

thanks for fast reply

That looks like a CPU ID to me.....

HEY NOW!!! I made that theme.

That sounds like Chipset drivers. On the other machine it most likely is a different driver, but the same "Unknown Device" status may have thrown you off.

edit: in some cases when you get an unknown device you can right click the "Unknown Device" and select uninstall. Next time you reboot it sometimes recognizes the device and magically finds the drivers for it. Kind of a strange XP quirk. It could also be some obscure driver like HECI or something, but most likely chipset.

Hope this helps!

Do you have one of those bumber stickers that says "My other computer is a Tangerine Imac"?

LOL naw mac really sucks...

I made the theme for my wife...

Wow this forum is like Melrose Place. You're either married to efrain or your wife has some splainin to do bout how he got her theme! If you are married to efrain, then that might explain the pink start button

hmmmm... ill try to remove the cpu id v1.45..

thats strange, I use the same driver before and I didnt encounter that.

kels themes are cool particularly the Kimbra theme my gf really loves it!

HAHAHAHA!!! LOL!!!

AAHAHAHA Thanks for the nod efrain...

You might like the slim version of midnight, let me upload it for you...

Sure my pleasure!!! :D:D:D:D

Thanks Kel!

K uploaded to the last post

sure you did. sure you did

Unknown Device solved!

CPU ID v1.45 is the culprit!