I've got the same problem with Base 7.05.2, LAN 7.05.1 and MassStorage 7.05. I want to slipstream driver packs into Windows XP SP2 MUI. I'm using Method 2.

I noticed, that slipstream with 7.04 and some older driver packs works fine. When I run 7.05.2 after running 7.04 even this works fine.

Maybe this could help to fix this issue.

Thanks, Elix

elseIf $set_qsc=="no" then
    local $destDir = $slip_dps_destDir
endIf

i made it

$fi_destDir = $slip_dps_destDir & "\" & $_BPEout

this added an extra \ to the path for slipstreaming when useing m1 (i guess we didn't test M1 before release)

Im almost done with a test run of 7.05.2

MORE fixing is expected.

If you look at the error message, there are two backslashes after the 'D' and before the 'DriverPack' toward the end of the error message.

Also, if I look at the file structure of the $OEM$ directory that's located in my target directory, I have:

$OEM$\$1\D\D\S\

then directories with names like Y, TR, T, SM, and so forth.  Should there be two D directories after the $1 directory?  Just curious...

i found you could click the cancel button on the box below the error and when you pressed ok it would end... but before I found that i did have to use the 3 fingered method....

Brett

Failed to CAB compress c:\download\XP_Driverpacks\tmp\DriverPack_Sound_B_wnt5_x86-32.ini to C:\download\SP2+\$OEM$\$1\D\\DriverPack_Sound_B_wnt5_x86-32.in_.

I can click OK, then get a second box saying that the temp directory can't be deleted...and it hangs.  I can click OK repeatedly but the box keeps reappearing.  The only thing that will end the program is to 3-finger salute, Task Manager, then select the process and end it.

I looked at the log file, but it gives no further detail other than the above message.

(it looks like M1 has some hardcoded folder locations in the module, and you can compare the location of the file that cannot be cabbed or copied with the folder content of the un7zipped pack.. This copy error is what I encountered.)

I tried method 1 today, and also had a problem.
(not same as yours... but still, a critical one)

Method 2 is the faster method of the two, so M1 is tested less often.
For now, I suggest you build a disc using method 2, while we try fix these errors.