Where can I get wshAPIToolkit?
in [VbScript]
|
From: Fosco on 17 Dec 2006 21:55 "Paul Randall" http://www.rogepost.com/n/2110870421 -- Fosco
From: Paul Randall on 18 Dec 2006 00:31 Thank you for working so hard to find this for me. My eyes have been fooling me. One script I've been playing with uses wshAPIToolkit. Another uses wshAPIToolkitObject. They look too much alike to my tired old eyes :-). The links you gave me were for wshAPIToolkitObject. Whether it is registered or unregistered, using TLViewer, when I search for wshAPIToolkit.ucDBDialog or wshAPIToolkitObject.ucATO, I get WSHController, which has one method, Function CreateScript(ByVal Command As String, [ByVal Server ]) As Object and is a member of WSHControllerLibrary.WSHController. I will have to continue working on this next month. -Paul Randall "Fosco" <fake(a)fake.invalid> wrote in message news:zqnhh.10710$K8.5541(a)news.edisontel.com... > "Paul Randall" > > http://www.rogepost.com/n/2110870421 > > -- > Fosco >
From: Fosco on 18 Dec 2006 01:00 Paul Randall: > Thank you for working so hard to find this for me. My eyes have been > fooling me. This is all I have on my Hard Disk (played with very little time ago) http://www.rogepost.com/n/4711957762 -- Fosco
From: mr_unreliable on 19 Dec 2006 16:01 A newer api toolkit was posted here in April, but was subsequently removed, I suppose the newsgroup admin could have been responsible for that. Can't have those scripters getting too excited about calling api's. Anyway the "wshAPIToolkitObject" is somewhat obsolete, except maybe for win98se users. The "wshAPIToolkit" is a newer version, with (imho) more "logical" api declarations. Then, along comes winXP, with its _outstanding_ secutity. And the "DEP" (Data Execution Protection) feature blew the apiToolkit out of the water. And so some changes had to be made to get around that. Now the apiToolkit is running again on winXP. However, that is not the end of the story. YOU have to know what you are doing (gasp!). Each new microsoft system has re-defined the api calls, sometimes subtly and sometimes not-so-subtly. You can't take a script (or app) with api calls from win98 and expect it to run on winXP _unless_ every api is exactly the same. This is why your applicaton vendors spend time with identifying what system they are running under, and then switching over to a code segment that will (hopefully) run correctly under that system. The newer api toolkit has been re-posted here. See below: "[Ann] wsh API Toolkit actX object, resurrected..." If you are interested, better get a copy before the ng admin strikes again. cheers, jw Paul Randall wrote: > I've seen a number of interesting scripts that use wshAPIToolkit. Could > someone post a current URL for obtaining it? > > Thanks, > -Paul Randall > >
From: Paul Randall on 19 Dec 2006 20:48 Thanks for the info. I'm either too late or too dumb. I googled "[Ann] wsh API Toolkit actX object, resurrected..." and found an April 2006 entry, but no link or attachment. I can't get my Outlook Express newsgroup reader go back any further than Sept 20 in the WSH newsgroup. -Paul Randall "mr_unreliable" <kindlyReplyToNewsgroup(a)notmail.com> wrote in message news:OWsw1D7IHHA.1468(a)TK2MSFTNGP04.phx.gbl... >A newer api toolkit was posted here in April, but was > subsequently removed, I suppose the newsgroup admin > could have been responsible for that. Can't have those > scripters getting too excited about calling api's. > > Anyway the "wshAPIToolkitObject" is somewhat obsolete, > except maybe for win98se users. The "wshAPIToolkit" > is a newer version, with (imho) more "logical" api > declarations. > > Then, along comes winXP, with its _outstanding_ secutity. > And the "DEP" (Data Execution Protection) feature blew > the apiToolkit out of the water. And so some changes > had to be made to get around that. > > Now the apiToolkit is running again on winXP. However, that > is not the end of the story. YOU have to know what you are > doing (gasp!). Each new microsoft system has re-defined the > api calls, sometimes subtly and sometimes not-so-subtly. > > You can't take a script (or app) with api calls from win98 > and expect it to run on winXP _unless_ every api is exactly > the same. This is why your applicaton vendors spend time with > identifying what system they are running under, and then > switching over to a code segment that will (hopefully) run > correctly under that system. > > The newer api toolkit has been re-posted here. See below: > > "[Ann] wsh API Toolkit actX object, resurrected..." > > If you are interested, better get a copy before the ng > admin strikes again. > > cheers, jw > > Paul Randall wrote: >> I've seen a number of interesting scripts that use wshAPIToolkit. Could >> someone post a current URL for obtaining it? >> >> Thanks, >> -Paul Randall
First
|
Prev
|
Pages: 1 2 Prev: Passing uint8 and uint64 values with VBScript? Next: Environment variables on remote computer |