15 replies to this topic

[69jakk]

Dear friends...

I already tried with success booting Windows 7 PE with syslinux 5.0 pre 13 and gpxe but now I'm getting the following error:

 

Loading wimboot...ok

Loading bootmgr@bootmgr...ok

Loading bcd@BCD...Out of memory: can't allocate memory for socket structure

Does anyone have an idea of what could be the problem?

By the way...I'm using apache on XP as http server.

Best regards.

Edited by 69jakk, 02 January 2013 - 09:44 AM.

[Sha0]

wimboot was designed for use with iPXE (and the most recent Syslinux' linux.c32 program), not gPXE.

 

As far as ideas go, this certainly looks like an out-of-memory condition.  I've seen this caused by someone entering gPXE or iPXE when it's been flashed to ROM and the user uses Control-B during POST to manually launch the CLI, instead of letting it launch "naturally" as part of the BIOS boot order.  I've also seen OOM because of too much chainloading, such as iPXE -> iPXE -> iPXE -> Oh now I finally interrupt it with Control-B.

 

But if you're using gPXE, wimboot is not expected to work.  But you haven't shared how you're booting it.

[69jakk]

Well...I forgot the lastime I booted wimboot it was with ipxe instead of gpxe...

I'm booting with the following embedded script into a ROM-O-MATIC iso image:

dhcp net0
set 209:string pxelinux.cfg/default
set 210:string http://69ddwrt.no-ip.org/
chain ${210:string}pxelinux.0

And pxelinux parses the following defult menu:

 

DEFAULT   vesamenu.c32
PROMPT     0
NOESCAPE         0
ALLOWOPTIONS 0
MENU BACKGROUND PCFixer.jpg
# Timeout in units of 1/10 s
TIMEOUT 300
#MENU WIDTH 40
#MENU MARGIN 0
MENU ROWS 16
MENU TIMEOUTROW 14
#MENU HSHIFT 5
#MENU VSHIFT 2
MENU COLOR BORDER 30;44    #00000000 #00000000 none
MENU COLOR TABMSG 1;36;44  #00000000 #00000000 none
MENU COLOR TITLE  1;40     #FF00BFFF #00000000 std
MENU COLOR SEL    5;34;44  #FF000000 #7F00FFFF
MENU TITLE Utilities
#MENU WIDTH 80
#MENU MARGIN 18

MENU SEPARATOR

MENU SEPARATOR

MENU SEPARATOR

MENU SEPARATOR

MENU SEPARATOR

label hd00
MENU LABEL Boot Hard Disk (hd0,0)
            localboot 0x80
            append SLX=0x80

MENU SEPARATOR

label Puppy_Slacko
MENU LABEL  Slacko 5.4
            kernel /images/slacko/VMLINUZ PDEV1=rootfs LOGLEVEL=7
            append root=http://69ddwrt.no-ip.../images/slacko/ boot=slacko netboot=nfs initrd=http://69ddwrt.no-ip...lacko/INITRD.GZ

MENU SEPARATOR

label Puppy_Lupu
MENU LABEL  Lupu 5.4
            kernel /images/lupu/vmlinuz loglevel=7
            append root=http://69ddwrt.no-ip.org/images/lupu/ boot=lupu netboot=nfs initrd=http://69ddwrt.no-ip.../lupu/initrd.gz

MENU SEPARATOR

label Parted_Magic
MENU LABEL Parted Magic
            linux /pmagic_pxe/pmagic/bzImage
            initrd /images/pmagic_pxe/pmagic/initrd.img
        append root=http://69ddwrt.no-ip...gic_pxe/pmagic/ edd=off load_ramdisk=1 prompt_ramdisk=0 rw vga=normal loglevel=9 max_loop=256

MENU SEPARATOR

label HBCD
MENU LABEL Hiren's BootCD 15.0
            kernel memdisk
            initrd /images/hirens/hirens.iso
            append iso

MENU SEPARATOR

label Win7PE
MENU LABEL Windows 7 PE
            com32 linux.c32
            append http://69ddwrt.no-ip.org/wimboot initrdfile=bootmgr@bootmgr,bcd@BCD,boot.sdi@boot.sdi,boot.wim@boot.wim

 
All entries work but my problem is the following:

I have no idea how to make or parse the above menu with ipxe firmware...Is there any pxelinux.0 compatible with ipxe?

I mean...I could boot wimboot with ipxe and the syslinux 5.0 pre 13 but the Windows 7 PE menu entry doesn't work because I'm parsing pxelinux.0 from gpxe so...Could I chain or parse the pxelinux.0 with ipxe firmware? Could I boot that entry in this way?

Thanks for your sharing Sha0.

Greets!

 

[Sha0]

All entries work but my problem is the following:

I have no idea how to make or parse the above menu with ipxe firmware...Is there any pxelinux.0 compatible with ipxe?

 

I mean...I could boot wimboot with ipxe and the syslinux 5.0 pre 13 but the Windows 7 PE menu entry doesn't work because I'm parsing pxelinux.0 from gpxe so...Could I chain or parse the pxelinux.0 with ipxe firmware? Could I boot that entry in this way?

All modern pxelinux.0 are compatible with iPXE.

• anything -> gPXE -> PXELINUX 5.00 -> vesamenu.c32 -> linux.c32 -> wimboot: This will work.
• anything -> iPXE -> wimboot: This will work.
• anything -> iPXE -> PXELINUX 5.00 -> vesamenu.c32 -> linux.c32 -> wimboot: This will work.
• BIOS -> PXE -> PXELINUX 5.00 -> vesamenu.c32 -> linux.c32 -> wimboot: This will work.
• anything -> any kind of Syslinux 5.00 -> vesamenu.c32 -> linux.c32 -> wimboot: This will work.
• anything -> gPXE -> wimboot: This will not work.

It only matters what the last thing before wimboot is.  Syslinux 5.00's linux.c32 and iPXE both work.  gPXE won't.

[69jakk]

Well...but...I'm using the first one...Why doen't it work?

[Sha0]

Well...but...I'm using the first one...Why doen't it work?

The first one includes "anything."  Can you detail what "anything" includes?

[69jakk]

The first one includes "anything."  Can you detail what "anything" includes?

 

You mean the media or the PC?

The media is an iso image got from ROM-O-MATIC and burnt with Nero and the PC is an old HP Desktop Computer with 2GB of RAM.

Sorry but I'm not sure what "anything" means...

[Sha0]

You mean the media or the PC?

The media is an iso image got from ROM-O-MATIC and burnt with Nero and the PC is an old HP Desktop Computer with 2GB of RAM.

Sorry but I'm not sure what "anything" means...

Yes, that answers my question; thanks.  That means that "anything" is: BIOS -> El Torito boot (optical disc boot) -> ISOLINUX.  So you have: BIOS -> El Torito boot -> ISOLINUX -> gPXE (gpxe.lkrn) -> PXELINUX 5.00 (pxelinux.0) -> vesamenu.c32 -> linux.c32 -> wimboot, right?  Did you include any scripts in the ROM-O-Matic build?

[69jakk]

Did you include any scripts in the ROM-O-Matic build?

 

Yes...this is the script:

dhcp net0
set 209:string pxelinux.cfg/default
set 210:string http://69ddwrt.no-ip.org/
chain ${210:string}pxelinux.0

By the way...I'm having a look at the access log in Apache and the boot.sdi file is never asked on the server...it just stops after bootmgr petition.

[69jakk]

Yes...this is the script:

dhcp net0
set 209:string pxelinux.cfg/default
set 210:string http://69ddwrt.no-ip.org/
chain ${210:string}pxelinux.0

By the way...I'm having a look at the access log in Apache and the boot.sdi file is never asked on the server...it just stops after bootmgr petition.

 

Strange thing on log...look at this Sha0

84.125.130.216 - - [02/Jan/2013:19:50:41 +0100] "GET /linux.c32 HTTP/1.0" 200 5991
84.125.130.216 - - [02/Jan/2013:19:50:41 +0100] "GET /wimboot HTTP/1.0" 200 11708
84.125.130.216 - - [02/Jan/2013:19:50:41 +0100] "GET /bootmgr HTTP/1.0" 200 383562
127.0.0.1 - - [02/Jan/2013:19:51:09 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
127.0.0.1 - - [02/Jan/2013:19:51:39 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
66.249.74.75 - - [02/Jan/2013:19:51:39 +0100] "GET /images/XP/I386/ASCTRLS.OC_ HTTP/1.1" 200 49438
66.249.74.75 - - [02/Jan/2013:19:51:54 +0100] "GET /images/XP/I386/MQUTIL.DL_ HTTP/1.1" 200 83955
127.0.0.1 - - [02/Jan/2013:19:52:09 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
127.0.0.1 - - [02/Jan/2013:19:52:39 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
127.0.0.1 - - [02/Jan/2013:19:53:09 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
127.0.0.1 - - [02/Jan/2013:19:53:39 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
127.0.0.1 - - [02/Jan/2013:19:54:09 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
66.249.74.75 - - [02/Jan/2013:19:54:25 +0100] "GET /images/XP/I386/ASCENT.JP_ HTTP/1.1" 200 61979

After bcd error my computer serves some files from the XP installation folder...and some of them to an external ip from United States...

Could am I suffering an attack from a Hacker and my bootmgr is corrupted?

Edited by 69jakk, 02 January 2013 - 07:03 PM.

[69jakk]

I could boot with ipxe and the boot.ipxe script with wimboot so the files are not corrupt.

The problem must be or syslinux or gpxe....

Strange...I have tried to boot syslinux 5.0 from ipxe but it stacks after the ipxe firmware welcome phrase...
 

Waiting for some light...

Greets!

[Sha0]

I could boot with ipxe and the boot.ipxe script with wimboot so the files are not corrupt.

The problem must be or syslinux or gpxe....

Strange...I have tried to boot syslinux 5.0 from ipxe but it stacks after the ipxe firmware welcome phrase...

Sorry!  I didn't pay close enough attention to realize that you were not actually getting to boot wimboot.  Above:

It only matters what the last thing before wimboot is.

But this fact is irrelevant, because you are not getting as far as booting wimboot.

 

At this point, I am thinking that it is a gPXE bug, since your PXELINUX is using HTTP, which is provided by the gPXE that came before PXELINUX.

 

If iPXE -> PXELINUX 5.00 is not working, that is a problem!  What is the error message, please?  I don't understand "but it stacks after the ipxe firmware welcome phrase..."

[69jakk]

If iPXE -> PXELINUX 5.00 is not working, that is a problem!  What is the error message, please?  I don't understand "but it stacks after the ipxe firmware welcome phrase..."

 

Theres is no error message...sorry for my english...I meant it just jams or stops in this sentence:

PXELINUX 5.00 5.00-pre13 Copyright © 1994-2012 H. Peter Anvin et al

After that sentence it does nothing...but the Apache server delivers some files...it's very weird...this is the log

84.122.97.221 - - [04/Jan/2013:00:59:03 +0100] "GET /pxelinux.0 HTTP/1.1" 200 41095
127.0.0.1 - - [04/Jan/2013:00:59:33 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
127.0.0.1 - - [04/Jan/2013:01:00:03 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
127.0.0.1 - - [04/Jan/2013:01:00:33 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
66.249.74.75 - - [04/Jan/2013:01:00:41 +0100] "GET /images/XP/I386/ANABNR2.GI_ HTTP/1.1" 200 15546
66.249.74.75 - - [04/Jan/2013:01:00:44 +0100] "GET /images/XP/I386/MSDAPS.DL_ HTTP/1.1" 200 78439
127.0.0.1 - - [04/Jan/2013:01:01:03 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
127.0.0.1 - - [04/Jan/2013:01:01:33 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
127.0.0.1 - - [04/Jan/2013:01:02:03 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
66.249.74.75 - - [04/Jan/2013:01:02:20 +0100] "GET /images/XP/I386/MS28_4.PN_ HTTP/1.1" 200 1113
127.0.0.1 - - [04/Jan/2013:01:02:33 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
127.0.0.1 - - [04/Jan/2013:01:03:03 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
127.0.0.1 - - [04/Jan/2013:01:03:33 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
66.249.74.75 - - [04/Jan/2013:01:03:53 +0100] "GET /images/XP/I386/ANDLSO.TT_ HTTP/1.1" 200 47875
127.0.0.1 - - [04/Jan/2013:01:04:03 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
66.249.74.75 - - [04/Jan/2013:01:04:12 +0100] "GET /images/XP/I386/XPMENU.WA_ HTTP/1.1" 200 743
127.0.0.1 - - [04/Jan/2013:01:04:33 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291
127.0.0.1 - - [04/Jan/2013:01:05:03 +0100] "GET /ADSAdClient31.dll?GetAd=&PG=IMSSPS&AP=1007 HTTP/1.1" 404 291

This was after formatting my server so it'd be very strange it is a virus... :S

Any idea Sha0?


 

[69jakk]

Sha0!!! Dear friend... I almost found the problem...

gpxe works again....

I remember it was working before some changes...The change was the menu... I changed the menu from menu.c32 to vesamenu.c32 and I don't know why but with the last one it doesn't work...

So I changed to the old menu.c32 menu and now it's working again...


But the pitty is that I want my own menu with my customized image...

What could I do Sha0?

[ady]

@69jakk,

 

If with menu.c32 works but not with vesamenu.c32, then *maybe* you need to verify if you have the following 2 files (from the same exact version of Syslinux):libutil_com.c32 and libcom32.c32. Additionally, maybe you might want to try version 5.00 (not pre13 but the final).

[69jakk]

Ok Sha0...

I'll try it after I got solved some other issues...

After booting Win7Pe over http the next issue is mapping network folder over http with the "net use" command but I think is better to open a new thread or topic...

Best regards...