search for: mbrs

Add detection code for "MS-DOS 3.30 through Windows 95 (A)" MBR to disklib. Signed-off-by: Gert Hulselmans <gerth at zytor.com> --- com32/gpllib/disk/mbrs.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/com32/gpllib/disk/mbrs.c b/com32/gpllib/disk/mbrs.c index 77e4180..37309e1 100644 --- a/com32/gpllib/disk/mbrs.c +++ b/com32/gpllib/disk/mbrs.c @@ -27,7 +27,6 @@ void get_mbr_string(const uint32_t label, char *buffer, con...

Add detection code for "FreeDOS (eXtended FDisk)" MBR to disklib. Signed-off-by: Gert Hulselmans <gerth at zytor.com> --- com32/gpllib/disk/mbrs.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/com32/gpllib/disk/mbrs.c b/com32/gpllib/disk/mbrs.c index 37309e1..6150fcf 100644 --- a/com32/gpllib/disk/mbrs.c +++ b/com32/gpllib/disk/mbrs.c @@ -27,7 +27,6 @@ void get_mbr_string(const uint32_t label, char *buffer, con...

...ve that xor in there. > But then better safe than sorry, and given that there is space _now_, > why not? I still agree. But while answering Ady's questions i get to a question of my own: Do all six fixed isohdp*.bin variations still fit into 432 bytes ? mbr/Makefile builds among other MBRs: isohdpfx.bin isohdppx.bin isohdpfx_c.bin isohdppx_c.bin isohdpfx_f.bin isohdppx_f.bin Their purpose is explained in the table at http://www.syslinux.org/wiki/index.php?title=Isohybrid#MBR_selection Have a nice day :) Thomas

Hi, H. Peter Anvin: > It means that the .iso can be booted from a partition using any of the > standard MBRs (not necessarily altmbr), But the --partok MBRs (isohdpp*) stem from altmbr ? If so: don't they need the partition number patched in ? (If not: i have to rethink the link to article "Mbr" at http://www.syslinux.org/wiki/index.php/Isohybrid#MBR_selection ) > One of the main u...

...ainer of third-party tools / packages) have a negative view / opinion regarding this change of directory. BTW, let's not forget the existence of the "diag/*" files in Syslinux. Regards, Ady. PS: Let's also not forget the existence of other methods / code to generate / install MBRs and/or VBRs such as: _ "sys.com" / "sys.exe" (v.3.8) from FreeDOS; _ "sys-freedos-linux"; _ "ms-sys" ( _code in C_ ) and its forks such as: _ "ms-sys-free" (current latest code is older than its parent); _ a fork of "ms-sys" by Pete...

Hi, i am trying to document the MBR selection by isohybrid option --partok. I assume it is related to "altmbr.bin" as described in http://www.syslinux.org/wiki/index.php/Mbr But there i read "altmbr.bin [...] boots from a partition with fixed number, see below." The "see below" probably refers to "The altmbr.bin (all 3 variants) is only 439 bytes long, -- one

Hi, Duncan Elliot wrote: > As far as I can see, this essentially trims off the first 3 bytes of the > custom isohybrid MBR image before applying it to the ISO. You probably mean this line: memcpy(mbr, &isohdpfx[hd0 + 3 * partok], MBRSIZE); The indize do not apply to bytes but to byte arrays of size MBRSIZE. extern unsigned char isohdpfx[][MBRSIZE]; (hd0 + 3 * partok) selects a particular MBR template from an array of six MBRs. See also http://www.syslinux.org/wiki/index.php?title=Isohybrid#MBR_selection It tells which...

Hi, currently syslinux fails to build from source in Debian as has been reported in https://bugs.debian.org/906414 . The reported error is: mbr.bin: too big (452 > 440) I've realized that this is because since a recent version, the linker adds a new section (.note.gnu.property). Discarding this section fixes the problem. I've attached a patch, please consider merging it. Thanks

...hard to do in any programming language, if you can open the stick device for read/write operations. > I had no idea at that > time that I needed to set _both_ the bootable flag and the (non- > standard?) "LBA" flag. But apparently both are vital. Now I know. As producer of MBRs i wonder where that LBA-flag is located. In bit 0 to bit 6 of byte 446 (where bit 7 means active/bootable) ? Is any background info known ? A flag to tell that C/H/S shall be ignored would be interesting. I am looking at https://git.gnome.org/browse/gparted/tree/ but don't find enlightenment...

...it was already done in Makefile some time earlier. Luckily, elsewise my local copy was up to date. > > [statements about off_t and fseeko(3)] > Please convert that into patches to the mailinglist. I got six patches now. The end version compiles and can run standalone without hardcoded MBRs. I will make some repacking tests with a Fedora image. Would diff -puN from one patched version to the next one be ok ? Have a nice day :) Thomas

I Have a Xen 3.0 running and want to resize a few images that are backup up with rsync. They are 20G and need them to be 5Gb. Can that be done? thank you. -- saludos! ------------------------- Alejandro Weintz Aguilar PixelEstudios.com. Tel. (506) - 5920328 Cel. (506) - 3080035 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

...eems a bit insane. If someone play with the syslinux's internal compilation process, he is probably aware that it may change completely on every single commit. We just do not support this usage. > PS: Let's also not forget the existence of other methods / code to > generate / install MBRs and/or VBRs such as: > _ "sys.com" / "sys.exe" (v.3.8) from FreeDOS; > _ "sys-freedos-linux"; > _ "ms-sys" ( _code in C_ ) and its forks such as: > _ "ms-sys-free" (current latest code is older than its parent); > _ a fork of &...

Hi Guys, I have a server running CentOS 4.2 with a 2.6.9-22EL-smp kernel. The system contains a 2.3 TB RAID 5 array. There is a 20GB root partition with the remainder of the drive configured one large LVM volume. (/u0) I have installed Veritas Netbackup on the server and am running a few tests. Small backups and restores work just fine. When I run a larger backup (500MB) and store the

...From your main system, from your Windows system (although this might be a last resort), etc. And/Or use the mbr.bin files from different syslinux versions. Make sure to not disturb the partitioning when doing this ("bs=440 count=1"). Can you make it boot then? If so you can compare the mbrs to see what's different if you want. For the partitioning: If not try partition the USB stick/disk with another partition tool. My experiences with gparted have been bad. With sfidks and fdisk acceptable (to add to the confusion, there were two different fdisks in Debian: one from util-linux...

> There's 0 need to build MBRs for > EFI At least gptmbr.bin might come to mind (after all, GPT is part of the UEFI specs). Isohybrid with UEFI options perhaps too? > and I'm looking at why utils/ depends on mbr/ isohybrid(.pl) and mkdiskimage come to mind here? I'm not saying for certain these are the r...

> It's source code looks like a BIOS MBR program which shall search > the "active" partition in GPT rather than in the MBR partition table. > See comments about "EBIOS" detection and "CHS" addresses in > https://github.com/geneC/syslinux/blob/master/mbr/gptmbr.S > > "Active" partitn would be the one which has bit 2 set in the

...--------- > 5 files changed, 1192 deletions(-) > delete mode 100644 core/syslinux.ld > delete mode 100644 core/x86_64/syslinux.ld > delete mode 100644 efi/syslinux.ld > delete mode 100644 mbr/mbr.ld > delete mode 100644 memdisk/memdisk.ld Removing mbr/mbr.ld makes 0 sense. MBRs are a BIOSism that won't be present on UEFI IA32 (aka i386) and X64 (aka x86-64 IA32-64 EM64T AMD64). I feel it makes more sense to remove the architecture-specific scripts. A MEMDISK-like system for UEFI would probably need to be implemented as a UEFI driver. As a result, it's questiona...

...may 2012 that all mbr/isohdp[fp]x*.bin begin by 33 ed 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 Can i safely refuse on MBR templates which do not bear that signature without inflicting injustice on future isohybrid MBRs ? (I will also accept the substituted bytes of isohybrid --mac: 45 52 08 00 00 00 90 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ) ---------------------------------------------------------------------- I tested my implementation...

...; wrote: > Hi, > > Duncan Elliot wrote: >> As far as I can see, this essentially trims off the first 3 bytes of the >> custom isohybrid MBR image before applying it to the ISO. > > You probably mean this line: > > memcpy(mbr, &isohdpfx[hd0 + 3 * partok], MBRSIZE); > > The indize do not apply to bytes but to byte arrays of size MBRSIZE. > > extern unsigned char isohdpfx[][MBRSIZE]; > > (hd0 + 3 * partok) selects a particular MBR template from an array of > six MBRs. See also > http://www.syslinux.org/wiki/index.php?title=Iso...

...otsector" of the bootloader) from the beginning of the selected partition * set DS:SI pointing to the selected partition table entry * jump to 0x7c00 (with CS set to 0, and DL set to the "drive number") " So the behavior of GRUB might matter and thus testing of other disk MBRs might be of interest. Have a nice day :) Thomas