Hi,

I posted this question to the WSH newsgroup but did not get any suggestions.
Cannot figure out why I suddenly lost an ability to debug scripts in WSH. I
used to be able to do it by executing cscript with //D //X flags, but when I
do it now, the script just runs without invoking a debugger. I set the
JITDebugging (or whatever it's name is) registry value to 1 (just in case),
but it still does not help. Any ideas? I am running WSH 5.6 on Win XP Pro SP
1.

Thanks,

Alek

Re: How to enable script debugging? by Johnny

Johnny
Sun Oct 10 06:34:17 CDT 2004

A few loose thoughts:

Have you checked Internet Explorer, Tools, Internet Options, Advanced,
Disable Script Debugging ?

Have you tried WSCRIPT ... //D //I //X ... ?

I can't remember if this also applies til XP: check Add Remove Programs, Add
Remove Windows Components, see if Script Debugger is istalled.


Regards
Johnny Nielsen

"Alek Davis" <alek_xDOTx_davis_xATx_intel_xDOTx_com> wrote in message
news:OcFs5jVrEHA.2028@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I posted this question to the WSH newsgroup but did not get any
suggestions.
> Cannot figure out why I suddenly lost an ability to debug scripts in WSH.
I
> used to be able to do it by executing cscript with //D //X flags, but when
I
> do it now, the script just runs without invoking a debugger. I set the
> JITDebugging (or whatever it's name is) registry value to 1 (just in
case),
> but it still does not help. Any ideas? I am running WSH 5.6 on Win XP Pro
SP
> 1.
>
> Thanks,
>
> Alek
>
>



Re: How to enable script debugging? by Alek

Alek
Mon Oct 11 10:57:06 CDT 2004

Thanks Johnny,

Unfortunately, neither one of these suggestions helped. Script debugging is
not disabled in IE (and I would not think that IE settings affect WSH, but
anyway). //D //I //X switched did not do much. And I do not see Script
Debugging option in Windows Components. Thanks for suggestions, though.

Alek

"Johnny Nielsen" <DONT.WRITE.THIStrap402@megabit.dk> wrote in message
news:OOtJm0rrEHA.3464@TK2MSFTNGP14.phx.gbl...
> A few loose thoughts:
>
> Have you checked Internet Explorer, Tools, Internet Options, Advanced,
> Disable Script Debugging ?
>
> Have you tried WSCRIPT ... //D //I //X ... ?
>
> I can't remember if this also applies til XP: check Add Remove Programs,
Add
> Remove Windows Components, see if Script Debugger is istalled.
>
>
> Regards
> Johnny Nielsen
>
> "Alek Davis" <alek_xDOTx_davis_xATx_intel_xDOTx_com> wrote in message
> news:OcFs5jVrEHA.2028@TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > I posted this question to the WSH newsgroup but did not get any
> suggestions.
> > Cannot figure out why I suddenly lost an ability to debug scripts in
WSH.
> I
> > used to be able to do it by executing cscript with //D //X flags, but
when
> I
> > do it now, the script just runs without invoking a debugger. I set the
> > JITDebugging (or whatever it's name is) registry value to 1 (just in
> case),
> > but it still does not help. Any ideas? I am running WSH 5.6 on Win XP
Pro
> SP
> > 1.
> >
> > Thanks,
> >
> > Alek
> >
> >
>
>



Re: How to enable script debugging? by Justin

Justin
Tue Oct 12 08:28:59 CDT 2004

Alek Davis wrote:
> I posted this question to the WSH newsgroup but did not get any suggestions.
> Cannot figure out why I suddenly lost an ability to debug scripts in WSH. I
> used to be able to do it by executing cscript with //D //X flags, but when I
> do it now, the script just runs without invoking a debugger. I set the
> JITDebugging (or whatever it's name is) registry value to 1 (just in case),
> but it still does not help. Any ideas? I am running WSH 5.6 on Win XP Pro SP
> 1.

I don't know if this affects script debugging, but have you checked the
"Debugger" value in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion?

Unfortunately I don't know what you would set it to to invoke Script
Debugger, but Microsoft's documentation on the subject is available at
http://tinyurl.com/6ccx4.

--
Justin Piper
Bizco Technologies
http://www.bizco.com/

Re: How to enable script debugging? by Alek

Alek
Tue Oct 12 10:55:45 CDT 2004

This entry point to

"C:\Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit.exe" -p
%ld -e %ld

Seems OK to me.

Alek

"Justin Piper" <jpiper@bizco.com> wrote in message
news:v_Qad.3176$PH6.1496@twister.rdc-kc.rr.com...
> Alek Davis wrote:
> > I posted this question to the WSH newsgroup but did not get any
suggestions.
> > Cannot figure out why I suddenly lost an ability to debug scripts in
WSH. I
> > used to be able to do it by executing cscript with //D //X flags, but
when I
> > do it now, the script just runs without invoking a debugger. I set the
> > JITDebugging (or whatever it's name is) registry value to 1 (just in
case),
> > but it still does not help. Any ideas? I am running WSH 5.6 on Win XP
Pro SP
> > 1.
>
> I don't know if this affects script debugging, but have you checked the
> "Debugger" value in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion?
>
> Unfortunately I don't know what you would set it to to invoke Script
> Debugger, but Microsoft's documentation on the subject is available at
> http://tinyurl.com/6ccx4.
>
> --
> Justin Piper
> Bizco Technologies
> http://www.bizco.com/



Re: How to enable script debugging? by Justin

Justin
Tue Oct 12 11:27:48 CDT 2004

Alek Davis wrote:

> This entry point to
>
> "C:\Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit.exe" -p
> %ld -e %ld
>
> Seems OK to me.
>
> Alek

Yes, that's what I have as well. I figured that was a long shot, but
since that seems to be the program that's executed when I use //X, I
thought it worth a shot anyway.

--
Justin Piper
Bizco Technologies
http://www.bizco.com/

Re: How to enable script debugging? by Alek

Alek
Tue Oct 12 14:11:25 CDT 2004

Thanks Justin. I appreciate the try.

"Justin Piper" <jpiper@bizco.com> wrote in message
news:8CTad.3109$mR.2779@twister.rdc-kc.rr.com...
> Alek Davis wrote:
>
> > This entry point to
> >
> > "C:\Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit.exe" -p
> > %ld -e %ld
> >
> > Seems OK to me.
> >
> > Alek
>
> Yes, that's what I have as well. I figured that was a long shot, but
> since that seems to be the program that's executed when I use //X, I
> thought it worth a shot anyway.
>
> --
> Justin Piper
> Bizco Technologies
> http://www.bizco.com/



Re: How to enable script debugging? by Rand

Rand
Wed Oct 13 19:03:34 CDT 2004

Dear Alek -
I don't have a solution, but have the same problem. I have never gotten
Script debugging to fire under just about any circumstance, except years
ago. Eric Phelp's discussion on the topic was enlightening
(http://www.ericphelps.com/scripting/ ), but nothing ( //X etc.) has ever
worked for me on my current XP Pro with VS.NET installed.
Surely someone out there has some insight into what might address this, or
is it just plain broken?

- Rand Wrobel,
Alameda,CA


"Alek Davis" <alek_xDOTx_davis_xATx_intel_xDOTx_com> wrote in message
news:%23edwG9IsEHA.1036@TK2MSFTNGP10.phx.gbl...
> Thanks Justin. I appreciate the try.
>
> "Justin Piper" <jpiper@bizco.com> wrote in message
> news:8CTad.3109$mR.2779@twister.rdc-kc.rr.com...
>> Alek Davis wrote:
>>
>> > This entry point to
>> >
>> > "C:\Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit.exe" -p
>> > %ld -e %ld
>> >
>> > Seems OK to me.
>> >
>> > Alek
>>
>> Yes, that's what I have as well. I figured that was a long shot, but
>> since that seems to be the program that's executed when I use //X, I
>> thought it worth a shot anyway.
>>
>> --
>> Justin Piper
>> Bizco Technologies
>> http://www.bizco.com/
>
>



Re: How to enable script debugging? by Michael

Michael
Wed Oct 13 21:32:43 CDT 2004

> ... Eric Phelp's discussion on the topic was
> enlightening (http://www.ericphelps.com/scripting/ ), ...

I especially liked the statement...

"Installing multiple debuggers could tear a hole in the universe."

--
Michael Harris
Microsoft.MVP.Scripting
Sammamish WA US

Re: How to enable script debugging? by Alek

Alek
Thu Oct 14 10:39:15 CDT 2004

Thanks for the link. Good references.

Alek

"Rand Wrobel" <rwrobel@viewstar.com> wrote in message
news:O9StBFYsEHA.1452@TK2MSFTNGP11.phx.gbl...
> Dear Alek -
> I don't have a solution, but have the same problem. I have never
gotten
> Script debugging to fire under just about any circumstance, except years
> ago. Eric Phelp's discussion on the topic was enlightening
> (http://www.ericphelps.com/scripting/ ), but nothing ( //X etc.) has ever
> worked for me on my current XP Pro with VS.NET installed.
> Surely someone out there has some insight into what might address this,
or
> is it just plain broken?
>
> - Rand Wrobel,
> Alameda,CA
>
>
> "Alek Davis" <alek_xDOTx_davis_xATx_intel_xDOTx_com> wrote in message
> news:%23edwG9IsEHA.1036@TK2MSFTNGP10.phx.gbl...
> > Thanks Justin. I appreciate the try.
> >
> > "Justin Piper" <jpiper@bizco.com> wrote in message
> > news:8CTad.3109$mR.2779@twister.rdc-kc.rr.com...
> >> Alek Davis wrote:
> >>
> >> > This entry point to
> >> >
> >> > "C:\Program Files\Common Files\Microsoft
Shared\VS7Debug\vs7jit.exe" -p
> >> > %ld -e %ld
> >> >
> >> > Seems OK to me.
> >> >
> >> > Alek
> >>
> >> Yes, that's what I have as well. I figured that was a long shot, but
> >> since that seems to be the program that's executed when I use //X, I
> >> thought it worth a shot anyway.
> >>
> >> --
> >> Justin Piper
> >> Bizco Technologies
> >> http://www.bizco.com/
> >
> >
>
>



Re: How to enable script debugging? by Paul

Paul
Sat Oct 23 21:07:31 CDT 2004

I just went through this myself with MSE7.exe on a fresh install of XP and
Office XP, and thought I was just going to have to settle on the Microsoft
Debugger on the scripting site.

Then I found this registry file ( make sure line 8 points to the correct
directory), and now MSE7.exe works with cscript //X. If it still does not
work after applying this file, kill mdm.exe from task manager and try again.





"Alek Davis" <alek_xDOTx_davis_xATx_intel_xDOTx_com> wrote in message
news:e6mM4PgsEHA.3412@TK2MSFTNGP14.phx.gbl...
> Thanks for the link. Good references.
>
> Alek
>
> "Rand Wrobel" <rwrobel@viewstar.com> wrote in message
> news:O9StBFYsEHA.1452@TK2MSFTNGP11.phx.gbl...
> > Dear Alek -
> > I don't have a solution, but have the same problem. I have never
> gotten
> > Script debugging to fire under just about any circumstance, except years
> > ago. Eric Phelp's discussion on the topic was enlightening
> > (http://www.ericphelps.com/scripting/ ), but nothing ( //X etc.) has
ever
> > worked for me on my current XP Pro with VS.NET installed.
> > Surely someone out there has some insight into what might address
this,
> or
> > is it just plain broken?
> >
> > - Rand Wrobel,
> > Alameda,CA
> >
> >
> > "Alek Davis" <alek_xDOTx_davis_xATx_intel_xDOTx_com> wrote in message
> > news:%23edwG9IsEHA.1036@TK2MSFTNGP10.phx.gbl...
> > > Thanks Justin. I appreciate the try.
> > >
> > > "Justin Piper" <jpiper@bizco.com> wrote in message
> > > news:8CTad.3109$mR.2779@twister.rdc-kc.rr.com...
> > >> Alek Davis wrote:
> > >>
> > >> > This entry point to
> > >> >
> > >> > "C:\Program Files\Common Files\Microsoft
> Shared\VS7Debug\vs7jit.exe" -p
> > >> > %ld -e %ld
> > >> >
> > >> > Seems OK to me.
> > >> >
> > >> > Alek
> > >>
> > >> Yes, that's what I have as well. I figured that was a long shot, but
> > >> since that seems to be the program that's executed when I use //X, I
> > >> thought it worth a shot anyway.
> > >>
> > >> --
> > >> Justin Piper
> > >> Bizco Technologies
> > >> http://www.bizco.com/
> > >
> > >
> >
> >
>
>


begin 666 InterDev.reg
M4D5'141)5#0-"@T*6TA+15E?0TQ!4U-%4U]23T]47$-,4TE$7'LX,S0Q,CA!
M,BTU,48T+3$Q1# M.$8R,"TP,#@P-48R0T0P-C1]70T*0#TB341-($1E8G5G
M(%-E<W-I;VX@4')O=FED97(@0VQA<W,B#0HB07!P240B/2)[.3(P.4(Q038M
M.38T02TQ,40P+3DS-S(M,#!!,$,Y,#,T.3$P?2(-"@T*6TA+15E?0TQ!4U-%
M4U]23T]47$-,4TE$7'LX,S0Q,CA!,BTU,48T+3$Q1# M.$8R,"TP,#@P-48R
M0T0P-C1]7$QO8V%L4V5R=F5R,S)=#0I /2)C.EQ<5VEN9&]W<UQ<4WES=&5M
M,S)<7&UD;2YE>&4B#0H-"EM(2T597T-,05-315-?4D]/5%Q#3%-)1%Q[.#,T
M,3(X03(M-3%&-"TQ,40P+3A&,C M,# X,#5&,D-$,#8T?5Q0<F]G241=#0I
M/2)-1$TN4T534U!23U8N,2(-"@T*6TA+15E?0TQ!4U-%4U]23T]47$-,4TE$
M7'LX,S0Q,CA!,BTU,48T+3$Q1# M.$8R,"TP,#@P-48R0T0P-C1]7%!R;V=R
M86UM86)L95T-"@T*6TA+15E?0TQ!4U-%4U]23T]47$-,4TE$7'LX,S0Q,CA!
M,BTU,48T+3$Q1# M.$8R,"TP,#@P-48R0T0P-C1]7%9E<G-I;VY);F1E<&5N
A9&5N=%!R;V=)1%T-"D ](DU$32Y315-34%)/5B(-"@T*
`
end


Re: How to enable script debugging? by Alek

Alek
Mon Oct 25 17:05:24 CDT 2004

Thanks Paul,

Tried it, but still no luck (I even added the ProgID key, which was not in
the .reg file), but still no debugging. :-(

Alek

"Paul McAllister" <pmcall@znet.com> wrote in message
news:e7eI74WuEHA.2128@TK2MSFTNGP11.phx.gbl...
> I just went through this myself with MSE7.exe on a fresh install of XP and
> Office XP, and thought I was just going to have to settle on the Microsoft
> Debugger on the scripting site.
>
> Then I found this registry file ( make sure line 8 points to the correct
> directory), and now MSE7.exe works with cscript //X. If it still does not
> work after applying this file, kill mdm.exe from task manager and try
again.
>
>
>
>
>
> "Alek Davis" <alek_xDOTx_davis_xATx_intel_xDOTx_com> wrote in message
> news:e6mM4PgsEHA.3412@TK2MSFTNGP14.phx.gbl...
> > Thanks for the link. Good references.
> >
> > Alek
> >
> > "Rand Wrobel" <rwrobel@viewstar.com> wrote in message
> > news:O9StBFYsEHA.1452@TK2MSFTNGP11.phx.gbl...
> > > Dear Alek -
> > > I don't have a solution, but have the same problem. I have never
> > gotten
> > > Script debugging to fire under just about any circumstance, except
years
> > > ago. Eric Phelp's discussion on the topic was enlightening
> > > (http://www.ericphelps.com/scripting/ ), but nothing ( //X etc.) has
> ever
> > > worked for me on my current XP Pro with VS.NET installed.
> > > Surely someone out there has some insight into what might address
> this,
> > or
> > > is it just plain broken?
> > >
> > > - Rand Wrobel,
> > > Alameda,CA
> > >
> > >
> > > "Alek Davis" <alek_xDOTx_davis_xATx_intel_xDOTx_com> wrote in message
> > > news:%23edwG9IsEHA.1036@TK2MSFTNGP10.phx.gbl...
> > > > Thanks Justin. I appreciate the try.
> > > >
> > > > "Justin Piper" <jpiper@bizco.com> wrote in message
> > > > news:8CTad.3109$mR.2779@twister.rdc-kc.rr.com...
> > > >> Alek Davis wrote:
> > > >>
> > > >> > This entry point to
> > > >> >
> > > >> > "C:\Program Files\Common Files\Microsoft
> > Shared\VS7Debug\vs7jit.exe" -p
> > > >> > %ld -e %ld
> > > >> >
> > > >> > Seems OK to me.
> > > >> >
> > > >> > Alek
> > > >>
> > > >> Yes, that's what I have as well. I figured that was a long shot,
but
> > > >> since that seems to be the program that's executed when I use //X,
I
> > > >> thought it worth a shot anyway.
> > > >>
> > > >> --
> > > >> Justin Piper
> > > >> Bizco Technologies
> > > >> http://www.bizco.com/
> > > >
> > > >
> > >
> > >
> >
> >
>
>
>



Re: How to enable script debugging? by Alek

Alek
Mon Nov 29 18:43:36 CST 2004

OK, after trying any suggestion I was able to find and solicit and getting
nowhere I decided to reinstall (repair) my Visual Studio.NET 2003, and
voila, 4 hours later it looks like I got my script debugging back. Only now
I see one option in the Just-In-Time Debugging dialog for the New instance
of Visual Studio.NET 2003. It used to offer VS 6.0 before, but VS.NET 2003
is what I normally picked so it is fine with me. If you experience the same
problem (script debugging does not work and none of the recommendations
help), try repairing Visual Studio. Just be aware that it will take
approximately twice as long as the original installation. Good luck.

Alek

"Alek Davis" <alek_xDOTx_davis_xATx_intel_xDOTx_com> wrote in message
news:OcFs5jVrEHA.2028@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I posted this question to the WSH newsgroup but did not get any
suggestions.
> Cannot figure out why I suddenly lost an ability to debug scripts in WSH.
I
> used to be able to do it by executing cscript with //D //X flags, but when
I
> do it now, the script just runs without invoking a debugger. I set the
> JITDebugging (or whatever it's name is) registry value to 1 (just in
case),
> but it still does not help. Any ideas? I am running WSH 5.6 on Win XP Pro
SP
> 1.
>
> Thanks,
>
> Alek
>
>