similar to: pxelinux efi64 boot woes on hyper-v gen 2

On Mon, Nov 24, 2014 at 3:24 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote: > http://www.niallbrady.com/2014/06/11/when-uefi-network-booting-on-a-hyperv-gen-2-vm-you-might-get-pxe-e99-unexpected-network-error/ > > P.S. It's not this and I'm getting a PXE-E99 tftp failure "Unexepected Network Error", so I'll guess I'll need to investigate what kind of

http://www.niallbrady.com/2014/06/11/when-uefi-network-booting-on-a-hyperv-gen-2-vm-you-might-get-pxe-e99-unexpected-network-error/ P.S. It's not this and I'm getting a PXE-E99 tftp failure "Unexepected Network Error", so I'll guess I'll need to investigate what kind of TFTP server makes hyper-v happy. Virtualbox, VmWare seem to have the same EFI boot code & output

On Thu, Nov 27, 2014 at 8:59 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote: > Gene, > > As it happened I started working on this again just as you mailed me. I saw it in IRC. > It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no

Gene, As it happened I started working on this again just as you mailed me. It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no joy. The bootfile size shows up as zero because that relates to "option boot-size" in dhcp and doesn't seem to

Gene, I found a document from IBM that explains why it didn't like Vendor-Class-Identifier option I was using "PXEClient" was causing EFI boot rooms to dummy spit, that's very useful, that combined with RTFMing the PXE specs 3.0-3.2 might solve my problem if I keep at it. http://www-01.ibm.com/support/docview.wss?uid=swg21247032 Even the PXELinux docs suggest encapsulating

I have an interest in booting Windows PE from PXELinux, and it seems that wimboot from ipxe project is the solution. http://ipxe.org/wimboot MENU LABEL Windows 8.1 Enterprise PE Rescue (wimboot) com32 linux.c32 /wimboot APPEND initrdfile=/windows/win81/bootmgr,/windows/win81/boot/bcd,/windows/win81/boot/boot.sdi,/windows/win81/sources/boot.wim The initrdfile= is supported in Syslinux from

Adding an option for initrdfile= boot argument to be ignored by wimboot worked just fine. They can add this patch, which is probably most sane, or syslinux could add the INITRDFILE configuration option instead of having to append the option for linux.c32 wimboot-2.4.0/src/cmdline.c @ Line ~107 } else if ( key == cmdline ) { /* Ignore unknown initial

> -----Original Message----- > From: Luke Ledgerd > Sent: Monday, November 24, 2014 1:10 PM > To: 'syslinux at zytor.com' > Subject: Windows PE booting without chainloading ipxe > > I have an interest in booting Windows PE from PXELinux, and it seems that wimboot from ipxe project is the solution. > http://ipxe.org/wimboot > > MENU LABEL Windows 8.1

I hope this message finds you well and thriving in your endeavors. As a fellow Vietnamese student currently pursuing education in the United States, I can't help but feel a sense of pride and excitement about the prospect of inviting you to experience the beauty and charm of my homeland, Vietnam. Vietnam is a land of captivating landscapes, rich history, and warm hospitality. From the

> Date: Thu, 25 Dec 2014 07:07:52 +0000 > From: Luke Ledgerd <luke.ledgerd at niteco.se> > To: "syslinux at zytor.com" <syslinux at zytor.com> > Subject: [syslinux] Chain-loading from WDS to PXELinux on a different > tftp server > Message-ID: <17ba7ad419d54b6cab685c2cedc3de95 at NI-MAILEX.niteco.se> > Content-Type: text/plain;

On Dec 25, 2014 2:11 AM, "Luke Ledgerd" <luke.ledgerd at niteco.se> wrote: > > Hey guys, > > We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off

> Hello James, > > > ----- Forwarded message from Geert Stappers via Syslinux > <syslinux at zytor.com> ----- > > Date: Thu, 8 Oct 2015 01:24:26 +0200 > From: Geert Stappers via Syslinux <syslinux at zytor.com> > To: "Clements, James" <James.Clements at affiliate.oliverwyman.com> > Cc: "syslinux at zytor.com" <syslinux at

On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux wrote: > > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux wrote: > > is for BIOS, not for EFI. So that suggestion can be scraped. > > > > Which makes > > * text which is on the screen of the netbooting (virtual) machine > > * when/why was the network capture stopped

> > > On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux > > wrote: > > > > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux > > wrote: > > > > is for BIOS, not for EFI. So that suggestion can be scraped. > > > > > > > > Which makes > > > > * text which is on the screen of

> On Fri, Oct 09, 2015 at 10:55:11AM -0500, Clements, James wrote: > > > On Fri, Oct 09, 2015 at 09:45:23AM -0500, Clements, James wrote: > > > > From: Geert Stappers [mailto:stappers at stappers.nl] > > > > Sent: 09 October 2015 15:39 > > > > > On Fri, Oct 09, 2015 at 09:14:55AM -0500, Clements, James wrote: > > > > > > From:

> On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux > wrote: > > On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux > wrote: > > > On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote: > > > > On Wed, Oct 07, 2015 Geert Stappers wrote > > > > > 13:36:47.974245 IP 192.168.205.50.1939 >

Hi, Please advice how to download utility for 'tar', 'cp' supporting RHAS3.0 RPMs listed in note 237997.1 are used for RHAS2.1 * Patch 2883583: fileutils-4.1-4.2.i386.rpm * Patch 2913284: tar-1.13.25-9.i386.rpm Best regards, Huy. == Nguyen Quang Huy Sr. Technical Sales Consultant Oracle Vietnam 53 Quang Trung St, Hanoi Email: quang.huy.nguyen@oracle.com Phone: +84 4 943 2595

> On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux > wrote: > > > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux > wrote: > > > is for BIOS, not for EFI. So that suggestion can be scraped. > > > > > > Which makes > > > * text which is on the screen of the netbooting (virtual) machine > > >

Dear all Wine-users, I'm last-year student of Hanoi University of Technology in Vietnam. My graduate thesis has important part relate to Wine and installation of Windows applications in Linux via Wine. I have completed all part of my thesis except Wine related part. I installed Office XP with Wine May 2005 and it always failed. Before installed Office, I had installed Dcom98.exe ,

On Wed, Oct 07, 2015 at 05:58:51PM -0500, Clements, James wrote: > James Clement > > Geert Stappers > > > On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James wrote: > > > > The screen displays the following: > > > > > > > > PXE Network Boot using IPv4 > > > > .... > > > > Station IP address is 192.168.205.50