1 Reply by Seiba

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

Hi Overflow smile,

First:
Thanks much for your tips, it is a pleasure for me to tell you more.

Second:
Yes you may be right, I could have done it a little bit easier - without uncompressing an things.
I know driverpacks fistly two weeks, and I had massive problems downloading it ...
But I wanted to know what's going on in my unattended installation.
Since integrating driverpacks with my method, network copy does not take noticeable more time.
If you have a fast network, this should be no problem.
For me it was a good deal to get it to work and to see what's going on.
The trick with patching setup.exe is great and genious, thanks to the patcher (Pyron an friends).

Third:
Setup.exe is started in GUI-Mode, not in Textmode.
Accordingly presetup.cmd.
So the drivers are shurely installed in 32-bit mode, because presetup.cmd and devpath.exe sets the devicepath in the registry before starting GUI-Mode.
So it is indifferent, if you copy the drivers with presetup.cmd or with my $1-feature !!!

Fourth:
I don't know what DSPdsblr.exe does.
It took it, and it worked.
Maybe I could leave it away, because in my Unattend.txt there is the statement "DriverSigningPolicy=Ignore" that disables policy warnings.
Maybe I will do a test next week.

Fifth:
You can use winnt32 to start unattended installation in the way it is documented by Microsoft.
Next week I will post my command-line, and unattend.txt and more.

Sixth:
I do unattended installations since NT4.0, and last 4 weeks I created an VistaPE boot media using winbuilder to start unattended installation in a domain environment.
I created serveral features like automatic partitioning, scripted start of unattended installation, running installation fully automatic, the only thing you have to tell is computername.

Seventh:
A few years ago I developed a tool. I call it the 'ProfileTree'.
With this tool you can install nearly 100 software packages in unattended mode (without interacting!)
The data it uses is stored in an Access database.
Access database stores all parameters that install scripts need.
Install scripts (VB-Scripts) that control package installation are created at runtime.
It is possible to select installation packages or not.
There is an installation control wether package is installed or not.
I have written it in Visual Basic 6 (I'm not a great programer!), and since long time I wanted to share it to the world ...
Maybe I do it anywhen.
A community could improve it shurely.

More next week. smile
Seiba

Go to forum: Feedback and Support - DriverPacks Base

2 Reply by Seiba

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

Thanks a lot
Seiba smile

Go to forum: Feedback and Support - DriverPacks Base

3 Reply by Seiba

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

Hi,

Seiba will do what you said (-:

There are many descriptions in the internet, how to create an unattended network installation.
I assume that you know how to
- create the distributionfolder with i386
- generate unattend.txt
- run winnt32.exe with unattend.txt

Your network share where your unattended installation lies may look like this:
\\server\autoinst\xp\i386.

1. Integrate all driverpacks to your network share \\server\autoinst\xp.
Start DPs_Base.exe
- Settings - Location - Location: \\server\autoinst\xp
- Settings - Location - Installation Platform: disc
- Settings - Driverpacks: All incl. Massstorage
- Settings - Driverpacks Method: Slipstream Method 2
- Settings - Finisher Method: RunOnceEx
Integrate.
This will integrate presetup.cmd and massstorage drivers into txtsetup.sif and dosnet.inf.

2. Now you have 2 new Folders near your \\server\autoinst\xp\i386 folder:
  - $OEM$ (see 3)
  - OEM (see 5-9)
Let them for the moment, you need them temporary, you delete them later!

3. Move folder \\server\autoinst\xp\$OEM$ to \\server\autoinst\xp\i386\$oem$.
There have to be 2 files: cmdlines.txt and roe.exe
(Normally $oem$ is your preparation folder when you use an unattended network installation).
Delete \\server\autoinst\xp\$OEM$.

4. Create the $1 folder in your new $oem$ folder.
Now it looks like this:  \\server\autoinst\xp\i386\$oem$\$1.
($1 folder will be %systemdrive% after installation)

5. Extract the driverpacks from \\server\autoinst\xp\OEM\*.7z to \\server\autoinst\xp\i386\$oem$\$1.
After extracting you will see \\server\autoinst\xp\i386\$oem$\$1\D folder and many subfolders where the drivers are extracted.

6. Copy \\server\autoinst\xp\OEM\aticpp.ins (if it exists) to \\server\autoinst\xp\i386\$oem$\$1.

7. Extract \\server\autoinst\xp\OEM\bin\DPsFnshr.7z to a temp directory.

8. Copy DevPath.exe and DSPdsblr.exe from temp directory to \\server\autoinst\xp\i386\$oem$\$1.
They are needed in PreSetup.cmd later.

9. Delete folder \\server\autoinst\xp\OEM completely.

11. Edit presetup.cmd in \\server\autoinst\xp\i386.

12. Delete whole text and add this 2 lines:
%systemdrive%\devpath.exe %systemdrive%\d
start %systemdrive%\dspdsblr.exe
Save it.

Now your unattended network installation is prepared to use the driverpacks.

Go to forum: Feedback and Support - DriverPacks Base

4 Reply by Seiba

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

Thanks,
just got it to work, but please don't touch winnt32.exe (-:
Patched Presetup.cmd and other stories.
If someone is interested, I can post the whole story.
Seiba

Go to forum: Feedback and Support - DriverPacks Base

5 Topic by Seiba

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

Hi,
I want to create a custom driverpack with some drivers.
How can I do that?
Is there a tutorial?
Seiba

Go to forum: Feedback and Support - DriverPacks Base

6 Topic by Seiba

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

Hi,
I install XP over the network installation using an 'unattend.txt', instead of 'winnt.sif'.
Unattend.txt is used with winnt32.exe.
When I integrate driverpacks using 'Method 2', I see that the 'setup.exe' in the 'i386' folder is patched.
Maybe this is done to start 'Presetup.cmd' during textmode setup.
Am I right?
Presetup.cmd then looks for the folder 'OEM' in the root of the cdrom and uncompresses the driverpacks to %systemdrive%.
and so on.
To integrate driverpacks in the network installation I should know what Presetup.cmd does, and how integrating works.
Can anybody tell me exactly that?
Thanks, Seiba

Go to forum: Feedback and Support - DriverPacks Base

7 Topic by Seiba

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

Hello,

I can't get the downloads to work.
Used IE7, Firefox2, no download manager.

Here is an example:

I go to http://driverpacks.net/DriverPacks/ and then click on DriverPack Chipset and then Proceed to download page and then Download DriverPack Chipset! (url=http://driverpacks.mirror.thesneaky.com/DP_Chipset_wnt5_x86-32_7101.7z).  That only brings me to http://driverpacks.net/leechwarning.php.

What I am making wrong?

Thanks, Seiba

Go to forum: Feedback and Support - DriverPacks Base