Software Deployment

Start by installing with verbose logging and report back what you find regarding installation failure.

OK, whilst doing the install with verbose logging enabled, I found it did install the core MSI with a non-modified transform. So that bit wasn't the issue, the issue is QuickCam.MSI doesnt install the drivers. It is done by a second setup.exe called after (?) the QuickCam.MSI is run.

So what I have tried to do is add the driver files into the transform and run difxapp to install, however this is waht was causing my install errors as the added files compile into a .CAB, yet on install the MSI is looking for them as flat files in the source path??

example of error from vb log attached...I'm sure I'm missing something really simple here:

MSI (s) (E4:70) [10:11:57:422]: Executing op: FileCopy(SourceName=lvPEPIc.inf,SourceCabKey=lvPEPIc.inf,DestName=lvPEPIc.inf,Attributes=0,FileSize=5190,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,,,,,,,)
MSI (s) (E4:70) [10:11:57:422]: File: C:\Program Files\Common Files\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf; To be installed; Won't patch; No existing file
MSI (s) (E4:70) [10:11:57:422]: Source for file 'lvPEPIc.inf' is uncompressed, at 'R:\Packaging\LogitechQuickCam11.10.2030.0101\First try\Common\LogiShrd\Qcdrv\x32\im\'.
MSI (s) (E4:70) [10:11:57:422]: Note: 1: 2318 2: C:\Program Files\Common Files\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf
MSI (s) (E4:70) [10:11:57:438]: Note: 1: 1309 2: 3 3: R:\Packaging\LogitechQuickCam11.10.2030.0101\First try\Common\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf
MSI (s) (E4:70) [10:11:57:438]: Note: 1: 2318 2: C:\Program Files\Common Files\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf
MSI (s) (E4:70) [10:11:57:453]: Note: 1: 1309 2: 3 3: R:\Packaging\LogitechQuickCam11.10.2030.0101\First try\Common\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf
MSI (s) (E4:70) [10:11:57:453]: Note: 1: 2318 2: C:\Program Files\Common Files\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf
MSI (s) (E4:70) [10:11:57:453]: Note: 1: 1309 2: 3 3: R:\Packaging\LogitechQuickCam11.10.2030.0101\First try\Common\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf
MSI (s) (E4:70) [10:11:57:453]: Note: 1: 2318 2: C:\Program Files\Common Files\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf
MSI (s) (E4:70) [10:11:57:453]: Note: 1: 1309 2: 3 3: R:\Packaging\LogitechQuickCam11.10.2030.0101\First try\Common\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf
MSI (s) (E4:70) [10:11:57:453]: Note: 1: 2318 2: C:\Program Files\Common Files\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf
MSI (s) (E4:70) [10:11:57:469]: Note: 1: 1309 2: 3 3: R:\Packaging\LogitechQuickCam11.10.2030.0101\First try\Common\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf
MSI (s) (E4:70) [10:11:57:469]: Note: 1: 2318 2: C:\Program Files\Common Files\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf
MSI (s) (E4:70) [10:11:57:469]: Note: 1: 1309 2: 3 3: R:\Packaging\LogitechQuickCam11.10.2030.0101\First try\Common\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf
MSI (s) (E4:70) [10:11:58:235]: Product: QuickCam -- Error 1309.Error reading from file: R:\Packaging\LogitechQuickCam11.10.2030.0101\First try\Common\LogiShrd\Qcdrv\x32\im\lvPEPIc.inf. System error 3. Verify that the file exists and that you can access it.
Action ended 10:11:59: InstallFinalize. Return value 3.
MSI (s) (E4:70) [10:11:59:188]: User policy value 'DisableRollback' is 0
MSI (s) (E4:70) [10:11:59:188]: Machine policy value 'DisableRollback' is 0

And yes the file is in that location as well as the cab file and it still cannot find it...

Thanks again.

Maybe try DPInst.exe to drop the driver files down for you?

I'll have a look at using DPInst, but we've just had another non-driver transform do the same thing when trying to add additional files...is this a fundamental transform rule I'm breaking here or something else...basically, the additional files cannot be found by the MSI/MST, even though they are both in a cab file created by the compiler (Wise), and I've moved them into the falt structure it is asking for when the error occurs...

I'm totally wierded out right now.

I had a similar problem on an app where I manually created the folder structure and dropped a file in there, rather than using the default property which Installshield sets out.

You possibly doing that?

And yes the file is in that location as well as the cab file and it still cannot find it...Have you checked permissions on that file? It wouldn't be the first time NTFS permissions were screwed on one file in a folder. Run ProcMon while the install is happening: that will flag any permissions or absent file issues differently.

Something else you can check is to look in the File Table and check the attributes column for each of the files you have added via the transform. For compressed source files, the value for Attributes needs to be at least 16384 (decimal), so if you have attribute values less than this, just amend this column entry by adding 16384 to whatever the existing value happens to be. Check also that the Media Table has an entry for the extra CAB file needed to hold these files and that the last sequence number for the entry looks sensible i.e. it should equal the sequence number of the last of the new files you added via the transform.

Another consideration is whether the installing account has access to the R: drive ? (e.g. does it have the R: drive mapped at all) Have you tried copying all the source files (MSI, MST and CAB files) onto a local folder rather than network folder and performed the installation from there ?

Regards,

Spartacus

VBSCab - yeah permissions are cool, we compile all our app sources from the network, to ensure we can pick up for our colleagues offline (India/Australia/NZ teams), so if it was that, all our apps would be dying!

Spartacus - you were bang on with the file attributes, so I've changed all those and the files appear to be compiling into the cab, will try the install now.

fingers crossed.

AIS,

Just stumbled accross this thread. I wonder if you managed to solve this riddle for you and what your solution was. Because we're trying to do the same thing here and Logitech says "not possible".

Thanks,
Dan

I did manage to get the pacakge done, it was a messy messy package in the end, and I could even then only get the drivers working (not the actual logitech suite of apps) which was enough for our requirement to use it with Office Communicator. I basically hacked out an install from the installed files/reg etc...

Unfortunately logitech wouldnt come to the party on this one at all, so that was the solution we ended up with. Basically do a setup capture, use difxapp to install the driver files found in the capture, and remove all the windows installer references and other garbage found by the capture.

I know its probably the worst possible way to pacakge this - but it was the only way I was able to get a working installer for network distribution.

If you want more info on this PM me and I'll try to get back to you asap.

ORIGINAL: AIS
If you want more info on this PM me and I'll try to get back to you asap.It would be MUCH more helpful if you were to add your findings to the 'Notes' section in the 'Package KB' article http://www.appdeploy.com/packages/detail.asp?id=1259

Hello AIS

I'm working on the similar package from logitech...
"Logitech Webcam Software"

there is no cmdline support for this package..
silent install is required with custom installation.

I'm tried all the options available and totally wierded out right now.

Thanks in advance.