Newsgroup: it.comp.lang.visual-basic
Titolo: [?] Installazione VB6

Ho un problema che mi sta procurando diversi notti insonni ed ancora non
sono riuscito a risolvere. Dopo aver scritto un'applicazione che accede a DB
access 97 tramite PROVIDER OLE-DB Microsoft JET 3.51, sto tentando di creare
il KIT di installazione ma non riesco a generare qualche cosa di
funzionante.
Provo ad installare su una macchina "pulita" con solo WIN98 2^ Ed. (Ho
provveduto ad installare anche MDAC 2.5)
Dopo aver installato, quando lancio la mia applicazione, mi dice CHE NON
ESISTE IL PROVIDER e che potrebbe non essere installato; io so che necessita
solo quello per JET 3.51!
A questo punto installo, dal CD di visula studio, solo la parte di accesso
ai dati (circa 6 MB). COme per magia ora funziona tutto. questo significa
che probabilmente mi viene installto correttamente il provider
OLE-DB.JET.3.51.
Le mie domande sono le seguenti:
    C'č qualche omissione da parte mia di REFERENCES all'interno del
progetto che non permette al programma di Creazione Pacchetto di
Installazione di capire che si utilizza il provider in oggetto e quindi non
me lo inserisce nel pacchetto?
    C'č qualcuno che conosce quali sono i file necessari per installare il
PROVIDER di cui ho bisogno? (Anche manualmente)
    C'č un sito dove trovare documentazione precisa e specifica ?
RINGRAZIO CHIUNQUE MI DARA' SUGGERIMENTI.

    C'è un sito dove trovare documentazione precisa e specifica ?


NO.
Utilizzo però 2 HD!
Ho la mia macchina con disco C: sulla quale sviluppo e genero il pacchetto
di installazione.
Spengo ed attacco un altro disco con installazione "pulita" come disco C: e
configuro il mio come D:
Lancio poi il Setup dal D: (quello di sviluppo!) ed installo su C:

Ieri per un problema simile ho trovato quest'articolo su technet prova a
vedere se ti puņ aiutare.
Cioa
Enrico
FIX: Setup Program Created by PDW Disables Windows 95/98 System [Q193034]
PSS ID Number: Q193034
Article last modified on 04-24-2000
WINDOWS:6.0
WINDOWS
======================================================================
----------------------------------------------------------------------------
---
The information in this article applies to:
- Microsoft Visual Basic Learning, Professional, and Enterprise Editions
for Windows, version 6.0
  on the following platforms: Win95, Win98
----------------------------------------------------------------------------
---
SYMPTOMS
========
The Package and Deployment Wizard (PDW) is used to create a standard
installation program for a program created in Visual Basic 6.0. The target
system is running Windows 95 and contains two hard drive partitions. The
first
hard drive partition contains the operating system files while the second
hard
drive partition contains the TEMP folder and the installation program.
When you run the installation program from the second hard drive partition,
the
following Setup Error message box appears:
   "Setup cannot continue because some system files are out of date on your
  system. Click OK if you would like setup to update these files for you
now.
  You will need to restart Windows before you can run Setup again. Click
Cancel
  to exit setup without updating system files."
After you click OK, one of the following occurs:
- The system restarts but does not completely install the program. When you
run
  the setup program, the following error message appears:
   A required .DLL file, C:\Windows\System\OLEAUT32.DLL was not found.
- During the Start Up process, the following error message appears:
   Windows could not upgrade one or more system files.
   You cannot start the system after seeing this message.
NOTE: This bug only occurs on systems with the following attributes:
- The system is running Windows 95 or Windows 98.
- The system contains at least two hard disk partitions.
- The system folder and the TEMP folder reside on different partitions.
CAUSE
=====
The following files were removed from the System folder and not updated
because
the Windows\System and Temp folders reside on different hard drive
partitions:
- ASYCFILT.DLL
- COMCAT.DLL
- MSVBVM60.DLL
- MSVCRT40.DLL
- OLEAUT32.DLL
- OLEPRO32.DLL
- STDOLE2.TLB
These files are updated during reboot via a mechanism built into Windows 95
and
Windows 98.
RESOLUTION
==========
1. Make sure the Windows\System and Temp folders are on the same drive.
2. If this bug has already occurred, you need to copy the following files to
the
  System directory and restart Windows:
   ASYCFILT.DLL
  COMCAT.DLL
  MSVBVM60.DLL
  MSVCRT40.DLL
  OLEAUT32.DLL
  OLEPRO32.DLL
  STDOLE2.TLB
These files are included in your Visual Basic distribution disks or you can
download the following file from the Microsoft Download Center:
   Vb6sys.exe
(
http://download.microsoft.com/download/vb60ent/Sample31/1/W9XNT4/EN-US/vb6s
ys.exe)
For more information about how to download files from the Microsoft Download
Center, please visit the Download Center at the following Web address
 
http://www.microsoft.com/downloads/search.asp
and then click "How to use the Microsoft Download Center".
Microsoft used the most current virus detection software available on the
date of
posting to scan this file for viruses. Once posted, the file is housed on
secure
servers that prevent any unauthorized changes to the file.
This self-extracting executable file contains the files required by the
System
directory. After you run the self-extracting executable file, copy the
expanded
files to your system directory and restart Windows.
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
MORE INFORMATION
================
When you run an installation program created by the Package and Deployment
Wizard (PDW), the installation copies files to the TEMP directory. As part
of
the installation process, the installation program checks the versions of
the
previously mentioned files stored in the system directory.
If those files in the System directory are older than the files copied to
the
TEMP directory, the installation program causes Windows to restart and to
replace the older files in the System directory with the newer files from
the
TEMP directory during the restart.
If these files are updated, Windows must be restarted.
While Windows is restarting, it first deletes the files in the System folder
then
attempts to replace them with the files in the TEMP folder. If the System
and
TEMP folders are on different hard drive partitions, the deletion succeeds
but
the replacement fails; the older version files are deleted from the System
directory but the newer version files are not copied to the System folder.
Additional query words: PDW Packaging Deploy
======================================================================
Keywords          : kbsetup kbwizard kbVBp600bug kbGrpVB kbVS600sp3fix
Version           : WINDOWS:6.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix
============================================================================
=
Copyright Microsoft Corporation 2000.

Prova con queste indicazioni di Sir JO:
"UDITE UDITE !!!!!!
Sono finalmente riuscito a capire perchč non funziona MAI sto ca**o di
provider OLE DB Jet 3.51 quando si distribuiscono le applicazioni.
Quando si installa MDAC (2.1 o 2.5) non viene installato il driver OLE DB
Jet 3.51
Per risolvere il problema si debbono aggiungere due DLL nel programma
di "Creazione Guidata Pacchetti di Installazione" (CGPI)
Quando il programma CGPI mostra la lista delle DLL da distribuire, scegliete
AGGIUNGI
e aggiungete queste due DLL:
C:\WINDOWS\SYSTEM\MSJT4JLT.DLL
C:\PROGRAMMI\FILE COMUNI\SYSTEM\OLE DB\MSJTOR35.DLL
Proseguite con il programma CGPI e quando vi mostra la lista di dove
verranno installate
le vostre DLL, ponete il cursore sulla voce MSJTOR35.DLL e modificate la
directory
denominata "Posizione installazione" in:
$(CommonFilesSys)\ole db
Spero di aver fatto cosa gradita a piů di una persona
Ciao
Sir Jo
"
Aggiungo solo che su NT i percorsi sono:
C:\WINNT\system32\MSJT4JLT.DLL
C:\Program Files\Common Files\System\OLE DB\MSJTOR35.DLL
Ciao
Basty


Alla faccia del quoting ... :-) :-/
_____________________________________________
James Tiberius Kirk, matricola SC 937-076 CEC
  Nato a Riverside, nello Iowa, USA, Terra
            il 1277.1 (26/03/2233)

 wrote in message 96j2oc$a79$1...@news.IT.net...
