Bummer... $50.00 down the drain

[EZapps]

I spent $50.00 today to enable a popular download site to evaluate and hopefully approve my app for redistribution. It didn't get very far. Evidently, during installation on their Windows 98 machine, an error occurred. As they state:

C:\WINDOWS\SYSTEM\RichEd32.dll
An access violation occured while copying the file.

I'm not sure there's a work around for this, but I only have so many $50 bills. I have a gut feeling though, that this error was no fault of my own. I'm betting this is a bug with Windows 98.

Anyway, has anyone else experienced this problem when re-distributing the riched32.dll?

Do I need to? Maybe every 32 bit systems have it?

Thanks in advance.

[Jmacp]

So they only give you one chance ? Thats a bit harsh for $50.

[EZapps]

Well, I don't want to bad mouth them as I've made that mistake before. To be honest, I'm not sure. Maybe if I sent them an email explaining my case, I could re-submit... I don't know.

However, if I can't find a solution soon, surely it's been a waste.

[MikkyThomeon]

Surely an access violation means that they already have a version of the component on their machines??

Tell the users to ignore the message and continue, or you could try to omit the component from the disttribution entirely. or you could ask them to restart windows and try installing again.

[EZapps]

Originally posted by MikkyThomeon
Surely an access violation means that they already have a version of the component on their machines??

Tell the users to ignore the message and continue, or you could try to omit the component from the disttribution entirely. or you could ask them to restart windows and try installing again.

Not sure about that. It could be that the access violation occurs because some other process is running that is also accessing the riched32.dll (perhaps, in the background) at the same time the installation program is being launched.

[MikkyThomeon]

I can't believe that all this time I have been using msdos batch files and the VB pdw to deply apps. This link kicks butt!!! The best and most flexible installer around!!!

http://www.jrsoftware.org/

I thinks with a bit of the pascal scripting you should be able to check and handle access violations on the target machines as well


Good luck

[BrianS]

Unless you care about Win98 Users, just say it's not compatible with it.

[MikkyThomeon]

After having read quite a bit on redistibutable dll's, I found on the Inno DB documentation that riched32.dll is one of the dll's which you should not try to redistribute - can cause all sorts of hassles.
This dll is shipped with windows so there should ne bo need to include it in your package.

This confirms what I said about access violations, just remove the dll from your installation package an you should be OK. Also note that M$ has done a few bad things with some of these components - even though the dll for one version of windows has the same name as another dll file, the two files are actually completely different dll's!!!!