Search options (Page 178 of 213)

try the fix listed above

thanks twig,

It's so awesome the way you keep the 3rd party DriverPack's organized and indexed.

it is a job - and like so many of the things we do, is in danger of not being appreciated for the work that it is.

i was thinking that i wished i could do something to reward you
and it hit me - how about some recognition and a new tool for your arsenal.

Jeff

shoot the HWID's at us and we will have a look see...

i am getting my head wrapped around the idea...

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

galepo has a tool that may just save your bacon ...

forum rule: English is required for posting, my apologies.

yes what you said.

I thought the old machine was still running in which case half the work is done already.

http://tracker.ryanvm.net/rss has the .net torrent links.

I don't think your post is off topic .net might be part or all of his problem too.

so
1 image related
2 .net related
3 KB883667 related

you are mistaken about #3 sir...

the $1 folder is COPIED to the local HDD during text mode

yes they are "installed" during PE (GUI setup), but that was not what i said was it? Nor was it my my point.
Please read more carefully.
it was about copying them from the source over the network to the destination that i was referencing.

my first method copies 300 meg in text mode.
(This may be our only choice if the NIC were not supported by PE prior to presetup and before the driverpacks installation occurs.)

my second method copies 300 meg in 32 bit mode and it extracts them on the fly utilizing resources that would be unused / idle on the target machine.

your method copies 1.5 gig in text mode.

I guarantee both of my methods are faster and reduce the size of your network copy by 1.2 gig.

#4 dspdisabler = Driver Signing Policy Dis-abler your unattended line will not help (by itself) if you use KTD.

#6 if you want to try and impress me your not going to do it by listing your accomplishments. I made my first dial-up connection in 1968 with an acoustic modem from a dumb terminal to a mainframe computer. I started learning on that mainframe.  My first PC was a KIT i had to assemble and we are talking about component level assembly not plugging cards in a slot. (it was a Poly88)

I didn't ask you what you did because i wanted to be taught. I asked you to see if i could offer some help. Sometimes when i see how people fail or choose poorly it helps me, in that i can potentialy avoid issues when i am programming. that way i can do error trapping to prevent them from making bad choices.

PS i am one of the coders for the base program and personally wrote the bartpe plugin
You may not be a good programmer but I am, and I have over 30 years practice.

#7 WPI (windows post installer) {what you planned to share} has already been done, and quite well i might add.
i also have over a hundred programs that are automated. So does every one else in the world...
at least the ones capable of finding there way here.

90% of the members / users here are hardened veterans with decades of experience, each and every one.
There are no noobs here. you are running with people here who have at least as much experience as you do.

We look forward to seeing you...
We're glad your here and giving back to the community you obviously love.

have a great day sir!

c:\windows\

Yes I have been thinking about RIS and SysPrep support for a while
feedback of this nature is the road to making it happen.

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

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)

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...