InstallAware

When I have the installation check for .Net and the machine doesn't have it. I get the Please Insert the Disk: WinWF setup files. Then the install fails as it cannot find the disk.

I built a cd build with all the files uncompressed. If the machine passes the .Net check then my program gets installed correctly.

I have attached a screen shot, how do I remedy this situation? I have the admin eval version of the version 7.

Thanks.

File Attached:

File Attached:

error.jpg

I'll go ahead and quote from the help file for this:

Installing .NET Framework 1.1 with Service Pack 1 on a system with .NET Framework 1.1 already installed will fail when using uncompressed builds running from removable media (CD, DVD). This failure condition will not occur when .NET Framework 1.1 is not already installed, when the uncompressed build does not reside on removable media (CD, DVD), or when any build type other than uncompressed builds are used (even if .NET Framework 1.1 is already installed and setup is running from removable media).

Thanks for the response, however the machine does NOT have .Net installed on it yet.

"This failure condition will not occur when .NET Framework 1.1 is not already installed,.. "

There is no version of .Net yet installed. So I am not sure this applies.

Thanks

I'm having the same error with InstallAware 9 when installing .NET 2.0, 3.0, and 3.5 (not 1.1). It works when compressed, however, my project includes 3.5 GB of media. Decompressing it takes forever and is simply not an option.

I've spent weeks on this. Hopefully, there is some resolution for this I have overlooked.

The Problem still existing with InstallAware 10.

What will InstallAware do to solve this Problem?
It is quite strange, that it is working when using a big single exe or a web setup but not if a DVD Layout is used.

On what OS(es) is the failure occurring?

This Problem occures on a clean Windows XP with SP3.

No .NET Framework is installed.

You can reprodcue this problem when creating an empty setup with .NET Framework 3.5 SP1 and Windows Installer 4.5.

Start the installation, the prerequisites are starting to install (Reboot after Windows Installer 4.5) and then the Error with "Please Insert the Disk: WinWF setup files" occures.

Edit:

The problem occures too, when having only .net 3.5 SP1 with Windows Installer 3.1 in the setup.

Can you post a sample project that exhibits this?

Sure I can.

See the attached zip-file. Just extract, open the "My dotNET Setup.mpr", build it as DVD and install it on a fresh Windows XP SP3 to reproduce the problem.

I couldn't reproduce it. I'm attaching my test case. It appears as if some of you are seeing this issue with different .NET versions and probably different environments.

What I would do at this point is to take the msi that it's failing on and run it from command line. Or you can try manipulating the command in the setup_net script:

Install/Remove MSI Package $NET351_BOOTPATH$\net351bin\vs_setup.msi[VSEXTUI=1] (get result into variable NET351_RESULT)

You can search msdn for options you can use [VSEXTUI=1].

Hi Andy Mills,

ok this sounds not so good.

The setup is failing during a .NET FW 3.0 setup (something with the Workflow Foundation).

Following line is failing: But only, if it is a cd/dvd setup. Web Setup workes fine.

I will upload the created setup to our webspace so you can try our version. If you wish, I can provide a virtual machine, where the problem occures.
Download: http://www.pathme.de/download/software/ ... tSetup.exe
Just extract the exe-file, it contains the uncompressed dvd setup.

Could it be, that it has something to do with the used InstallAware Version? I've used InstallAware Studio and you Studio Admin.

Edit:
So, I've tried it with InstallAware Studio Admin and have the same result. Now I will try it on a physical device, maybe it is only a problem in a virtual machine.

Edit 2:
So, now I have tried to install it on a physical machine. I ran into the same problem "Insert the Disk: WinWF Setup Files".

How could you produce a setup which works, and some Users of your software couldn't?
I created the setup on a Windows Server 2008 Enterprise x64 (English) with actual patch level, Visual Studio 2010 --> Problem
I created the setup on our build server (Windows Server 2003 x32) --> Problem

Again, I couldn't reproduce the issue in my environment.
I'm confident this is an issue with the environment.

Technically, I'm considering this a Microsoft issue, but I'm willing to help try to resolve it.

I wouldn't think the edition (studio/admin) would matter.

Do you use VMware? A VM may be helpful in this situation. Since it can be such a large file, you may want to consider mailing a DVD to us, but I may be able to download it over the course of a night.

Hi,

sorry for the late reply.

We use VmWare and Hyper-V.

I have this problem in a VM and a Physical PC.

I'm going to create a fresh VmWare with a Windows XP Professional SP3 inside. The DVD, which I created is linked in my post above.

I will edit this post, when the vm is uploaded.

EDIT:
I've found the solution. I didn't cached the installation files on disk, so I've got the error. After I changed the setup to cache all installation files on disk (due to another problem), the installation goes through without an error.

It is a little bit strange, but it works now.

Thanks,

Thomas

I had the same problem.

Looking into it a little further it's the WorkFlow part of .NET 3.0 that's not installing. I pulled out the problem msi file (Wf_3.0_x86.msi) from the .NET 3.0 installer and ran some tests. It works fine when installed from the hard disk but not from a CD/DVD.
My fix was going to be to comment out that part of the .NET 3.0 installation script until I saw the caching fix.

I found it worked great to a point. .NET 3.0 goes on without any problems but now I'm having problems with .NET 4.0 - the whole installer set is smaller when the caching option is enabled... It's almost as if it's not including everything correctly.
The installer I have is a combined 32bit/64bit installer with an if branch that conditionally performs the detection of the relevant 32/64bit pre-requisites.

I'm not sure why there should be a difference in the files that are included when cached mode is enabled.

Solution: The installer wants .Net Framework 1.1, make it available by ticking the box for Microsoft .Net Framework 1.1 in Application Runtimes.
Who am I to decide what Microsoft should have?