OverFlow wrote:
WsnoW wrote:
cometoluc wrote:

Hello, i tried your program but when i try to use it i get a message that my language is not correct and i can not install. I am using a dutch windows xp pro. Please advice, i really would want this to work with the dutch version of xp

best regards
cometoluc

in DPInst.xml change section -<language code="0x0409"> to - <language code="0x0413">

command line parameter
/el
Sets the enableNotListedLanguages flag to ON, which configures DPInst to enable all of the supported languages that are not explicitly enabled by language XML elements in a DPInst descriptor file.

supported languages

Arabic (Saudi Arabia) 1025 0x401 
Chinese (People's Republic of China) 2052 0x804 
Chinese (Taiwan) 1028 0x404 
Czech (Czech Republic) 1029 0x405 
Danish (Denmark) 1030 0x406 
German (Germany) 1031 0x407 
Greek (Greece) 1032 0x408 
English (United States) 1033 0x409 
Spanish - Modern Sort (Spain) 3082 0xC0A 
Finnish (Finland) 1035 0x40B 
French (France) 1036 0x40C 
Hebrew (Israel) 1037 0x40D 
Hungarian (Hungary) 1038 0x40E 
Italian (Italy) 1040 0x410 
Japanese (Japan) 1041 0x411 
Korean (Korea) 1042 0x412 
Norwegian (Bokmål) (Norway) 1044 0x414 
Dutch (Netherlands) 1043 0x413 
Polish (Poland) 1045 0x415 
Portuguese (Brazil) 1046 0x416 
Portuguese (Portugal) 2070 0x816 
Russian (Russia) 1049 0x419 
Swedish (Sweden) 1053 0x41D 
Turkish (Turkey) 1055 0x41F

Hello, sorry that it took so long for me to reply. Thanks for the answer.

Where do i have to put the /el parameter? In the xml file? And can i do so with a normal editor? I know nothing about xml files

jaws1975 wrote:
agni wrote:

When I run driverupdater with the presetup switch it does not detect any driverpacks.
But when I run it normally it detects them.
I am on a x86 machine.

Please help.

Sorry. I made a bunch of changes last update and I didn't test "presetup".

It's fixed now!

update at first post.

I also changed the presetup timeout from 60 seconds to 30 seconds. The timer will stop if user interaction detected.

Hello, where can you change the timeout? 60 seconds is really short and 30 seconds even shorter. If one has to stay and sit down before the screen to be able to interact at the 30 seconds, there's not much unattended. Is it possible to change that timeout somewhere to 240 seconds and if so where and how?

For the rest it's a very nice and much appreciated function to be able to choose whitch drivers to unpack.

3

(4 replies, posted in Software)

Hello,

i like this very much because it is indeed much faster then unpacking and copying everithing.
I have only one big problem. If i use it on e englisch version everything works fine but on a dutch version i get the error that it is not supported in this language. So your program can only be used in the english version of xp.
Do you have any suggestions please. I did already tried to copy the new version of dpinst.exe but it gives the same error. Strange however because when used this file in the normal driverpack there is never a problem with language.

Hello, i tried your program but when i try to use it i get a message that my language is not correct and i can not install. I am using a dutch windows xp pro. Please advice, i really would want this to work with the dutch version of xp

best regards
cometoluc

Hello,

i'm using the driverpacks for a while now and have the same problem as stated on top of this post.
When a installation is resealt with sysprep there should be no need to start the finisher at next login because the whole installation is already done. I also know that this is only cosmetic and one only has to click the error away but it is very annoying. When the finisher is run during the installation it should remove itself entirely and that is what the program does not do. It's a pitty because it all works so beautifull.
- Creating a unattended dvd with the updatepacks from ryan vm
- adding the driverpacks
- create the image and write it on dvd

Then one can put that dvd into any pc or notebook and it installs everything perfectly. I tested it on many devices.
The only problem ( cosmetic ) is when i try to reseal with sysprep so the first time the pc or notebook is booted up the user only has to put in the username and a few setting with the windows serial, there comes the error that windows can not find the finisher program. ( Windows has no need to search for that program because it is not neccecary anymore.

Probably the finisher leaves something somewhere in the registry to make the program start the first time it's bootup with an new user and it's just that place in the registry that i would like to know so i can remove it before i do a sysprep.

Is there someone who knows where the entry is hidden in the registry?