![]() ![]() |
Nov 14 2009, 03:15 PM Post
#141 | |
| André Guimarães Casal ![]() ![]() Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771 |
My best guess: When you are creating the ISO file, the batch command start cdimage.exe -lDVD -t01/01/2006,12:00:00 -b\DVD\BOOT\loader.bin -h -n -o -m \DVD C:\AIODVD.iso imprints the loader.bin into the corresponding section of the ISO. This loader.bin actually comes with CDImage itself, so it's not related to CD Shell. Think of the loader.bin file as the binary code that tells the machine (where) to start loading stuff from the DVD. What happens next is that the machine starts to load the CD Shell "operating system" wich in turn launches the menu. The loader.bin file is the same for pretty much any DVD, except DVD's with secure data.
This post has been edited by andregcasal: Nov 14 2009, 03:16 PM |
| | |
Nov 14 2009, 03:21 PM Post
#142 | |
| Advanced Member ![]() ![]() ![]() Group: Members Posts: 345 Joined: 29-September 05 Member No.: 74988 | So, I think this means you need to burn cdshell's No, loader.bin is not located at sector 17. Read the CD boot specs again.loader.bin to that sector QUOTE and that loader.bin sector on the iso tells the machine to check the folder /BOOT for the next step? Loader.bin load cdshell main application: cdsh.bin. By the way: cdshell is not developed since 2005. |
| | |
Nov 14 2009, 03:23 PM Post
#143 | |
| André Guimarães Casal ![]() ![]() Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771 | |
| | |
Nov 14 2009, 03:48 PM Post
#144 | |
| Advanced Member ![]() ![]() ![]() Group: Members Posts: 345 Joined: 29-September 05 Member No.: 74988 | This loader.bin actually comes with CDImage itself, so it's not related to CD Shell. CD Shell contain a loader.bin. It's recommended to use this loader for CD Shell.BTW, is there any leading open source booter around? What's a leading booter?There are two open source booter developed currently: grub4dos and syslinux. |
| | |
Nov 14 2009, 03:51 PM Post
#145 | |
| André Guimarães Casal ![]() ![]() Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771 | |
| | |
Nov 14 2009, 05:09 PM Post
#146 | |
| a joy forever ![]() ![]() Group: Members Posts: 126 Joined: 24-July 08 From: Langford, Canada Member No.: 202362 OS: XP Pro x64 | What's a leading booter? Leading stads for leadership, the leader, the best, the most used. grub4dos must do the job. Thank you. |
| | |
Nov 16 2009, 03:04 PM Post
#147 | |
| Advanced Member ![]() ![]() ![]() Group: Members Posts: 345 Joined: 29-September 05 Member No.: 74988 |
General grub4dos informations: integrated help file http://grub4dos.sourceforge.net/wiki/index...ub4dos_tutorial http://diddy.boot-land.net/grub4dos/Grub4dos.htm Grub4dos can chainload setupldr.bin: no need for a boot sector file. Grub4dos was enhanced recently, 14th Nov 2009: http://nufans.net/grub4dos/tinybit/ Editing in RAM is possible now. CODE title Loading XP install - plain /I386/SETUPLDR.BIN chainloader /I386/SETUPLDR.BIN title Windows XP Home\n Windows XP Home - multi boot - unattended map --mem /XHO1/SETUPLDR.BIN (rd) cat --locate=i386 --replace=XHO1 (rd)+1 chainloader (rd)+1 root () title Windows XP Home\n Windows XP Home - multi boot - attended map --mem /XHO1/SETUPLDR.BIN (rd) cat --locate=i386 --replace=XHO1 (rd)+1 cat --locate=WINNT.SIF --replace=WINNT.OFF (rd)+1 chainloader (rd)+1 root () title Windows XP Home System Builder\n Windows XP Home - multi boot - mass storage drivers floppy image map --mem /INST/F6FLOPPY.IMA (fd0) map --mem /INST/F6FLOPPY.IMA (fd1) map --hook map --mem /XHO1/SETUPLDR.BIN (rd) cat --locate=i386 --replace=XHO1 (rd)+1 chainloader (rd)+1 root () title Windows XP PRO 64 SP2 - multi boot map --mem /XP64/I386/SETUPLDR.BIN (rd) #checksum: geitonaki http://www.msfn.org/board/index.php?showtopic=58410 write --offset=0x2060 (rd)+1 \xEB\x1A #cdob SetupSourcePath="\XP64\"; BootPath=\XP64\AMD64\ #http://www.msfn.org/board/index.php?s=&showtopic=126480&view=findpost&p=814566 cat --locate="\\i386\\ntdetect" --replace="\\XP64\\ntdetect.com" (rd)+1 cat --locate="amd64\\" --replace="XP64\\\x00" (rd)+1 cat --locate="AMD64\\" --replace="XP64\\\x00" (rd)+1 cat --locate="\\AMD64" --replace="\\XP64\x00" (rd)+1 cat --locate=I386 --replace=XP64 (rd)+1 chainloader (rd)+1 root () @meowing Yes 0x00 is importand, space won't work. |
| | |
![]() ![]() |
| Lo-Fi Version | Time is now: 21st November 2009 - 08:12 PM |