LiveXP is a very flexible PE 1x, using Explorer as shell, supporting SATA/IDE drives, USB devices, and many other features and tweaks. This project is based on PE environment and will use a Windows ™ XP/2003 Install CD.

Download server link to use with the WinBuilder Download Centre: www.livexp.galapo.net.

Download the most recent archive of the project:

2 Pages V  < 1 2  
Reply to this topic
 PXE / TFTP Boot of LiveXP now working!
post Jul 30 2008, 09:34 AM
Post #12
was_jaclaz
Finder   ******
Group: Advanced user

  Joined: 14-July 06 From: Gone in the mist

Posts: 7,230
Thank(s): 564


Italy


I am confused, you appear to be trying to PXE (read RAMDISK) boot a RAMDISK booting image. unsure.gif

It looks to me like "Matryoshka booting" (a neologism I just invented wink.gif):
http://en.wikipedia.org/wiki/Matryoshka_doll

Try doing the following:
Use this as your PXE dir WINNT.SIF:
CODE
[SetupData]
BootDevice="ramdisk(0)"
BootPath="\i386\System32\"
OsLoadOptions="/noguiboot /fastdetect /minint /rdexportashd /rdpath=BootSDI.img"


Transfer via PXE the BootSDI.img, NOT the livexp.iso containing it.

The BootSDI.img, UNLIKE the name suggests, is NOT a SDI format image, but rather a RAW image of a partition (or if you prefer a "superfloppy" image).
As thus it can be mounted using either IMDISK (suggested in this case) or FILEDISK or VDK, some links:
http://www.boot-land.net/forums/?showtopic=1507

Alternatively, re-build your LIVEXP WITHOUT the BootSDI option checked, make sure that the RAMDISK.SYS inside the .iso is the right one, and serve via PXE the "plain" livexp.iso, keeping your PXE dir WINNT.SIF:
CODE
[SetupData]
BootDevice = "ramdisk(0)"
BootPath = "\i386\System32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=livexp.iso"


In other words, what you want as your system directory is:
WARNING PSEUDO-CODE:
CODE
ramdisk(0)\i386\System32\

i.e. something like:
CODE
ROOT(BootSDI.img)\i386\System32\

or:
CODE
ROOT(livexp.iso)\i386\System32\


What you are having now (maybe) unsure.gif:
WARNING PSEUDO-CODE:
CODE
ramdisk(0)\i386\ramdisk(0)\I386\System32\

i.e. something like:
CODE
ROOT(livexp.iso)\i386\ROOT(BootSDI.img)\i386\System32\


jaclaz


--------------------
+Quote Post
post Jul 30 2008, 10:10 AM
Post #13
yurry
Newbie   *
Group: Members

  Joined: 23-July 08
Posts: 17
Thank(s): 0


Slovenia


Yes, you are right!

I know the matryoshka, in fact, I have a few at home tongue.gif

I didn't understand how this really works. I have managed to get passed the status 14 now, of course. I have just extracted the BootSDI.img file and loaded it.

I have one last (I hope) hurdle now. I get a BSOD error UNMOUNTABLE_BOOT_VOLUME. It says stop: 0x000000ED.

I presume this has something to do with the ramdisk driver? There is a file included on the boot CD, next to the image file, called BOOTFIX.BIN. This is the image created with the SDI option. Does it fix some stuff in the CD booting sequence to prevent this error?

I will try building a normal iso with krokodox's script. I think I now understand why it broke my txtsetup.sif file smile.gif
+Quote Post
post Jul 30 2008, 10:31 AM
Post #14
was_jaclaz
Finder   ******
Group: Advanced user

  Joined: 14-July 06 From: Gone in the mist

Posts: 7,230
Thank(s): 564


Italy


QUOTE (yurry @ Jul 30 2008, 12:10 PM) *
Yes, you are right!

I know the matryoshka, in fact, I have a few at home tongue.gif

I didn't understand how this really works. I have managed to get passed the status 14 now, of course. I have just extracted the BootSDI.img file and loaded it.

I have one last (I hope) hurdle now. I get a BSOD error UNMOUNTABLE_BOOT_VOLUME. It says stop: 0x000000ED.

I presume this has something to do with the ramdisk driver? There is a file included on the boot CD, next to the image file, called BOOTFIX.BIN. This is the image created with the SDI option. Does it fix some stuff in the CD booting sequence to prevent this error?

I will try building a normal iso with krokodox's script. I think I now understand why it broke my txtsetup.sif file smile.gif


No, the BOOTFIX.BIN is only responsible for the "Press any key to boot from CD" message.

The 0x000000ED BSOD is generally connected to "corrupted data", typically (on a "normal" booting using a 40 leads IDE cable on ATA drives - that need 80 leads cables)
With ramdisk booting that error has been reported:
http://www.911cd.net/forums//index.php?showtopic=21559
when using improperly the /rdexportascd or /rdexportashd parameter.

jaclaz


--------------------
+Quote Post
post Jul 30 2008, 11:56 AM
Post #15
yurry
Newbie   *
Group: Members

  Joined: 23-July 08
Posts: 17
Thank(s): 0


Slovenia


This was the issue. I changed the parameter to /rdexportashd and it booted.

Thank you for all your help. cheers.gif
+Quote Post
post Jul 30 2008, 12:16 PM
Post #16
was_jaclaz
Finder   ******
Group: Advanced user

  Joined: 14-July 06 From: Gone in the mist

Posts: 7,230
Thank(s): 564


Italy


QUOTE (yurry @ Jul 30 2008, 12:56 PM) *
This was the issue. I changed the parameter to /rdexportashd and it booted.

Thank you for all your help. cheers.gif


Happy to hear a story of success smile.gif

cheers.gif

jaclaz


--------------------
+Quote Post
post Aug 12 2008, 03:59 AM
Post #17
magic12kenneth
Member   **
Group: Members

  Joined: 6-August 08
Posts: 75
Thank(s): 4


United States


I'm also trying to do a PXE using LiveXP to help someone install Windows XP for a laptop without bootable cd, dvd, floppy or USB. However I do not have a copy of Windows Server for this tutorial.

Will it work if I replace Microsoft's TFTP server with Tftpd32 server? If so, what are the steps? I just need to get an idea how to setup the TFTP to boot LiveXP on the target computer and start Windows XP setup.

Kenneth
+Quote Post
post Aug 14 2008, 10:51 AM
Post #18
yurry
Newbie   *
Group: Members

  Joined: 23-July 08
Posts: 17
Thank(s): 0


Slovenia


I can not give you a full anwser, because I used linux for this part.

The TFTP server is not an issue here. Using any should be fine as long as it is configured properly. I think you can draw the configuration parallels from krokodox's work with Microsoft's server.
+Quote Post
post Aug 19 2008, 09:32 PM
Post #19
magic12kenneth
Member   **
Group: Members

  Joined: 6-August 08
Posts: 75
Thank(s): 4


United States


QUOTE (yurry @ Aug 14 2008, 03:51 AM) *
I can not give you a full anwser, because I used linux for this part.

The TFTP server is not an issue here. Using any should be fine as long as it is configured properly. I think you can draw the configuration parallels from krokodox's work with Microsoft's server.


Thanks. I'll give it a try. If I get it to work, I'll post the result here.

Kenneth
+Quote Post

2 Pages V  < 1 2
Reply to this topic
1 User(s) are reading this topic ()



Collapse

  Topic Replies Topic Starter Views Last Action
No New Posts Boot Land Stats, August
4 Nuno Brito 155 Yesterday, 02:07 PM
Last post by: NFX
No new Topic has attachmentsLiveXP wb server discussion
14 amalux 270 Yesterday, 12:55 PM
Last post by: Nuno Brito
No New Posts boot full ubuntu from grub4dos
3 sara - pmedia 146 Yesterday, 08:12 AM
Last post by: Wonko the Sane
No New Posts Offline Registry
Read and Write to an offline registry hive
4 erwan.l 1,165 28th August 2010 - 09:41 AM
Last post by: erwan.l
No new booting vista/2008/w7 from usb sub folder
grub4dos launches bootmgr but bootmgr cannot find what it needs?!?
112 anystupidname 16,945 27th August 2010 - 07:41 PM
Last post by: steve6375