/build/static/layout/Breadcrumb_cap_w.png

First package

I am trying to use Wise Package Studio to make my very first package. The package is DialOut EZ. Part of this packaging will inculde setting up a modem. Can anybody point me in the right direction.

Thanks in advance for ANY help.

0 Comments   [ + ] Show comments

Answers (8)

Posted by: Aaron 20 years ago
Senior Yellow Belt
0
Unless you have the same modem on the same COM port across your organization, this may not work too well. You may want to use a custom action to setup the modem rather than capturing it as part of the install.
Posted by: dockland 20 years ago
Senior Yellow Belt
0
That's the one reply I was worried about getting. Guess I better get reading!

Would I start out with do the Dial Out capturing and then go into the MSI Script? Or am I just way off base here?

Thanks for your help.
Posted by: MSIMaker 20 years ago
2nd Degree Black Belt
0
First capture the modem installation.....you will have to fiddle about with it after the capture to get it to work in the msi.

Then capture the app install and add it to the msi. Clear out any rubbish you find in te capture.

Test and test and test :)
Posted by: dockland 20 years ago
Senior Yellow Belt
0
The correct com port for the modem is not avaviable until after the installation of the "Dial Out" network modem. I am trying to caputer the "Dial Out" first.

At first glance, it looks like the hardware registry keys did not get copied. Has a problem with Wise Package Studio 5.1 been found in this area?
Posted by: MSIMaker 20 years ago
2nd Degree Black Belt
0
Go to your setup capture configuration and tick the box to monitor hardware changes.
Posted by: dockland 20 years ago
Senior Yellow Belt
0
I really don't know what I am doing! But this has been made my main project for the now. In other words, please excuse any stupid questions.

I have the monitor hardware checked. When I test the installation on another machine, it pops up errors while trying to put information into registry.

I have also tried to use the "Device Driver" templete. I followed the directions from the Wise site. Should I be using this?

Would it be possible to just do a capture of the app., install the .inf for the modem and then import the registry keys for the modem?
Posted by: Zulumika 20 years ago
Senior Yellow Belt
0
This is a good one. I do not recommend packaging this software for 2 reasons:
1. http://www.tactical-sw.com/faq.php?id=37
2. On a laptop (compaq m700 - winXP PRO), the physical modem is detected on COM3 and my package used COM3 and COM4. After installing my own package, the laptop blue screened continuousely before logon. (read conflict on COM3). I had to re-image the laptop.

What I recommend is: to package the software without modem drivers and without COM ports. (just copy the modem driver to destination). A few steps will be required to setup the rest of the installation : Installing the modem drivers and select the COM you want. (I realize the this is almost like installing it manualy...[&:]) This is a lot safer and reduces the number of call to our support center.

You can try making a package with dialout/EZ but I strongly recommend verifying the COMs before rebooting and test on several machine models.
Cheers.
Posted by: MSIMaker 20 years ago
2nd Degree Black Belt
0
If you have a "locked down" workstation then installing a modem as a User isnt going to work. Your best bet is to add the modem to the modem pool in the msi by installing the inf file.

The modem will at least be in the modem list and if it is PNP.....it will autodetect once its added to the COM port and the drivers will be available on the local machine.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ