zamzon

Hi John, thank you for your answer: > I suggest to start with a fresh copy of your original CD files/folders and do all your integration in one nLite session. Unfortunately I'd just like to add some SATA drivers my board needs to an already pretty nice enhanced installation. So this is no very attracive solution to me. > It sounds like you have nLited the same source more than once. This often leads to errors that are multifarious and strange. But to make the behaviour less 'strange': Has anyone any idea if nLite (or cablib) might 'expect' anything in or of the driver CAB? How does the CAB file corruption check (introduced in 1.3?) work? Can I get any closer to the source of the error? E.g. the results of cablib.dll which obviously get's interpreted by nLite (maybe in the wrong manner)? toolazy wrote: > 2) When I tried to unpack the DRIVERS.cab file using Winrar 3.70/3.80 & powerArchiver 10, I got an error telling me it was corrupted, but the file worked fine > when I tried extracting it using 7-Zip & Universal Extractor, no idea if this means anything just thought to put it out. O.K. There seems to be different 'feature(sets)' or versions of CABs. I'll try to dig there.. Thank you.

How can nLite (1.4.9.1) or the cablib.dll claim that a driver.cab is corrupted (dialog box), although the very same file can be tested (verified) and unpacked (extraced) by other programs? I also tried 1.4.8 and another PC (both XP one SP3 other SP2). Both systems have at least 1GB and plenty of RAM free. The driver.cab is already modified once (by nlite) and about 77MB. An untouched driver.cab can be extraced and repacked successfully. I found some other users, which faced the same error message, but there where no hints or answers to this issue, yet. Thank you. Thomas