similar to: Question about hdt and UEFI

If I remember correct HDT is a .C32 executable and not .EFI, so no it will not work. On Tue, Apr 10, 2018 at 10:02 AM, Gene Cumm via Syslinux <syslinux at zytor.com > wrote: > On Thu, Mar 8, 2018 at 4:43 AM, Nicolas L?cureuil via Syslinux > <syslinux at zytor.com> wrote: > > > i am trying to use hdt with an UEFI install. It does not start and > freeze. > >

Dear Syslinux folks, For a firmware update I am following the Gentoo Wiki [1] to create a floppy image of 20 MB, so that the vendor update utility fits. Unfortunately, FreeDOS does not load, and it seems to hang loading the FreeDOS kernel. The original FreeDOS image boots. Do you know if that issue is memdisk related? It?s started from GRUB with the commands below. linux16 /boot/memdisk

You mind to elaborate? I'd like to re-use HDT as well, but I was forced to abandon it years ago due to lack of UEFI support and lack of development. Heck even the website hdt-project is now owned by a domain-grabber (The Syslinux wiki is still linking to it when I check 3 weeks ago... might want to remove that link). On Tue, Apr 10, 2018 at 10:10 AM, Gene Cumm <gene.cumm at gmail.com>

In other words: I'm suggesting to use WinImage as it also allows easy injection of new files *and* updating of already existing files. May I ask which vendor is distributing a DOS FW update that is 20MB? I'd like to see the files. Sometimes you just need the .bin/.rom and the actual FW update EXE and it would fit a 5MB FDD image. On Mon, Jun 18, 2018 at 2:03 PM, R S <rene.shuster at

As suggested, I have made a 6.04-pre3 release. In addition to updating gnu-efi to the latest version available (3.0.9 + a few patches) I wanted to make the tree compile with -Werror on my box, which resulted in pulling a thread which in turn caused a whole bunch of things to unravel :) The end result was that I ended up refactoring much of the tree so that it now avoids building a ton of

Hi all, It has been the case for quite a while that the master tree is unambiguously better than 6.03. I have thus tagged and pushed out a syslinux-6.04-pre2 release, however, due to the issues with continuing to keep the main archive on kernel.org, I have moved the release archive to: https://www.zytor.com/pub/syslinux/ Other than the URL, there is no difference from the kernel.org archive.

On Tue, Apr 10, 2018 at 10:08 AM, R S <rene.shuster at bcsemail.org> wrote: > If I remember correct HDT is a .C32 executable and not .EFI, so no it will > not work. Syslinux on EFI won't load arbitrary .efi files but there are 3 different flavors of COM32 files, one per firmware. > On Tue, Apr 10, 2018 at 10:02 AM, Gene Cumm via Syslinux > <syslinux at zytor.com>

Hi. I prefer using the syslinux boot loader and recently undertook a project of creating a multiboot USB drive that boots using syslinux. The aim is to create a medium from which various live linux environments can be run for things like system maintenance, installation, and perhaps demonstration. I anticipate using this multiboot USB drive on mostly legacy, BIOS systems, if that matters. As

Haven't yet had a need for 10MB FDD images. The biggest I had to create was 5MB (5760kb). At that time I had to use WinImage to create the FDD image and it took me a while to figure out the correct settings. My notes state: "I'm getting 'missing FAT' errors in WinImage, and 7-zip complains about 'unexpected end'. The fix is to increasing the FDD Heads from 2 to 4 and

Thanks. Any chance to update the changelog as well. The NEWS file in the archive over at https://www.zytor.com/pub/syslinux/Testing/6.04/ only lists changes for 6.03 On Tue, Feb 5, 2019 at 5:08 PM H. Peter Anvin via Syslinux < syslinux at zytor.com> wrote: > Hi all, > > It has been the case for quite a while that the master tree is > unambiguously better than 6.03. I have thus

The narod.ru images are super outdated (FreeDOS kernel 2028) unfortunately. If you are interested I could provide a 5MB FDD image template based on FreeDOS 2041 kernel (the latest available at that time in 2014) where you would just inject your ROM and EXE (and possibly adjust autoexec.bat to autostart/apply the FW update). It's a minimal FreeDOS FDD image that defaults to a clean boot with

On Thu, Mar 8, 2018 at 4:43 AM, Nicolas L?cureuil via Syslinux <syslinux at zytor.com> wrote: > i am trying to use hdt with an UEFI install. It does not start and freeze. > > Does someone know if it is supposed to work ? > > Btw i have enough machines here to do real QA :) Personally, I have never tried. The symptoms would seem to indicate it's trying to execute some

The dynamically alloc'd string to protect from strtok modification has not been free'd on start_auto_mode() function Signed-off-by: Felipe Pena <felipensp at gmail.com> --- com32/hdt/hdt-cli.c | 1 + 1 file changed, 1 insertion(+) diff --git a/com32/hdt/hdt-cli.c b/com32/hdt/hdt-cli.c index 7542da8..6c5baf1 100644 --- a/com32/hdt/hdt-cli.c +++ b/com32/hdt/hdt-cli.c @@ -779,6

HDT 0.3.3 has just been released. This release aims at solving some CLI bugs and adds a some new memory mapping detection. I'd like to thanks Dag Wieers for reporting many CLI bugs & pierre for his work on the memory mapping. Here come the changelog: - A new memory mode Memory items can be reached via the new "memory>" mode. - Memory mapping display Pierre did integrate

It is now possible to build a bootable floppy image which contains HDT, with my patch applied to Erwans HDT branch: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=16b37fe2266c920087f88cdec94243b71218d871 Unpack the Syslinux archive and build whole Syslinux first, then cd to ./com32/hdt/ and make hdt.img $ make $ cd ./com32/hdt/ $ make hdt.img Now you have a 2.88 MB floppy image which

HDT 0.3.3 has just been released. This release aims at solving some CLI bugs and adds a some new memory mapping detection. I'd like to thanks Dag Wieers for reporting many CLI bugs & pierre for his work on the memory mapping. Here come the changelog: - A new memory mode Memory items can be reached via the new "memory>" mode. - Memory mapping display Pierre did integrate

Dear developers, Thanks a lot for designing HDT. It is really a great tool to have. I have come here to know more about the usability of HDT. HDT is called by syslinux. What to do if I like to call it by grub2 ? and what to do if I like to run within my debian box ? Thanks

Hi, So the 'modules.pcimap' file, needed by Hardware Detection Tool to display kernel modules, is now missing. pciutils/kmod deprecated usage of this file adn depmod lost its -m option. So here are may questions: 1- How to generate a "modules.pcimap" or an equivalent file nowadays? 2- Is it still needed by HDT ? 3- What if it is missing, is HDT semi-broken? Thanks.

From: Matt Fleming <matt.fleming at linux.intel.com> Don't link against libmenu.a, it no longer exists as it was removed in commit 74518b8b691c ("elflink: Make ELF the default object format"). This fixes the following build error, make[2]: *** No rule to make target `../cmenu/libmenu/libmenu.a', needed by `hdt.c32'. Stop. Signed-off-by: Matt Fleming

This patch builds a floppy image with contains HDT, so users of GRUB or GRUB4DOS can use HDT too, without installing Syslinux. When you compile Syslinux, this floppy image isn't build automatically. To build it, runthe following from the extracted Syslinux source: $ cd ./com32/hdt $ make hdt.img As suggested by Pierre-Alexandre Meyer, all extra files required for building the floppy