Re: Parms Editor Crash
$99_dbug.exe v1.0 looks for Debugging Tools for Windows (which includes kd) to be installed in one of these 4 locations -
Code:
[FONT=Lucida Console]%ProgramFiles(x86)%\Debugging Tools for Windows (x86)\
%ProgramFiles%\Debugging Tools for Windows (x86)\
%ProgramFiles%\Debugging Tools for Windows (x64)\
%ProgramW6432%\Debugging Tools for Windows (x64)\[/FONT]
I had my reasons for hard-coding those directory names back in 2008. :smile:
This is the best soltuton, as Richard mentioned -
niemiro said:
I need to make a new build which makes the $_dbugdir parm editable, so that you can specify this directory manually. I will need to quickly run this past jcgriff2 when he comes online. It will be done absolutely as soon as possible.
You'll be able to edit the
$_dbugdir parm file and enter the path name location for Windbg (kd). You may ask why the app doesn't do a search and fill it in -- because many of us run multiple versions of Debugging Tools for Windows. I myself run three versions - 6.11, 6.12, 6.2.8229.0 (W8 Developer) and will soon add a 4th - W8 Consumer.
For info, a little background on the paths listed -
The following assumes your OS drive =
c:
On x86 or x64 systems -
%ProgramFiles% =
c:\Program Files
On x86 systems there is only 1
\Program Files folder -
Code:
[FONT=Lucida Console]
ProgramFiles=C:\Program Files[/FONT]
On x64 systems, there are 2
\Program Files folders -
Code:
[FONT=Lucida Console]ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
[/FONT]
On x64 systems, in addition to the 2
\Program Files environment variables, there is an additional environment variable for WOW - so x86 apps can access the
\Program Files (x64) folder -
Code:
[FONT=Lucida Console]ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
[h34]ProgramW6432[/h34]=C:\Program Files[/FONT]
I usually ran the scripts from
Altap Salamander 2.54, which is an x86 app, so it used the
%ProgramW6432% environment variable to get to
\Program Files (x64) -
When I ran the scripts via Windows Explorer, it used
%ProgramFiles% to get to
\Program Files (x64) -
Is it therefore installed in %ProgramW6432%\Windows Kits\Debugging Tools for Windows (x64)?
You should be fine for now if you install Windbg to -
Code:
[FONT=Lucida Console]c:\Program Files\Debugging Tools for Windows (x64) [/FONT]
You can see all of the above for yourself running ECHO or SET from a CMD/DOS screen - both \system32 and \syswow64 -
Code:
[FONT=Lucida Console]set > 0 & start notepad 0 [/FONT]
Results -
\windows\system32\cmd.exe -
Results -
\windows\syswow64\cmd.exe -
I used the x64
Altap Salamander 3.0 beta 1 (PB79) during testing and never gave much thought to the Windbg installation location.
Apologies for that oversight.
