Visual Basic, Package & Deployment Wizard Problem

Package & Deployment Wizard Problem

Author	Message
KaEnterk #1 / 6	Package & Deployment Wizard Problem I've found a problem with the Package & Deployment Wizard (PDW) that comes with VB 6.0. If the last part of the executable file name has numbers in it, the installation program created by the PDW messes up the disk numbers. For example, if I've created a program "foo" version 1.1, I call the executable FOO11.EXE, because of company policy. When I create an installation for this application using the PDW, I create it for floppy disks. If the installation consists of three disks, the user is asked to insert disk 12 for disk 2, and disk 13 for disk 3. If I increase the number on the executable to FOO12.EXE, the user is asked to insert disks 22, and 23. I've tried several ways to work around this problem. I've changed the "setup.lst" file so that the cab file opens the file "FOO1.CAB". This works fine until disk 3, when the user is asked (after having been asked to insert disk 3) to insert disk 13, which puts the setup into a semi-infinite loop (the user can cancel out of the setup). I looked on Microsoft's Knowledge Base for this problem, but they don't have a solution for my problem. If anyone has found this problem and knows of a solution, your help would be much appreciated. Thanks, Katie -------------------------------------------------------------------------- -------------------------- Logic: An organized way of going wrong with confidence, just ask any one who's tried to prove anything in mathematics.
Fri, 05 Oct 2001 03:00:00 GMT

Ovidi #2 / 6	Package & Deployment Wizard Problem Quote: >I've found a problem with the Package & Deployment Wizard (PDW) that comes with >VB 6.0. If the last part of the executable file name has numbers in it, the >installation program created by the PDW messes up the disk numbers. >For example, if I've created a program "foo" version 1.1, I call the executable > FOO11.EXE, because of company policy. When I create an installation for this >application using the PDW, I create it for floppy disks. If the installation >consists of three disks, the user is asked to insert disk 12 for disk 2, and >disk 13 for disk 3. If I increase the number on the executable to FOO12.EXE, >the user is asked to insert disks 22, and 23. >I've tried several ways to work around this problem. I've changed the >"setup.lst" file so that the cab file opens the file "FOO1.CAB". This works >fine until disk 3, when the user is asked (after having been asked to insert >disk 3) to insert disk 13, which puts the setup into a semi-infinite loop (the >user can cancel out of the setup). >If anyone has found this problem and knows of a solution, your help would be >much appreciated. If you are not distributing your app on diskettes then make a single CAB setup package. It is slower but I guess your problem will dissapear this way. Ovidiu
Wed, 10 Oct 2001 03:00:00 GMT

Steve Johnso #3 / 6	Package & Deployment Wizard Problem Quote: Quote: > >I've found a problem with the Package & Deployment Wizard (PDW) that comes > with > >VB 6.0. If the last part of the executable file name has numbers in it, > the > >installation program created by the PDW messes up the disk numbers. > >For example, if I've created a program "foo" version 1.1, I call the > executable > > FOO11.EXE, because of company policy. When I create an installation for > this > >application using the PDW, I create it for floppy disks. If the > installation > >consists of three disks, the user is asked to insert disk 12 for disk 2, > and > >disk 13 for disk 3. If I increase the number on the executable to > FOO12.EXE, > >the user is asked to insert disks 22, and 23. > >I've tried several ways to work around this problem. I've changed the > >"setup.lst" file so that the cab file opens the file "FOO1.CAB". This > works > >fine until disk 3, when the user is asked (after having been asked to > insert > >disk 3) to insert disk 13, which puts the setup into a semi-infinite loop > (the > >user can cancel out of the setup). > >If anyone has found this problem and knows of a solution, your help would > be > >much appreciated. > If you are not distributing your app on diskettes then make a single CAB > setup package. It is slower but I guess your problem will dissapear this > way. > Ovidiu this may be irrelevant, but i got an unofficial update/upgrade/bugfix for pdw from msft. it's quite new (it wasn't part of service pack 2). you can't download it from their site yet because they haven't tested it enough, but i think it was relatively small. there isn't an setup program for it yet, but there are only 5 or 6 files. you just back up the old files and add the new ones.
Fri, 12 Oct 2001 03:00:00 GMT

Page 1 of 1

[ 6 post ]