And this can be easily avoided: 1. double-click 2. the .exe extracts the installation files 3. setup.exe is auto-fired 4a. setup.exe finds MDAC is not correct version and fails with message box about the fact 4b. setup.exe is satisfied by MDAC version and ODBC is installed 5. extracted files are deleted. Thus both installations will have similar behavior and chances for confusion will be less. And "That's something we can consider for future releases.". So wait for a while and it will come for free ;-)
Zlatko Krastev IT Consultant Gerald Wichmann <[EMAIL PROTECTED]> on 06.11.2001 21:30:53 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: ODBC Driver Theres no real difference in the scenarios you present but that's not really what we were discussing either. We were comparing installing the BA Client to the ODBC driver. BA client: Doubleclicking on the .exe will cause it to unpack and automatically run setup.exe so you can continue with the installation. i.e. after it unpacks you don't have to manually go find the setup.exe file and run it yourself because the packaged BA Client does it for you. ODBC driver: Doubleclicking on the .exe will cause it to unpack into a fairly obscure default directory and then exit. The setup.exe file doesn't automatically launch for the reasons Andy explained below. Thus you have to go find the setup.exe file and figure this out. Initially when you doubleclicked the .exe it's not entirely clear whether the driver was installed or not (it wasn't). If you just installed the BA Client beforehand, you may very well assume it did. Thats where the confusion comes up. Gerald Wichmann System Engineer StorageLink 408-844-8893 (v) 408-844-9801 (f) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Remco Post Sent: Tuesday, November 06, 2001 2:38 AM To: [EMAIL PROTECTED] Subject: Re: ODBC Driver Hmmm, now I don't see the logic, tell me the functional difference between the following sequences: 1- verify the MDAC is installed 2- unpack and install the odbc driver or: 1- unpack the odbc driver 2- verify the MDAC is installed 3- install the ODBC driver I must be missing some obvious information here.... > Hi Gerald, > > Glad to hear that you've got it working! > > You are, of course, correct... ideally the ODBC driver install would > launch as soon as it is unpacked. > > The reason we don't do this is because of the prerequisite that the MDAC > be installed prior to running the setup.exe program. If the MDAC is not > installed (as could be the case for Windows 95, 98 and NT 4.0), then the > ODBC setup program should not be run until you've verified that you have > the correct MDAC install package (or you can install the MDAC on your own, > then run the ODBC setup program). The README file for the ODBC driver > discusses this in the "Installation" sections. > > I think that there are areas of the install process that can be improved, > especially for the case where MDAC is already installed. That's something > we can consider for future releases. > > Thanks for your feedback. > > Regards, > > Andy > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Development > Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS > Internet e-mail: [EMAIL PROTECTED] > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > > > > > Gerald Wichmann <[EMAIL PROTECTED]> > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > 11/05/2001 15:08 > Please respond to "ADSM: Dist Stor Manager" > > > To: [EMAIL PROTECTED] > cc: > Subject: Re: ODBC Driver > > > > That was the problem. After running the BA Client exe which runs the > install after it unpacks, I just assumed the ODBC .exe would do the > same. I noticed by the README you suggested that there should be a > /program files/Tivoli/TSM/odbc directory and there was none. Then I > noticed the behavior of the ODBC exe and dug down to find that disk1 > directory and ran setup.exe. > > Problem solved.. works fine once you figure that out. Confusing way of > doing things though. You guys should package the two similarly IMO. > > Gerald Wichmann > System Engineer > StorageLink > 408-844-8893 (v) > 408-844-9801 (f) > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of > Andrew Raibeck > Sent: Monday, November 05, 2001 11:20 AM > To: [EMAIL PROTECTED] > Subject: Re: ODBC Driver > > One more thing occurs to me: the executable from the FTP sit just > extracts > the install image. Did you subsequently run the setup.exe program, which > performs the actual install? > > Regards, > > Andy > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Development > Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS > Internet e-mail: [EMAIL PROTECTED] > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > ----- Forwarded by Andrew Raibeck/Tucson/IBM on 11/05/2001 12:18 ----- > > > Andrew Raibeck > 11/05/2001 11:55 > > > To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > cc: > From: Andrew Raibeck/Tucson/IBM@IBMUS > Subject: Re: ODBC Driver > > > > > > > Please have a look at the README file that accompanies the ODBC driver. > In > particular, you should look at the "Troubleshooting/Diagnostics" > section. > > Regards, > > Andy > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Development > Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS > Internet e-mail: [EMAIL PROTECTED] > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > > > > > Gerald Wichmann <[EMAIL PROTECTED]> > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > 11/05/2001 11:18 > Please respond to "ADSM: Dist Stor Manager" > > > To: [EMAIL PROTECTED] > cc: > Subject: ODBC Driver > > > > I just installed the ODBC driver on win2k server which comes with the > latest TSM 4.2.1 client on tivoli's website. After installing both the > BA client and ODBC driver, I open the ODBC connections dialog box and > try to add an ODBC connection but the TSM ODBC driver isn't listed in > the list of ODBC drivers. > > Any suggestions? > > Gerald Wichmann > System Engineer > StorageLink > 408-844-8893 (v) > 408-844-9801 (f) > -- Met vriendelijke groeten, Remco Post SARA - Stichting Academisch Rekencentrum Amsterdam High Performance Computing Tel. +31 20 592 8008 Fax. +31 20 668 3167 "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams
