similar to: Failed to boot from one particular system

Hi all I have built a preliminary debian package for dev86, required to build xen with vmx support. you can get my packages here: http://debian.nsp.co.nz/dev86. I have also trivially patched the rules for xen 3 to build the vmxloader and include it in the resulting packages, my builds/sources for these packages are here: http://debian.nsp.co.nz/xen3/. I''m working with debian-mentors

Please, I would like to know how to generate a truncated multivariate normal distribution k - dimensional, X ~ NT(mu, Sigma), where the elements of X to be non-negative (except the first), and the first dimension is strictly larger than zero. Example: X ~ NT_2(mu, Sigma), where mu=c(0.5, 0.5) and Sigma=c([120, 191], [191,154]), with X_1>0 and X_2>=0 Could anybody help

Hi! Facing a strange problem about not being able to access the floppy drive after booting from a rescue-floppy with 2.2.x kernel on an asus p4te mainboard, i searched the net and found a bug in the bootsector of the 2.2.x kernels. Before control is redirected to the kernel, the floppy drive is shut down in a way, that freezes the FD-Controller on recent mainboards (like the ASUS P4T-E). The

where can I get the lastest nasm to compile syslinux 1.75. http://www.cryogen.com/Nasm is not accessible and the latest on ftp://ftp.kernel.org/pub/software/devel/nasm/source/ is nasm-0.98.tar.bz2 Thanks, Jeff [ jchua at fedex.com ]

>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

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

On Tue, Jan 21, 2014 at 2:41 PM, mike setzer <qualityana at sbcglobal.net> wrote: > hello Gene, > > good to get your message > > I have not seen a link to reply to a particular thread, > so I am replying to you right now > hopefully the thread can be made to look right, also I double posted since my connection was lost > right during the first posting. Sorry, I

Mr Anvin, is there a specific loading address used with the Syslinux bootsector (to load ldlinux.sys)? like msdos 0x70, freedos 0x60 we're trying to have a SYS program that can create bootsector for other OS's than FreeDOS only. not much luck though :( this way I'm trying to avoid the use of syslinux.exe/com (need the diskspace that it would save by not including this program) I

(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > Hi there, > I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... > what is the problem can anybody tell me.. > please read Syslinux and Memdisk

Apparently there's a semi-new feature in SYSLINUX that will allow you to, from what I've heard, boot DOS. I've got a portable USB flash drive and I've managed to make it multi-boot with disk images, but that takes quite a bit of memory. I think bootsector booting is the best way to go, but I have no idea how to do it. Tell me if I've got this right: So, I want to get a flash

On 07/26/2013 01:36 PM, Raphael S Carvalho wrote: > > Bootsector is installed into the 0-512 range, whereas 2 copies of ADV > into (65536 - 2 * ADV_SIZE). > Then basically ldlinux.sys must fit between the bootsector and two > copies of ADV whose size may vary. > > The range 0-64k is laid out something like this, right?! > [0](bootsector)[512](ldlinux.sys)[65536 - 2 *

> Hello, > > We are experiencing a strange behaviour on an embedded system (i386 PC board). > > The structure of our disk is the following one : > - A 2GB fat16 partition with DOS and syslinux > - A 100GB Ext4 partition with Extlinux an several linux images to boot on ram > - A swap partition > > The system boot on syslinux to choose among Dos and Linux boot using

Hello, We are experiencing a strange behaviour on an embedded system (i386 PC board). The structure of our disk is the following one : - A 2GB fat16 partition with DOS and syslinux - A 100GB Ext4 partition with Extlinux an several linux images to boot on ram - A swap partition The system boot on syslinux to choose among Dos and Linux boot using chain. When Linux is chosen, syslinux chains to

On Tue, Oct 20, 2015 at 1:08 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> Hello, >> >> We are experiencing a strange behaviour on an embedded system (i386 PC board). >> >> The structure of our disk is the following one : >> - A 2GB fat16 partition with DOS and syslinux >> - A 100GB Ext4 partition with Extlinux an several linux images

While playing with some less than usual configurations, I've got bitten few times by geometry settings in case of, usually, microsoft[ish] systems. First two examples, then the improvement idea. Example #1 My usb stick has zip-compatible geometry, which should work fine both in hdd and zip modes. It usually does, at least as far as syslinux and normal software is considered - excluding

Was messing with a polycom 501 and changed the IP from dhcp to static. Working with a user remotely. Now, the user says the phone does not show anything on the LCD and does not respond to any buttons. When rebooting, there is text shown as it proceeds. ?? Is there a way to reset this to a default? Does not respond to ping on the address we set. joe a.

On Fri, Jul 26, 2013 at 4:58 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/26/2013 08:10 AM, Matt Fleming wrote: > > On Wed, 24 Jul, at 08:05:16AM, Raphael S.Carvalho wrote: > >> Check if ldlinux.sys is larger than 64k at build time. > >> > >> Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> > >> --- > >>

On Fri, Jul 26, 2013 at 5:42 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/26/2013 01:36 PM, Raphael S Carvalho wrote: > > > > Bootsector is installed into the 0-512 range, whereas 2 copies of ADV > > into (65536 - 2 * ADV_SIZE). > > Then basically ldlinux.sys must fit between the bootsector and two > > copies of ADV whose size may vary. > >

Hello Peter, The attached patch contains three small (although 2 of them are fundamental :) fixes for pxelinux 1. Alignment error when more than one initramfs are loaded using initrd - the alignment of the last disk is discarded in calculations but is ALWAYS present when the loading procedure is called. As a result - the second image (cpio) is not recognized. 2. On some platforms

Peter, does this look OK to you? Raphael, I can't work out why ADV_SIZE is a constant in this file? On Sat, 31 Aug, at 05:01:20PM, Raphael S.Carvalho wrote: > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. > ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. > Thus, the size of ldlinux.sys (limit) can be at most: