| Author |
Message |
|
Martin Dunmor
#1 / 10
|
 WSH ver 2.0 Ok, I've installed Windows Script Host v 2.0 (supposedly) but when I open the references list in VB to include it in a project all I can see is Windows Host Script Object Model ver 1.0 (which I had anyway) NOT ver 2.0 How do I actually reference WSH ver 2.0 in a project??? I really could
do with the stdin, stdout, stderr functionality in a project i'm working
on.
Any Ideas?
Cheers,
Martin
--
=======================================================
Computing Dept. tel: +44 (0)1524 593819
Lancaster University fax: +44 (0)1524 593608
Lancaster LA1 4YR
UK
=======================================================
|
| Fri, 13 Sep 2002 03:00:00 GMT |
|
 |
|
Shaw
#2 / 10
|
WSH ver 2.0 This is implemented in the Microsoft Scripting Runtime which gets updated with WSH 2.0 install (if I remember right). Reference Microsoft Scripting Runtime in your project and then inside Standard Stream Types you will find these. Shawn
Quote: > Ok, I've installed Windows Script Host v 2.0 (supposedly) but when I > open the references list in VB to include it in a project all I can see > is Windows Host Script Object Model ver 1.0 (which I had anyway) NOT ver > 2.0 > How do I actually reference WSH ver 2.0 in a project??? I really could
> do with the stdin, stdout, stderr functionality in a project i'm working
> on.
> Any Ideas?
> Cheers,
> Martin
> --
> =======================================================
> Computing Dept. tel: +44 (0)1524 593819
> Lancaster University fax: +44 (0)1524 593608
> Lancaster LA1 4YR
> UK
> =======================================================
|
| Fri, 13 Sep 2002 03:00:00 GMT |
|
|
|
Michael Harri
#3 / 10
|
WSH ver 2.0 The descriptive text in the type library embedded in wshom.ocx is wrong. Check the binary version of the ocx itself. It will be 5.1.0.4615 (it's slightly different on Win2K I think but it's the same binary). --
Michael Harris
MVP Scripting
Ok, I've installed Windows Script Host v 2.0 (supposedly) but when I
open the references list in VB to include it in a project all I can see
is Windows Host Script Object Model ver 1.0 (which I had anyway) NOT ver
2.0
How do I actually reference WSH ver 2.0 in a project??? I really could
do with the stdin, stdout, stderr functionality in a project i'm working
on.
Any Ideas?
Cheers,
Martin
--
=======================================================
Computing Dept. tel: +44 (0)1524 593819
Lancaster University fax: +44 (0)1524 593608
Lancaster LA1 4YR
UK
=======================================================
|
| Fri, 13 Sep 2002 03:00:00 GMT |
|
|
|
M
#4 / 10
|
WSH ver 2.0 Actually, it's 5.1.0.4615 on Win2K, as well. All of the products in the Windows Script V5.1 release have a build number of 4615, with one exception - on Japanese, Chinese Simplified, Chinese Traditional and Korean, WScript.exe and CScript.exe may be build 4711 - it depends on where you got them from (from our website - 4711; from Win2K - 4615, IIRC). Mike Whalen
Windows Script Dev
Quote: > The descriptive text in the type library embedded in wshom.ocx is wrong.
Check the binary version Quote: > of the ocx itself. It will be 5.1.0.4615 (it's slightly different on
Win2K I think but it's the Quote: > same binary). > --
> Michael Harris
> MVP Scripting
> Ok, I've installed Windows Script Host v 2.0 (supposedly) but when I
> open the references list in VB to include it in a project all I can see
> is Windows Host Script Object Model ver 1.0 (which I had anyway) NOT ver
> 2.0
> How do I actually reference WSH ver 2.0 in a project??? I really could
> do with the stdin, stdout, stderr functionality in a project i'm working
> on.
> Any Ideas?
> Cheers,
> Martin
> --
> =======================================================
> Computing Dept. tel: +44 (0)1524 593819
> Lancaster University fax: +44 (0)1524 593608
> Lancaster LA1 4YR
> UK
> =======================================================
|
| Fri, 13 Sep 2002 03:00:00 GMT |
|
|
|
M
#5 / 10
|
WSH ver 2.0 You might want to get a new copy, but I don't recall ever releasing the 4411
build to anyone ever. I just checked the setup from the website, and it
installed wshom.ocx with a version of 4615. Build 4411 was a release
candidate at one point, and I may have made a setup package at one point
with that build in it, but I didn't think it was ever released to anyone
outside of MS. If it was, that was a mistake. Where did you get the package
from?
Does anyone else have an ste51en.exe that has a 4411 file in it? If so,
you'll want to update, and I'll want to know where you got it from 8).
Mike Whalen
Windows Script Dev
Quote: > Interesting, ste51en.exe download installs wshom.ocx with version > 5.1.4411. > Any thoughts?
> Robert Hoogstraat
> -----Original Message-----
> Posted At: Monday, March 27, 2000 4:36 PM
> Posted To: wsh
> Conversation: WSH ver 2.0
> Subject: Re: WSH ver 2.0
> Actually, it's 5.1.0.4615 on Win2K, as well. All of the products in the
> Windows Script V5.1 release have a build number of 4615, with one
> exception - on Japanese, Chinese Simplified, Chinese Traditional and
> Korean,
> WScript.exe and CScript.exe may be build 4711 - it depends on where you
> got
> them from (from our website - 4711; from Win2K - 4615, IIRC).
> Mike Whalen
> Windows Script Dev
> > The descriptive text in the type library embedded in wshom.ocx is
> wrong.
> Check the binary version
> > of the ocx itself. It will be 5.1.0.4615 (it's slightly different on
> Win2K I think but it's the
> > same binary).
> > --
> > Michael Harris
> > MVP Scripting
> > Ok, I've installed Windows Script Host v 2.0 (supposedly) but when I
> > open the references list in VB to include it in a project all I can
> see
> > is Windows Host Script Object Model ver 1.0 (which I had anyway) NOT
> ver
> > 2.0
> > How do I actually reference WSH ver 2.0 in a project??? I really
> could
> > do with the stdin, stdout, stderr functionality in a project i'm
> working
> > on.
> > Any Ideas?
> > Cheers,
> > Martin
> > --
> > =======================================================
> > Computing Dept. tel: +44 (0)1524 593819
> > Lancaster University fax: +44 (0)1524 593608
> > Lancaster LA1 4YR
> > UK
> > =======================================================
|
| Mon, 16 Sep 2002 03:00:00 GMT |
|
|
|
Robert Hoogstraa
#6 / 10
|
WSH ver 2.0 Mike, it was downloaded from the MSDN scripting site just prior to the message post. Robert Hoogstraat
Quote: -----Original Message-----
Posted At: Thursday, March 30, 2000 6:59 PM
Posted To: wsh
Conversation: WSH ver 2.0
Subject: Re: WSH ver 2.0
You might want to get a new copy, but I don't recall ever releasing the
4411
build to anyone ever. I just checked the setup from the website, and it
installed wshom.ocx with a version of 4615. Build 4411 was a release
candidate at one point, and I may have made a setup package at one point
with that build in it, but I didn't think it was ever released to anyone
outside of MS. If it was, that was a mistake. Where did you get the
package
from?
Does anyone else have an ste51en.exe that has a 4411 file in it? If so,
you'll want to update, and I'll want to know where you got it from 8).
Mike Whalen
Windows Script Dev
.
> Interesting, ste51en.exe download installs wshom.ocx with version
> 5.1.4411.
> Any thoughts?
> Robert Hoogstraat
> -----Original Message-----
> Posted At: Monday, March 27, 2000 4:36 PM
> Posted To: wsh
> Conversation: WSH ver 2.0
> Subject: Re: WSH ver 2.0
> Actually, it's 5.1.0.4615 on Win2K, as well. All of the products in
the
> Windows Script V5.1 release have a build number of 4615, with one
> exception - on Japanese, Chinese Simplified, Chinese Traditional and
> Korean,
> WScript.exe and CScript.exe may be build 4711 - it depends on where
you
> got
> them from (from our website - 4711; from Win2K - 4615, IIRC).
> Mike Whalen
> Windows Script Dev
> > The descriptive text in the type library embedded in wshom.ocx is
> wrong.
> Check the binary version
> > of the ocx itself. It will be 5.1.0.4615 (it's slightly different
on
> Win2K I think but it's the
> > same binary).
> > --
> > Michael Harris
> > MVP Scripting
> > Ok, I've installed Windows Script Host v 2.0 (supposedly) but when I
> > open the references list in VB to include it in a project all I can
> see
> > is Windows Host Script Object Model ver 1.0 (which I had anyway) NOT
> ver
> > 2.0
> > How do I actually reference WSH ver 2.0 in a project??? I really
> could
> > do with the stdin, stdout, stderr functionality in a project i'm
> working
> > on.
> > Any Ideas?
> > Cheers,
> > Martin
> > --
> > =======================================================
> > Computing Dept. tel: +44 (0)1524 593819
> > Lancaster University fax: +44 (0)1524 593608
> > Lancaster LA1 4YR
> > UK
> > =======================================================
|
| Tue, 17 Sep 2002 03:00:00 GMT |
|
|
|
Robert Hoogstraa
#7 / 10
|
WSH ver 2.0 Mike, Mystery solved. v5.1.0.4411 came from the test system with W2KP RC1.
Apparently the STE51EN.EXE downloaded yesterday did not replace the
WSHOM.OCX during its setup. Running a WINZIP to extract WSHOM.OCX from
the STE51EN.EXE allowed me to get the correct WSHOM.OCX copy. Now we
have v5.1.0.4615. I tried the same install on a NTS4SP5 system and the
install worked, except for an annoying "must restart" (not good on a
server).
Thanks for your alert.
Quote: -----Original Message----- From: Robert Hoogstraat Posted At: Friday, March 31, 2000 8:19 AM
Posted To: wsh
Conversation: WSH ver 2.0
Subject: Re: WSH ver 2.0
Mike, it was downloaded from the MSDN scripting site just prior to the
message post.
Robert Hoogstraat
-----Original Message-----
Posted At: Thursday, March 30, 2000 6:59 PM
Posted To: wsh
Conversation: WSH ver 2.0
Subject: Re: WSH ver 2.0
You might want to get a new copy, but I don't recall ever releasing the
4411
build to anyone ever. I just checked the setup from the website, and it
installed wshom.ocx with a version of 4615. Build 4411 was a release
candidate at one point, and I may have made a setup package at one point
with that build in it, but I didn't think it was ever released to anyone
outside of MS. If it was, that was a mistake. Where did you get the
package
from?
Does anyone else have an ste51en.exe that has a 4411 file in it? If so,
you'll want to update, and I'll want to know where you got it from 8).
Mike Whalen
Windows Script Dev
.
> Interesting, ste51en.exe download installs wshom.ocx with version
> 5.1.4411.
> Any thoughts?
> Robert Hoogstraat
> -----Original Message-----
> Posted At: Monday, March 27, 2000 4:36 PM
> Posted To: wsh
> Conversation: WSH ver 2.0
> Subject: Re: WSH ver 2.0
> Actually, it's 5.1.0.4615 on Win2K, as well. All of the products in
the
> Windows Script V5.1 release have a build number of 4615, with one
> exception - on Japanese, Chinese Simplified, Chinese Traditional and
> Korean,
> WScript.exe and CScript.exe may be build 4711 - it depends on where
you
> got
> them from (from our website - 4711; from Win2K - 4615, IIRC).
> Mike Whalen
> Windows Script Dev
> > The descriptive text in the type library embedded in wshom.ocx is
> wrong.
> Check the binary version
> > of the ocx itself. It will be 5.1.0.4615 (it's slightly different
on
> Win2K I think but it's the
> > same binary).
> > --
> > Michael Harris
> > MVP Scripting
> > Ok, I've installed Windows Script Host v 2.0 (supposedly) but when I
> > open the references list in VB to include it in a project all I can
> see
> > is Windows Host Script Object Model ver 1.0 (which I had anyway) NOT
> ver
> > 2.0
> > How do I actually reference WSH ver 2.0 in a project??? I really
> could
> > do with the stdin, stdout, stderr functionality in a project i'm
> working
> > on.
> > Any Ideas?
> > Cheers,
> > Martin
> > --
> > =======================================================
> > Computing Dept. tel: +44 (0)1524 593819
> > Lancaster University fax: +44 (0)1524 593608
> > Lancaster LA1 4YR
> > UK
> > =======================================================
|
| Tue, 17 Sep 2002 03:00:00 GMT |
|
|
|
Mark L. Ferguso
#8 / 10
|
WSH ver 2.0 Mike W posted the full IExpress argument syntax in a previous thread. Below is the relevant quote for the reboot switch <setup exe file name> /R
Control or force restart.
Administrators would like ability to actually force a restart also. This ensures the update takes
effect right way. This issue was not fixed for the SP1 silent mode CAB we provided.
Wextract uses: NEVER_REBOOT reboot mode when calling InstallHInfsection to ensure that setupx.dll
will return to wextract and leave the reboot job to wextract. Wextract.exe will decide if reboot is
needed in the rules below:
Check on reg key:
HKLM\...\Currentversion\setup
wextractreboot 128 or 132 .... (reboot mode defines)
If the above key value does not exists, or it is exists and is not one of the NEVER_xxx or
ALWAYS_xxx mode, wextract.exe checks:
if Reboot =1 in the install INF file or
if \windows\wininit.ini is not empty.
If reboot is needed, it provides prompt or silent reboot handling based on the result from above.
Administrators can control the restart logic with the following entries:
R = /R:A (Default)
/R:= /R:A (Default)
/R:N -- Never reboot, overrides INF settings in package
/R:A -- Always reboot, prompt user with reboot choice
/R:I -- Reboot if needed, prompt user with reboot choice
/R:AS -- Always reboot, silent and don't prompt user
/R:IS -- Silent reboot if needed, silent and don't prompt user
/R:ND -- Tell Wextract to check for reboot state before running any RegisterOCX sections. If
machine is in reboot state before the install and that state wasn't caused by the package then queue
up registrations in Runonce automatically. This usually is used for cases where an install depends
on something that was installed earlier, but maybe hasn't finished for some reason.
--
Mark L. Ferguson Please reply in Newsgroup
marfers notes for OE 5.0 > http://www.geocities.com/SiliconValley/Bay/6386/IE_ng_notes.htm
Quote:
> Mike, > Mystery solved. v5.1.0.4411 came from the test system with W2KP RC1.
> Apparently the STE51EN.EXE downloaded yesterday did not replace the
> WSHOM.OCX during its setup. Running a WINZIP to extract WSHOM.OCX from
> the STE51EN.EXE allowed me to get the correct WSHOM.OCX copy. Now we
> have v5.1.0.4615. I tried the same install on a NTS4SP5 system and the
> install worked, except for an annoying "must restart" (not good on a
> server).
> Thanks for your alert.
> -----Original Message-----
> From: Robert Hoogstraat
> Posted At: Friday, March 31, 2000 8:19 AM
> Posted To: wsh
> Conversation: WSH ver 2.0
> Subject: Re: WSH ver 2.0
> Mike, it was downloaded from the MSDN scripting site just prior to the
> message post.
> Robert Hoogstraat
> -----Original Message-----
> Posted At: Thursday, March 30, 2000 6:59 PM
> Posted To: wsh
> Conversation: WSH ver 2.0
> Subject: Re: WSH ver 2.0
> You might want to get a new copy, but I don't recall ever releasing the
> 4411
> build to anyone ever. I just checked the setup from the website, and it
> installed wshom.ocx with a version of 4615. Build 4411 was a release
> candidate at one point, and I may have made a setup package at one point
> with that build in it, but I didn't think it was ever released to anyone
> outside of MS. If it was, that was a mistake. Where did you get the
> package
> from?
> Does anyone else have an ste51en.exe that has a 4411 file in it? If so,
> you'll want to update, and I'll want to know where you got it from 8).
> Mike Whalen
> Windows Script Dev
> .
> > Interesting, ste51en.exe download installs wshom.ocx with version
> > 5.1.4411.
> > Any thoughts?
> > Robert Hoogstraat
> > -----Original Message-----
> > Posted At: Monday, March 27, 2000 4:36 PM
> > Posted To: wsh
> > Conversation: WSH ver 2.0
> > Subject: Re: WSH ver 2.0
> > Actually, it's 5.1.0.4615 on Win2K, as well. All of the products in
> the
> > Windows Script V5.1 release have a build number of 4615, with one
> > exception - on Japanese, Chinese Simplified, Chinese Traditional and
> > Korean,
> > WScript.exe and CScript.exe may be build 4711 - it depends on where
> you
> > got
> > them from (from our website - 4711; from Win2K - 4615, IIRC).
> > Mike Whalen
> > Windows Script Dev
> > > The descriptive text in the type library embedded in wshom.ocx is
> > wrong.
> > Check the binary version
> > > of the ocx itself. It will be 5.1.0.4615 (it's slightly different
> on
> > Win2K I think but it's the
> > > same binary).
> > > --
> > > Michael Harris
> > > MVP Scripting
> > > Ok, I've installed Windows Script Host v 2.0 (supposedly) but when I
> > > open the references list in VB to include it in a project all I can
> > see
> > > is Windows Host Script Object Model ver 1.0 (which I had anyway) NOT
> > ver
> > > 2.0
> > > How do I actually reference WSH ver 2.0 in a project??? I really
> > could
> > > do with the stdin, stdout, stderr functionality in a project i'm
> > working
> > > on.
> > > Any Ideas?
> > > Cheers,
> > > Martin
> > > --
> > > =======================================================
> > > Computing Dept. tel: +44 (0)1524 593819
> > > Lancaster University fax: +44 (0)1524 593608
> > > Lancaster LA1 4YR
> > > UK
> > > =======================================================
|
| Tue, 17 Sep 2002 03:00:00 GMT |
|
|
|
M
#9 / 10
|
WSH ver 2.0 That's System File Protection kicking in - ste51en.exe will not work on
Windows 2000. You should update all of your machines to Win2K release if you
want the latest versions. There will be setups in the future that will allow
you to upgrade on Win2K, but considering that Win2K comes with Script 5.1,
we didn't use the Win2000 process in that package (it's a different
installation technique, due to SFP).
Also - rather than using WinZip (a fine product, but not needed here), you
might want to extract the files using the "ste51en /c /t:pathspec" command.
This works with any IExpress based installation package.
Mike Whalen
Windows Script Dev
Quote: > Mike, > Mystery solved. v5.1.0.4411 came from the test system with W2KP RC1.
> Apparently the STE51EN.EXE downloaded yesterday did not replace the
> WSHOM.OCX during its setup. Running a WINZIP to extract WSHOM.OCX from
> the STE51EN.EXE allowed me to get the correct WSHOM.OCX copy. Now we
> have v5.1.0.4615. I tried the same install on a NTS4SP5 system and the
> install worked, except for an annoying "must restart" (not good on a
> server).
> Thanks for your alert.
> -----Original Message-----
> From: Robert Hoogstraat
> Posted At: Friday, March 31, 2000 8:19 AM
> Posted To: wsh
> Conversation: WSH ver 2.0
> Subject: Re: WSH ver 2.0
> Mike, it was downloaded from the MSDN scripting site just prior to the
> message post.
> Robert Hoogstraat
> -----Original Message-----
> Posted At: Thursday, March 30, 2000 6:59 PM
> Posted To: wsh
> Conversation: WSH ver 2.0
> Subject: Re: WSH ver 2.0
> You might want to get a new copy, but I don't recall ever releasing the
> 4411
> build to anyone ever. I just checked the setup from the website, and it
> installed wshom.ocx with a version of 4615. Build 4411 was a release
> candidate at one point, and I may have made a setup package at one point
> with that build in it, but I didn't think it was ever released to anyone
> outside of MS. If it was, that was a mistake. Where did you get the
> package
> from?
> Does anyone else have an ste51en.exe that has a 4411 file in it? If so,
> you'll want to update, and I'll want to know where you got it from 8).
> Mike Whalen
> Windows Script Dev
> .
> > Interesting, ste51en.exe download installs wshom.ocx with version
> > 5.1.4411.
> > Any thoughts?
> > Robert Hoogstraat
> > -----Original Message-----
> > Posted At: Monday, March 27, 2000 4:36 PM
> > Posted To: wsh
> > Conversation: WSH ver 2.0
> > Subject: Re: WSH ver 2.0
> > Actually, it's 5.1.0.4615 on Win2K, as well. All of the products in
> the
> > Windows Script V5.1 release have a build number of 4615, with one
> > exception - on Japanese, Chinese Simplified, Chinese Traditional and
> > Korean,
> > WScript.exe and CScript.exe may be build 4711 - it depends on where
> you
> > got
> > them from (from our website - 4711; from Win2K - 4615, IIRC).
> > Mike Whalen
> > Windows Script Dev
> > > The descriptive text in the type library embedded in wshom.ocx is
> > wrong.
> > Check the binary version
> > > of the ocx itself. It will be 5.1.0.4615 (it's slightly different
> on
> > Win2K I think but it's the
> > > same binary).
> > > --
> > > Michael Harris
> > > MVP Scripting
> > > Ok, I've installed Windows Script Host v 2.0 (supposedly) but when I
> > > open the references list in VB to include it in a project all I can
> > see
> > > is Windows Host Script Object Model ver 1.0 (which I had anyway) NOT
> > ver
> > > 2.0
> > > How do I actually reference WSH ver 2.0 in a project??? I really
> > could
> > > do with the stdin, stdout, stderr functionality in a project i'm
> > working
> > > on.
> > > Any Ideas?
> > > Cheers,
> > > Martin
> > > --
> > > =======================================================
> > > Computing Dept. tel: +44 (0)1524 593819
> > > Lancaster University fax: +44 (0)1524 593608
> > > Lancaster LA1 4YR
> > > UK
> > > =======================================================
|
| Tue, 17 Sep 2002 03:00:00 GMT |
|
|
|
Robert Bradle
#10 / 10
|
WSH ver 2.0
In microsoft.public.scripting.wsh, Mike Whalen (MS)
Quote: >That's System File Protection kicking in - ste51en.exe will not work on
>Windows 2000.
It's nice to know that it works. --
Robert Bradley
I am not a mindreader, so I don't know everything.
|
| Wed, 18 Sep 2002 03:00:00 GMT |
|
| |
|
