search for: bblaauw

I know there's a module to check which syslinux bootloader was used, but is there also a module for detecting MEMDISK? Basicly I want to use the same isolinux.cfg for a CD which boots an ISO. Issue is that the inner ISO also uses same Isolinux (+ menu), which isn't very user-friendly. So: CD --> ISOLINUX (menu) --> MEMDISK CDROM.ISO --> ISOLINUX (menu) --> diskette

I've recently purchased an SSD with the goal of having a portable MS-Windows installation, something which Windows 8's "Windows to Go" feature allows (install to, and boot/run from, USB flash device). Housing the SSD in an external Zalman VE300 case allows presenting ISO files as hardware CD/DVD/BD drive with inserted medium. Having the ISO files present, it's tempting

...n putting togehter a 55MB distribution on cdrom, and your ISOLINUX project proves it's very easy to add it to existing cdrom's to make them (multi)bootable. Thanks to both your effors and those of the FreeDOS people the smallest multiboot cdrom is now 1.71MB big [http://members.home.nl/bblaauw/fdbootcd.iso] This way, the 1.71MB + 50MB FreeDOS distro can be added to computer magazine's cdrom's as a promotion means. Also, this small bootcdrom allows for easy bios flashing (can't do that in Linux AFAIK). In short: no more "I have win2000/linux/whatever on my pc, how do...

Hi there, I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... what is the problem can anybody tell me.. Regards, Yogesh

Would it be a usefull addition to memdisk's "pause" parameter if it showed the loading speed for the specified disk image file? The idea is to verify if a device is really loading an operating system's data at the intended device/controller/interface/bus (etc) speed. My own system has a habit of setting usb2.0 interface to 1.1-speeds for example. With (hopefully) bootable

Hello, I would like to boot dos image through PXE linux with menu where the user will have option of booting A: Dos b: Linux Any how to or guide , will help me out any links will also help Regards K.dinesh *********************************************************************** In a World Without Fences Who Needs GATES ? ***********************************************************************

THX, helps a lot On 17.08.2013 15:09 Gene Cumm wrote: > Can you deal with a client taking 1-4 minutes to just fetch files? If > not, you will have a performance issue. > Unfortunally not, the performance issue is known )-: > > Where does startrom.0 come from? Some Windows file? > I don't know, it is build by the company where we get the .nbis from > > So planning

I'm running into an issue which I didn't expect to encounter. When specifying the "nopassany" parameter to hide physical drives, I'm getting different output from ELTORITO.SYS (v1.5, syslinux distro) such that it fails. My intent is a LiveCD functionality with a DOS RAMDISK program taking over as drive C:, meaning either no FAT partitions on harddisks and removable disks

Op 18-6-2018 om 20:19 schreef R S via Syslinux: > 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

MEMDISK included in the freshly released Syslinux v3.10 is unfortunately broken. v3.09 works properly. Scenario: Isolinux --> MEMDISK --> FDBOOT.IMG (FreeDOS 360KB diskette image). Then try to access drive B: , which normally is your first diskette drive with driveletter A:. However, in this case MEMDISK occupies A:, and real diskdrive becomes B: Bug: when accessing B:, you're asked

(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > Hi there, > I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... > what is the problem can anybody tell me.. > please read Syslinux and Memdisk

I'm currently trying to integrate ReactOS's bootloader into my concept bootdisk with standard layout. It uses Syslinux 4.10pre15. This is failing on two parts: 1) bootsector method only works if specifying huge cluster size (16KB) 2) Multiboot method fails due to opening bootloader's configuration file from harddisk instead of bootdisk.

Is there any documentation available about what block size MEMDISK uses to load (big iso/harddisk) image files? Experimenting with cptime.c32 on a Lexar Triton Jumpdrive (64GB, 170MB/s read in Windows, 150MB/s write in Windows) on bootable USB3.0 resulted in the following, depending on specified block size: * 2048 bytes --> 25MB/s * 2MB --> 61MB/s It would be nice to know at which speed

Christoph Hanle schreef op 17-8-2013 18:08: > I think I will use gxpelinux.0 from 4.07 or 4.05 for "quick and dirty" > boot and have the 5.1x with gpxelinux.0 or lpxelinux.0 in the lab and > testing phase. Wouldn't iPXE be an option? It might have a couple of menu options nowadays, like Syslinux always has had. http://ipxe.org/wimboot Bernd

I've recently returned to working on FreeDOS again after quite some time, and read about an unmerged MEMDISK branch that allows to boot DOS-based ISOs. This seemed quite usefull to me as it allows for faster modifications to my code/scripts/disklayout. The general idea was to install Syslinux 3.83 to harddisk, then add the modified Memdisk from that boot-land forum, as well as my ISO. In

I'm running into some issues with regard to isolinux and memdisk, and am not sure where to ask/look in the best way possible. These are DOS-related issues. So here goes: * Can MEMDISK map a imagefile (compressed? harddisk?) to more than (and/or beyond) 4GB of memory? Say you'd have 8/16GBGB and want 4GB available to the user so might as well use the other 4/12GB for MEMDISK. Or max

Dear Syslinux bootloader list, I'm running into a few issues concerning Syslinux modules here, hoping you can answer one or more of the following questions: * Where's "ifmemdsk.c32" ? 4.05, 4.06pre1 and latest 4.10pre seem to lack it. Only the "ifmemdsk.c" file, which is likely sourcecode. Not seeing any "ifmemdsk.cbt" legacy comboot module. * Do COM32

H. Peter Anvin schreef op 9-8-2013 7:37: > Sorry. If you are substituting any files you should substitute them all. I assume it's not possible to store a copy of the LDLINUX.SYS binary at the end or inside of either ISOLINUX.BIN or LDLINUX.C32 then? Then at least it could be extracted, for those distributions not having LDLINUX.SYS / SYSLINUX(64).EXE present on their CD. Having