Vista - Drag&drop on vbs files

As I wrote before, after installing SP3 I had vbscripts not working properly.
While drag&drop works on every other type of file, when files or directories are released
on a vbs script nothing happens. ObjArgs.count is zero.
I had several scripts which worked fine and now they act like they received no argument.
I downloaded script56 and installed it but had no relief.
I downloaded script57 but I could not install it because the SP3 is newer and the
istallation process was terminated.

I have some other wscript.exe files automatically saved by XP in other directories
(lastgood, i386,..) with other build numbers, but it seems nothing changes when I put them
in the system32 directory.
It could be something related to the dll's?

In the registry the vbsfile entry has shell/open2/command with a value
%SystemRoot%\System32\WScript.exe "%1" %*
Is this correct?

Can anybody give me a hint?
Thank you.
Giovanni.

--
Giovanni Cenati (Bergamo, Italy)
Write to "Reventlov" at katamail com
http://digilander.libero.it/Cenati (Esempi e programmi in VbScript)
--

I think the ability to handle drag-drop is
probably this key:

HKCR\VBSFile\ShellEx\DropHandler\

On my system (Win98SE) there's only a single value,
the default value, of:

{60254CA5-953B-11CF-8C96-00AA00B8708C}

HKCR\CLSID\{60254CA5-953B-11CF-8C96-00AA00B8708C} points to:

Shell Extension For Windows Script Host

HKCR\CLSID\{60254CA5-953B-11CF-8C96-00AA00B8708C}\InProcServer32\ :

C:\WINDOWS\SYSTEM\WSHEXT.DLL

Il giorno Mon, 1 Dec 2008 19:02:01 -0500, "mayayana" <mayaXXyana@xxxxxx> ha scritto:
Thanks a lot.
I'll try.
Giovanni.

--
Giovanni Cenati (Bergamo, Italy)
Write to "Reventlov" at katamail com
http://digilander.libero.it/Cenati (Esempi e programmi in VbScript)
--

Il giorno Wed, 03 Dec 2008 21:05:14 GMT, noone@xxxxxx (Reventlov) ha scritto:
My settings are the same as yours and it still does not work.
I'll keep on searching.
Giovanni.

--
Giovanni Cenati (Bergamo, Italy)
Write to "Reventlov" at katamail com
http://digilander.libero.it/Cenati (Esempi e programmi in VbScript)
--

> My settings are the same as yours and it still does not work.That's odd. I can disable drag/drop by renaming
HKCR\vbsfile\Shellex\DropHandler\ to nonsense.
Just to be thorough, under
HKEY_CLASSES_ROOT\CLSID\{60254CA5-953B-11CF-8C96-00AA00B8708C}

I have the default value plus a value named AppID, with data
that's the same GUID. And under the InProcServer32 key
I also have a value ThreadingModel with data "Apartment".

Security has gotten so carried away in XP that I wonder
if you might have some sort of well meaning protection --
like AV or some XP function -- that's causing the problem.

If it were me I might try running filemon and regmon while
dropping to see if that turns up anything. (Preferably use an
older version of each. Mark Russinovich, the author of
those programs, now works for Microsoft. I would no longer
trust recent versions to provide an uncensored report.)

mayayana wrote:GASP!!! Are you suggesting that ms may be hiding some
sneaky dll which it doesn't want anybody to know about???
If there ever was such a thing, then I suspect that all
those super-hackers who DON'T work for ms would be loudly
"outing" that discrepancy...

Incidentally, for an interesting discussion of how to implement
a drag-and-drop target from scratch, see Jose Roca's discussion:

http://www.jose.it-berater.org/smffo...2&topic=2265.0

Note: Jose Roca is the "MVP" for PB (PowerBasic). Nothing to
do with VB, but most likely if you can read VB then you can
read PB as well.

cheers, jw

>Maybe. Maybe not. MS has always had undocumented
APIs, and they've been gradually blocking control over
the OS: Services go online without asking... In Vista only
MS can completely access the System folder.... Things
like that. No one knew that XP was updating itself *even
with Windows Update disabled* until an update bug caused a
problem on machines that were supposedly not contacting
MS. So it wouldn't surprise me to hear that MS was also
using a number of clandestine Registry operations and had
asked Mark Russinovich to "veil" them. (They actually did
something similar with ZoneAlarm when XP first came out.
In the next ZA update, ZA was allowing the svchost.exe
process to get through without informing or allowing it
to be blocked. Only someone who kept an eye on the list
of allowed programs would know that services were going
online. Only someone familiar with services could know
what services were going online under the guise of svchost.
And only someone who used another firewall could stop it.)