I have solve this By Search
Ò»¡¢Ê²Ã´ÊÇWSH£¿
£ £ WSHÊÇWindows Scripting Host£¨Windows½Å±¾Ö÷»ú£©µÄËõÂÔÐÎʽ¡£WSHÕâ¸ö¸ÅÄî×îÔç³öÏÖÓÚWindows 98²Ù×÷ϵͳ£¬ÊÇÒ»¸ö»ùÓÚ32 λ Windows ƽ̨¡¢²¢¶ÀÁ¢ÓÚÓïÑԵĽű¾ÔËÐл·
¾³¡£±ÈÈ磺Äã×Ô¼º±àдÁËÒ»¸ö½Å±¾Îļþ£¬Èçºó׺Ϊ .vbs »ò .js µÄÎļþ£¬È»ºóÔÚ
Windows ÏÂË«»÷ ²¢Ö´ÐÐËü£¬Õâʱ£¬ÏµÍ³¾Í»á×Ô¶¯µ÷ÓÃÒ»¸öÊʵ±µÄ³ÌÐòÀ´¶ÔËü½øÐнâÊͲ¢Ö´ÐУ¬¶øÕâ¸ö³ÌÐò£¬¾ÍÊÇ Windows Scripting Host£¬³ÌÐòÖ´ÐÐÎļþÃûΪ Wscript.exe £¨ÈôÊÇÔÚ
DOSÃüÁîÌáʾ·ûÏ£¬ÔòΪ Cscript.exe£©¡£
£ £
£ £ ÏëÖªµÀ×Ô¼ºµÄ»úÆ÷ÉÏÓÐûÓÐWSHÂ𣿲鿴һÏÂÄãµÄ»úÆ÷ÀïÓÐûÓС°Wscipt.exe¡±»òÕß¡°Cscript.exe¡±ÕâÁ½¸öÎļþ¾Í¿ÉÒÔÁË¡£Èç¹ûÕÒµ½£¬¹§ ϲÄ㣡ÄãÒѾ°²×°ÁËWSH¡£·ñÔò£¬×Ô¼ºÊÖ¶¯°²×°°É£º
£ £ ÔÚWindows 98»·¾³Ï£¬WSHÊÇ×÷Ϊ²Ù×÷ϵͳµÄÒ»¸ö×é¼þ×Ô¶¯°²×°µÄ£¬Èç¹û²»É÷¶ªÊ§ÁËÕâ¸ö×é¼þ£¬¿ÉÒÔ´ÓÒÀ´Î´ò¿ª¡°¿ØÖÆÃæ°å-->Ìí¼Ó/ɾ³ý³Ì Ðò--¡µWindows°²×°³ÌÐò--¡µ¸½¼þ¡±,È»ºó½«¡°Windows
Scripting Host¡±Ç°µÄ»®ÉÏ¡°¡Ì¡±£¬ÔÙÈ·¶¨¼´¿ÉÍê³ÉWSH×é¼þµÄ°²×°¡£
£ £
£ £ ¶þ¡¢½Å±¾ÓïÑÔÓëWSHµÄ¹Øϵ
£ £ ´ó¼ÒÖªµÀ£¬½Å±¾ÓïÑÔ£¨°üÀ¨JavaScriptºÍVBscriptÓïÑԵȣ©¾³£»á±»Ö²ÈëÍøÒ³Ö®ÖУ¨ÆäÖаüÀ¨ HTML Ò³Ãæ¿Í»§»ú¶ËºÍ ASP Ò³Ãæ·þÎñÆ÷¶Ë£© ¡£¶ÔÓÚÖ²Èë HTML Ò³ÃæµÄ½Å±¾£¬Æä
ËùÐèµÄ½âÎöÒýÇæ»áÓÉ IE ÕâÑùµÄÍøÒ³ä¯ÀÀÆ÷ÔØÈ룻¶ÔÓÚÖ²Èë ASP Ò³ÃæµÄ½Å±¾£¬ÆäËùÐèµÄ½âÎöÒýÇæ»áÓÉ IIS£¨ Internet Information Services£©Ìṩ¡£¶ø¶ÔÓÚ³öÏÖÔÚ HTML ºÍ ASP
Ò³ÃæÖ®ÍâµÄ½Å±¾£¨ËüÃdz£ÒÔ¶ÀÁ¢µÄÎļþÐÎʽ´æÔÚ£©£¬¾ÍÐèÒª¾ÓÉ WSH À´ ´¦ÀíÁË¡£ÐèҪ˵Ã÷µÄÊÇ£ºWSH ÒªÏëÕý³£¹¤×÷£¬»¹Òª°²×°IE 3.0 »ò¸ü¸ß°æ±¾µÄ IE£¬ÒòΪ WSH ÔÚ¹¤×÷ʱ»áµ÷ÓÃ
IE ÖÐµÄ VBScript ºÍ JavaScript¡¡½âÎöÒýÇæ¡£ [δ½áÊø][iduba_page]ÔÚÕâЩ±»Ö²ÓÚÍøÒ³µÄ½Å±¾ÓïÑÔÖУ¬¾ø´ó¶àÊýÊÇÓëÍøÂ簲ȫÎ޹صġ£µ«Ò²ÓÐÉÙÊý±ðÓÐÓÃÐĵĺÃÊ Õߣ¬°ÑһЩÑÏÖØΣ¼°ÍøÂ簲ȫµÄ´úÂ루ÎÒÃÇ
³£³£³Æ֮Ϊ¡°¶ñÒâ´úÂ롱£¬ËûÃÇͨ³£¶¼ÒªÍ¨¹ýÐÞ¸Ä×¢²á±í´ïµ½¡°¶ñÒ⡱µÄÄ¿µÄ£¡£©£¬»ì·ÅÔÚÕý³£µÄ ½Å±¾Ö®ÖУ¬³£³£ÈÃÎÒÃÇ·À²»Ê¤·À¡£µ«ÊÇ£¬Èç¹ûÎÒÃÇÁ˽âÒ»µã¹ØÓڽű¾ÓïÑÔµÄÖª
ʶ£¬ÕâЩ¡°¼¿Á©¡±¶¼ÊǷdz£ÈÝÒ×ʶÆƵġ£»¹ÊÇÈÃÎÒÃÇ´Ó¼¸¸ö¼òµ¥ µÄʵÀý¿ªÊ¼°É¡¡
£ £
£ £ Èý¡¢WSHÓ¦ÓþÙÀý
£ £ WSH¿ÉÒÔ´¦Àí½Å±¾³ÌÐò£¬ÔõÑùÔĶÁºÍ±àдWSHµÄ½Å±¾Ô´ÎļþÄØ£¿Ö»ÒªÄãÓÐÒ»µãBasic£¨»áVBµÄ±à³Ì¸üºÃ£¬ºÇºÇ£©ÓïÑԵĻù´¡£¬Ñ§»á¿´¶®WSH½Å ±¾ÓïÑԵijÌÐò²¢²»ÊÇÒ»¼þÄÑÊ¡£È¥C:WINDOWSSAMPLESWSHÄ¿
¼ÒÔϽ«¿´¿´°É£¡ÀïÃæÌṩÁ˼¸ÀྵäµÄ½Å±¾Àý×Ó£¬¶øÇÒ·Ö±ðÌṩÁËVBScriptºÍ
JavaScriptÁ½¸ö°æ±¾£¬ÎÒÃÇÖ»ÒªÓüÇʱ¾´ò¿ªËüÃDz¢×ÐϸÑо¿¾Í²»ÄÑѧµ½Ò»Ð©»ù±¾µÄWSHÓ¦Óá£
£ £
£ £ ÄãÖ»ÐèÔÚ¼Çʱ¾ÖÐÒÀ´ÎÊäÈëÒÔÏÂÿ¸öʵÀýÖеĴúÂ룬²¢±£´æΪÏàÓ¦µÄ¡°*.vbs¡±Îļþ£¬Ë«»÷Õâ¸öÎļþ£¬Äã¾Í¿ÉÒÔ¿´µ½ÏàÓ¦µÄЧ¹ûÁË¡£
Q: How do I open script files? Trying the above solution makes Windows XP
throw an error?
A: This is similar to the *.js association problem. Some machines seem to,
for some reason, lose their *.vbs association. It's not that the files open
with dreamweaver or whatever -- it's that the machine just doesn't know how
to run them. If you have a scheduled task, "Could not run" will appear in
the status column.
So, you're a smart person and read through the FAQ. You find the *.js
extension problem, and you try that fix: you run it as "wscript
c:\path\to\script.vbs". But that, in turn, produces a pop-up error, this
time a "Windows Scripting Host" error: "There is no script engine for file
extension '.vbs'." So, for some reason, wscript doesn't even know what to do
with *.vbs files.
The solution to this problem is to run the script as:
wscript //e:vbscript c:\path\to\script.vbs
The "//e:vbscript" tells wscript to use the vbscript engine to parse the
script. It will then run correctly.
A few alternative solutions, perhaps easier are:
1.. Rename it .vbe (VBScript Encoded Script File). Not sure if this is a
bad idea, but it seemed to work for some scripts.
2.. Make a new association for VBS. Open up my computer, select Tools
menu-> Folder Options, and go to the File Types tab. There probably isn't a
VBS association listed if you have this problem. Select New, type in VBS,
and hit Advanced>>. Then, from the pull-down menu, select "VBScript Script
File". Making this selection automatically takes care of the association,
along with the //e:vbscript problem. This is probably the "correct"
solution...
This problems usually occurs only on Windows XP machines, but the cause is
not known. A Microsoft KB article on this issue can be found here. Thanks
goes to Bob_2k for writing this FAQ entry.
