🚀 go-pugleaf

I know this is a month late, but if you can't right click on a link in
IE, and click Open in New Window, go to a command prompt, go to your
system32 directory, and type the following line.  It should work
again, once you restart IE.

regsvr32 urlmon.dll

That should do it for ya.  :)

On Thu, 25 Oct 2001 15:23:37 +0200, "Ingrid van Vliet"
<iv.vliet@netjob.dk> wrote:

>Hi Trevor
>
>Thanks for your mail !You are right, I can use the debugger when I have
>changed the default security. And when I do that I get the problems you
>mention:
>
> 1. Your MSAgents will stop working.
> 2. When you right click on hyperlink on IE. You cannot open them in a new
>window. If any of you have a solution for this
>
>So I am also very interested to hear how to solve that !!
>
>Best regards
>Ingrid
>Netjob
>
>
>
>
>
>
>
>"Trevor Benedict R" <*trevor_benz*@yahoo.com> wrote in message
>news:OBS7qQUXBHA.2020@tkmsftngp07...
>> Hi Ingrid,
>> You may have to run DCOMCNFG.Exe and then click on Default Security Tab.
>In the default access Permissions, click on the
>> Edit Default button, and then click on the Add button and add the
>IUSR_MachineName account and click on OK. You'll be
>> able to debug you VB Code.
>>
>> There's 2 problems here.
>> 1. Your MSAgents will stop working.
>> 2. When you right click on hyperlink on IE. You cannot open them in a new
>window. If any of you have a solution for this
>> kindly let me know.
>>
>> After you remove the permission from DCOMcnfg everything will work
>normally, but the debuggin part.
>>
>>
>> Regards
>>
>> Trevor Benedict R
>> Software Engineer
>> Mascot Malaysia Sdn Bhd
>>
>>
>> "Ingrid van Vliet" <iv.vliet@netjob.dk> wrote in message
>news:mgQB7.39$lk7.1096@news.get2net.dk...
>> | I have just upgraded my server to WIN2000 and IIS 5.0.  After that I can
>run
>> | my components (DLL) in ASP but I can't debug them anymore.
>> |
>> | The way I used to debug them in NT 4 and IIS 4 : OPen the component in
>VB,
>> | press the start button and set some breakpoints and load my ASP file
>calling
>> | the component. This worked fine.
>> |
>> | When I try to do the same in WIN2000 and IIS 5.0 I can't even get my asp
>> | file to run. I get a http 500 - internal server error.
>> |
>> | Anyone out there who can help ?
>> |
>> | Thanks in advance !
>> |
>> | Ingrid
>> | Netjob
>> |
>> |
>> |
>> |
>>
>