similar to: EDD error RE: Re: SYSLINUX 2.12-pre7 released

Displaying 20 results from an estimated 4000 matches similar to: "EDD error RE: Re: SYSLINUX 2.12-pre7 released"

2004 Dec 09
1
EDD error RE: Re: SYSLINUX 2.12-pre7 released
(Sorry, Outlook webmail prohibits me from proper replying/quoting) >it has the nice effect that you can load the El Torito >CD-ROM driver. Which seems logical if you boot a kernel (like Linux, or Memdisk with an imagefile), but not when doing a local boot (diskette/harddisk) In other words: boot from cdrom, and if you then load a disk-image, eltorito.sys should load. If not loading a
2004 Dec 09
1
EDD error RE: Re: SYSLINUX 2.12-pre7 released
>The way the El Torito CD-ROM is going to look like to the program, is >that it looks like an additional hard disk which a very high drive >number (typically 9Fh or so); MS-DOS will normally ignore this since it >asks the BIOS how many drives there are and ignores the rest. >Does the error message come from UDMA2.SYS or...? > -hpa yes, it comes from UDMA2.SYS, it does a
2004 Dec 08
1
EDD error RE: Re: SYSLINUX 2.12-pre7 released
I have an application/program which shows 'bios EDD error' when using Isolinux (with either loading an image directly through MEMDISK, or booting to A:), and not when using a bootdisk directly or booting a bootdisk directly which has SYSLINUX on it. configuration: bootable cdrom with Isolinux 2.11/2.12pre9 as bootloader. 1.44MB bootdisk with MSDOS.SYS/IO.SYS and the UDMA2 dos driver,
2004 Dec 10
1
EDD error RE: Re: SYSLINUX 2.12-pre7 released
>No, but you can write a comboot/com32 module to do it if you wish. I meant for syslinux.exe/com (the installer). that BIOS issue is now handled in the driver the author wrote. Unfortunately I can't find another cdrom which boots but lets me access A: to really demonstrate it's the BIOS which is doing this. Every non-emulation cdrom either uses isolinux (even ReactOS bootloader) or
2009 Jul 31
1
[PATCH] [memdisk] Additional EDD Device Parameter Table fields
Some additional fields from the EDD-4 spec. draft for the Device Parameter Table have been added into the structure in setup.c and memdisk.inc. These were added in the hopes of resolving a FreeDOS MEMDISK bug on IBM ThinkPads. --- memdisk/memdisk.inc | 11 +++++++++++ memdisk/setup.c | 10 ++++++++++ 2 files changed, 21 insertions(+), 0 deletions(-) diff --git a/memdisk/memdisk.inc
2004 Aug 17
1
syslinux write intended bootsector to bootsectorfile support?
HPA, is it possible to add a parameter/argument to syslinux.com/syslinux.exe to specify a file? currently it's something like SYSLINUX A: I'd like the following also to be possible: SYSLINUX A: A:\SYSLINUX.BIN It still copies LDLINUX.BIN to A:, but writes the generated bootsector intended for drive A: to a 512byte user-specified file Perhaps to allow both at the same time even SYSLINUX
2004 Nov 30
2
feature request/reminder - alias / bootsector
HPA, a longterm reminder. See below. Can you also make a LABEL ignore other labels if no KERNEL statement is found in between? That way you could define multiple aliasses for an entry. label foo label bar label memtest kernel memtestp foo ignores 'label bar' , 'label memtest' and executes 'kernel memtest' bar ignores 'label memtest' and executes 'kernel
2004 Dec 29
4
SYSLINUX 3.00-pre8: Let's try this release thing again
Okay, spending the time to dot t's and cross i's (or something like that), I think I have something now that can be called 3.00-worthy, so let's call it a release candidate. Changes over the earlier 3.00 prereleases: - -m and -a options now supported by the DOS installer. - PXELINUX now allows IP addresses, FQDNs, and truncated hostnames when specifying an alternate TFTP server
2013 Dec 10
1
Multiple errors after upgrade to 10.0-PRERELEASE
Morning All, I upgraded from 9.2-STABLE to 10.0-PRERELEASE #0 r259144 last night and I am now getting this every 2 seconds in /var/log/messages: Dec 10 07:54:31 Shop kernel: ata1: FAILURE - zero length DMA transfer attempted Dec 10 07:54:31 Shop kernel: ata1: setting up DMA failed cat /var/log/messages | grep ata1: cd0 at ata1 bus 0 scbus3 target 0 lun 0 cd0: <TSSTcorp DVD-ROM TS-H352C
2008 Jan 05
9
SYSLINUX 3.55-pre5 and 3.60-pre7 - RC status
Hi all, I have just pushed out SYSLINUX 3.55-pre5 and 3.60-pre7. I have decided to give them both release candidate status, with the intent of having a simultaneous 3.55 (bug fixes only) and 3.60 (new functionality) release. Please test them out and let me know how they do. -hpa
2008 Jul 17
3
Slow Samba writes over NFS
Hello... Currently in the process of upgrading Samba v2.0.10 to Samba v3.0.x, while conducting some minimal testing, it turns-out that Samba v3.0.x is performing slower than Samba v2.0.10. Set-ups: A. Samba v3.0.x --> Same PC client is accessing the samba share running on Red Hat 4.5 (64bit, HP DL380) which in turn has an NFS mount coming from another SAN attached Red Hat 4.5 (64bit, HP
2006 Mar 17
3
SYSLINUX 3.20-pre7 pushed out, with mboot fixes
Hi all, I have merged Tim's patches to the mboot loader, and have pushed it out as 3.20-pre7. I guess I'm going to actually have to make a 3.20 here soon... -hpa
2019 Nov 27
1
Services will not start automatically
Since upgrading a Linksys WRT3200ACM router from firmware DD-WRT v3.0-r39654 std (04/25/19) to firmware DD-WRT v3.0-r41586 std (11/21/19), the Samba Services will not start automatically. If the power is lost or the router is rebooted, the Samba Server has to be restarted (without making any setting changes) by Applying and Saving the Settings. Are there specific configurations and/or settings
2011 Nov 23
0
[LLVMdev] Follow-up questions after successful upgrade to LLVM 3.0rc4
> 2) I had no problem running the V3.0 regression tests according to the instructions. However, the instructions in the Testing Infrastructure Guide for running the Test Suite presume the existence and use of llvm-gcc, http://llvm.org/docs/TestingGuide.html, both on-line and in the rc4 kits. Now that llvm-gcc is gone for V3.0, it isn't completely obvious how to run the test-suite
2011 Nov 28
2
[LLVMdev] Follow-up questions after successful upgrade to LLVM 3.0rc4
陳韋任 <chenwj at iis.sinica.edu.tw> writes: >> 2) I had no problem running the V3.0 regression tests according to the instructions. However, the instructions in the Testing Infrastructure Guide for running the Test Suite presume the existence and use of llvm-gcc, http://llvm.org/docs/TestingGuide.html, both on-line and in the rc4 kits. Now that llvm-gcc is gone for V3.0, it
2012 Apr 20
1
Upgrading from V3.0 production system to V3.3
Before I undertake this upgrade I thought I would see if anyone has any advice on how to do this on a production system. Maybe someone has already "fought this dragon". Current config Gluster V3.0.0. This has been in production for over 16 months: 2 servers with 8 x 2TB hard drives (bricks) replicated svr1:vol1 <-> srv2:vol1 -> rbrick1 svr1:vol2 <-> srv2:vol2 ->
2011 Nov 29
0
[LLVMdev] Follow-up questions after successful upgrade to LLVM 3.0rc4
On Nov 28, 2011, at 3:44 PM, David A. Greene wrote: > 陳韋任 <chenwj at iis.sinica.edu.tw> writes: > >>> 2) I had no problem running the V3.0 regression tests according to the instructions. However, the instructions in the Testing Infrastructure Guide for running the Test Suite presume the existence and use of llvm-gcc, http://llvm.org/docs/TestingGuide.html, both on-line
2013 Jan 13
0
[LLVMdev] Using C++'11 language features in LLVM itself
Hello all, Using the Apache Wiki [1] I summed up what can be used simultaneously by gcc, MSVC and clang. I mostly considered only the latest versions of the proposals where there were several, where not there is a link to a note at the bottom. Furthermore I did not scourge through 3 bug databases and I implicitly trusted the wiki page. I drew up a list of profiles, listing the base
2008 Nov 21
3
hda: no DRQ after issuing WRITE
I upgraded my Centos 4.7 server last night. Switched from a cheaper 50$ asus motherboard to a Supermicro motherboard. I also, using dd, copied entire 500g SATA seagate drive to new 500g SATA seagate drive so as to have two copies in case something went wrong. Anyway, now I keep getting this error: Nov 21 06:08:33 server kernel: hda: status timeout: status=0xd0 { Busy } Nov 21 06:08:33 server
2011 Nov 22
4
[LLVMdev] Follow-up questions after successful upgrade to LLVM 3.0rc4
We were successful in upgrading our JIT project to LLVM 3.0rc4 last week, after initially struggling with the various usage and IR changes from V2.9. But we have some follow-up questions: 1) In spite of building and running our tests cleanly with DEBUG+ASSERTS and RELEASE builds, we consistently see a crash when we use a DEBUG build without ASSERTs. The crash appears whenever we use the