Wise Installation System 9.02 installer spanning multiple CDs hangs or thinks media is corrupt

Presumably the install works if you put it on DVD as a single file installer?  Is there any compelling reason why you have to put it on CD as there cannot be many users left who are still running only CD drives?

Going on, when you get to the end of the first CD - do you get any sort of message asking for the next media?
Have you tried going to a custom size, and specifying 500000 (500Mb) as the size, to even up the amount on each CD?

Finally, are you testing on a real machine with its own CDROM or are you mapping to a remote machine?  Have you tried on another system to exclude the possibility that your optical device has a fault?

Thanks for the reply.  I will first answer your questions then provide an update.

Yes, presumably it does work on a DVD since it does work as a single file from the hard drive. 

Yes, I have a compelling reason for putting it on a CD.  The reason is that is how the customer wants it.

As to whether I get the message, I do not.  Sometimes the setup just hangs and sometimes it hangs for a while and then says the installation is corrupt.

I have not tried a smaller size (yet).

I am testing on a real CD-ROM.  On two different machines with the same result.

As to the update:  I had originally given the setup executable a different name from the .wse project (which has previously never been a problem).  I renamed the setup executable to the same name as the project and that version worked.  However since this "solution" makes little sense--I am still concerned that there still may be an intermittent problem (unless someone can tell me that they had the same problem with a multiple media install that they solved the same way).

I would assume that at compile time, the name of the project file is embedded in the first EXE so that it knows which file to look for on the second media item. If you change the name of the EXE after compile, and the name of the W02 file as well, then the name embedded in the exe that points at the W02 file will be wrong.

As a test, try renaming the EXE but leaving the W02 filename unchanged and see if that works also.

Thanks again for your reply. 

I think you may have misinterpreted me.  I never changed the name of the .exe (or the W02) after compile.  What I did was, originally, in build settings, I put MyProject_setup.exe as the name of the setup executable.  And that's what I got for an .exe.  And of course the second file was MyProject_setup.W02.  These did not work.

In the one that works, in the build settings I changed the name of the  setup executable from MyProject_setup.exe to MyProject.exe.

Either way I hope it is as you say..i.e. that for some reason it is always looking for [nameofproject].W02 rather than the .exe name in the build settings.  Although this would be a bug the workaround is not a problem for me.

I am going to have the setup tested on several more machines at which point I will know if it is really fixed.

Thanks again,

Mark