There is no disk in the drive message at end of setup

[DLee65]

Here is the email from Macrovision:
"This problem has been reproduced and determined to be an issue in our software. This issue has been submitted to our Engineering team as issue #<IOC-000042357>. At this moment, there is no estimated time frame for when this issue will be fixed. For an immediate resolution, I recommend:

Do not include a Setup.exe in the build. Instead just ship the MSI. The disadvantage is that machines that do not have MSI 2.0 will require the end user to install it from Windows - Updates or from an included EXE file in your release media.

There is one other possible workaround. This would involve using the 10.5 version of the setup.exe file instead of the 11.5 version. Many things have changed between the versions so this may not work. Just as a test, try replacing the setup.exe in the built uncompressed release with version 10.5 of the EXE. You should be able to find this in the following folder:
C:\Program Files\Macrovision\IS11.5\Redist\Language Independent\Legacy\1050

You can track the status of this issue using the issue number by checking product release notes or searching our Knowledge Base through eService."

[Stefan Krueger]

So they accepted this as a bug - at least you dion't have to search any longer for the cause.
To answer your previous question: no, I don't recommend using idential valoume labels in your release version, I only suggested this as a test to see if that's the cause for the problem.

[Peter Roca]

I am trying to build an install of one of our programs and I was getting this error on a previous version. The way I fixed it was to start from scratch with a new project and rebuild it. I am making an update to our program now, and I am getting the same error and remaking the project does not fix it this time. this is a MAJOR problem for us and it is forcing me to rethink how the program is installed, such as making a web install and making them into RAR files that the user will have to extract themselves to avoid disk spanning on CD-ROMS.

I wish installshield had a better answer than "we dont know when it will be fixed"

[jazeboy1]

does anyone know if this has been fixed in installshield 12 or 2008?

Is there any reference number for this bug?

[DLee65]

I am told that this was fixed in IS2008, although I have not tested it yet. We have moved to DVD media distribution for most of our installs now so space is not an issue.