DriverPacks.net Forum - Upgrade functionality of Setup refuses to work

Re: Upgrade functionality of Setup refuses to work

null@example.com (Newser) — Sun, 24 Jan 2010 16:15:30 +0000

Hey guys, that just worked! Thanks very much.

Re: Upgrade functionality of Setup refuses to work

null@example.com (OverFlow) — Thu, 08 Jan 2009 15:58:31 +0000

One post per issue is usually enough... cross posting is frowned on

Welcome to DriverPacks your other post was answered

Re: Upgrade functionality of Setup refuses to work

null@example.com (Bledi) — Thu, 08 Jan 2009 11:30:22 +0000

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

Re: Upgrade functionality of Setup refuses to work

null@example.com (kmoltiti) — Thu, 24 May 2007 00:05:30 +0000

I have a same problem, "Fake setup call himself instead original "setup.exe" - Setup Abort". My PC restart to this error then restart again. I cannot do anything. Please someone give me to download a CD or disk for reboot my PC.

Best Regards
Kmoltiti

Re: Upgrade functionality of Setup refuses to work

null@example.com (felipegeek) — Tue, 30 Jan 2007 14:01:17 +0000

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

Re: Upgrade functionality of Setup refuses to work

null@example.com (DizzyDen) — Wed, 04 Oct 2006 09:11:52 +0000

You can make even cleaner with:

DEL /F %systemroot%\system32\setupold.exe

Re: Upgrade functionality of Setup refuses to work

null@example.com (wixfigur) — Mon, 25 Sep 2006 10:40:07 +0000

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

Rename wrote:

ren setup.exe setupold.exe
ren setupORG.exe setup.exe

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.

Delete Old wrote:

%systemdrive%
cd %systemroot%\system32
DEL /F setupold.exe

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.

Re: Upgrade functionality of Setup refuses to work

null@example.com (Wim Leers) — Sun, 24 Sep 2006 17:31:40 +0000

That's just the fake setup.exe being renamed to oldsetup.exe and the real setup being copied from setupORG.exe to setup.exe then.

Re: Upgrade functionality of Setup refuses to work

null@example.com (wixfigur) — Sun, 24 Sep 2006 17:06:40 +0000

If installation breaks, there are 3 into system32: setup, originalsetup and oldsetup.

Re: Upgrade functionality of Setup refuses to work

null@example.com (Wim Leers) — Sun, 24 Sep 2006 16:43:14 +0000

The renaming is done by the fake setup itself. And there's only 2 setups, not three.

Re: Upgrade functionality of Setup refuses to work

null@example.com (wixfigur) — Sun, 24 Sep 2006 16:21:53 +0000

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.

Re: Upgrade functionality of Setup refuses to work

null@example.com (Wim Leers) — Sun, 24 Sep 2006 14:07:41 +0000

Well, then it should have worked with the fake setup I'm using too. It does the exact same thing: how would you expect that the real setup could continue otherwise?

But you got it working, and that's all what matters. I will not use that fake setup of Pyron though: it sometimes fails to work properly in case of certain XP SP2 installation discs.

Re: Upgrade functionality of Setup refuses to work

null@example.com (wixfigur) — Sun, 24 Sep 2006 12:24:52 +0000

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

Re: Upgrade functionality of Setup refuses to work

null@example.com (Wim Leers) — Sun, 24 Sep 2006 11:58:11 +0000

That won't work - did you try it? That's exactly the same method I'm using.

Re: Upgrade functionality of Setup refuses to work

null@example.com (wixfigur) — Sun, 24 Sep 2006 11:18:24 +0000

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:

%systemdrive%
cd %systemroot%\system32
DEL /F setupold.exe
if exist setup.exe ren setup.exe setupold.exe
if exist setupORG.exe ren setupORG.exe setup.exe
start /WAIT setup.exe -newsetup

this will work.