Displaying 20 results from an estimated 10000 matches similar to: "NEWS: change BIOS to floppy?"
2008 Aug 01
2
SYSLINUX 3.71 released
Hello everyone,
I have just released SYSLINUX 3.71. This is pretty much a bug fix and
hardware support release. The major new *features* are the "initrd"
command (syntactic sugar, but it supposedly makes it easier for some
tools), the "hide" option to chain.c32, and the ifcpu64.c32 module.
As always, special thanks to rPath, Inc., my employer, for the countless
hours I
2006 Oct 30
2
SYSLINUX 3.32-pre4 released: MEMDISK floppy drive workaround
Hi all,
I have pushed out a SYSLINUX 3.32-pre4. This version attempts to work
around the "missing floppy drive" issue.
If you have systems on which MEMDISK doesn't work without a floppy
drive, I would appreciate it if you would test this out.
-hpa
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
2003 Jul 20
1
Memdisk problems again (2.05)......
Hi... I'm Jaspreet.
I've been having the memdisk memory overlapping problems since 2.04
Its always seen in the compressed images whereas the uncompressed images
works just fine !!!
It just stops at the error "Ran out of input data".. Even the memdisk 2.05
dint solve my problem !!! maybe there r still some bugs remaining. !!
My motherboard is Intel 845GEBV2 and i've got
2003 Jul 16
0
SYSLINUX 2.05 released
Greetings,
I have released SYSLINUX 2.05. It is almost identical to 2.05-pre4.
I'm about to leave for a trip, so if there are any issues please let me
know, but don't expect a response any time soon.
-hpa
2.05 is mostly a bug fix/maintenance release.
Changes in 2.05:
* PXELINUX: Add a default query based on the hardware address
of the boot device. This is in lower
2003 Aug 23
1
Memdisk Problem persists !!!
Hi,,
I wud just like to inform that the previous issue of memdisk not booting
compressed images still persists !! The release 2.05 that was supposed to
fix this issue dint yet solve the problem !!
Please, let me know if more info on the problem is required !!
Bye,
Jassi
>From: syslinux-request at zytor.com
>Reply-To: syslinux at zytor.com
>To: syslinux at zytor.com
>Subject:
2003 Aug 23
3
SYSLINUX 2.06 released
I have released SYSLINUX 2.06; it's basically identical to 2.06-pre4.
I'm doing this now because the bug fixes are so major and because I am
not sure I'll be around next week.
-hpa
2.06 is a bug fix release.
Changes in 2.06:
* ALL: Fix problem that would occationally cause a
boot failure, depending on the length of the kernel.
* ISOLINUX: Fix problem
2006 Nov 21
1
memdisk requires floppy drive to boot
Hello!
Below is an excerpt from the thread in October. I have the same problem,
but my laptop (which is a Brand new HP Compaq NC6230) does not have options
in the BIOS to enable or disable floppy support. It just doesn't have one.
I assume it leaves it enabled for USB Floppy support, but does not come with
the drive.
My ISOLinux setup is a UBCD. I tried to make my own, but the lack of
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
2005 May 29
1
memdisk and floppy images on 4801
Im trying to boot memtest86 via pxelinux, memdisk,
I found this advice on http://forum.x86-secret.com/viewtopic.php?t=2906
folks are making the image match a floppy size by one of the following:
dd if=memtest86+-1.xx.bin of=memtest.img bs=360k count=1 conv=sync
or
dd bs=360k count=1 conv=sync if=memtest86+-1.xx.bin|gzip > memtest.gz
I did the former, it did suppress the warning/errors I saw
2007 Jun 08
2
syslinux-3.36 Physical Floppy Disk Access Problem
Hello,
I am using the pxelinux.0 and memdisk files from distribution syslinux-3.36.
I am no longer able to access the real floppy disk drive B: instead I just
get a mirrored copy of the emulated floppy disk A:
The default config file is as follows
label 1
kernel memdisk
append initrd=kd202.img
I was previously using the sysliunx-3.20 distribution which gave me access
to the real floppy
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
>>
2010 Oct 23
0
SYSLINUX 4.03 released
It was actually released yesterday, but due to some technical
difficulties I didn't get a chance to announce it properly:
Syslinux 4.03 is primarily a bug fix release.
Changes in 4.03:
* Don't hang if no configuration file is found.
* Better support for booting from MBRs which don't pass
handover information.
* EXTLINUX: Try to be smarter about
2003 Sep 12
3
Updating BIOS with pxe syslinux memdisk & DOS problems
Hi all,
We are hoping to update our BIOSes remotely with pxelinux and memdisk (it is
for a 600 node Beowulf cluster with no floppy access). The DOS floppy loads
and starts, however somehow the flash utility 'phlash.exe' or 'phlash16.exe'
are both unable to load the provided rom image and just stop doing nothing.
It looks like it can't access the rom image somehow, which is
2006 Sep 26
1
SYSLINUX 3.31 released
I have just released SYSLINUX 3.31. It is functionally identical to
SYSLINUX 3.31-pre4.
Changes in 3.31:
* The simple menu system (menu.c32 and vesamenu.c32) now
support loading more than one configuration file at a time,
using MENU INCLUDE or by specifying multiple filenames.
* The MENU COLOR statement can now control the shadowing mode.
Changes in
2008 Jul 09
5
boot disk failure
Hello,
i've got a problem with boot pxe on pc, all my pc works fine except in a room
where all the same pc doesnt works :
my configuration (dhcp tftp etc...) works fine also
here is a part of my tftpboot directory
ghost/
memdisk
menu.c32
pxelinux.0
pxelinux.cfg/
./ghost:
ghost288.IMA
ghost_geii_101.IMA
ghost_MM.IMA
ghost_MM.IMA.old
./pxelinux.cfg:
default
here is a part of my default
2009 Nov 20
2
MEMDISK El Torito Emulation
A very special thanks to H. Peter for finding the time to [at least
partially, if not wholly] scrutinize and merge the El Torito emulation
code for MEMDISK!
I'd like to ask that those who've previously used the stale MEMDISK-ISO
switch to this latest[1] MEMDISK proper and report any failures.
Gert, I believe this version addresses the PloP .ISO trouble you
reported. Could you
2009 Apr 16
0
SYSLINUX 3.75 released
3.75 is a bug fix release for 3.74.
Changes in 3.75:
* PXELINUX: fix the "keeppxe" option, which was broken in
3.74.
* MEMDISK: correct the extraction of geometry information from
the MBR of a hard disk image, again broken in 3.74.
* extlinux(1) man page from Brian Pellin.
* Simple menu: MENU SAVE is now controllable on a menu-by-menu
2018 Jun 25
0
Memdisk and big floppy images
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
> would just inject your ROM and EXE (and possibly adjust autoexec.bat to
> autostart/apply the FW update).
2008 Jul 31
1
PXE Booting floppy image
Anyone know the correct syntax for specifying a floppy image in the /tftpboot/pxelinux.cfg/default file?
I am trying to use:
label Dos Bootdisk
MENU LABEL Dos bootdisk
FDIMAGE discimage.img
But when I select it the menu, I get a message saying "Automatic boot in 30 seconds" and nothing happens.
I would use:
label Dos Bootdisk 2
MENU LABEL Dos bootdisk 2