(instmsi.exe) Please insert disk #2

[Ambient2002]

Some of our customers get the following error message when using LabWindows/CVI standard installer (XP, SP 2):

Please insert disk #2. If the files on this disk can be found in another location... (etc.)

with a browse button.

The installation fails at that point in time.

The installation program has not been customized. I am running CVI V6.0.

[jlaney]

I will try and reproduce today. I want to get this straight before I try.

You have CVI 6.0 and are building a Distribution Kit of your project. When installed on a XP SP2 machine you get an error for instmsi.exe about a second disk.

This is strange since that is the MSI installer and should not install because a newer version is preinstalled on XP SP2.

If I have something wrong please post to let me know exactly what is causing this issue. I will post if I can\can not reproduce.

Jeff
NI

[jlaney]

I was not able to reproduce on 2 different machines with XP SP2. I built 3 different applications using the Distribution Kit for the test.

Can you provide me with some more information about the build system and the application in question?

What OS is the build machine for this Application? Are you building using the CVI DistKit? Are you doing any postprocessing?

What libraries does the application include, i.e. DataSocket, DAQ, etc.? Does the application use any external libraries?

Any other special info?

Jeff
NI

[Ambient2002]

I appreciate the work you did to support this problem. I contacted the customer again, and they said it now works. I am not sure what he did, but I told him to turn off all programs and virus protection, and it worked.

I do have a follow up question - if the customer does not have a c:\ drive (perhaps they change it to f:\ for some odd reason - some customers do this), the installer fails. There must be something hard coded in the installer. I tell customers to map their f:\ drive (for example) to the c:\ drive, and that takes care of the problem (a bit clunky, but it works).

Any ideas?

[jlaney]

Well, we no longer use the installer technology that was used with CVI 5.5 due to shortcomings. CVI versions 6.0 and above will not have this problem during a distribtuion kit installation.

Jeff
NI

[Ambient2002]

Hi Jeff,

I am using Version 6.0.0 (105).

[jlaney]

Oops,

I must have had you mixed up with another poster. Let me look into this, it should create a distribution kit that doesn't care about the install location. I will try and reproduce and turn logging on to get information about what is happening.

Jeff
NI

[jlaney]

Hello,

I am having a heck of a time trying to create a system that does not have a C: drive. Everytime I think I have it figured out Windows just sets itself or another partition back to the C: drive. Can you give me some more information about this system so that I can try and recreate it.
Are they using a bootmanager? What OS? Is there a C: drive and Windows is on F: or is there not a C: drive?

Thanks,
Jeff

[Ambient2002]

The issue occurs on all platforms. I have to admit, I do not know how to set-up a non-C:\ drive machine. There is a workaround for my customers though - I have them map their primary drive to the C:\ drive

Ed