Help! Stuck in .Net Framework SDK hell...

Warning, this question applies to win98se, but I'm hoping that there is
somebody out there that can shed some light.

Up until recently (perhaps before installing some recent microsoft
system updates), whenever I coded up an error (gasp!) in an html page or
hta script, I was presented with a dialog asking me if I wanted to
debug. If I clicked "yes", then I was taken to mse (microsoft script
editor) for a debugging session.

Now, I get presented with a dialog.

Dialog Titlebar: "Microsoft .Net Framework SDK (English)"

Dialog Text:

"The feature you are trying to use is on a network resource that is
unavailable."

"Click OK to try again, or enter an alternate path to a folder
containing the installation package 'netfxsdk.msi' in the box below."

O.K. I do have a much older version of .net framework installed (v1.1
beta) but that apparently is not good enough. So, I went online and
downloaded the current net framwork sdk (which takes several hours at
dialup speed).

When the above dialog popped up again, I gave it the correct path to the
installer.

What I got back was ANOTHER dialog, informing me:

"This component cannot be installed on Microsoft Windows 95, Windows 98,
Windows ME, or Windows NT 4.0. Upgrade your operating system to Windows
2000, or higher, and then rerun setup".

So, there you have it. Microsoft is telling me that I can't debug my
script code with mse anymore unless I upgrade to w2k or winXP.

My question is: does anybody know how I can just get the debug
capability (with mse) back again, _WITHOUT_ upgrading to winXP???

I'll be eternally grateful for any helpful solution, jw


p.s. I am aware of "Lord Omlette's" page: "Using the .NET SDK on Windows
98", unsupported by microsoft though it may be. I may try to work my
way through that. But still, there is no guarantee that even if I did
get the latest net framework sdk installed, that script debugging would
work again. I would just like to go back to using the unvarnished mse
to debug my html and/or hta scripts.

mayayana
Sat Oct 14 16:39:46 CDT 2006

I've never used anything for debugging
other than WSH and IE error messages,
but one thing you might check:

With Visual Studio 6 a section is added
to win.ini named "Aedebug" and a "debugger"
key is added. The default VS debugger is buggy
spyware, the name of which I've forgotten.
If that's deleted then VS will assign VC.
Then anything that crashes and needs debugging
gets opened in the VC editor.

All of that's to say that I wonder if
you might have installed something that overwrote
that setting. Maybe just try re-installing "mse",
whatever that is.


> Warning, this question applies to win98se, but I'm hoping that there is
> somebody out there that can shed some light.
>
> Up until recently (perhaps before installing some recent microsoft
> system updates), whenever I coded up an error (gasp!) in an html page or
> hta script, I was presented with a dialog asking me if I wanted to
> debug. If I clicked "yes", then I was taken to mse (microsoft script
> editor) for a debugging session.
>
> Now, I get presented with a dialog.
>
> Dialog Titlebar: "Microsoft .Net Framework SDK (English)"
>
> Dialog Text:
>
> "The feature you are trying to use is on a network resource that is
> unavailable."
>
> "Click OK to try again, or enter an alternate path to a folder
> containing the installation package 'netfxsdk.msi' in the box below."
>
> O.K. I do have a much older version of .net framework installed (v1.1
> beta) but that apparently is not good enough. So, I went online and
> downloaded the current net framwork sdk (which takes several hours at
> dialup speed).
>
> When the above dialog popped up again, I gave it the correct path to the
> installer.
>
> What I got back was ANOTHER dialog, informing me:
>
> "This component cannot be installed on Microsoft Windows 95, Windows 98,
> Windows ME, or Windows NT 4.0. Upgrade your operating system to Windows
> 2000, or higher, and then rerun setup".
>
> So, there you have it. Microsoft is telling me that I can't debug my
> script code with mse anymore unless I upgrade to w2k or winXP.
>
> My question is: does anybody know how I can just get the debug
> capability (with mse) back again, _WITHOUT_ upgrading to winXP???
>
> I'll be eternally grateful for any helpful solution, jw
>
>
> p.s. I am aware of "Lord Omlette's" page: "Using the .NET SDK on Windows
> 98", unsupported by microsoft though it may be. I may try to work my
> way through that. But still, there is no guarantee that even if I did
> get the latest net framework sdk installed, that script debugging would
> work again. I would just like to go back to using the unvarnished mse
> to debug my html and/or hta scripts.