You might give that a shot and see if it helps.

a clean enterprise 2003 R2, ..  no nlite, no rvm ..
base 610, all available packs and a few 3rd party.
Method 2, no KTD, the machine is currently running updates, and finisher cleanup was succesful .

it don't need much to break, I believe.

I spoke too brashly when I said I made succesful 2003 server using MSDN source.
And I apologise for having made you think I did.

the MSDN DVD has five OSes, and I was using base 610.
when I finally got to ENTERPRISE server 2003 WITH the packs, I got as far as (( 7zip.exe is not a valid win32 application ))

so I posted a lie, but in good faith.. what had happened?
the standard server version I tried back then had simply not been base streamed. the four other OSes were.. this weren't

(Mind you, I am pleased that the three XP version in there work...)

I also think I saw a bugtracker report that looks like it has a solution to our problem.

We have no reason to complain too.
Server 2003 is actually not officially supported in driverpacks and DPs_Base.

I hope that will change.

I only had those 4 driverpacks in the driverpacks folder.

I still get the same error just before Windows logs in for the first time:

Line 0 (File "C:\DPsFnshr.exe"):
for $i=1 to $exceptions[0][0]
for $i=1 to $exceptions^ ERROR
Error: Subscript used with non-Array variable.

I can't understand why I get this error! Its driving me crazy!

you can post the log on the way you used DPsBase..

I have made succesful 2003 server using MSDN sources.

I also realise there are issues when one uses DPs_Base  6.10 with KTD.
OTOH, default settings in DPs_Base  have not been cause of many issues?

did you select only those you wanted, while all packs are in the driverpacks and 3rdparty packs folders(s), or do you just put the packs you want in the folder(s).

I ask, for I wonder wether the error is caused by selection handling rather than exception filter.
(it could actually be a a combo of both, when unselecting files present in the folders.)

I tend to not put files I am not gonna use in the folders.
I know I can reproduce the error when  I do things to the files (like repacking some packs)

the exeption filters look for files, and if files in the expanded packs are not (no longer.. cuz of repacked) in there, it freaks with that error.

Thijs van leer played a nice tune in exception.

If I slipstream every driverpack, I get no problems.

If I slipstream any other combination of driverpacks, for instance
only the MassStorage pack, I get this error...

http://img407.imageshack.us/img407/7407 … rorgs7.png

This comes up just before Windows logs in for the first time.

Using the latest BASE (v6.10) to do this.

Post #9 here explains the exact same thing, but theres no replies after that...

http://forum.driverpacks.net/viewtopic.php?pid=5674

This thread explains the same thing but again, theres no solution to it...

http://forum.driverpacks.net/viewtopic.php?id=748