@mikelm: What you describe (not remembering the settings for DriverPack MassStorage text mode and QuickStream Cache), is impossible - UNLESS you've opened the DPs_BASE.ini with a text editor that's using a write lock. You can ask any one on the forum, but you're definitely the only one with that problem. You must be doing something wrong, probably without realizing it - and that's something that happens to every one once every while.
You could try Unlocker to find processes that have locked the DPs_BASE.ini.

When I ran the betas and release candidates and encountered a problem with one method, I would save the logs to a folder.
Then I deleted the entire content of DriverPacks folder, and unpacked the Base download to it all over again.
This created fresh base files.
Then I'd copy the driverpacks into the driverpacks subfolder, and also copy the source files to a cleaned out folder.

When things improved, I did some trials with sources I had done another method DriverPacks slipstream on.
But when I bailed out DURING a slip (lets say because I saw the path limit was exceeded), I would usually start anew, using fresh content in the folders.
I thought I'd better spend four minutes loading a fresh copy, than waste 50 minutes while running a trial setup that got botched because I made it difficult for the slipstream process.

all in all, DPsBase detects quite a few things that happened previously.
I often wondered wether I had more luck than others.
I also made sure I had plenty room on the hard disk.
((after twenty trials or so I had less than 28 Gb free on a 160 partition, so I moved 90 giga to another drive.. ))

I think you must have at least ten percent free room (a windows annoyance), plus 2 giga for the temps, so twenty percent free room is better..

I don't think folder permissions would be an issue here.

if it can not create the DPs_Base.ini, you might try unpack 6.08.6 in a fresh folder, and try again.

i only delete QSC folder, all ini´s and logs and make an new BTSinit ...

and also i every time cleared the QSC folder but this not works ...

Sereby's is like a copy of RVM's integrator in German...
I would not know wether there are bugs left in either one.

in RVM's integrator, you must click advanced, to enable the unicode to ANSI tool.
I would imagine this is the same in Sereby's.

And then please DELETE the directory I mentioned. Then slipstream again. The QuickStream Cache will now have been rebuilt and it should be a valid one this time.

1. with a pur xp pro sp2 now it works...

2. with a pur xp pro sp2 + sereby´s it works too

the error can be reproduced any time ..

i used a blank xp, then i put sereby´s updatepack , then i make changes with nlite and at least i use Bâshrat the Sneaky with M2

did u have icq ore msn ? this would be easier to communicate and find the problem ..

the other question i have is why the base programe forget every time i started it all the konfiguration? every time i must set all  information new. which driverpacks an anything else ..

QSC\wnt5_x86-32_uni_DP_MassStorage_608_textmode

?

it looks like it had a method 1 done on it before, and/or sereby's
(which I have not used before)

the M2 I just did was done on a source where the hotfixes were slipped in with RyanVM integrator, and the last six versions I did like that gave no error whatsoever..

I just ran a method 2 slip, (all packs..)

ALIIDE.org and ALIIDE.SY_ are both present here.

this makes me think you don't see the file, even when it is there...
in windows, how are folder options set?

i only found an ALIIDE.ORG in the i386 no aliide.sy_ 

i also couldn´t believe that there is a difference between uppercase and lowercase during instal

have you  msn oder icq so is it easier to communicate .

When i had this issue the atiide.sy_ was in lower case in the i386 folder.

Converting the files in the i386 to UPPERCASE will fix it but having said that the latest DP base should do that for you automatically i dunno why it did;nt for you.

That could indeed be the cause. But it should be UPPER case automatically now... Could you please verify that, mikelm?

Converting the files in the i386 to UPPERCASE will fix it but having said that the latest DP base should do that for you automatically i dunno why it did;nt for you.