From: MarceepooNu on
I think that scrrun.dll is messed up (New technical term) somehow. But if I
knew what I am talking about, I wouldn't be bothering you folks.

This line: Set fso = CreateObject("scripting.filesystemobject")
causes this error message to appear:
Error: (null) Code: 8002801D

I've dragged scrrun.dll onto regsvr32.exe several times (just to be sure I
actually had done it) , each time getting the message: DllRegisterServer in
C:\Windows\System32\scrrun.dll succeeded.

I'm running WinVista Ultimate 64bit, completely updated.

Does anybody have any ideas about how I can get the filesystemobject working
again? I'm crippled w/o it.

Thanks,

Marc





--
MarceepooNu
From: mayayana on

> I think that scrrun.dll is messed up (New technical term) somehow. But if
I
> knew what I am talking about, I wouldn't be bothering you folks.
>
> This line: Set fso = CreateObject("scripting.filesystemobject")
> causes this error message to appear:
> Error: (null) Code: 8002801D
>
> I've dragged scrrun.dll onto regsvr32.exe several times (just to be sure I
> actually had done it) , each time getting the message: DllRegisterServer
in
> C:\Windows\System32\scrrun.dll succeeded.
>

Windows 64 is a mess. The 64-bit system folder is named
System32, while the 32-bit folder has the ridiculous and
misleading name of "SysWOW64". So if you're dragging
scrrun.dll from System32 onto RegSvr32 then you have the
wrong mix. (Or it's only partially registering. I haven't used
Win64. I know there are two versions of wscript.exe. I assume
there are also two versions of scrrun.dll, but I'm not certain.)

I would think that your script would find the right version
either way. If it really is not registered then the question is
how either version could have become unregistered.
Virus? A busybody who thinks scrrun.dll is unsafe. (A lot of
corporate network admins think so.)

I did a quick search and don't find anything like what you're
describing, except from people who are trying to create FSO
from ASP.

> I'm running WinVista Ultimate 64bit, completely updated.
>
> Does anybody have any ideas about how I can get the filesystemobject
working
> again? I'm crippled w/o it.
>
> Thanks,
>
> Marc
>
>
>
>
>
> --
> MarceepooNu


From: MarceepooNu on
Thank you. Very helpful.
--
MarceepooNu


"mayayana" wrote:

>
> > I think that scrrun.dll is messed up (New technical term) somehow. But if
> I
> > knew what I am talking about, I wouldn't be bothering you folks.
> >
> > This line: Set fso = CreateObject("scripting.filesystemobject")
> > causes this error message to appear:
> > Error: (null) Code: 8002801D
> >
> > I've dragged scrrun.dll onto regsvr32.exe several times (just to be sure I
> > actually had done it) , each time getting the message: DllRegisterServer
> in
> > C:\Windows\System32\scrrun.dll succeeded.
> >
>
> Windows 64 is a mess. The 64-bit system folder is named
> System32, while the 32-bit folder has the ridiculous and
> misleading name of "SysWOW64". So if you're dragging
> scrrun.dll from System32 onto RegSvr32 then you have the
> wrong mix. (Or it's only partially registering. I haven't used
> Win64. I know there are two versions of wscript.exe. I assume
> there are also two versions of scrrun.dll, but I'm not certain.)
>
> I would think that your script would find the right version
> either way. If it really is not registered then the question is
> how either version could have become unregistered.
> Virus? A busybody who thinks scrrun.dll is unsafe. (A lot of
> corporate network admins think so.)
>
> I did a quick search and don't find anything like what you're
> describing, except from people who are trying to create FSO
> from ASP.
>
> > I'm running WinVista Ultimate 64bit, completely updated.
> >
> > Does anybody have any ideas about how I can get the filesystemobject
> working
> > again? I'm crippled w/o it.
> >
> > Thanks,
> >
> > Marc
> >
> >
> >
> >
> >
> > --
> > MarceepooNu
>
>
> .
>