mapping LiveXP ISO image to (hd32) from CD vs HDD External links Options

[gbrao]

I just created a minimal LiveXP iso from XP SP3 using "Complete recovery build with advanced tools" at "LiveXP with BootSDI".

I then realised I do not have and blank CDs, but was very eager to test it. I saw the post at link which says this works :

CODE

title LiveXP_ISO.iso - mem
find --set-root /LIVEXP_ISO.ISO
map --mem /LIVEXP_ISO.ISO (hd32)
map --hook
chainloader (hd32)

So I just added those lines to the menu.lst file I have on my ( g4d mbr ) HDD. I put the iso in the same directory. When I choose the option to boot LiveXP, XP starts booting but then I get a BSOD. I assumed since the iso is loaded to memory, it won't matter whether it is loaded from CD or HDD.

Which got me wondering if the LiveXP iso can only be loaded from a CD. That is, the menu.lst file & iso file have to be on a CD ( and not on a HDD ). True ?


Also, I have never created a Live XP CD before. I was surprised that the iso was created without asking for the XP serial. This OK ?

[was_jaclaz]

When I choose the option to boot LiveXP, XP starts booting but then I get a BSOD.



Which got me wondering if the LiveXP iso can only be loaded from a CD. That is, the menu.lst file & iso file have to be on a CD ( and not on a HDD ). True ?

Of course not.
You are not having "a" BSOD you are having a BSOD with a STOP ERROR CODE! (which I guess being 0x0000007b ), which is probably due to somethning NOT working connected to the RAMDISK, possibly a "wrong" set of SETUPLDR.BIN/NTDETECT.COM/RAMDISK.SYS (they should come from Server 2003 SP1 or R2, NOT "gold", NOT SP2)

Double check what you did with this:
http://www.boot-land.net/forums/index.php?...=5041&st=22
PARTICULARLY last few lines of it.

Also, I have never created a Live XP CD before. I was surprised that the iso was created without asking for the XP serial. This OK ?

Sure, although improperly named, "liveXp" is NOT a "live" XP, but a (live or dead , as in your case) PE.

jaclaz

[gbrao]

Thanks. Again !

I did the "Add Win 2k3sp1 setupldr.bin and ramdisk.sys" enabled step. But not the "Create xx_ISO.ISO" button pressed step. Could you please explain what that step is ?

The setupldr.bin and ramdisk.sys provided by lx76hfcxaf.exe are the ones to be used, right ? I don't have to get them myself ?

[Lancelot]

Hi gbrao

From this word

lx76hfcxaf

and this question

Could you please explain what that step is ?

I understand you do not get LiveXP with winbuilder, so you do not have an updated LiveXP.

with updated LiveXP, create iso script have "Create xx_ISO.ISO" button "

So now follow this:
With winbuilder
Click Download at right top
select only livexp on server list
than select only create iso script in the download list,
Click download
==> you get the latest create iso script which have "Create xx_ISO.ISO" button "


Official LiveXP distributed with winbuilder which do not have setupldr.bin and/or ramdisk.sys

Other ready packages you may find around is verrrry helpfull, but since project updates very frequently some scripts inside them can be outdated in time.

Good luck

[Lancelot]

@jacklaz

although improperly named, "liveXp" is NOT a "live" XP, but a (live or dead , as in your case) PE.

I remember I wrote long time ago I agree with you. Besides I do not like the "XP" in name since it is a PE not a full XP (also there is 2k3). (sometimes people expect a full XP on ufd but it is PE, vice versa etc...)

Is it appropriate to change the name of the project after long time now ? What will be consequences ?? Does it worth to change the name ???

Benefit is obviously a better name saying right message to user about what project is.
Maybe LivePE1 ? orrr ???

Besides you, I wonder what Nuno & Galapo think about these too.

CU

[was_jaclaz]

Is it appropriate to change the name of the project after long time now ? What will be consequences ?? Does it worth to change the name ???

I guess there is ALREADY ENOUGH confusion about projects with actual status:

• "active"
• "no-active"
• "retired"
• "on hold"
• "missing in action"
• "not working with Winbuilder 0.7x"

to add categories like:

• "misnamed"
• "renamed"

The whole Winbuilder and projects situation is a mess, with outdated links, non-working .scripts, conflicting .scripts, missing bits and ends, developers who retire AND delete projects, other ones that simply vanish in thin air, etc., etc..

Among these "apocaliptycal" situations, the only two projects that mantain an apparent stability are LiveXP and some other ones of the native_EX "family", so PLEASE DO NOT EVEN THINK OF CHANGING the "stupid" name of LiveXP! Please, please...




jaclaz

[Lancelot]

Winbuilder and projects situation is not my concern, i stopped writing my ideas long while ago.

Here is a news for you, My Crystal ball says one more to your list on the way

• "NEVER use with older wb than Winbuilder 0.7.x"

-->old wb cause scripts made by new wb malfunction-->Maybe there is a term exists but i dont know, guessing "forward incompatibility"

PLEASE DO NOT EVEN THINK OF CHANGING "stupid" name of LiveXP!

I dont think reasons you wrote is directly related to project name, besides it wont be my decision to change the name, I was just asking your ideas about naming, also wondering Galapo , Nuno and other LiveXP users idea about the name.


Well, since you have your reasons having LiveXP name unchanged, maybe it will be nicer not to complain about the name

CU

[Galapo]

Too late to change the name, I think.

Actually, I like the name, even if it is not really accurately descriptive.

Regards,
Galapo.

[dera]

Hi

Nice to see you Galapo!

I also like the name

[was_jaclaz]

Too late to change the name, I think.

Actually, I like the name, even if it is not really accurately descriptive.

Regards,
Galapo.

Sure , absolutely nothing against the name, only something against it's accuracy in describing the object.

Maybe we could add (without "changing" anything) an "illustrative sub-title", like

LiveXP
"the most flexible PE on earth"

or something of the like.



jaclaz