ComDat.Dll (An access violation Occured) ?

[CT]

Greeting.

I used the VB6 package and development wizard to compile my newly developed
VB6 program into 8 sy# diskette.
I then copy these files into different diskettes and took it to my user
place who is running window nt for installation. When I copy the last
diskette this message stare straight into my face!

C:\Windows\Sysem32\Comcat.dll
An Access violation occured while copying the file
<Retry> <Cancel><Ignore>

When I try pressed ignore button, the setup program ask me to insert
diskette #2 into <A> drive which I duely did. But the setup program kept
asking me to insert disk 2 cause it cannot find file A:\Pcosys~2.cab. I did
a dir on <A> drive and discovered that pcosys~2.cab is actually inside this
diskette no. 2

What did I done wrong???? can it be that i missed something on the package
and development wizard. or is ti due to the copy sy1 to sy 8 method? I did a
simple copy of sy1.cab to sy 8.cab into <a> drive and copy setup.exe,
setup.lst into another diskette. Oops, I am using Window 98SE for
development work.

Any suggestion to overcome the problem above is most welcome.

Regards

[Dim]

The violation most likely occurs because the dll is being used by some other aplication. I don't think you HAVE to install a new one, as long as the user has it. But if you must, then close down ALL running applications and try doing it then.

Gl,
D!m

PS. I would suggest using the one cab file and the two setup files. It's much simpler.

[HDR]

Unfortunately, (or maybe fortunately) comcat.dll is used by Windows. It is the "Component Category Manager Library". You do not ever have windows in a state where it isn't in use. My problem is that on a machine I loaded my application on, the app dies when it can't find it's entry point in comcat.dll. That machine is using a newer version of the DLL. It is a COM component, and I thought one of the great things about COM, was that you never gomered up previous version of programs using the component. Maybe that doesn't apply to Microsoft.

[CT]

If that is the case, how do I overcome this comdat.dll problem. Surely there must be a way to do it ?

Best Regards
CT