KACE Product Support

Great feedback Antti, I'm sure Bob will appreciate it!

Allthough it should be used for "smaller" capture "projects" it should recognize ODBC entries if I recall correct.
Regarding the shortcuts pointing to .ws files that seems correct as that is how the shortcut is installed by the original installation, the .ws file extension will be associated with the corresponding EXE.

and also own node for each main registry path. i.e (HKEY_LOCAL_MACHINE).
Once again if I recall correct; the nodes are bundled around components and if not they should as a components is the way to "group" resources.

I do indeed appreciate the feedback very much. With over 6,000 downloads so far I've had very little of this kind of feedback.

I've never seen the setup fail to launch as you describe (nor has it been reported). There is no issue with spaces in the path, or use of a UNC path as I do both regularly. Just what is the problem there I don't know but would love to see it for myself. Is there a public download link where I can try this first hand?

Please give an example of the types of changes you are making so I can make them myself and see if this is a reproducible situation. The application is doing a full scan of the file and registry systems before and after and simply comparing those scans. I don't know why it would fail to pick up this change in particular. Could it be that the change was automatically excluded and needed to be added back in? Like most any problem, if I can reproduce it, I'm sure we can correct it so please provide whatever steps you can offer so I may attempt to do so.

The shortcuts might show up as files, but the Windows Installer shortcuts to be generated by the MSI require you to use the shortcut dialog. We can see about how to best go about offering other file types besides EXE files for shortcuts. Remember, the idea is to keep things simple here, but I can see how this could sometimes present a problem as it is now.

The XML file is really for sharing purposes and was not created with manual editing in mind. If your package has as many elements as you seem to suggest, I'm not sure even the most sparse schema would be helpful. This was improved during beta but there was little feedback then as well. Changing it now would either break any existing recipes out there or require substantial work on our end to provide backward compatibility.

So, the XML will probably stay how it is, but your other points are all well taken. If I can reproduce any of your issues I'm sure we can get them fixed so please offer whatever specifics you can to do so.

Thank your for your time,
Bob

If I recall from packaging "IBM iSeries Access for Windows V5R4M0" previously it is not available for public download from ibm.com.
However while search for "iSeriesAccessWI.exe" I found it at http://avantae-it.com/public/downloads/ dunno which version it is though

Thanks! Aren't you clever [;)]

I usually give that advice to newcomers, use the search engine [:D]

Based on what AngelD offered as a download source, I was able to run this setup from a UNC share that included spaces. The setup is for a CTP (preview) release of version 5.4.06 (specifically, iSeries Access for Windows Technology Preview + SP6 (SI27741)). I repackaged this only to realize that it really just dumped the installation files to ProgramFiles. The actual setup I then repackaged was 5.04 and ran through without error.

I am testing on XP right now, perhaps you are using Vista and I should try that? Any other ideas about what could be different between your system and my test environment?

I'd hate to loose your feedback, but I feel compelled to point out that this is a Windows Installer setup already. At least a lot of it is-- there is a cwbinstall.msi install alongside several cab files. The AppDeploy Repackager pops up and warns of this (that a Windows Installer setup was detected). It is not advisable to repackage Windows Installer setups.

Bob,

If I recall (again); the cwbinstall.msi is not triggered by default during installation through the setup.exe (however, it is extracted).

At least for me, it was triggered for me when running the default (which was the "complete" feature). Hopefully the OP is choosing a installation set that does not include the Windows Installer portion.

Hello,

sorry for my late reply, but I have been on a course for a few days.

The machine was a Windows XP (lang. finnish). I don't know if that got something to do for that problem. It was running on top of Virtual Box, because I wanted to keep the source machine clean as possible.

I don't mind about that the setup.exe didn't start automaticly, because I like to do things by myself anyway:)

I also noticed that when I created some .ws scripts with the automatic .ws wizard. The .ws files didn't show up at all in the Include/Exclude files list. I created those files in C:\Program Files\IBM\Client Access\Private\Emulator folder. I also didn't find those files listed in the xml file that I tried to edit manually. Also Orca didn't list those files in the package, but when I installed the package the files were in the correct folder.

Actually I didn't check if the ODBC entries were applied also, I can check that tomorrow. They were not on the registry include / exclude list.

One other thing you should consider is enabling resizing the program window in the Include/Exclude screens. It would be a lot easier to view all the files / registry keys if you could resize the window.

I'll look into it deeper, but I can't imaging why it would not have detected the additional file changes you made as long as you did so before the second scan of the system. If the installation ultimately installed them that is even more puzzling-- perhaps an oddity of this application.