Upgrade functionality of Setup refuses to work

If you click setup in your Windows CD (out of windows ) you can choose New Install or Update.
Why not using it? For many people its an easy method for a fast repair. You are right, that its better to reinstall, but its not the only solution.

If its not supported, I will try to fix it for myself.
I think, put the Patched setup.exe, originalsetup.exe and presetup.cmd into §OEM§\$$\System32 and copy/overwrite them via OEMpreinstall should be right. If I have no winnt.sif setup does the normal mode - so in the  Update/Upgrade.
Right?

But maybe you can rewrite the Setup.exe to enable this?

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.

Last edited by wixfigur (2006-09-24 22:53:37)

Yeah - it works. the trick is to delete the oldsetup.exe before. It coudnt be wrote twice.

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 installation breaks, there are 3 into system32: setup, originalsetup and oldsetup.

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.

Last edited by wixfigur (2006-09-25 22:14:49)

Thanks! That information made my life easier today.  I have a nicely working set of DP v6 integrated discs.  I renamed WINNT.SIF in my DP integrated disc image and made a new disc to allow repair mode to work then ran into the 'fake setup' problem at boot.  I usually use another XP install disc with only RyanVM's updates integrated for repairs but ran into a laptop that has a SATA drive and controller but no BIOS support for ATA compatibility mode so the text mode setup would fail.  The DP integrated disc with the mass storage drivers did the trick but then I ran into the 'fake setup' problem.

Note: To fix the system on which I already had run the repair install option without having to do it again with fixed presetup.cmd version of the XP disc I booted into repair console mode and deleted the setupold.exe manually.  After a reboot setup continued normally.

Thanks again to wixfigur!

-felipe

yes i have the same problem but i didnt understand it    someone explain me how to do that please