Newsgroup: it.comp.lang.visual-basic
Titolo: Aiuto nel creare un pacchetto di installazione

Ho il VB6 Ed. Enterprise
Mi sono sempre servito della autocomposizione per creare pacchetti si
installazione, ma ora ho l'assoluta necessità di usare un altro programma
(Inno Setup), e quindi vorrei capire alcune cose molto importanti.
Usando ancora l'autocomposizione in VB6 ho ottenuto il file SETUP.LST
Ve ne riporto solo alcune righe:
[Bootstrap]
SetupTitle=Installa
SetupText=Copia dei file in corso. Attendere.
CabFile=Ordini.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1
E' importante sapere il significato delle righe precedenti?  Ad ogni modo,
il loro significato mi sembra facilmente intuibile.
[Bootstrap Files]
File1=@VB6STKIT.DLL,$(WinSysPathSysFile),,,8/5/98 12.00.00
AM,102912,6.0.81.69
File2=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,6/1/98 12.00.00
AM,22288,4.71.1460.1
File3=@MSVCRT40.DLL,$(WinSysPathSysFile),,,6/1/98 12.00.00
AM,326656,4.21.0.0
queste 3 istruzioni, mi sembra di capire che servono per copiare i tre files
in questione nella cartella c:\Windows\System:
PRIMA DOMANDA: Sono sicuro che prendendo questi 3 files dal mio computer e
copiandoli nel computer ove intendo installare il mio programma (rispettando
ovviamente il percorso), non creo nessun tipo di problema?
Voglio dire: i files verranno creati nel computer "destinatario" e se erano
già presenti files con lo stesso nome verrebbero sovrascritti! Ciò non
creerà difficoltà per altri programmi installati nel computer
"destinatario"?
Andiamo avanti...
[IconGroups]
...
[Clienti 1.0]
...
[Setup]
Title=Ordini 1.0
DefaultDir=$(ProgramFiles)\Ordini
AppExe=Ordini.exe
AppToUninstall=Ordini.exe
[Setup1 Files]
File1=@dbPrezziario.mdb,$(AppPath),,,12/11/00 6.23.38 PM,165888,0.0.0.0
File2=@dbClienti.mdb,$(AppPath),,,12/12/00 1.51.02 AM,96256,0.0.0.0
File3=@MDAC_TYP.EXE,$(AppPath),,,8/10/98 12.00.00 AM,6507072,4.72.3110.0
File4=@RDO20IT.DLL,$(WinSysPath),,$(Shared),8/5/98 12.00.00
AM,66560,6.0.81.63
File13=@MSADO20.TLB,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/8/00
5.00.00 PM,61440,2.50.4403.4
File14=@MSDERUN.DLL,$(CommonFiles)\designer,$(DLLSelfRegister),$(Shared),6/9
/98 12.00.00 AM,137216,6.0.0.3005
File22=@MSREPL35.DLL,$(WinSysPathSysFile),,,6/8/00 5.00.00
PM,430080,3.51.3225.0
SECONDA DOMANDA: Perchè a volte c'è scritto (WinSysPath)   e a volte
(WinSysPathSysFile) ?
non si riferiscono entrambi alla cartella c:\Windows\System ?
Ad ogni modo ciò che per me è importante sapere è: copiando questi file dal
mio computer su quello in cui intendo installare il mio programma, il mio
programma funzionerà... e non creerò problemi ad altre applicazioni che
usano gli stessi files?
Grazie per la gentilezza di chi ha voluto leggere questo messaggio.


Benvenuto all'inferno fratello...
M$ dovrebbe scrivere sul PDW
Per me si va nella citta' dolente
Per me si va ne l'eterno dolore
Per me si va tra la perduta gente
Ingiustizia mosse il mio alto (*) fattore
    ((*) uhm... Gates mica e' tanto alto
Fecemi l'infernale potestate,
La somma insipienza e la sete di potere
Dinanzi a me non saran cose create
Se non malferme, e impossibili da vedere
Lasciate ogni speranza, o voi che programmate
E che Dante mi perdoni la rivisitazione :)
Cmq scherzi a parte il setup e' la parte piu' problematica di qualunque
programma, leggi i molti post in merito che ci sono sempre nel NG...
Hai due opzioni (non fornite di serie col PDW, devi usare un altro tool):
1) far andare il tuo programma e fanc' al mondo: installi tutto quello che
ti serve, esclusi forse kernel32 e shell32, a quel punto o il programma
funziona o il sistema crasha. Solo che sono eventi equiprobabili :)
2) far andare il mondo e fanc' al tuo programma: se il file esiste non lo
sovrascrivi mai, ma a quel punto il tuo programma potrebbe non funzionare se
sono installati componenti piu' vecchi.
Ciaotutti,
Alessandro

 ha scritto nel messaggio
news:946nr2$c9kiv$1...@ID-68324.news.dfncis.de...


 ha scritto nel messaggio
news:947r17$oug$1...@lacerta.tiscalinet.it...


 Qualcuno e' gia' inciampato in questo errore?
Su msdn ho trovato questo articolo:
FIX: Application Setup Errors While Displaying "Copying Files, Please Stand
By"
----------------------------------------------------------------------------
----
The information in this article applies to:
Microsoft Visual Basic Learning, Professional, and Enterprise Editions for
Windows, version 6.0
----------------------------------------------------------------------------
----
SYMPTOMS
When you run a Setup that was created using the Package and Deployment
Wizard (PDW), you receive one of the following error messages:
Cannot start main setup program! (CreateProcess() returned error code
0x000000C1H)
VB6stkit.dll is not a valid Windows NT image
The system could not locate the file '<Temp
Folder>\Msftqws.pdw\Vb6stkit.dll'. Would you like to browse for the file
yourself?
The system could not locate the file '<Temp
Folder>\Windows\Temp\Msftqws.pdw\St6unst.exe'. Would you like to browse for
the file yourself?
where <Temp Folder> is the Windows\Temp folder on Windows 95/98 or the
folder specified by the TEMP environment variable on Windows NT.
CAUSE
If the symptom occurs on all target computers where you run Setup, the cause
of the problem is most likely one of the following:
A damaged diskette.
A damaged setup file.
If the symptom only occurs on some target computers, the cause may be one of
the following:
Left-over files from a previous installation attempt.
A machine-specific issue.
RESOLUTION
Test for Damaged Diskette
Try deploying the Setup package to a different set of diskettes, or use a
disk scanning utility, such as ScanDisk, to verify the integrity of the
current set of diskettes.
NOTE: When using ScanDisk, select the Thorough option. The Standard option
does not detect all disk errors.
Test for Damaged Files
Create a test folder on the hard drive of the target computer.
Copy the files from the Setup diskettes to the test folder:
If you receive error messages indicating the copy failed, the diskette may
be damaged (see the "Test for Damaged Diskettes" section of this article),
or there may be a problem with the floppy disk drive.
If the copy succeeds, continue with the next step.
Run Setup.exe from the test folder on the hard drive.
If the Setup succeeds when run from the hard drive, this indicates one of
the diskettes may be damaged (see the "Test for Damaged Diskettes" section
of this article), or there may be a problem with the floppy disk drive.
If the Setup fails with one of the error messages listed in the "Symptoms"
section of this article, continue with the next step
If the Setup succeeds when run from the hard drive, this indicates one of
the diskettes may be damaged (see the "Test for Damaged Diskettes" section
of this article), or there may be a problem with the floppy disk drive.
If the Setup fails with one of the error messages listed in the SYMPTOMS
article, continue with the next step.
To determine whether a .cab file is corrupt, manually extract the files from
the .cab file(s). To extract the contents of a cabinet file, you must use
the Extract utility.
Extract.exe can be found in your Windows or Winnt folder or on your Windows
95, Windows 98, Windows NT, or Windows 2000 installation CD or diskettes.
Extract.exe is a command-line utility. Therefore, it is used from an MS-DOS
command prompt. To extract the files within a cabinet file, be sure the
Extract.exe utility is in the MS-DOS path, or copy the Extract utility to
the same folder as the cabinet file.
From the MS-DOS command prompt, you can run the following command to extract
all of the files in a .cab file into the current directory:
extract.exe /e /a <File Name>.cab
where <File Name> is the name of your cabinet file. If there are multiple
.cab files in the setup, <File Name> should be the first .cab in the series.
If all the files extract successfully, the .cab file is not corrupted.
However, the .cab file is corrupted if you receive the following error
message:
ERROR: Cabinet file <File Name>.cab is corrupted
where <File Name> is the name of the .cab file you just extracted.
NOTE: In some cases, a .cab file may be damaged even though you are able to
successfully extract the files from it. Try re-running the PDW or running
the .bat file in the \Support folder to recreate the .cab file(s). After
recreating the cabinet file(s), verify that they are not corrupt by manually
extracting the files again, and then retrying the installation.
For additional information about rebuilding cabinet files by running a .bat
file, please see the following article in the Microsoft Knowledge Base:
Q191212 HOWTO: Modify and Rebuild .cab Files Built with PDW
For more information on using the Extract.exe utility, you can type the
following command at an MS-DOS command prompt:
extract.exe /?
For even more information on Extract.exe, please see the ActiveX SDK
documentation as referred to in the REFERENCES section of this article.
Test for Setup Files Left on System
If the symptom occurred after a previous installation attempt of the same
application failed (for example, the computer stopped responding during
setup), follow these steps:
On the target computer, search for a copy of your application's .cab file(s)
in the Windows folder (or Winnt folder on NT or Windows 2000). If found,
delete the .cab file(s).
Setup places the .cab file(s) in the Windows or Winnt folder and removes
them at the end of a successful Setup. However, if the installation program
exits abnormally, the .cab files may be left on the system.
In the Windows\Temp folder (or the folder specified by the TEMP environment
variable on NT or Windows 2000), look for a subfolder named Msftqws.pdw. If
found, delete the subfolder.
On the target computer, locate the following files. If any of these files
have a size of 0 bytes, delete the file:
\Windows\System\Vb6stkit.dll (or \Winnt\System32\Vb6stkit.dll)
\Windows\St6unst.exe (or \Winnt\St6unst.exe)
Run Setup again.
Machine-Specific Problem
If the troubleshooting suggestions in this article do not resolve the
problem, there may be something specific about the configuration of the
target computer that is causing the error.
Please contact Microsoft Technical Support for further assistance.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at
the beginning of this article.
This bug was corrected in Visual Studio 6.0 Service Pack 3.
For more information about Visual Studio service packs, please see the
following articles in the Microsoft Knowledge Base:
Q194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
Q194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed
REFERENCES
For more information about using Extract.exe, please see the documentation
found in the ActiveX Software Development Kit (SDK). The ActiveX SDK is
available for download from the following location:
http://www.microsoft.c
 om/workshop/misc/activexsdk/default.asp
Additional query words: find reboot
Keywords : kbwizard kbtophit kbAppSetup kbVBp600bug kbGrpVB
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbbug
Technology :
Last Reviewed: June 28, 2000
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.
----------------------------------------------------------------------------
----
^^^^^^^^^^^^^^^^
hth
Ciao
Aldo