Displaying 20 results from an estimated 3000 matches similar to: "pxelinux/memdisk booting MSDOS floppy image requires local floppy disk"
2007 Oct 04
4
Any workaround for ThinkPad memdisk?
Hi,
I saw the Nov. 2006 message on Memdisk having a problem with ThinkPads. I also
saw the comment in the memdisk code enabling and disabling A20.
I've got a ThinkPad x61t that memdisk is not loading disk images on. The
symptom is that it gets as far as saying "Loading boot sector... booting..."
Then image partially runs - FreeDOS prints out its kernel message and it's
2014 Jul 08
3
Possible memdisk issue
I'm having trouble getting memdisk 6.03pre18 to boot large floppies and
wondering whether I'm doing something incorrectly.
1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz
2) gunzip FDOEM.144.gz
3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img
4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img
5) Use following pxelinux.cfg:
LABEL works
LINUX syslinux/memdisk
INITRD
2018 Jun 18
3
Memdisk and big floppy images
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
2007 Jul 13
1
[memdisk] collision between memdisk and emm386 (FreeDOS)
Hi
I'm using memdisk as part of CD Shell' isolinux. I've created custom floppy
disk image 8440kB size. I've put FreeDOS kernel and bootsector into the
floppy. Boot process goes fine with this command:
isolinux /boot/memdisk initrd=/ximg/fdos.img c=60 h=8 s=36 floppy
The problems begin when I try to run FreeDOS memory manager emm386 from the
floppy image.
my config.sys:
...
2014 Jul 09
5
Possible memdisk issue
On Tue, 08 Jul 2014 15:54, H. Peter Anvin wrote:
>
>On 07/08/2014 11:26 AM, Ady wrote:
>>
>> It's interesting that you ask this, because every document related to
>> newmkfloppyimg.sh specifically recommends adding:
>> floppy c=$CYLINDERS s=$SECTORS h=$HEADS
>> to the MEMDISK arguments.
>>
>
>It would be important for floppies to know
2007 Apr 11
3
Large Floppy Images
I have periodically been trying to get memdisk to boot images
larger than your average 1.44Mb floppy and have always been
unsuccessful. I cannot boot anything greater than 1.44Mb. The systems
I'm attempting to do this with are not too old but they are not recent
either. One is a Asus P5A and the other is a Intel SE440BX both with
the most recent bios firmware patches available applied. If
2003 Dec 01
1
Memdisk/XMS bug, big floppy image
>that image under B: or X: or whatever. This will allow us to cross the
>size limit of 2.88MB floppies. Ofcourse when I say "mount" I dont expect
>memdisk to mount it, just that set things up so that DOS mounts it there.
I'm using a 5MB image which emulates floppydisk.
label test
kernel data/memdisk
append initrd=data2/test.img c=80 h=8 s=18 floppy
problems are
2012 Oct 22
1
[PATCH] memdisk: adjust order of DPT values in mstructs.h
This is a resubmission of my patch sent Jun 18, 2011 since it does not
seem it was accepted. Please let me know if I am doing something
wrong in how I am submitting this patch. Thank you.
The below patch will swap order of sectors/track with bytes/sector to
match diskette
parameter table order (as pointed to by INT 1Eh).
References: (additional ones available if necessary)
'System BIOS for
2018 Jul 06
1
Memdisk and big floppy images
2018-06-26 2:10 GMT+08:00 H. Peter Anvin via Syslinux <syslinux at zytor.com>:
> On 06/18/18 13:06, R S via Syslinux wrote:
>> 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
>>
2014 Jul 15
4
Possible memdisk issue
On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao
Miller, Kenneth Davis, wrote:
> [...]
Thank you all for your responses. You helped me solve my problem. For
anyone else that runs into similar trouble and finds this thread, here
follow summaries of what I've learned.
To recap, our PXE server holds Dell BIOS updates in FreeDOS floppy
images booted via MEMDISK.
2003 Dec 30
5
Pxelinux/memdisk with XP "MS-DOS" boot disk
I'm trying to use this universal DOS TCP/IP boot disk available here:
http://members.iinet.net.au/~bdriver/bootdisk/
It requires an MS-DOS formatted disk created by Windows XP. It works great as a floppy but doesn't boot at all with memdisk. The problem can be simplified down to just the XP boot disk. If you make an MS-DOS startup disk with XP on a floppy, dd the floppy to an image
2006 Oct 31
3
Laptop+SDMMC+Extlinux+Memdisk+Floppy images=headaches
Hello syslinuxers
I'm stuck with a scientific problem which gives me headaches:
I have a laptop (Gateway MX3410) which has a SD memory card reader.
Recently an interesting thought crossed my mind: why don't I setup
a 2GB SD card as a harddrive and put some rescue tools on it.
So I dug on the net and I came across the idea of using memdisk
to boot floppy images without the need of a
2004 Jun 04
2
chainload cdrom
perhaps the boot-from-cdrom code in Smart Boot Manager?
Bernd
>>>
No, since booting from CD-ROM requires that the El Torito part of the
BIOS is activated, which it won't be if it didn't boot from CD-ROM in
the first place.
----------------------------------------------------------------
Op deze e-mail zijn de volgende voorwaarden van toepassing:
2018 Jun 18
4
Memdisk and big floppy images
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
2018 Jun 18
2
Memdisk and big floppy images
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
2003 Dec 09
3
Last call before syslinux 2.08
I am planning to release SYSLINUX 2.08 in the next day or so; basically
2.08-pre9 without any further changes.
So, I would appreciate any and all testers for this...
-hpa
2005 Apr 05
5
memdisk - reboot loaded image
Is there a method to reboot a memdisk (floppy) image?
I'm working on a DOS-based installation floppy that needs to repartition the hard disk
prior to proceeding. DOS will only recognize the updated partition table after a reboot, but
I'd like to be able to save information to the currently loaded memdisk floppy disk and
simply reboot the image. Possible?
I haven't had any luck with
2002 Oct 28
3
memdisk hard disk image
Can anyone please tell me how to create a bootable 10MB hard disk image
for use with memdisk? I'd like to use FreeDOS. And I know little of
DOS.
Thanks.
2014 Jul 09
2
Possible memdisk issue
On 07/09/2014 04:00 PM, H. Peter Anvin wrote:
>
> So this would seem consistent that this is the FAT12/FAT16 boundary that
> breaks stuff. Perhaps FreeDOS has a problem with FAT16 on floppies?
If I understand things correctly, a bootable floppy has two key pieces
of executable code: the 512-byte boot sector, and the kernel loaded by
that boot sector.
The kernel can be large, and thus
2014 Jul 08
3
Possible memdisk issue
On 07/08/2014 05:55 PM, H. Peter Anvin wrote:
> On 07/08/2014 03:05 PM, Alexander Perlis wrote:
>>
>> Question: what's special about the transition from 8203KiB to 8204KiB?
>> Both have CHS=8/64/32 and both involve a fractional end cylinder.
>
> Fractional cylinders with floppy disks is almost certainly a very bad thing.
>
Agreed, but that doesn't appear to