Where can I get wshAPIToolkit?

I've seen a number of interesting scripts that use wshAPIToolkit. Could
someone post a current URL for obtaining it?

Thanks,
-Paul Randall

Fosco
Sat Dec 16 22:49:17 CST 2006

"Paul Randall"
> I've seen a number of interesting scripts that use wshAPIToolkit.
> Could someone post a current URL for obtaining it?


http://www.rogepost.com/n/1449935890

--
Fosco

Paul
Sun Dec 17 12:53:13 CST 2006

Thanks you, Fosco.
Have you tried all the demo scripts? I tried
ChangeSystemCursor_DBDlgDemo1.vbs, and it is not working as I expected.
I did this, to successfully register the 'take 7' version:
C:\...\wshAPIToolkitObjOCX_Take7>regsvr32 wshAPIToolkitObject.ocx
I then ran the change cursor demo. The cursor changed to an hourglass
immediately when I clicked the OK button on the 'Are you ready?' message
box. I expected the cursor to revert to the arrow immediately upon clicking
the OK button of the 'Read to restore cursor' message box. The cursor
remains an hourglass. Also, while the timer for the dialog box was running,
the clicking the exit button had no effect although the dialog says clicking
it should close the dialog box.

Running the demo a second time restores the normal cursor when the OK button
is clicked on the 'Are you ready?' message box. Again, clicking on the
dialog box's exit button had no effect.

Do you think this means the OCX is defective or incompatible with my WXP SP2
system, or is the demo script defective? Or maybe the API changed?

Thanks for any help you can give me.

-Paul Randall

"Fosco" <fake@fake.invalid> wrote in message
news:h%3hh.10563$K8.2241@news.edisontel.com...
> "Paul Randall"
>> I've seen a number of interesting scripts that use wshAPIToolkit.
>> Could someone post a current URL for obtaining it?
>
>
> http://www.rogepost.com/n/1449935890
>
> --
> Fosco
>
>
>

Fosco
Sun Dec 17 20:23:30 CST 2006

"Paul Randall"
> Thanks you, Fosco.
> Have you tried all the demo scripts? I tried
> Do you think this means the OCX is defective or incompatible with my WXP SP2
> system, or is the demo script defective? Or maybe the API changed?


Tested and works fine here on a Win98se

--
Fosco

Fosco
Sun Dec 17 20:45:30 CST 2006

"Paul Randall"
"Fosco"
>> Have you tried all the demo scripts? I tried
>> Do you think this means the OCX is defective or incompatible with my WXP SP2
>> system, or is the demo script defective? Or maybe the API changed?

> Tested and works fine here on a Win98se

Tested right now on a winXP pro sp2 and I have the same behavior
as you with the hourglass .. maybe it's unsupported on XP

PS :
Try also this activex page
http://freenet-homepage.de/gborn/WSHBazaar/WSHBazaar.htm

--
Fosco

Fosco
Sun Dec 17 20:55:25 CST 2006

"Paul Randall"

http://www.rogepost.com/n/2110870421

--
Fosco

Paul
Sun Dec 17 23:31:57 CST 2006

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@fake.invalid> wrote in message
news:zqnhh.10710$K8.5541@news.edisontel.com...
> "Paul Randall"
>
> http://www.rogepost.com/n/2110870421
>
> --
> Fosco
>

Fosco
Mon Dec 18 00:00:06 CST 2006

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

mr_unreliable
Tue Dec 19 15:01:37 CST 2006

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
>
>

Paul
Tue Dec 19 19:48:07 CST 2006

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@notmail.com> wrote in message
news:OWsw1D7IHHA.1468@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