erukian

Windowblinds 5 has full support for x64. That should keep you happy with the eye candy.

I see what your trying to tell me. I did as you asked, used expand.exe and yes, the files were missing. I used expand like this "expand DRIVER.CAB -F:* C:\DRIVER" and it errors out during expanding. I'm really confused why if I have a corrput driver.cab, then how come all my installations w/o nLite went fine? from pre-sp1, to sp1 slipsreamed, to sp2 slipstreamed? Do i have to contact MS to let them know my copy of XP is bad to get a replacement? -Joe

How can the cab be corrupted if the files exist on my Pre SP1 XP Professional CD? EVERY time i start from scratch, download the latest nlite, then the SP2 network install from microsoft. I copy the files off the CD to C:\XPCD then i slipstream SP2. At this point if I make an .iso image using nlite i get _no missing files_ but if I actually use nlite's features and try to remove say the language pack or integrate RyanVM or anything, it'll rip out those files listed earlier. I just can't see how that's a problem on my end. I love nlite, but right now i'm forced to manually just pull the .dll's and .sys files that XP requests out of my pre-sp1 driver.cab and then drop them in C:\windows\driver cache\i386 so XP doesn't freak about missing files when i do driver installations. -Joe

I've had the same problem's since i've been using nLite... I normally just open up the pre-SP1 driver.cab and copy the files out of it I need for the setup. Please mr. nlite creator, me and a couple of my friends love nLite but hate how it's ripping out so many files listed earlier in this topic, it's just really annoying!! I love your work but this is enough to make me not even use the software and do everything by hand post-install. -Joe