Displaying 20 results from an estimated 10000 matches similar to: "win98 on a second hard drive"
2007 Feb 09
6
syslinux-3.36-pre8 feedback
Tested floppy boot on two machines (one PII 350, one 486DX4)
Floppy boot with syslinux is very very slow, more than 18 mn to boot a linux
kernel from floppy on the 2 machines.
Tested with 3 different disquettes that were know to work, boot is reached
after this very long time.
Noise from floppy head make think floppy wait approximatly one minute
between each read.
No problem with pxe boot with
2009 Apr 14
5
"keeppxe" broken in 3.74 - short-cycle 3.75
It appears that the 3.74 completely broke the "keeppxe" directive -- not
due to the command-line parser, but due to mishandling of the flag later.
I consider this to be severe enough to do a short-cycle 3.75. As a
result, I would like help with:
a) are there any other bugs that snuck through?
b) once I have a 3.75-pre1, I would really appreciate help testing it.
The goal is to have
2011 Jan 30
1
[PATCH] Very minor various typo fixes
Signed-off-by: Gilles Espinasse <g.esp at free.fr>
---
scripts/Makefile.host | 2 +-
usr/klibc/CAVEATS | 2 +-
usr/klibc/README.klibc | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/scripts/Makefile.host b/scripts/Makefile.host
index d8ab687..6a6b949 100644
--- a/scripts/Makefile.host
+++ b/scripts/Makefile.host
@@ -5,7 +5,7 @@
#
# Both C and C++ is
2007 Jan 31
2
syslinux-2.11 boot, syslinux-3.20 fail
We used syslinux package on IPCop with success to install from floppy, from
cdrom, from usb key and pxe.
I upgrade the distribution nine month ago from 2.11 to more recent versions
(3.11, later 3.20).
We add one consistent report of a laptop machine that boot with 2.11 but
fail with 3.11 and 3.20
Symptom is that the machine don't display anything after loading the kernel
and initrd.
with
2007 Feb 12
2
syslinux-3.36 and 3.35 compilation broke /dev/null
I have tested with 3.31 (does not broke /dev/null) and 3.35/3.36 that broke
/dev/null
I verify that /dev/null exist, then compile one of the target available on
top Makefile and /dev/null no more exist.
Example
root:/usr/src/syslinux-3.36# cat /dev/null
root:/usr/src/syslinux-3.36# make .depend
Makefile:274: .depend: No such file or directory
rm -f .depend
for csrc in syslxmod.c gethostip.c ; do
2010 Nov 17
4
Trouble with Superfloppy format
Hello,
are there known issues with some bioses not booting from Superfloppy format?
All I get is the Syslinux (c) line and nothing else happens afterwords.
Everything works fine if a partition is added to the device. Unfortunately
however the target device can not be partitioned.
Any hint?
Sven
--
Why are there so many Unix-haters-handbooks and not even one
Microsoft-Windows-haters
2009 Apr 18
1
modules.pcimap
I have seen it's been planned to change the default file name to be shorted
than module.pcimap.
One way to solve the longer than 8.3 name issue should be to recommend using
mkisofs -J -r
But is not module.pcimap going to disappear?
Should HDT not parse module.alias instead?
An option has been added on module-init-tools to remove generation of all
module.*map files.
Default behavior is still
2011 Mar 29
1
[PATCH] Fix gpxe compilation when gcc is patched to compile by default with -fPIE -Wl, -pie
Signed-off-by: Gilles Espinasse <g.esp at free.fr>
---
gpxe/src/Makefile.housekeeping | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/gpxe/src/Makefile.housekeeping b/gpxe/src/Makefile.housekeeping
index 1f5e115..d49416e 100644
--- a/gpxe/src/Makefile.housekeeping
+++ b/gpxe/src/Makefile.housekeeping
@@ -134,6 +134,16 @@ SP_FLAGS := $(shell $(SP_TEST)
2004 Oct 07
1
memdisk and usb flash devices as primary hard drives.
Has anybody tried to boot a dos disk via memdisk with a usb flash device
as a primary hard drive?
I have a 512MB flash key that when connected becomes my primary hard
drive (new bios) - 0x80. If I boot a MS-DOS 7.10 floppy, one gets the
command prompt and I can see the contents of my flash key as drive C:.
But, if I make a image of the floppy and boot the image via memdisk,
then memdisk
2011 Dec 09
1
[PATCH] Fix compilation when gcc is patched to default to -fPIE -Wl, -pie
gcc hardened by default is seen on gentoo, alt-linux, HLFS, etc.
Patch fix on syslinux this error during gpxe compilation:
[BUILD] bin/cpu.o
arch/i386/core/cpu.c: In function 'get_cpuinfo':
arch/i386/include/bits/cpu.h:79: error: can't find a register in class 'BREG' while reloading 'asm'
arch/i386/include/bits/cpu.h:79: error: can't find a register in class
2007 Feb 11
1
syslinux-3.36 nopie patch
I made a patch that depending of gcc flavor add -no-pie or -nopie on
libutil and dos Makefile.
This fix fatal error like this
sha1hash.c: In function `SHA1Transform':
../include/netinet/in.h:24: error: can't find a register in class `BREG'
while reloading `asm'
../include/netinet/in.h:24: error: can't find a register in class `BREG'
while reloading `asm'
2010 Apr 27
1
include insmod patch
Am I wrong saying that actually anyone that use klibc has to use insmod
patch or build a monolithic kernel?
Could not the insmod patch be include?
That will make everyone life easier on klibc upgrade.
Gilles
2010 Jul 20
2
a list of which kernel versions work with klibc
Is there a list of which kernel versions (are supposed to) work with
(each version of) klibc?
I do recall reading something that said klibc should run under any
version of the kernel, regardless of which version it is compiled
against. Following the new instructions on this list earlier (to use
the KLIBCKERNELSRC= parameter to point to the installed kernel
headers) as well as also making the
2008 Dec 29
1
klibc broken on ppc with linux-2.6.27 and workaround
Compilation was ok with klibc-1.5.10 on linux-2.6.25.
Distrib does not matter as it is inside a chroot a la LSF
With the upgrade to linux-2.6.27 it broke on 1.5.10 (I try too the last
1.5.14) with
make[1]: Entering directory `/usr/src/klibc-1.5.14'
GEN klcc/klibc.config
GEN klcc/klcc
HOSTCC scripts/basic/fixdep
KLIBCCC usr/klibc/__static_init.o
KLIBCCC usr/klibc/vsnprintf.o
2004 Jan 20
4
Bug-report: Booting DOS images from USB
Hi,
I'm doing a small hobby project writing some tools to put DOS boot images
and Linux rescue images on a USB stick.
For this I have partitioned my USB stick in 2 partitions, one 192MB
partition with a VFAT filesystem (for the normal use) and a second
partition with an ext3 filesystem.
My aim was to provide a graphical menu (grub) to access the different
images using memdisk. Since
2008 Jun 08
1
Unable to cat raw /dev/fd0 more than one time
Trying to be not long, on x86 I have 3 floppies images boot, root-1, root-2
Booting from boot image with no problem, I try reading root-1 and root-2
image in raw format.
Reading root-1 and root-2 is made from boot init script, using klibc-1.5.9
or klibc-1.5.10 with debian insmod patch, and a vanilia linux-2.6.24.7
root-1 and 2 images are smaller than 1440 kB and are made the same way with
cd
2009 May 22
5
Booting firmware harddisk image with memdisk fails
Hi,
I once again have a problem with memdisk failing to boot a harddisk image
to update my Thinkpad X200s firmware. I extracted the harddisk image
from the eltorito type 4 ISO using the isobar tool.
Then I added memdisk using this image as initrd to my grub, rebooted and it
boots into PC DOS and then freezes (ctrl-alt-del still works to reboot the
system).
Inside Qemu however it works fine
2003 Aug 12
3
the ugly win98
Hello
For a special task whit win98 i need to boot this sytem in a image of 160mb
(created with virtualpc 5.2 and dskread) with memdisk, but the system shows
me an error whit the master boot record and switchs
in dos compatibility mode. Sorry for my english and i know that is an error
out of linux.
Thanks.
_________________________________________________________________
MSN 8 with e-mail
2008 Mar 13
5
Adding memdisk or similar when booting linux
Hi
Thanx guys for the help on understanding howto read dmi info!
I now have a custom boot menu for install of different linux versions based if they have been installed before (reinstall is ok for users, first install is not), and installquirks like if we detect odd hardware, we add install options to redhat installer so it can install anyhow (for instance hp dc7800 who needs pci=nommconf as
2004 Jan 22
2
Standard file extensions for zipped floppy images
Hi,
I was wondering what's the best standard file extension for zipped DOS
disk images and ramdisks. I've been using the following standard:
.zi kernels, memtest86, memdisk
.igz .img.gz zipped floppy images and ramdisks
I'd rather have a different extension for ramdisks, maybe
.zim zipped floppy images
.zrd zipped ramdisks
Any ideas ?
It would also be nice if syslinux