You have basically reverted an M2 install to an M1 install without the benefit of cab compression.
Good thinking and my respect. big_smile 

Let's consider some options to improve on your method (if possible).

notes:
Since you are moving the drivers to the $OEM$ folder they are copied during textmode (16bit mode).
It is preferable to copy them from presetup because in GUI mode we are useing 32 bit drivers.
Ideally we would copy the original packs which would mean a smaller transferred size and at a higher speed.

It may be a textmode copy is unavoidable. I am not convinced that is true just yet... but let's assume it is.
     
  If they must be copied during text mode may i suggest you do it this way...
     move the OEM folder to the  \\server\autoinst\xp\i386\$oem$\$1\ folder.
     creating a \\server\autoinst\xp\i386\$oem$\$1\OEM\ folder (replaces step 4)
        This will reduce the size of the text mode copy from 1.5 gig to 300 meg.
        This will be a huge reduction in transfer time and network load.
        This technique will also eliminate steps 5, 6, 7, 8, and 9. (what happened to step 10?)
     use this modified version of presetup.cmd (replaces steps 11 and 12)

REM +==========================================================================+
REM |                                                                          |
REM |   This presetup.cmd file was dynamically generated by the DriverPacks    |
REM |   BASE, to work with the DriverPacks without any further editing.        |
REM |   However, if you would like to add some custom functionality, you can   |
REM |   edit this file without any problems. Just take into record that this   |
REM |   file will be erased if you run the DriverPacks BASE on these Windows   |
REM |   installation files again!                                              |
REM |                                                                          |
REM |   With special thanks to:                                                |
REM |   -Pyron, a06lp and iLE for their help with this method;                 |
REM |   -schalti for the optional 'Keep the Drivers' system and Pyron (again)  |
REM |    for turning it into an executable.                                    |
REM |   -SuperTibaldoKart for creating un7zip.exe                              |
REM |                                                                          |
REM +==========================================================================+


REM +==========================================================================+
REM |   Finding CD/DVD driveletter is modified to point to system root.        |
REM |--------------------------------------------------------------------------|

SET CDDRIVE=%SystemDrive%


REM +==========================================================================+
REM |   Decompressing the DriverPacks to the harddisk - using un7zip.exe.      |
REM |--------------------------------------------------------------------------|
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\DP*.7z %SystemDrive%\


REM +==========================================================================+
REM |   Copying/decompressing the files to finish the installation.            |
REM |--------------------------------------------------------------------------|
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\bin\*.7z %SystemDrive%\
COPY /Y %CDDRIVE%\OEM\bin\DPsFnshr.ini %SystemDrive%\
IF EXIST %CDDRIVE%\OEM\*.ins COPY /Y %CDDRIVE%\OEM\*.ins %SystemDrive%\


REM +==========================================================================+
REM |   Scanning for driverdirectories.                                        |
REM |--------------------------------------------------------------------------|
%CDDRIVE%\OEM\bin\DevPath.exe %SystemDrive%\D



REM +==========================================================================+
REM |   Deleting the source 7zip files used for the Network install.           |
REM |--------------------------------------------------------------------------|
IF EXIST %CDDRIVE%\OEM\  RD /S /Q %CDDRIVE%\OEM



REM +==========================================================================+
REM |   Disable Driver Signing Policy and keep it disabled.                    |
REM |--------------------------------------------------------------------------|
START %SystemDrive%\DSPdsblr.exe


EXIT

if it is possible to copy them from presetup.cmd that would be even better.
Then it would only be necessary to change the below lines in presetup.cmd
This would eliminate copying the OEM folder in text mode to the local drive.

the copy and extraction would be a single step process that takes advantage of the improved processing and IO performance of the PE platform. It is alsoexact same technique DriverPacks uses and supports with standard M2 CD / DVD install (that we support) wink

IE
     move the OEM folder to the  \\server\autoinst\xp\i386\$oem$\ folder.
     creating a \\server\autoinst\xp\i386\$oem$\OEM folder replacing steps 4, 5, 6, 7, 8, 9 and [potentially] 10 )

REM +==========================================================================+
REM |   Finding CD/DVD driveletter function now sets Network source location   |
REM |--------------------------------------------------------------------------|
net use z: \\server\autoinst [pass /user:admin /Y]
SET CDDRIVE=Z:\xp\i386\$oem$

If the servername or share name are not 8.3 then it can be in quotes and the [pass /user:admin /Y] is optional
IE    net use z: "\\MyServerHasLongName\AutoInstallationFolder"
or    net use z: "\\MyServerHasLongName\AutoInstallationFolder" Pa55w0rd /user:Administrator /Y

Thanks so much for sharing... if you dare to try my ideas can you give us a further update!!!

your one of the people who contribute, making DriverPacks a great place to be. thanks!

PS you gave no details on winnt32...

4,452

(38 replies, posted in DriverPack Graphics)

can you post your setupapi.log (we only need the relevant section not the entire file)

the problem is not the driver for the video card per se.

I belive the problem is the video card drivers support for your monitor see this thread...

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

It seems from your screen shot that you might be useing a wide screen?

It may be that this is a result of the image that you used is not the correct size / format, and can not be fixed without replaceing the image itself. It seems that you have changed the default image used for boot and shut down and it may be that you created your own problem by changing it.

4,454

(74 replies, posted in Vista-Tool)

Working on it too... and reading a lot...

4,455

(3 replies, posted in Other)

Hey Siginet...

It takes most (but not all) of my spare time to code base.
I would be honoured to donate what time is left to your incredible projects.

jeff

4,456

(74 replies, posted in Vista-Tool)

Now that is what I'm Talking About!!!!

I don't intend to run Vista as my primary OS i just need to be able to install and test it efficiently.

i think the key is in the $OEM$ (or network install equivalent) folders

4,458

(5 replies, posted in Dutch)

thanks jaak... as we say in america "it's all dutch to me" wink
but i'm learning...

4,459

(74 replies, posted in Vista-Tool)

any progress on a cheat sheet "learning pains" for graphics... he asks with baited breath...

I feel pretty comfortable with doing it, or assisting with it, but... you are the "master"

try running a tracert
i think you will find the fault is not with the server...
we (the driverpacks admin's) have not altered anything.

4,461

(74 replies, posted in Vista-Tool)

well i was thinking of you more as a severed right hand wink ... but i accept.

4,462

(5 replies, posted in Dutch)

Ik spreek Nederlands niet en ik gebruik google om naar Engels en http://www.freetranslation.com te vertalen/ om dit naar Nederlands te vertalen. Ik verontschuldig me indien het heel goed heeft niet gewerkt.

801RC2 is het recentste verkrijgbaar.

De nightlies werkboete, meestal.

U bent welkom hen te gebruiken en wij kijken altijd voor meer mensen om hen te testen.

Vertel alstublieft ons hoe zij voor u werkten. Bedankt voor het zijn hier! smile

you are (of course) quite welcome.

It is quite refreshing to find quality contributors to the greater good of the community

4,464

(74 replies, posted in Vista-Tool)

i have gone to MS and gotten the WAIK and documentations
step 1 - i will be reading them tonight.

step 1.1  polishing some rough edges on base rc3 so i have clean code to start on vista.
(if xp sp3 goes live i will offer rc3 on the news page for a few days or a week 
and if it fairs as well as its predicessors publish it officialy)

step 2 if jaak is correct it will take me a month of evenings to code.
too bad i need to make adjustments for the different versions of vista or it would be quicker.

step 3 and possably the stopper. we need testers...
XP users outnumber vista users at least a 1000:1
We have about ten testers for XP
applying what we know i will have .01 (or less) people to test vista packs.
it will be tough to maintain our quality control when our vista testing team is a severed left foot. wink big_smile tongue

4,465

(3 replies, posted in Feedback and Support - DriverPacks Base)

that warning is associated with method one
if you use method two then it will not appear or affect you.

4,466

(74 replies, posted in Vista-Tool)

well everyone has been after me to get on this - and i am ready, willing and ATM have the time.
i was hoping someone would toss me a bone... i guess a "messy" pack is kind of a bone.

perhaps reinventing the wheel has the advantage of possibly not heading down the wrong road to start with.

are you sure it's not white out... wink (very old blonde joke sorry) big_smile

no problem

http://unattended.msfn.org/unattended.x … f9dc439e6/

use steps one and four...

since your original machine is useing standard IDE your already half way there.
in most cases setting the driver to standard IDE before shutting down / imageing
is the forgotten and most important step

did you notice your title?...

you need to give us some details to go on... or nothing happens

can you get to the download page?
are you running a software or hardware firewall?
which version of base?
what packs do you have?
what is your OS?
do you have internet connectivity? (it would seem so)
are you behind a proxy?
what do you mean it is "connecting"???
if you were connecting then you wouldn't be posting for help???
do you assume we can read minds?

it is working for me right now...

yes check out these two posts.

mass storage instructions http://forum.driverpacks.net/viewtopic.php?id=2461

3rd party DriverPack instructions http://forum.driverpacks.net/viewtopic.php?id=5

Remember that mass storage drivers for text mode,
the ones required to create / choose a partition at the start of the install. (the F6 drivers)
are only added from the mass storage pack.

we do have a search feature available in the menu bar at the top of every page wink

have a nice day.

4,472

(74 replies, posted in Vista-Tool)

Muiz i don't think we are communicating well.

I thought the idea was for me to add the required code to base ?

I had not planned to add the tool to the base code...
so that means i will have to start from scratch with no documetation.

so i guess you are not in a hurry for this and your not intending to help?

unfortunately that is a no no... and we can't recomend it to others.

licence violation.

Sorry that is not supported.

you were right jaak he is a pie rat...

Love to hear the whole story...