[gret]

Bâshrat the Sneaky, on Mar 2 2005, 05:46 AM, said:

Yes you can...

in your winnt.sif:

[Shell]
CustomDefaultThemeFile = "%WinDir%\Resources\Themes\MyTheme.theme"

Please do some research next time

More info can be found in the offical guide!

EDIT: but don't forget to use a hacked uxtheme.dll!

Please don't ask any further in this thread, but search the forums instead. If you still can't find things you need to know, please post a new topic in the appropriate forum!
<{POST_SNAPBACK}>

yea, i know... but i want to get rid of the winnt.sif
actually, i did get rid of the winnt.sif... but it gives me the default desktop theme after it reboots....
thanks...
um, doesn't the uxtheme.dll change the gui-setup background? (if i'm not mistaken)

EDIT: sorry... disregard this question... i'll search further in the forums...

[Toolman]

Can this methode also be used to skip pressing F6 to load additional drivers ???

Because the massstorage driver pack does not work, I always get an error after the first boot ... whatever methode I use ...

[xn85turbo]

Finally something that works for a NTupgrade=yes in the winnt.sif for adding third party drivers during the win xp install process. But here is my delima, I need to use these tools for a network install not cd.

Basically I want to upgrade from a remote share or copy the install directories to the local hard drive and run it from there. I am going to upgrade 700+ computers.

Any ideas?

[xn85turbo]

When i try to run the upgade from a local hard drive it fails on the copy section;

setuporg.exe = 1,,,,,,,2,0,0
presetup.cmd = 1,,,,,,,2,0,0

So I guess I can either try to manually copy these files with the logon script to the %systemroot%\system32

to see if that brings resolution.

[Bâshrat the Sneaky]

Toolman, on Mar 20 2005, 12:32 PM, said:

Can this methode also be used to skip pressing F6 to load additional drivers ???

Because the massstorage driver pack does not work, I always get an error after the first boot ... whatever methode I use ... 
<{POST_SNAPBACK}>

Yes, it can


That problem only exists with some controllers... But I'm working on it!

[PoNi]

Sorry was just trying to get help and I didn't pm you ?

[Bâshrat the Sneaky]

This is the WRONG topic!

And yes, the OEM folder is correct...

P.S.: do NOT post and PM me the exact same thing!

[crazyboot]

Hi

First at all, a big hello from France to all you guys from this reference-forum ;o)

My english is from school, so forgive it if the mistakes are shocking, please

I went throught this topic from the official guide

I then read all this topic and some Bâshrat's instructions. Sometimes, I m not sure I understood everything...

So here I go with some questions, if you don't mind :

"Bâshrat's KB" said:

Q: What about this 'OEM' folder? Why isn't it '$OEM$'? Are they the same?

A: No, they aren't the same! You MUST have the OEM folder, and another important thing: it must be at the root of your UWXPCD (so it must be next to the I386 folder and - if you have this one - next to the $OEM$ folder.
The OEM folder contains file necessary to make this method work. Don't start messing with it!

Well, in the official guide they've put :

Quote

» Making Changes to presetup.cmd
Open presetup.cmd in Notepad
Scroll down to the lines containing SetDevicePath.exe and correct the path. Change \Drivers to where you saved the files on in your source and the parameter ( %CDROM%\Drivers ) to where you saved all your driver files. Also correct the path in the line directly below it as well.

» Summarizing
You have just completed allowing your Windows setup to install the drivers from CD. SetDevicePath.exe will scan the recursively all the directories in the path you specify (see the presetup.cmd file for example), so even subfolders are also scanned. Any INF's found are added to the Device Path that Windows checks when it find new hardware. In this fashion, just drop any future drivers into your driver folder, and Windows will automatically use them if neccesary during setup.

So, the question is :

I have made a multi-boot DVD with the choice of install methodes, and among them, windows XP PRO SP2 integrated whose system path is \SETUP\WINXPPRO\I386.
At the same level than I386, I've put INSTALL\DRIVERS\001_...
and two tools (SetDevicePath.exe and WatchDriverSigningPolicy.exe) in INSTALL\DRIVERS, like suggested in the official guide (if I understood everything...).
I downloaded the tools on the official guide and am trying to put drivers for 10 differents PCs, so that the same unattended DVD can be used for all of them.

I put these lines in Presetup.cmd :

%CDDRIVE%\SETUP\WINXPPRO\install\Drivers\SetDevicePath.exe %CDDRIVE%\SETUP\WINXPPRO\install\Drivers
start %CDDRIVE%\SETUP\WINXPPRO\install\Drivers\WatchDriverSigningPolicy.exe

Is all this correct ? Should it work ?

I also used setup debug and tried the ISO on VMWARE. The cmd windows was showed during the install and no error on the screen. I also put the SVGA II driver for VMWARE on the drivers path. At the end, I made a look in the device manager and see that the SVGA II wasn't installed. I installed it then (from the same ISO but manually, so it was accepted with no problem). Is that meaning that the scan of Pyron's method didn't work ?

Thank you very much for your help and cheers
;o))

[Bâshrat the Sneaky]

That will of course work.

The problem was that soooo many newbies (back then & now) asked if this 'OEM' folder is correct. My FAQ currently only affects if you follow Pyron's instructions to the letter.

I'll change it immediately.

EDIT: updated the article.

This post has been edited by Bâshrat the Sneaky: 28 April 2005 - 01:20 PM

[crazyboot]

thank you very much for your fast reply, Bâshrat !!!

EDIT :
in the meanwhile, i've noticed this :

Quote

An important note:you can NOT verify that the drivers you added are working in VMware or VirtualPC! You HAVE to test it on a real pc to ensure it's working properly!

So, is it also true for SVGA II - specific VMWARE driver for XP ?
If yes, I will burn a DVD and try it on my PC ;o))

[Bâshrat the Sneaky]

No, Win XP doesn't include a 'VMWare driver', VMWare simply emulates a very old piece of PC hardware... And yes, you'll have to test on a real pc

[crazyboot]

Thanks again Bâshrat !
I test it this week-end...and then go bring you info back ;o))

if everything's OK, next stop will be integrating your packs which seem very very complete ;o))

PS : is there a topic or topics about how to expand INF files from differents setup.exe (original driver install packs) ? is there a sure method of extracting all the necessary files for integrating drivers when the setup doesn't support any expand switch ? if not, is there a KB ?
for example, i succedded to extract INF from INTEL CHIPSET setup.exe using -A -S -P swithes, but this didn't worked with INTEL EXTREME GRAPHICS setup.exe

[Bâshrat the Sneaky]

There is. Check the unattended Windows XP guide. Extracting driverfiles is the same as extracting applications

i.e.: any archiving application would be sufficient.

[crazyboot]

Hello again, Bâshrat

Sorry, I didn't understand well. What is "extracting applications" in the offical guide ? Where can I find it ?
And what about "archiving application" ? If you mean like winzip or winrar, I always try them first of all, but very often "open with winrar" is not possible. Or, it is possilbe with the first exe, but then there is still no INF files but only a new setup.exe which cannot be opened by winrar...

See ya'

[Bâshrat the Sneaky]

That was exactly what I meant. But I tend to use 7-zip (freeware).

If it's a InstallShield app (tagfiles: data1.cab, data1.hdr, data2.cab, data2.hdr, etc.), you'll have to use the CLI tool 'i6comp.exe' to extract the files.

If you just have a setup you cannot seem to extract, you have 2 possiblities: 1) it's an Intel drivers setup, if so, please do a search for it; 2) execute the setup but do NOT proceed the installation process. Check the folders 'Downloaded Installations' or 'Temp' or...

[crazyboot]

Hi and ta (thanks again ;o))))

I've made a little search for i6comp.exe and found this interesting how to example ;o)

but my trials with

i6comp.exe e -r data1.cab

and

i6comp.exe x data1.cab

weren't succesfull

EDIT : neither pause nor -v in cmd file made the log stay on the screen, so i don't know why it makes nothing...

[Bâshrat the Sneaky]

The second one should work just fine ... I've used it NUMEROUS times. Are you in the directory where data1.cab is located in?

[crazyboot]

Hello again,

Well the week-end was very nice (beautiful weather ;o))
But, my install of Pyron,'s method didn't made the drivers recognized by my (real) PC
Three yellow "!" for :
- audio driver
- video driver
- modem driver
and all three were in the path...
I ve just installed them manually, after the windows install finished.

My debug of setup windows was well displayed, after the first reboot, and all the lines were OK. It waited a while for SetDevicePath.exe and WatchDriverSigningPolicy.exe jobs, and then made setup continue without any problem.

So, I really don't know how to find where is the problem, and I feel a little far from how to fix it

For the use of i6comp.exe, i tried it on speedtouch driver, and i put the i6comp.exe on system32 directory, and made a little cmd line in the same directory where tdata1.cab was located. But, for this problem I m not too worried, it seems not important to me, compared to the general problem of drivers not recognized during windows xp installation...

See ya'

[scankurban]

Try this...
i6comp x -f data1.cab

[Bâshrat the Sneaky]

Try the setup.ex_ from my DriverPacks BASE then. And are you sure all your paths are right? It seems to me that your drivers didn't get extracted