I've been looking around for information about MBRCheck and decided to
look at a disk that I ran syslinux on to see what it claims afterwards
What should I see as an sha1 hash for a disk that has been made
bootable by syslinux?
I remember reading that I should make a disk bootable in linux by the command
dd if=mbr.bin of=/dev/sd[x]
and am starting to think this could get ugly for a verifiable checksum
for mbrcheck as I think it always looks at the first 440 bytes but
from what I see the mbr.bin that comes with slax is only 404 bytes
thus if there was stuff in the last (440-404=) 36 bytes it would be
left un-clobbered causing a different checksum depending on what was
already on the disk. I don't know what the windows version of syslinux
does to make a device bootable and am asking this mailing list.
The slax version of is run from a batch file bootinst.bat that contains the line
\boot\syslinux\syslinux.exe -maf -d \boot\syslinux %DISK%:
that it uses to make the disk bootable. I'll ask on the slax forum for
the version number they used with slax 6.1.2 the version I am using.
Question again is
What does the windows version of syslinux do (in terms of how to run
the linux version) given the following arguments
\boot\syslinux\syslinux.exe -maf -d \boot\syslinux %DISK%:
does it do the equivalent of "dd if=mbr.bin of=/dev/sd[x]" and then a
syslinux on the first partition on the disk?
