As John said, you should be able to change it at installation. The problem is that the "default" directories the tool currently supports are all old. The directories you are seeing there are the new "defaults" for ~Windows 8 versioned debugging tools. If you were to install an old version of the tool, dating from ~XP - Vista, you would see the default directories as the ones the tool currently supports.
What we need to do is add these new, extra default directories to the tool. The problem is that this is actually much more involved that one might at first imagine, and requires me to get a block of free time to do it.
Didnt see this till just now. Dont know if this answer is still relevant but. I did initially install to the default location, and after having some grief, moved both the symbols, and WinDBG to the default location.
I am sorry that you are having such problems. This looks to be a bug in the program rather than a problem with any of your configuration. I have been having some serious problems with that piece of code, and now it appears to be crashing too!
Could you please run the program again, leave the "$99_dbug.exe has stopped working and was closed." message on screen, open up Task Manager normally if you are using a 32bit computer, or manually via %WinDir%\SysWOW64\TaskMgr.exe if on a 64bit computer (it is essential that you open the 32bit Task Manager using this method if using a 64bit computer).
In Task Manager, from the Processes Tab, right click on $99_dbug.exe > Create Dump File, and then copy the created .dmp file from the %Temp% directory (Task Manager will tell you where it was created) to a safe location. Only now may you exit from the "$99_dbug.exe has stopped working and was closed." message.
Could you then please right click on the created dump file > Send to > Compressed (zipped) folder, and check the size of it. If it is of a reasonably small size, could you please upload it somewhere, and provide me with a link. If it is of an unreasonable size, please do not upload it, and I will collect the data in a different way.
Thanks for the info on the admin rights. I will add that to the instructions. I really should do more testing off a normal account, rather than my admin account. I test some things that way, but clearly not enough! Also, thanks for uploading that report. It was extremely helpful.
The crash itself actually seems to be caused by the program stumbling over $_dvrref_table_98. Does this parm file actually exist on your computer? What is its contents? It should be one of either: