Log in
Register
What's new
Search
Search
Search titles only
By:
Menu
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums
Tutorials
About
Rules
What's New
Driver Reference Table
Donate
Search titles only
By:
Latest activity
Register
Sysnative BSOD Analyst App Repository
BSOD Processing Apps Download | Info + Discussion
AutoBlue BSOD Tool Development
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="AceInfinity" data-source="post: 144" data-attributes="member: 4"><p>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.</p><p></p><p>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.</p><p></p><p>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 :)</p><p></p><p>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.</p></blockquote><p></p>
[QUOTE="AceInfinity, post: 144, member: 4"] 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. [/QUOTE]
Insert quotes...
Verification
Post reply
Sysnative BSOD Analyst App Repository
BSOD Processing Apps Download | Info + Discussion
AutoBlue BSOD Tool Development
Menu
Log in
Register
Top
