You have to associate the extension with wscript or cscript followed by
your script name, i.e. "c:\path\wscript.exe d:\path\script.vbs %1." I've
never tried that specifically, but I associate a custom extension with
an HTA script using
C:\Windows\SysWOW64\mshta.exe "E:\books\tools\libcheck.hta" %1
--
Crash
One man's weed is another man's wildflower.
In any case, it's all in the Registry under HKCR.
If you look under HKCR\.vbs you'll probably see that
the official file "class" name is "vbsfile". If you then
look under HKCR\vbsfile you'll see all the info. Windows
uses to handle the extension. So if you want you filetype
to act like a VBS then just set the default value in the
extension key to the default value in the .vbs key:
HKCR\.vbs default value: vbsfile
HKXR\.xyz default value: vbsfile
.xyz would now be an alias of VBS.
--
--
"Dudule" <ni...@niconnu.com> wrote in message
news:4d2042da$0$1584$426a...@news.free.fr...
Thanks to everybody,
I associated the link:
c:\windows\system32\wscript.exe "e:\mypath\script.vbs" %1
to the open statment in the file association extensions...
And everything works...
Thanks again and happy new year