A New Feature Breaks My Install

[NewsArchive]

I know you did it for my own good but here's what's happening. ;-)

I have three exe's which need different treatment depending on whether they
are installed on XP or Vista.

I let SB copy the three files to an XP Folder and a Vista folder on my hard
drive.

Then I was treating the XP folder as a patch.
If %OSCHOICE% Equals "1" Then:
Install File yada
...
Delete Files "%_SB_INSTALLDIR%\BACKUP\mmms6.001
End

Now I get a message "The file yada.exe is not a valid previous version and
could not be upgraded".

This is true because the files are identical.

So what to do?

--
Lynn Howard
www.linkedsoftware.com

[NewsArchive]

Lynn,

With "New Feature Breaks My Install", you mean that you have changed your
script logic and this breaks your install, right? You do not mean that "a
new SetupBuilder version breaks my install".

I would suggest to check if the files are really identical! For example,
zip the file up and check the CRC32 value. I am sure the CRC32 value is not
the same ;-) This message is to protect you. The file is not a valid
previous version and cannot be updated. If it would be an identical file,
the installer would automatically skip this item and continue. But the
CRC32 is different in your case.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

I did not change my script.

I use SB script to copy the files to the two different directories (XP and
Vista) so by definition they are the same.

This is most interesting. The CRC of the files themselves are identical.
But the files of the Zip values of the copied files are identical but
different from the zipped original file. I used XP Send To to create the zip
folders.

The CRC values of all three unzipped files are identical.

Say what?

Lynn

[NewsArchive]

Hi Lynn,

If the script is the same then something changed with the copied files. The
installer is *definitely* correct. If it says that "The file is not a valid
previous version and cannot be updated" then you can be 100% that this is
so. In this case the file to be updated is NOT the file you have defined as
your "Source Filename" and it is 100% not a file that can be updated with
the file(s) defined in your Previous File list for that Source Filename ;-)

It the file to be updated would be identical to the file defined as your
Source Filename then it would not display the error message.

Does this help?

Friedrich

[NewsArchive]

Thanks Friedrich.

When I compile I get the warning message that the three files are identical
as before.

But I get the error message anyway.

Would it help to send you the script?

Where else to look?

Lynn

[NewsArchive]

Lynn,

I fear the script alone does not help. Your problem is that you are
packaging the wrong files (that's why the compiler warns you!) and then you
are trying to apply the patch on the wrong files! It's not a SetupBuilder
bug or issue :) You are using the wrong files. The compiler message means
that your SOURCE FILES and the files to be PATCHED are the same!!

Perhaps this gives you and idea where you make the mistake?

http://www.lindersoft.com/forums/showthread.php?t=6064

If this does not help and you cannot find it, feel to send your script, and
all the files required.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Friedrich I'll study the thread.

But one more question am I doing something illegal that was not caught
before?

Using the same files I am putting one set into an XP folder, considering it
a patch and not adding a Vista Manifest and the other in a Vista folder and
adding the Manifest. I am using the SB copy to do this.

The error occurs when testing on an XP machine.

Lynn

PS I also mistakenly sent this to your email, Sorry!

[NewsArchive]

Lynn,

I think your source files changed so you are packing/patching the wrong set
of files now.

If you are interested, send your script and I'll see if it already gives us
enough information.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Thanks again Friedrich.

I've sent the project to you.

Probably done something stupid (again)!

Lynn

[NewsArchive]

Lynn,

Not received yet.

Friedrich

[NewsArchive]

Hi Friedrich,

Sent it again.

Had an exe attached on first so that probably messed it up.

Lynn

[NewsArchive]

Hi Lynn,

Received. I'll check it now...

Friedrich

[NewsArchive]

Hi Friedrich,

Why does this happen?

Folder\file.exe
is manually copied to Folder\XP\file.exe
and to Folder\Vista\file.exe

They all have the same crc values as expected.

If I zip them up they all have different crc values.

Using XP send to.

Lynn

[NewsArchive]

Hi Lynn,

> Why does this happen?
>
> Folder\file.exe
> is manually copied to Folder\XP\file.exe
> and to Folder\Vista\file.exe
>
> They all have the same crc values as expected.
>
> If I zip them up they all have different crc values.
>
> Using XP send to.

Unfortunately, I have no idea. I have never used the built-in Windows XP
zip feature. I would suggest to use WinZip or you can even use the built-in
"#zip file" compile directive to zip your files ;-)

Does this help?

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

I thought since it was Microsoft it would always work properly. ;-)

Lynn Howard

[NewsArchive]

>
>I thought since it was Microsoft it would always work properly. ;-)
>

Yeah, of course <bg>

Friedrich

[NewsArchive]

See your email about a new development.

Lynn

[NewsArchive]

Answered via private email.

Friedrich

[NewsArchive]

Hi Lynn,

I see where your problems are. See attached screenshot.

First of all, the source filename (left dialog) and the previous filename
(right dialog) point to the SAME file. You cannot create a patch from the
same file <g>. You need a *new* and a *old* version ;-)

This is the same in all of your other patch files (fd6.exe and mms6.exe).

Okay, I think what you are trying to do is to install, say, campaign6.exe
(without a Vista-aware manifest) on all non-Vista machines and then patch it
to a Vista-aware version on Vista/2008, correct? In other words, your PATCH
should only have the Vista and Windows 2008 condition enabled. But it has
the Windows 95 - Windows Server 2003 conditions selected. You never execute
anything on Vista/2008 with your current settings! And you do not create
any patch for a Vista/2008 version!

I think you would like to do the following:

The installer should install a campaign6.exe that does not have a
Vista-aware manifest and on Vista/2008 the installer should patch this file
to a Vista-aware file, right?

So you have to install campaign6.exe on ALL Windows versions (you have
selected Win95 - 2003 only, which is wrong because if nothing is installed
on Vista then nothing can be patched). Change this back to "OS
Independent". On Vista/2008 you would like to patch campaign6.exe to a
Vista-aware version. Select (in the File Properties for that patch) the
Vista/2008 conditions only. Do *not* select the Win95-2003 options. And
you have to change the Source File / Previous File settings in the patch:

Source Filename is:
C:\Ship MMSV\Programs\vista\campaign6.exe

Previous File:
C:\Ship MMSV\Programs\XP\campaign6.exe

What is does now is, it installs campaign6.exe (WITHOUT a Vista-aware
manifest) on all machines. Then, if it is a Vista/2008 machine, the
installer patches this campaign6.exe to a version that has a Vista-aware
manifest.

Does this help?

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Perfect!

Thank you!

Lynn

[NewsArchive]

You are very welcome!

Friedrich