similar to: [PATCH] [memdisk] Additional EDD DPT 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

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

Hello, I'm trying to get to grips with the c interface of llvm intending to eventually develop a front end for Purebasic Though I've hit the wall already writing an iterative Fibonacci function. While I think the module dump looks ok it doesn't work for any input > 2 the function returns 2, the loop only executes once Hopefully someone can see what the problem is from the

Ok, so I've been chugging away at AVX and added some new features in TableGen to facilitate writing generic patterns. Here's an example: //===----------------------------------------------------------------------===// // Dummy defs for writing generic patterns //===----------------------------------------------------------------------===// def SRCREGCLASS; def DSTREGCLASS; def MEMCLASS;

Before wasting a lot of time going at this in the wrong list, I would like to confirm whether my thinking is on or off base with respect to source and destination ports. Samba is being blocked by fw2loc even though I have accept rules set up. I believe I can explain why, but I could be wrong. I think that for some reason, samba is sourcing stuff on the commonly used port 137, but trying to send

EDD (https://en.wikipedia.org/wiki/Enhanced_Disk_Drive) is a BIOS INT 13h subcall for communicating the extended size of the boot disk over 8GB to the OS. Since libguestfs doesn't use a boot disk, and the appliance disk is limited to 4GB, and we use virtio-scsi, this is all useless. EDD is also broken currently on RHEL 7.3, see: https://bugzilla.redhat.com/show_bug.cgi?id=1404287 Also the

​Hi all, I am using llvmlite for pyvex and I want the output of my code (which is written based on llvmlite) to be like pyvex. In pyvex, (https://github.com/angr/pyvex). Considering pyvex, I tried to implement the following statements in pyvex to llvmlite: for stmt in irsb.statements: if isinstance(stmt, pyvex.IRStmt.Store): print "ST%s(%s) = %s" % (self.endness[-2:].lower(),

Hi all! Running Centos-6.latest on an AMD six-core Vishera processor. It's been running for a year on that hardware. today I swapped out the video card (from Nvidia 9800GT to Nvidia 460 GTX) hoping to get a little more horsepower, and the ability to run the Folding At Home GPUclient. I know that's an old card, it's a hand-me-down from my son who just replaced it with a new 970 GTX

Two additions to MEMDISK to support OS drivers. The "safe hook" structure ("Safe Master Boot Record INT 13h Hook Routines") is a means for an OS driver to follow a chain of INT 13h hooks, examining the hooks'' vendors and assuming responsibility for hook functionality along the way. For MEMDISK, we guarantee an additional field which holds the physical address for the

I *think* I have found and fixed the Thinkpad MEMDISK problem. The problem with MS-DOS I understand... not so when it comes to an apparently unrelated FreeDOS problem, and as such I really don't know *why* the hack I did works, nor if it will *stay* fixed, but at least it seems to boot on my T61 (at least until it crashes due to another error...) -hpa -- H. Peter Anvin, Intel Open Source

I ran into this when I was reviewing what was outstanding to get NetWare to run fully virtualized. The BIOS emulator code has the segment and offset backward in the returned buffer for the int 13h, fn 48h BIOS call. BTW: This is fixed in current Bochs emulator upstream code. Signed-off-by: Bruce Rogers <brogers@novell.com> diff -r 59b8768d0d0d tools/firmware/rombios/rombios.c ---

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,

>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

>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

Op 2014-02-20 om 13:23 schreef Andy Alex: > DL register is not set to drive number when detecting EDD for drive, so detection may fail. > > Signed-off-by: Andy Alex<andy at r-tt.com> > --- > diff -uprN syslinux-6.02.orig/core/fs/diskio_bios.c syslinux-6.02/core/fs/diskio_bios.c > --- syslinux-6.02.orig/core/fs/diskio_bios.c 2013-10-13 21:59:03.000000000 +0400 > +++

On 05/19/2014 11:20 AM, Anatol Pomozov wrote: > Hi > > I have a computer with BIOS and Linux Arch installed. > > Starting from a recent syslinux update (6.02->6.03pre9) I am not able > to use syslinux anymore. I try to boot my computer and the only thing > I see is "EDD Load error - Boot error" message. When I install 6.02 > back the system is completely

Op 2014-05-19 om 11:20 schreef Anatol Pomozov: > Hi > > I have a computer with BIOS and Linux Arch installed. > > Starting from a recent syslinux update (6.02->6.03pre9) I am not able > to use syslinux anymore. I try to boot my computer and the only thing > I see is "EDD Load error - Boot error" message. When I install 6.02 > back the system is completely

On May 19, 2014 5:17 PM, "Anatol Pomozov" <anatol.pomozov at gmail.com> wrote: > Besides syslinux itself other things has changed e.g. gcc (but I > really hope my problem not because of compiler). This alone can be the trigger.This might be a starting point: build 6.02 with your current toolchain. --Gene

On May 20, 2014 12:33 AM, "Anatol Pomozov" <anatol.pomozov at gmail.com> wrote: > > Hi > > On Mon, May 19, 2014 at 6:58 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > > On May 19, 2014 5:17 PM, "Anatol Pomozov" <anatol.pomozov at gmail.com> wrote: > > > >> Besides syslinux itself other things has changed e.g. gcc (but I >

On 05/20/2014 12:24 PM, Paulo Alcantara wrote: > > Actually, there is *no* 64KiB limit on btrfs. Look at btrfs-progs > (ctree.h:830): > > " > /* > * We don't want to overwrite 1M at the beginning of device, even though > * there is our 1st superblock at 64k. Some possible reasons: > * - the first 64k blank is useful for some boot loader/manager > * -