Dependency scrrun.dll is out of date.

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Stan Hilliard - 03 Sep 2004 21:34 GMT

The Packaging and Deployment wizard tells me that the dependency of
scrrun.dll is out of date.

SCRRUN.DEP 6/4/98

scrrun.dll 6/26/01

How can I get a set of the DLL and DEP files that match?

I want the installed program to run on win 9x, 2000, ME, and XP.

Information will be appreciated,

Stan Hilliard

Reply to this Message

Stan Hilliard - 03 Sep 2004 22:05 GMT

>The Packaging and Deployment wizard tells me that the dependency of
>scrrun.dll is out of date.
[quoted text clipped - 10 lines]
>
>Stan Hilliard

I just discovered that there is a bug in SCRRUN that is fixed by
downloading either:

scripten.exe for Windows 2000 and XP, or

scr56en.exe for Windows 98, Windows Millennium Edition, and Windows NT
4.0

Does this mean that I have to have two different setup programs -- one
for win2k, XP and another for Win98,ME,NT?

Stan Hilliard

Reply to this Message

MikeD - 03 Sep 2004 23:10 GMT

> >The Packaging and Deployment wizard tells me that the dependency of
> >scrrun.dll is out of date.
[quoted text clipped - 21 lines]
> Does this mean that I have to have two different setup programs -- one
> for win2k, XP and another for Win98,ME,NT?

In all probability, yes. You'd be MUCH better off not including this DLL in
your package, let alone using it in the first place. There are many versions
of it floating about and certain versions will screw up Windows.
Furthermore, I believe this file is protected by Windows File Protection
(under Win2000/XP/ME), so PDW wouldn't be able to replace it anyway.

What are you using from this DLL? If the FSO, that's another reason for
dropping it. There's no *good* reason to use the FSO in VB. Even if you're
using something else from this DLL (the only other thing I can see from it
that's not associated with the FSO is the Dictionary object), you're still
likely to run into problems because cautious admins (or even users who are
admins of their own PCs) will remove this file and/or heavily restrict its
use (simply by disabling all scripting).

If you tell us what you're using it for, somebody can likely inform you of
alternatives.

Mike

Reply to this Message

Stan Hilliard - 04 Sep 2004 02:47 GMT

>> >The Packaging and Deployment wizard tells me that the dependency of
>> >scrrun.dll is out of date.
[quoted text clipped - 40 lines]
>
>Mike

Thanks mike,

I use scrrun.dll for the Dictionary object.

I have a large project and the dictionary object is quite central to
it.

Stan Hilliard

Reply to this Message

Stan Hilliard - 04 Sep 2004 04:38 GMT

>>> >The Packaging and Deployment wizard tells me that the dependency of
>>> >scrrun.dll is out of date.
[quoted text clipped - 49 lines]
>
>Stan Hilliard

More information: My goal is to use PDW to generate setup.lst for the
list of files that my project needs, and then to use Inno Setup to
build the install file.

My project successfully uses scrrun.dll even though the .dep file is
out of date. This, both in the VB6 environment and after compiling.
Could it be that setup.dep is unnecessary except for PDW?

Stan Hilliard

Reply to this Message

VB Forum / Deployment / September 2004

Dependency scrrun.dll is out of date.