Problems with Packaging and Development Wizard

[1 is a prime!]

I'm on the verge of releasing my first application. I'm using the Packaging and Development Wizard (with Visual Studio) to to make everything stand alone. It is fine apart from one thing...

I can make the CAB files and Set Up file fine, but I get error messages when I try to run the Set Up program. These are the errors:

1) "An access violation occured while copying the file C:\Windows\System\MSVCRT.DLL"

2) "An error occured while registering the file 'C:\Windows\System\EXPSRV.DLL'

If both these errors are ignored (using the subsequent message boxes), the set up completes successfully, and my application works fine! It's just not very professional to have these error messages cropping up.

I figure the errors are because the set up program is trying to replace DLL's that Windows has already. It think one of them is a graphics DLL, right? Is it safe to leave the offending DLL's out of the stand alone?

If anyone has any idea how to prevent these errors from occuring during set up, I would be very grateful if you could help me. Thanks in advance,

Steve.

[Evan]

Hi!

The simple answer is use the
code in the directory of the
setup to make your own setup
program! Just program it to
Ignore errors.

Also. There are programs to
set up your program online
if you would like to use one
of those. They look very
professional.

[1 is a prime!]

Evan,

Thanks very much for the help. However, I'm still fairly new to VB, and don't understand what you mean. Could you tell me in more detail what you mean about ignoring errors please. How do I do it? If possible, I would prefer to package my application using the Packaging and Development Wizard.

Hope you don't mind explaining it to me in more detail. Thanks in advance,

Steve.

[Evan]

OK,

Hmm, I dont want to lead you
in the wrong direction so ill
let one of the gurus handle
this..

If no one trys to help you
I will.

[1 is a prime!]

OK! Thanks for the help Evan!

Can anyone (Gurus especially!) else help?


Here's the thread:

http://64.4.14.250/cgi-bin/linkrd?_l...readid%3d36020
Thanks,

Steve.

[CoreyS]

In the setup directory, check out the file SETUP.LST. This file is a text file. Take out the line that has the MSVCRT.DLL (a VisualC++ DLL I believe) and renumber the lines. That will eliminate that problem. As for the other problem, check out that file, maybe you will see something in there that you can remove to get rid of that problem.

[1 is a prime!]

OK, thanks for the advice CoreyS.

Just one more thing: If I take out the line regarding MSVCRT.DLL, this means the setup wont install this DLL, right? Can I always assume that it will be in the users machine already? Is it a standard Windows DLL? Could taking this DLL out be a source of more errors?

Hope you can help! Many thanks,

Steve.

[CoreyS]

Yeah, that will take it out of the installation. I don't know if it is a Standard .DLL or not but I had the same problem and I removed it from the list and am not having any more problems with regards to that file.

[1 is a prime!]

OK! Thanks for the help - I'll give it a try!

Steve.

[rupertsantos]

Got the exact same problem with my application. actually besides msvcrt.dll, i also get ole32.dll access violation errors. I also decided to remove it as part of the set up file but am not sure of it's success if I try it in many other work stations. Please tell me if you have succeeded .. Thank you very much in advance.

rupert

[Mensoid]

It would be ill-advised to remove those dll's from the install package, they are required for VB to work properly. They are not standard file that some with windows until win2K and I'm not sure about XP. Win 98 feq comes up with those errors, NT sometimes, depending on SP version, win 2K I don't belive errors, and XP does not. The porblem occurs in that to the install package the files are older, but according to windows, they're newer, on the newer OS's VB recognizes that the ones in the install package are older and dosen't try toinstall them, hence no errors. However in 98, NT, and older OS's the files aren't present/aren't new enough and may cause application errors. The best bet is to use a freeware software packaging program, as opposed to the Package and Deployment wizard that comes with VB, and alternative would be to distribute two files, one is the (FULL) install package and the other(SIMPLE) the compiled EXE and any OCX's or other files that aren't part of a simplest install package. And specify instructions to try the SIMPLE one first. should if not function, then try the FULL, or something along those lines. Alot of programs use those DLL's so providing the SIMPLE installer, will work with those systems without difficulty, while still providing the FULL install for the older systems.

[1 is a prime!]

Surprised this thread is still attracting attention, but glad it is still helping people.

Yeah, with two years of full on programming experience under my belt, I'd recommend against using P & D Wizard full stop. InstallShield make some fantastic installer packages these days. The downfall of them though, is that with extra control comes extra complexity - infact, InstallSheild has it's own programming language! ...not to mention the fact that they cost money too, unlike the P & D Wizard, which is free with VB6/VS6.

Mensoid's idea seems pretty sound - another approach would be to make a release of the app. that doesn't install the problem dll's as suggested, and a second installer that installs JUST the dll's. Then you could tell users to install just the installer at first. If the program experiences problems, then the small dll installer could be run. You could call the small package a component update installer or something, then you sound really professional!!!

Good luck!