That's most likely due to your settings, for syntax errors check the configuration, and make sure the setlist of commands is correct for kd.exe. I didn't check those when I released these versions. But latest version appends ;q to the end of the commandlist automatically.
Open up "config.set" file and check this commandlist:
These are the list of commands it will run through, also make sure your symbols are pointed to the correct path through the config.
Latest version: Please update the program by clicking the update button on the application, it may be slow, but for v1.2.7 which i'm officially releasing right now, it should litterally take no more than a second to update from any update from now on in the future.
I've fixed a few things, and had some major changes in functionality and increased performance.
Please for testing make sure you have v1.2.7, i'd like to see how this version goes, updates should no longer freeze the form/GUI, i've multi-threaded everything.
One thing I am working on to improve is to make sure that the user should be able to almost use the program without having to look through the instructions, or require any help with it
I am able to make this program's source more secure by modifying the PE/DOS header as a preventative for basic disassemblers, however doing this is not bad, it is a pseudo method for some AV's to detect it as a false positive for a program. (Mostly on the very terrible AV's that most people have unheard of.)
Not sure if it's possible, but can you implement the windbg debugger into your software? For example, I am at work now and I want to run some dumps. If I use your program I would need the debugger installed on this comptuer and that isn't an option
That would mean combining the filesize of KD.exe WinDbg.exe and my program executable itself though which is a fairly large/decently large filesize for a program though. WinDbg and KD though are portable executables aren't they? I wasn't required to install any of them when I downloaded the programs. They came straight to me in the Microsoft 64 bit debugging tools for Windows zip archive.
However, if I was to include it to the program, you'd still need to have all of the symbols anyways to run it properly. Do you have a USB or anything like that which you can take to work? I know that's what i'd probably do, just to keep my symbols KD and/or WinDbg on the key, along with my program and then you wouldn't need anything else.
It is possible, but for most big applications, the reason why they are installed is because they try to keep the application executable itself a small filesize for performance reasons. All the installation does is it adds the dll's or any other config files to a file layout in your programs folder in the way the program wants to read from them, and IF it requires any other settings, programs ONLY make registry edits if that's the way they store their settings. Otherwise they keep it in an xml or ini file for example. My application though and WinDbg as far as I know was a portable app, along with KD. They gave me the exe files straight from the zip file and I was able to use them right after extraction to my desktop when I first downloaded them
My app doesn't do any registry changes either, I meant for it also to be a portable app, and the only thing that should be taken care of when moving it around is that the AutoBlue folder with it's contents just needs to stay in the same directory as the executable itself. Otherwise on startup it will create those files, but it does not generate the README or the MS driverlist or the Return list.
It's a permission issue with the debugger itself being able to load the symbols on a removable media drive. You'd have to move them to the actual computer drive with accessible permissions. Otherwise, what are the settings you're using?
Is it correctly pointing to the debugger and your symbols? If you configure it at home and you move the USB to another computer there's a chance that it might not use the same drive letter keep in mind. Those settings are crucial.
What about running as admin?
Edit: By what I see you're settings for kd/windbg and symbol path should be in "K:\" it appears though that you're loading from "K:\symbols" though.
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kext) failed, Win32 error 0n2
"The system cannot find the file specified."
I may have this permission error fixed if I can include a shared set of permissions using the Fileshare enumeration values in a method that allows such a parameter to read the filestream. Above all that though, everything else seems to be working for an independent app. I'll be working more on the current version that I have now before making it available as an update or download