PDA

View Full Version : MSVBVM50.DLL - can I put it anywhere else but windows\system?



NewsArchive
08-14-1997, 12:00 AM
I've developed an app in VB5 and am now building the setup for it. It
is compiled native and I understand that I still need to include the VB5
virtual machine dll - MSVBVM50.DLL.

However, I want to install all the files, dlls, ocxs, exes - the whole
lot - into one directory on a network drive so that more than one user
can use the app at a time.

When I did this and installed the entire app and associated files into
one directory on a network drive I got an error saying that MSVBVM50.DLL
could not locate OLEAUT32.DLL when I ran the program, even though they
were both in the installation directory.

I changed the setup to install the MSVBVM50.DLL and the other dll's into
the c:\windows\system directory on the test machine and the app worked
fine.

I realise that you are now supposed to put these system files into the
windows\system directory, but this means that the app will only work on
the machine it is installed on, meaning it has to be installed separatly
onto each machine we want to use it on.

I'm guessing that MSVBVM50.DLL *has* to be in the windows\system
directory, am I correct? Does anyone know if you can work around this?

TIA for any help anyone can give.
Cheers,
--
Andy Bibby
ADG Computer Systems Ltd
Oxford, UK.

NewsArchive
08-15-1997, 12:00 AM
Hi Andy.

When I have an app that is run on our network, I create an installation
directory beneath directory where the app itself will be run. I copy all
the Installshield files to this directory. Each user can then run the
install from this directory. The installation will copy all the necessary
DLL's, OCX's, etc to their individual \windows\system directory and copy
(re-install) the rest of the files to the network app directory. This has
worked very well for us.

Let me know if I can be of any more help.

And remember...

"When the going gets tough, the weird turn pro."
-- R. Duke


Andy Bibby <andybibby@usa.net> wrote in article
<33F2E5FC.9639FE5A@usa.net>...
> I've developed an app in VB5 and am now building the setup for it. It
> is compiled native and I understand that I still need to include the VB5
> virtual machine dll - MSVBVM50.DLL.
>
> However, I want to install all the files, dlls, ocxs, exes - the whole
> lot - into one directory on a network drive so that more than one user
> can use the app at a time.
>
> When I did this and installed the entire app and associated files into
> one directory on a network drive I got an error saying that MSVBVM50.DLL
> could not locate OLEAUT32.DLL when I ran the program, even though they
> were both in the installation directory.
>
> I changed the setup to install the MSVBVM50.DLL and the other dll's into
> the c:\windows\system directory on the test machine and the app worked
> fine.
>
> I realise that you are now supposed to put these system files into the
> windows\system directory, but this means that the app will only work on
> the machine it is installed on, meaning it has to be installed separatly
> onto each machine we want to use it on.
>
> I'm guessing that MSVBVM50.DLL *has* to be in the windows\system
> directory, am I correct? Does anyone know if you can work around this?
>
> TIA for any help anyone can give.
> Cheers,
> --
> Andy Bibby
> ADG Computer Systems Ltd
> Oxford, UK.
>