Visual Studio 6.0 Ent - Component Probs

Microsoft Visual studio v.6.0 enterprise...
June 4, 2011 at 16:37:44
Specs: Windows XP/2K, amd/1024
I have Visual Studio 6.0 Enterprise version and a project that we have had for years at where I work. Everything has worked fine for a long time. Because of bloated and junked up Windows I had to crash about 2 months ago and re-install everything on my PC.

So I re-installed VS 6.0 on my PC after everything else, all of a sudden when I launch my app I get a bunch of Component Licensing problems like the image below all over the place when I pull up a form to edit.

Every form has some component on it that does this. Then at the end I get a message saying there is a problem with the License.dat file I think it was. And it won't display any of those components at all on the form.

So I got fed up and installed it on an empty Win XP I have in VirtualBox. Hmmm everything works fine there, no licensing problems at all!!

So fine, for programming purposes and not junking up my PC I have created a win2k VirtualBox that is for programming in this system and application only. After installing SQL server and the program I copied the source over to the Box and then installed Visual Studio 6.0, fully mind you, not just VB.

Same problem, so why here and on my PC but not on the other VirtualBox with XP, which is what my system is?

Does anyone know of a way to fix this, I can only imagine that some files got copied wrong and screwed up. But why does it work on a clean system but not on this system that doesn't really have a lot on it, or mine??

See More: Visual Studio 6.0 Ent - Component Probs

Report •

June 4, 2011 at 17:27:58
You will find that when you reinstalled the Operating system on the old computer you deleted the licence files for the third party components.

When you installed on the clean system you started a new trial period and after that has expired that will start popping with the same screen, usually after 30 days.

You need to install the third party controls with the original install disk and registration code. Active Thread Plus is not part of VS6.


Report •

June 5, 2011 at 06:17:41
Ok I understand what your saying and I would agree seeing what you just explained. But, the second install is on a Win2K virtual machine, it's brand new system install yesterday, never been used before. So in theory it should have 30 days also right? But yet it doesn't work.

The one I said does work I just turned on that virtual machine and moved the clock forward to 2012 and they all still work, no problems. So that can't be it if I moved it a year ahead and they still work.

Report •

June 5, 2011 at 07:16:43
Changing the system clock will have little effect on the way these third party components work. As they are interacting with the system a low level there are all kinds of subtle ways of checking the validity of licences. Just changing the system clock would be too easy. There are all kinds of ways of checking, the system date, registry entries and possible even a small modification of the control itself and they all have to match up.

They are designed so that when the control is distributed with an application it cannot be used in a development environment although it works fine in a compiled application that was compiled with a legitimate licence in place.

Believe me, I have a number of these third party controls and it is impossible to circumvent the licensing requirements


Report •

Related Solutions

Ask Question