> > Hi all.
> > When trying to debug my asp code, I'm getting a "can't attach to 
> > machine '????' where '????' = my server name. with the option of do you 
> > want to continue yes or no. If I select no debugger stops. If I select 
> yes 
> > it picks up the local copy of the page and dosen't stop at my break 
> points.
> > 
> > Does anyone know what's going on here and how do I fix this ???? 
> > 
> > Cheers.
> 
> 
> try locating a file called viddbg.exe. u can find it on the internet or 
> it even might be on one of the VS CD's. Run this utility from the command 
> prompt and this should help you to pin point the promblem 
>                                            
>                                            Good Luck.

I have a similar problem. When I try to debug my asp. Interdev invokes the browser with this 
url: Http://mymachine/mydir/index.asp and I get  a HTTP 500 error. When I replace mymachine 
with localhost the page comes up with no problem. I ran viddbg.exe and part of the output 
was:
  ASP.DLL Version Information
--------------------------------------------------------
        Location:       C:\WINNT\System32\inetsrv\asp.dll
        FileVersion query failed
        File Size:      334608 bytes

        VID Debugging requires 4.02.0622 (330448 bytes) or greater.
My version is: 5.0.2195.2966
Does anybody know why I am still having a problem? Is it possible to have interdev place 
localhost instead of mymachine?