Search options

Hmmm - sorry, but Im not talking about the finisher.
2 Weeks ago I had a notebook to install, where I wished to skip DriverPacks, cause installation worked only without DP.
Anyway ---

OK - thats the problem.
I think your renaming is the same as this:

and thats what happens:

   1st line  - if theres an existing setupold.exe, DP setup.exe cannot renamed to oldsetup.exe.
   2nd line - if there exists an setup.exe ( cause first line failed ), setuporg.exe stays the same.

Effect is, that setup.exe doesnt change and calls itself.

If setupold is deleted before renaming, maybe by adding this line to presetup.cmd, renaming process can work properly.

If theres no setupold.exe ( like the first install ), the line doesnt have any sense.

And now - update function is working with DriverPacks setup.exe ( not adding the old one from MSFN ).

Ive tested it - works fine.

Hmmm - very strange!
In the MSFN forum posts, you can read, that renaming is job of presetup.cmd. In DriverPacks presetup.cmd is no entry for renaming, so, I think its setup.exe´ job.
If I look into the system32 dir after setup breaks down, I can see some mess with the different setup files.
And also, if I use DriverPacks setup.exe, renaming with presetup doesnt work.
So, logically, therers something wrong with the renaming of the 3 setups. If I do not delete the originasetup before, I have also a break into setup.
I cannot look inside DriverPacks setup, cause i do not know the Coding Language. But there MUST be a difference between yours setup and pyrons.

If somebody is interested - Ive found the solution for that problem by reading an old article at MSFN. The problem is the renaming/restart of the patched setup.exe. An old version, which is still available, does it with the presetup.cmd.

For those who also want to fix it, download this SETUP.EXE and put  it into your I386  directory.
then add following lines to the end of presetup.cmd:

this will work.