Update: I moved the ROOT folder to another drive (SSD), restarted VS6Installer, and reset the ROOT location. Now all three "Prepare" blocks are greyed out, and it appears that the installation is ready to proceed (which I'll do tomorrow).
Printable View
Update: I moved the ROOT folder to another drive (SSD), restarted VS6Installer, and reset the ROOT location. Now all three "Prepare" blocks are greyed out, and it appears that the installation is ready to proceed (which I'll do tomorrow).
Hello,
have you tried soultion from : http://www.vbforums.com/showthread.p...-problem/page2
that shows:
Quote:
date of post : 19/4/2013, 02:59AM:
The problem has been resolved by running the following in elevated command prompt:
cd C:\Windows\SysWOW64\
regtlib msdatsrc.tlb
I hope this helps.
Hello gibra & dhernandez,
gibra, I first tried to install VB6 using VS6Installer, and got as far as attempting to install SP6, which failed, saying that it was "unable to open acmsetup.stf". I then went to the 3SP6_VBPro folder and manually ran SP6 by running setupsp6.exe. The first time, it failed saying that it required "elevation", so I ran it again as an administrator. The installation appeared to go ok, with no errors.
Started up VB6, tried to load the RichTextBox control, and still the same "not registered" error.
dhernandez, I then did try to do what you suggested, running the command line, "regtlib msdatsrc.tlb".
Unfortunately, I'm getting the error, "RegisterTypeLib of msdatsrc.tlb failed : 8002801c".
This all looks like this may be permissions related, but I'm the admin (have administrator rights) to my PC, so I don't know where to go from here.
As I've previously said, I've installed VB6 in Win7 (and XP) 32 bit machines without any issues. It's just my 64-bit PC that's giving me fit's.
Thanks,
Bill
Hello,
I've Windows 7 SP1 64 bits with vb6 IDE working perfectly.
With one patch of Microsoft(i don't remember wich one) I had to made the:
regtlib msdatsrc.tlb
But I'm using the "Microsoft Application Compatibility Tooklit" for running well the vb6 ide.
I've applied a "patch" using that programs that permits me running vb6 ide without elevation prompt and running well ide.
I'm attaching the file used with "Microsoft Application Compatibility Tooklit"
Attachment 112101
For applying it i've opened "compatibility administrator (32-bit)" , right click on "custom databases". Selected "Open" and selecting the file attached (the file inside zip file). Then in the new entry of "Custom databases" (named "para visual basic 6 ide") click on "install".
Then closed program and started vb6 ide.
Problem solved. It just came down to running everything as an administrator. That includes "setup.exe" for VB6-Pro, "setupsp6.exe" for SP6, and even running the command prompt as administrator to register the Mouse Wheel (VB6IDEMouseWheelAddin.dll) add-in. MSDN self installed after a reboot from the VB6-Pro installation was complete.
Thanks to all for your help and insight.
Also thanks to gibra for his VS6Installer program. While I had some issues making it work, one feature thing that really speed up the full installation was that VS6Installer facilitated creating three separate installation folders for VB6, MSDN, and SP6. I'm fortunate that I have an SSD drive, so installation took seconds rather than minutes to install.
Today after I installed/uninstalled one application, MSCOMCTL.ocx got problem. I tried to reinstall SP6 but still failed to load MSCOMCTR.ocx. "regsvr32 mscomctl.ocx" also didn't work.
I follow DrUnicode's reply at #12 (http://www.vbforums.com/showthread.p...=1#post4380787), delete the node "{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}" then reinstall SP6, then problem resolved.
Before I delete the registry node, I noticed there're two children, 2.0 and 2.1. After I delete this entry and reinstall SP6 there is only one child: 2.0.
Old Entry:
new install:Code:Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0]
@="Microsoft Windows Common Controls 6.0 (SP6)"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0\0]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0\0\win32]
@="C:\\Windows\\System32\\MSCOMCTL.OCX"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0\FLAGS]
@="2"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0\HELPDIR]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.1]
@="Microsoft Windows Common Controls 6.0 (SP6)"
"PrimaryInteropAssemblyName"="mscomctl, Version=10.0.4504.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.1\0]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.1\0\win32]
@="C:\\Windows\\system32\\MSCOMCTL.OCX"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.1\FLAGS]
@="2"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.1\HELPDIR]
@="C:\\Windows\\system32\\"
Win7,32 bit,VB6/SP6.Code:Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0]
@="Microsoft Windows Common Controls 6.0 (SP6)"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0\0]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0\0\win32]
@="C:\\Windows\\system32\\MSCOMCTL.OCX"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0\FLAGS]
@="2"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0\HELPDIR]
@=""
Interestingly, doing a search on the node "{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}" revealed many 2.1 entries, but like you just one 2.0 entry.
It seems that after a certain point, all the hits are related to controls within MSCOMCTL.ocx.Code:HKEY_CLASSES_ROOT\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0
PrimaryInteropAssemblyName
mscomctl, Version=10.0.4504.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
And just for my 2 cents worth, us VB6 die hards will keep it alive for one reason. MS made the mistake of creating a fabulous platform that's as robust as you imagination take you. On a professional level, I use VB6 for automated test and control, alone with various stand alone applications. To us long term VB6 users, its simple, powerful, and can be written so ANYONE can understand it. I've personally developed over 40 automated test systems, one of which having over 40,000 lines of code. I'm not at liberty to say what it does, but I can say that I'm controlling various instruments on GPIB, Digital I/O on PCI, RS-232, RS-422, and USB platforms all on the same (XP) PC, soon to be upgraded to Win7. Obviously, when .NET and later versions of VB came out, I at least attempted to do a migration, but the wizard just barfed half way through. At the end of the day, I either had to spend 6 months completely re-writing code, or "just don't fix what ain't broke". I went for the latter. I've been pounding out code for more that 40 years, using Assembly, Pascal, C (although I gave up on that long ago), and many others, but VB and its early siblings just made program development a breeze, so I spend less time figuring out code that only a cryptographer can understand and get the job done.
Win7,32 & 64 bit,VB6/SP6
My 2 cents.
I try to minimize dependencies, and I avoid MS ones like the plague.
Codebank allows tutorial or code snippets or attachments and pictures.
http://www.vbforums.com/forumdisplay...-6-and-earlier