posnorm
asked on
OCX Dependancy #2
See my question OCX "Dependancy Question" for a complete history, which got quite lengthy. Recap:
Using VB5 (upgrade installed over VB3). Suddenly, the setup wizard started reporting that COMCTL32.OCX and COMDLG32.OCX had dependancy files that were out of date. VBGuru very kindly educated me.
Question #1: If these files were updated during my internet sessions, without my knowledge, and without updating the dependancy files, can I expect this to happen again from time to time? I am profoundly disturbed at that.
Following VBGuru's instructions, I downloaded VBSP3.EXE (took 2.5 hours!). Didn't know where to put it, and not wishing to clutter my desktop, I put in a file "norm". Executed it. It created two new subfiles under "norm".
"vs97_sp3" contains setup.exe, 10 subfolders with three letter names, and two .ico files.
Question #2: What is all that, and what should I do with it?
The other subfolder is named "v42", and I was astonished to see that it evidently contains a complete set of setup files for my application! I have three versions of my app, in different folders. Which one did it pick? Why? I could run those setup files and see. I would have expected that the service pack would fix the dependancy problem, and I would then create my setup files as usual.
Question #3: Should I delete all that stuff, move VBSP3.EXE to the folder where my VB5 lives, and then execute it?
Question #4: Exactly what is the proper procedure for using service packs?
I'm offering a lot of points for a careful tutorial covering these questions. I appreciate your help. -- Norm
Using VB5 (upgrade installed over VB3). Suddenly, the setup wizard started reporting that COMCTL32.OCX and COMDLG32.OCX had dependancy files that were out of date. VBGuru very kindly educated me.
Question #1: If these files were updated during my internet sessions, without my knowledge, and without updating the dependancy files, can I expect this to happen again from time to time? I am profoundly disturbed at that.
Following VBGuru's instructions, I downloaded VBSP3.EXE (took 2.5 hours!). Didn't know where to put it, and not wishing to clutter my desktop, I put in a file "norm". Executed it. It created two new subfiles under "norm".
"vs97_sp3" contains setup.exe, 10 subfolders with three letter names, and two .ico files.
Question #2: What is all that, and what should I do with it?
The other subfolder is named "v42", and I was astonished to see that it evidently contains a complete set of setup files for my application! I have three versions of my app, in different folders. Which one did it pick? Why? I could run those setup files and see. I would have expected that the service pack would fix the dependancy problem, and I would then create my setup files as usual.
Question #3: Should I delete all that stuff, move VBSP3.EXE to the folder where my VB5 lives, and then execute it?
Question #4: Exactly what is the proper procedure for using service packs?
I'm offering a lot of points for a careful tutorial covering these questions. I appreciate your help. -- Norm
While installing vb5, the setup was informing you that you had old files(ocx's). And they will be upgraded. You just have to continue with the setup process by clicking continue. After completing the vb5 installation you can run sp3 as JSA mentioned.
Oh yeah, as for question#3. Don't move vbsp3.exe, just run the setup program from where it is, like I explained in my last comment.
While installing vb5, the setup was informing you that you had old files(ocx's). And they will be upgraded. You just have to continue with the setup process by clicking continue. After completing the vb5 installation you can run sp3 as JSA mentioned.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Looks like I should have posted my answer as an answer instead of a comment!
ASKER
Many thanks to all those who took the time to help me!!
VBGuru: Thank you! The length of my first stab at this was getting out of hand, so I re-asked. I'm glad you answered. I must say that you are an excellent teacher. Your discourse is quite complete and to the point. Sometimes a reply is so terse that one has a "loose ends" feeling.
Many thanks again. -- Norm
VBGuru: Thank you! The length of my first stab at this was getting out of hand, so I re-asked. I'm glad you answered. I must say that you are an excellent teacher. Your discourse is quite complete and to the point. Sometimes a reply is so terse that one has a "loose ends" feeling.
Many thanks again. -- Norm
ASKER
VBGuru: After executing "setup.exe" in folder "vs97_sp3" (which were created by executing "vbsp3.exe", the download) I again tried the setup wizard for my app. Now it only reports that the dep file for "comctl32" is out of date. It seems this is not yet fixed. What now? -- Norm
What version is your comctl32.ocx?
Please check and let me know.
To check the version number go to c:\windows\system\ and select comctl32.ocx. On right clickng you will get a conext menu selsect properties. It opens a property sheet. Select the version tab.
If it is version of COMCTL32.OCX later than 5.00.3714 then
these are all the possible information you get from msdn.
http://support.microsoft.com/support/kb/articles/Q172/8/88.ASP
http://support.microsoft.com/support/kb/articles/Q167/1/21.asp
http://support.microsoft.com/support/kb/articles/Q167/1/23.asp
http://support.microsoft.com/support/kb/articles/Q172/7/02.ASP
http://support.microsoft.com/support/kb/articles/Q167/1/23.asp
Now i think you are not facing problems with COMDLG32.OCX?
So the sp3 had taken care to fix that problem.
This time you download http://support.microsoft.com/download/support/mslfiles/Comctlzp.exe and install and don't worry it doesn't take much time to download. When you download it copy the file and into a new directory and double click it will extrct the seup.exe on the same folder. Now double click setup.exe. I think it should fix the problem with the comctl32.dep.
Let me know your feedback
Please check and let me know.
To check the version number go to c:\windows\system\ and select comctl32.ocx. On right clickng you will get a conext menu selsect properties. It opens a property sheet. Select the version tab.
If it is version of COMCTL32.OCX later than 5.00.3714 then
these are all the possible information you get from msdn.
http://support.microsoft.com/support/kb/articles/Q172/8/88.ASP
http://support.microsoft.com/support/kb/articles/Q167/1/21.asp
http://support.microsoft.com/support/kb/articles/Q167/1/23.asp
http://support.microsoft.com/support/kb/articles/Q172/7/02.ASP
http://support.microsoft.com/support/kb/articles/Q167/1/23.asp
Now i think you are not facing problems with COMDLG32.OCX?
So the sp3 had taken care to fix that problem.
This time you download http://support.microsoft.com/download/support/mslfiles/Comctlzp.exe and install and don't worry it doesn't take much time to download. When you download it copy the file and into a new directory and double click it will extrct the seup.exe on the same folder. Now double click setup.exe. I think it should fix the problem with the comctl32.dep.
Let me know your feedback
ASKER
First: To the comments other's have provided: This problem is NOT the installation of VB5. VB5 has been used here for quite some time when this problem suddenly appeared. I mentioned my VB5 was an upgrade to VB3 in case it mattered.
VBGuru: Yes, SP3 took care of COMDLG32.OCX.
My version of COMCTL32.OCX was 5.01.4319. I followed your latest instructions from http-----/mslfiles/Comctlz
(Unzipping COMCTLZP.EXE gave me COMCTL32.EXE, not "setup.exe".)
I will investigate the five .asp files you gave me. Some time back I purchased Cybermedia's "Uninstaller", and got myself in trouble by deleting something by mistake. Took some doing to fix that.
This thing came with something called "Oil Change", and no information about it. I understand it goes out on the net and updates various stuff. I've never used it (scared to death of it), but thought it was worth mentioning to you. -- Norm
VBGuru: Yes, SP3 took care of COMDLG32.OCX.
My version of COMCTL32.OCX was 5.01.4319. I followed your latest instructions from http-----/mslfiles/Comctlz
(Unzipping COMCTLZP.EXE gave me COMCTL32.EXE, not "setup.exe".)
I will investigate the five .asp files you gave me. Some time back I purchased Cybermedia's "Uninstaller", and got myself in trouble by deleting something by mistake. Took some doing to fix that.
This thing came with something called "Oil Change", and no information about it. I understand it goes out on the net and updates various stuff. I've never used it (scared to death of it), but thought it was worth mentioning to you. -- Norm
Hi to your comment >>Unzipping COMCTLZP.EXE gave me COMCTL32.EXE, not "setup.exe".
Yes, i installed this long time back so i forgot. As for as your version concerned it is the same as mine 5.01.4319! And after installing COMCTLZP.EXE it fiexd that probelem of dependency. did you run COMCTLZP.EXE ? sorry for the confusion
Yes, i installed this long time back so i forgot. As for as your version concerned it is the same as mine 5.01.4319! And after installing COMCTLZP.EXE it fiexd that probelem of dependency. did you run COMCTLZP.EXE ? sorry for the confusion
ASKER
Yes, I first ran comctlzp.exe, which gave me comctl32.exe and a readme. I ran comctl32.exe, and it seemed to run normally.
I took the trouble to check my versions of oleaut32.dll, comcat.dll, olepro32.dll, asycfilt.dll, and stdole2.tlb, and they all have versions numbers greater than those specified in http----/q167/1/21.asp
They all now terminate in version "4275" and comcat.dll is version 5.0. From this, they appear to have been installed together, I guess from sp3. Before, they all had various version numbers. -- Norm
I took the trouble to check my versions of oleaut32.dll, comcat.dll, olepro32.dll, asycfilt.dll, and stdole2.tlb, and they all have versions numbers greater than those specified in http----/q167/1/21.asp
They all now terminate in version "4275" and comcat.dll is version 5.0. From this, they appear to have been installed together, I guess from sp3. Before, they all had various version numbers. -- Norm
ASKER
Also: I checked the version of COMCTL32.DEP, and it is "version 5.0.38.28". This is what it says when I open it with notepad. -- Norm
Sounds like there are some lazy distributors out there who aren't taking the time to add the dependancy files to thier distributions. The only way I can see solving this is to periodically update these files manually.
Regarding Questions #2 & #4, the SP3 files you downloaded were just self-extracting EXE's. When you ran them, they just un-expanded themselves. All you have to do is run SETUP.EXE. It will find the location of VB and update it. When it is complete, you can completely delete your "norm" folder, and all of it's subdirectories...VB has already been updated, and you don't need them anymore.