Windows Scripting Host on Windows 95 OSR2 
Author Message
 Windows Scripting Host on Windows 95 OSR2

I am trying to get to use WSH on a network of mostly Windows 95 machines,
mostly running OSR2.  We have configured a bare bones machine with OSR 2 to
test our scripts before deploying, but when we run them on the machine we
get object errors.  Looking on TechNet we determined we needed DCOM 95 and
the scripting engine 5.  Maybe IE 4 as well.  After installing that and
Office 97 Pro, the scripts still did not work.  Yet, the scripts run fine on
Windows 98 machines.

Does anybody know what exactly has to be installed to make WSH work on
Win95b?



Sun, 30 Dec 2001 03:00:00 GMT  
 Windows Scripting Host on Windows 95 OSR2
Hi,

We are currently running scripts on a mixture on different versions of 95,
from vanilla through to OSR2.5, and here is what we use as a minimum to
guarantee the scripts will work:

1. IE 4.0 or above (this gets round the DCOM stuff)
2. WSH version 1.0
3. VBScript version 5.0
4. JScript version 5.0

All our machines run exactly the same scripts fine

Happy scripting, hope this helps....

Daud Sweetland


Quote:
> I am trying to get to use WSH on a network of mostly Windows 95 machines,
> mostly running OSR2.  We have configured a bare bones machine with OSR 2
to
> test our scripts before deploying, but when we run them on the machine we
> get object errors.  Looking on TechNet we determined we needed DCOM 95 and
> the scripting engine 5.  Maybe IE 4 as well.  After installing that and
> Office 97 Pro, the scripts still did not work.  Yet, the scripts run fine
on
> Windows 98 machines.

> Does anybody know what exactly has to be installed to make WSH work on
> Win95b?



Sun, 30 Dec 2001 03:00:00 GMT  
 Windows Scripting Host on Windows 95 OSR2
Couple problems with that sir.

(A)  We don't want to push IE 4 out unless it is a last resort.
(B)  We are using WSH 2 Beta 2
(C)  The Engine Install 5 fails

Any suggestions?

Thank you anyway,
BJ Wyatt


Quote:
>Hi,

>We are currently running scripts on a mixture on different versions of 95,
>from vanilla through to OSR2.5, and here is what we use as a minimum to
>guarantee the scripts will work:

>1. IE 4.0 or above (this gets round the DCOM stuff)
>2. WSH version 1.0
>3. VBScript version 5.0
>4. JScript version 5.0

>All our machines run exactly the same scripts fine

>Happy scripting, hope this helps....

>Daud Sweetland



>> I am trying to get to use WSH on a network of mostly Windows 95 machines,
>> mostly running OSR2.  We have configured a bare bones machine with OSR 2
>to
>> test our scripts before deploying, but when we run them on the machine we
>> get object errors.  Looking on TechNet we determined we needed DCOM 95
and
>> the scripting engine 5.  Maybe IE 4 as well.  After installing that and
>> Office 97 Pro, the scripts still did not work.  Yet, the scripts run fine
>on
>> Windows 98 machines.

>> Does anybody know what exactly has to be installed to make WSH work on
>> Win95b?



Sun, 30 Dec 2001 03:00:00 GMT  
 Windows Scripting Host on Windows 95 OSR2
You mention in the original post that you get object errors. Do you mean
that the scripts "run" but can't access objects or some particular object?
What are the exact errors that you are receiving? What objects are you
trying to work with?

Mike Whalen
Windows Script Dev


Quote:
> Couple problems with that sir.

> (A)  We don't want to push IE 4 out unless it is a last resort.
> (B)  We are using WSH 2 Beta 2
> (C)  The Engine Install 5 fails

> Any suggestions?

> Thank you anyway,
> BJ Wyatt



> >Hi,

> >We are currently running scripts on a mixture on different versions of
95,
> >from vanilla through to OSR2.5, and here is what we use as a minimum to
> >guarantee the scripts will work:

> >1. IE 4.0 or above (this gets round the DCOM stuff)
> >2. WSH version 1.0
> >3. VBScript version 5.0
> >4. JScript version 5.0

> >All our machines run exactly the same scripts fine

> >Happy scripting, hope this helps....

> >Daud Sweetland



> >> I am trying to get to use WSH on a network of mostly Windows 95
machines,
> >> mostly running OSR2.  We have configured a bare bones machine with OSR
2
> >to
> >> test our scripts before deploying, but when we run them on the machine
we
> >> get object errors.  Looking on TechNet we determined we needed DCOM 95
> and
> >> the scripting engine 5.  Maybe IE 4 as well.  After installing that and
> >> Office 97 Pro, the scripts still did not work.  Yet, the scripts run
fine
> >on
> >> Windows 98 machines.

> >> Does anybody know what exactly has to be installed to make WSH work on
> >> Win95b?



Sun, 30 Dec 2001 03:00:00 GMT  
 Windows Scripting Host on Windows 95 OSR2
Hi,

The one feature that Win98 has that you might have
left out in the OSR2 install is the Famous....
        Active Desktop Update

When you right click anywhere in the desktop window,
the Active Desktop menu should be there- if not
you will need this update.

HTH,
        M A R K

Quote:

>Couple problems with that sir.

>(A)  We don't want to push IE 4 out unless it is a last resort.
>(B)  We are using WSH 2 Beta 2
>(C)  The Engine Install 5 fails



Sun, 30 Dec 2001 03:00:00 GMT  
 Windows Scripting Host on Windows 95 OSR2
We have a clean install of 95B, and whenever we install the file ste50en.exe
(Windows Scripting Engine 5) we get the error "Error registering the OCX
C:\Windows\System\jscript.dll" and we can't do anything.  This happens
before or after DCOM 95 and/or windows scripting host 2 beta 1.  However,
even after running wsh20en.exe we cannot run any scripts to get the exact
error message.

The scripts we are attempting to run are trying to access the filesystem
object, the shell object, environment, and the network components.

If we install IE 4, the scripts run, after copying and registering
scrrun.dll on a bare Win95B machine with the scripting host 2 beta 1.

Thank You,
BJ Wyatt

Quote:

>You mention in the original post that you get object errors. Do you mean
>that the scripts "run" but can't access objects or some particular object?
>What are the exact errors that you are receiving? What objects are you
>trying to work with?

>Mike Whalen
>Windows Script Dev



>> Couple problems with that sir.

>> (A)  We don't want to push IE 4 out unless it is a last resort.
>> (B)  We are using WSH 2 Beta 2
>> (C)  The Engine Install 5 fails

>> Any suggestions?

>> Thank you anyway,
>> BJ Wyatt



>> >Hi,

>> >We are currently running scripts on a mixture on different versions of
>95,
>> >from vanilla through to OSR2.5, and here is what we use as a minimum to
>> >guarantee the scripts will work:

>> >1. IE 4.0 or above (this gets round the DCOM stuff)
>> >2. WSH version 1.0
>> >3. VBScript version 5.0
>> >4. JScript version 5.0

>> >All our machines run exactly the same scripts fine

>> >Happy scripting, hope this helps....

>> >Daud Sweetland



>> >> I am trying to get to use WSH on a network of mostly Windows 95
>machines,
>> >> mostly running OSR2.  We have configured a bare bones machine with OSR
>2
>> >to
>> >> test our scripts before deploying, but when we run them on the machine
>we
>> >> get object errors.  Looking on TechNet we determined we needed DCOM 95
>> and
>> >> the scripting engine 5.  Maybe IE 4 as well.  After installing that
and
>> >> Office 97 Pro, the scripts still did not work.  Yet, the scripts run
>fine
>> >on
>> >> Windows 98 machines.

>> >> Does anybody know what exactly has to be installed to make WSH work on
>> >> Win95b?



Sun, 30 Dec 2001 03:00:00 GMT  
 Windows Scripting Host on Windows 95 OSR2
Thanks, but I tried that theory this morning.  If you install IE 4 without
the Active Desktop update the scripts still run.  We're trying to avoid
making everyone install IE 4, though.

Thanks anyway,
BJ

Quote:

>Hi,

>The one feature that Win98 has that you might have
>left out in the OSR2 install is the Famous....
>        Active Desktop Update

>When you right click anywhere in the desktop window,
>the Active Desktop menu should be there- if not
>you will need this update.

>HTH,
>        M A R K


>>Couple problems with that sir.

>>(A)  We don't want to push IE 4 out unless it is a last resort.
>>(B)  We are using WSH 2 Beta 2
>>(C)  The Engine Install 5 fails



Sun, 30 Dec 2001 03:00:00 GMT  
 Windows Scripting Host on Windows 95 OSR2
In addition:  ste50en installs fine after IE 4, but not before

Quote:

>We have a clean install of 95B, and whenever we install the file
ste50en.exe
>(Windows Scripting Engine 5) we get the error "Error registering the OCX
>C:\Windows\System\jscript.dll" and we can't do anything.  This happens
>before or after DCOM 95 and/or windows scripting host 2 beta 1.  However,
>even after running wsh20en.exe we cannot run any scripts to get the exact
>error message.

>The scripts we are attempting to run are trying to access the filesystem
>object, the shell object, environment, and the network components.

>If we install IE 4, the scripts run, after copying and registering
>scrrun.dll on a bare Win95B machine with the scripting host 2 beta 1.

>Thank You,
>BJ Wyatt


>>You mention in the original post that you get object errors. Do you mean
>>that the scripts "run" but can't access objects or some particular object?
>>What are the exact errors that you are receiving? What objects are you
>>trying to work with?

>>Mike Whalen
>>Windows Script Dev



>>> Couple problems with that sir.

>>> (A)  We don't want to push IE 4 out unless it is a last resort.
>>> (B)  We are using WSH 2 Beta 2
>>> (C)  The Engine Install 5 fails

>>> Any suggestions?

>>> Thank you anyway,
>>> BJ Wyatt



>>> >Hi,

>>> >We are currently running scripts on a mixture on different versions of
>>95,
>>> >from vanilla through to OSR2.5, and here is what we use as a minimum to
>>> >guarantee the scripts will work:

>>> >1. IE 4.0 or above (this gets round the DCOM stuff)
>>> >2. WSH version 1.0
>>> >3. VBScript version 5.0
>>> >4. JScript version 5.0

>>> >All our machines run exactly the same scripts fine

>>> >Happy scripting, hope this helps....

>>> >Daud Sweetland



>>> >> I am trying to get to use WSH on a network of mostly Windows 95
>>machines,
>>> >> mostly running OSR2.  We have configured a bare bones machine with
OSR
>>2
>>> >to
>>> >> test our scripts before deploying, but when we run them on the
machine
>>we
>>> >> get object errors.  Looking on TechNet we determined we needed DCOM
95
>>> and
>>> >> the scripting engine 5.  Maybe IE 4 as well.  After installing that
>and
>>> >> Office 97 Pro, the scripts still did not work.  Yet, the scripts run
>>fine
>>> >on
>>> >> Windows 98 machines.

>>> >> Does anybody know what exactly has to be installed to make WSH work
on
>>> >> Win95b?



Sun, 30 Dec 2001 03:00:00 GMT  
 Windows Scripting Host on Windows 95 OSR2
In addition to my previous questions:  Does anyone happen to know what about
IE 4 makes it work?  Maybe the cab or something so we could deflate the cab
and manually register the necessary objects/links?

Thanx,
BJ Wyatt

Quote:

>In addition:  ste50en installs fine after IE 4, but not before


>>We have a clean install of 95B, and whenever we install the file
>ste50en.exe
>>(Windows Scripting Engine 5) we get the error "Error registering the OCX
>>C:\Windows\System\jscript.dll" and we can't do anything.  This happens
>>before or after DCOM 95 and/or windows scripting host 2 beta 1.  However,
>>even after running wsh20en.exe we cannot run any scripts to get the exact
>>error message.

>>The scripts we are attempting to run are trying to access the filesystem
>>object, the shell object, environment, and the network components.

>>If we install IE 4, the scripts run, after copying and registering
>>scrrun.dll on a bare Win95B machine with the scripting host 2 beta 1.

>>Thank You,
>>BJ Wyatt


>>>You mention in the original post that you get object errors. Do you mean
>>>that the scripts "run" but can't access objects or some particular
object?
>>>What are the exact errors that you are receiving? What objects are you
>>>trying to work with?

>>>Mike Whalen
>>>Windows Script Dev



>>>> Couple problems with that sir.

>>>> (A)  We don't want to push IE 4 out unless it is a last resort.
>>>> (B)  We are using WSH 2 Beta 2
>>>> (C)  The Engine Install 5 fails

>>>> Any suggestions?

>>>> Thank you anyway,
>>>> BJ Wyatt



>>>> >Hi,

>>>> >We are currently running scripts on a mixture on different versions of
>>>95,
>>>> >from vanilla through to OSR2.5, and here is what we use as a minimum
to
>>>> >guarantee the scripts will work:

>>>> >1. IE 4.0 or above (this gets round the DCOM stuff)
>>>> >2. WSH version 1.0
>>>> >3. VBScript version 5.0
>>>> >4. JScript version 5.0

>>>> >All our machines run exactly the same scripts fine

>>>> >Happy scripting, hope this helps....

>>>> >Daud Sweetland



>>>> >> I am trying to get to use WSH on a network of mostly Windows 95
>>>machines,
>>>> >> mostly running OSR2.  We have configured a bare bones machine with
>OSR
>>>2
>>>> >to
>>>> >> test our scripts before deploying, but when we run them on the
>machine
>>>we
>>>> >> get object errors.  Looking on TechNet we determined we needed DCOM
>95
>>>> and
>>>> >> the scripting engine 5.  Maybe IE 4 as well.  After installing that
>>and
>>>> >> Office 97 Pro, the scripts still did not work.  Yet, the scripts run
>>>fine
>>>> >on
>>>> >> Windows 98 machines.

>>>> >> Does anybody know what exactly has to be installed to make WSH work
>on
>>>> >> Win95b?



Mon, 31 Dec 2001 03:00:00 GMT  
 Windows Scripting Host on Windows 95 OSR2

Quote:

>We have a clean install of 95B, and whenever we install the file
ste50en.exe
>(Windows Scripting Engine 5) we get the error "Error registering the OCX
>C:\Windows\System\jscript.dll" and we can't do anything.  This happens
>before or after DCOM 95 and/or windows scripting host 2 beta 1.  However,
>even after running wsh20en.exe we cannot run any scripts to get the exact
>error message.

I have exactly the same experience.


Fri, 04 Jan 2002 03:00:00 GMT  
 Windows Scripting Host on Windows 95 OSR2
I have similar problems with WSH as a network component.  300+
machines, all 95 osr2, all Office97.  

I would like to implement scripting but I haven't been able to find
enough pieces ( and I guess experience ) to get it going cleanly.  I
wouldn't mind IE4 but it requires several questions that would
paralyze my users and I haven't been able to get a quiet install
working.

From the news groups I can gather that all this stuff works but it is
really not all that clear - even to you guys - what is necessary to do
X.  Probably because different installs provide different components
in various ways.

What Scripting needs is a script to check for the existence of
required components and either install them silently - catch the
reboot next time or log some serious problem - disk space; wrong base
os; whatever  to a network file for personal attention later.

I would like to create something to do the above but at the moment I
am missing the knowledge to know what to look for.  
How do I know that regobj.dll is required if my script contains a
objRegKey call?  What else might it require?  

The shotgun approach - to install 75 meg of programs and all the
complexity and possible breakage it entails seems like not a very good
idea when what I really need is half a dozen dlls and some registry
settings.

Pete Turner



Quote:
>I am trying to get to use WSH on a network of mostly Windows 95 machines,
>mostly running OSR2.  We have configured a bare bones machine with OSR 2 to
>test our scripts before deploying, but when we run them on the machine we
>get object errors.  Looking on TechNet we determined we needed DCOM 95 and
>the scripting engine 5.  Maybe IE 4 as well.  After installing that and
>Office 97 Pro, the scripts still did not work.  Yet, the scripts run fine on
>Windows 98 machines.

>Does anybody know what exactly has to be installed to make WSH work on
>Win95b?



Tue, 12 Feb 2002 03:00:00 GMT  
 
 [ 11 post ] 

 Relevant Pages 

1. Windows 95 OSR1 and Windows Scripting Host

2. Research: Windows Script Host or Windows Scripting Host

3. Problems Installing Windows Script 5.0 and Windows Script Host 2.0 Beta on Windows NT 4.0

4. Windows scripting host - Checking a service in Windows NT 4

5. Windows Scripting Host for Windows 98 Book

6. Windows 95 GDI or Windows printing system driver.

7. it's work with windows NT not with Windows 95

8. vbscript login scripts - starting a script from the Windows 95 command prompt

9. Windows 95/PowerPoint 95 Postscript Printing Problem

10. Debugging ASP-script using PWS on Windows 95

11. Question About Using a Post Script Printer with Windows 95

12. Creating a script to modify a HKEY_LOCAL_MACHINE variable in windows registry (98/95)

 

 
Powered by phpBB® Forum Software