https://sourceforge.net/p/bootdebug/wiki/Tools/Recent changes to ToolsenTue, 25 Mar 2014 23:43:32 -0000https://sourceforge.net/p/bootdebug/wiki/Tools/<div class="markdown_content"><pre>--- v1 +++ v2 @@ -12,12 +12,12 @@ When specifying a path to data located inside of an image the root of the path is used to indicate the partition to access in the format of (hd0) where 0 is the partition number. So if you wanted to reference the BootDebug you would use a path something like *(hd1)\BootDebug.exe* -**Usage: DiskTools.exe COMMAND ImageFile [Options]** +**Usage: DiskTools.exe COMMAND ImageFile \[Options\]** **Command list** -* INFO ImageFile: Returns info on the Image file -* DIR ImageFile [Path]: Lists the contests of a folder -* COPY ImageFile SrcFile [DestFile]: Copies the SrcFile from the Image to DestFile (or console if not provided). -* Add ImageFile SrcFile DestFile: Copies the SrcFile into the Image at DistFile + * INFO ImageFile: Returns info on the Image file + * DIR ImageFile \[Path\]: Lists the contests of a folder + * COPY ImageFile SrcFile \[DestFile\]: Copies the SrcFile from the Image to DestFile (or console if not provided). + * Add ImageFile SrcFile DestFile: Copies the SrcFile into the Image at DistFile LibMaker ----------------- </pre> </div>Fox CutterTue, 25 Mar 2014 23:43:32 -0000https://sourceforge.netc2c981501366d683b37d34297831775a3160d2edhttps://sourceforge.net/p/bootdebug/wiki/Tools/<div class="markdown_content"><h2 id="headerset">HeaderSet</h2> <p>This is a simple tool to set the Mulitboot headers inside of a PE file. It will use the header information in the file itself to generate the load information. This should work with any base, but it's best to use 1 meg just to be safe. </p> <p><strong>Usage: HeaderSet.exe "Path to PE file"</strong></p> <h2 id="disktools">DiskTools</h2> <p>A simple command line tool to work with disk images. Allowing you to list information and files, read the contests of files and add/update files. This is useful for quickly updating the version of BootDebug in an existing image without having to fiddle around with anything other then the image itself.</p> <p>When specifying a path to data located inside of an image the root of the path is used to indicate the partition to access in the format of (hd0) where 0 is the partition number. So if you wanted to reference the BootDebug you would use a path something like <em>(hd1)\BootDebug.exe</em></p> <p><strong>Usage: DiskTools.exe COMMAND ImageFile <span><span>[Options]</span></span></strong><br /> <strong>Command list</strong><br /> <em> INFO ImageFile: Returns info on the Image file<br /> </em> DIR ImageFile <span>[Path]</span>: Lists the contests of a folder<br /> <em> COPY ImageFile SrcFile <span><span>[DestFile]</span></span>: Copies the SrcFile from the Image to DestFile (or console if not provided).<br /> </em> Add ImageFile SrcFile DestFile: Copies the SrcFile into the Image at DistFile</p> <h2 id="libmaker">LibMaker</h2> <p>This tool is a simple batch file. When run Visual Studio command environment it will find the provided lib file, extract out a know set of objects representing necessary support functions (for 64bit math and stack checking) and built a new output library with them.</p> <p>It will use the current folder to story temporary files. </p> <p><strong>Usage: LibMaker.bat SourceLib OutputLib</strong></p> <h2 id="makelibs">MakeLibs</h2> <p>When run under the Visual Studio command environment, this will generate the Core.lib and Cored.lib files.</p></div>Fox CutterTue, 25 Mar 2014 23:41:40 -0000https://sourceforge.net70e4eb29d8e52827556163d289c8b9694193f801