44 replies to this topic

[MedEvil]

You have to have the ramdisk. You can't just throw it away.
The PE expects certain data to be precisly at that address, if even just a foldername is missing, PE won't be able to boot successfully anymore!

If you want your LiveXP to boot without the Randisk you will need to put all the data that's usually on it to the HDD and then go and fix all registry entries to reflect this change.

btw. LiveXP will still be forgetting each and every registry setting you do on each shutdown.

[cdob]

Well, of course I put the i386 folder to the root, now renamed to minint, and I copied over the setupldr.bin and NTDETECT.com files, and I renamed setupldr.bin to NTLDR.

Thanks for confirming. Yes, that's the proper approach.

Why do you suggest increasing the Vm memory?

Low RAM may get a lsass error. Contrary 512MB should be sufficient.

Do yo use multi processor at virtual machine? Try one CPU only.

[TGP1994]

MedEvil: Ok, all data is on the hard drive. Can you give me a list of registry keys that need altering? And I can disable the forgetting the registry settings by taking away the /minint switch, correct?

cdob: That's odd, I though vmware would tell me it was running out of ram. And I only have one processor/processor core.

[MedEvil]

MedEvil: Ok, all data is on the hard drive. Can you give me a list of registry keys that need altering?

All that point to the now missing Ramdrive. Which those are, you have to find yourself.

And I can disable the forgetting the registry settings by taking away the /minint switch, correct?

False. When taking aways the /minint switch, you boot into setup mode.

[TGP1994]

Intersting... well, I wouldn't be able to touch that anyways since I have no way of editing the startup files. So what exactly will I be searching for in the registry entries?

And, all I really need to know is how I can find out what this "object" that lsass is referring to.

[TGP1994]

Update:

Using actual live xp NTLDR: I still manage to get to the lsass.exe error, but I think I may be onto something.

Using standard NTLDR that simply boots from the system directory, I now get a BSOD saying Stop 0xC0000009A SYSTEM_LICENSE_VIOLATION, which as I read means windows has detected some modifying in the registry. No kidding. I know this is getting near the edge of piracy, but does anyone know how to get around that?

[was_jaclaz]

I know this is getting near the edge of piracy, but does anyone know how to get around that?

IMHO, this is getting nowhere near the edge of piracy , but I see it as dangerously near to the edge of nonsense.

More explicitly, I find it strangely similar to the infinite monkeys approach :
http://en.wikipedia...._monkey_theorem

which in my experience never gave tangible results in a finite amount of time.



jaclaz

[MedEvil]

Do you hear anything we say, but what you wanna hear?
It's a PE, not a XP!

Right now your loading a PE like a XP and XP then complains that there is no XP, just a PE.

[TGP1994]

Do you hear anything we say, but what you wanna hear?
It's a PE, not a XP!

Right now your loading a PE like a XP and XP then complains that there is no XP, just a PE.

I've actually been trying both ways, as you can see in my most recent reply. And I don't see how either should not work. Storage device should not matter. Pretty much the same files.

[MedEvil]

Hadn't you just found out a few days ago that the storage device makes a difference?

And about

Pretty much the same ....

Humans for instance share 99% of their DNA with pigs. Draw your own conclusions.

[TGP1994]

Hadn't you just found out a few days ago that the storage device makes a difference?

And about

Humans for instance share 99% of their DNA with pigs. Draw your own conclusions.

Actually, according to this, we share 99% of our dna with other humans...

But I see what you mean. It isn't exactly the same thing. So? It seems like all I have to do is make a few registry changes . That's where you guys seem to get a little stubborn. All I need to know is what registry keys. And it seems like the reason lsass.exe is putting up that stink is actually because of a missing registry key, I just don't know which.

[was_jaclaz]

It seems like all I have to do is make a few registry changes .

It is possible, but not probable.
This is what it seems to you, and it may be inaccurate.

That's where you guys seem to get a little stubborn.
All I need to know is what registry keys.

And exactly where you seem as well stubborn with your fixation with registry changes to be made.

And it seems like the reason lsass.exe is putting up that stink is actually because of a missing registry key, I just don't know which.

And again the "it seems" is your personal perception of the problem and of what is causing it.

I will try to re-phrase.

Normally a PE build can be "migrated" from CD to USB stick by simply following the basic steps already mentioned. (NO REGISTRY CHANGES ARE NEEDED!)

You completely omitted to post details of your build and setup, and it is very hard for us to try and help you without knowing such details.

You may want to re-start from scratch, from here:
http://www.boot-land...?showtopic=4111

Read the part titled "Setting up an external USB HD" and follow it to the letter.

Report what happens.

jaclaz

[TGP1994]

It is possible, but not probable.
This is what it seems to you, and it may be inaccurate.


And exactly where you seem as well stubborn with your fixation with registry changes to be made.


And again the "it seems" is your personal perception of the problem and of what is causing it.

I will try to re-phrase.

Normally a PE build can be "migrated" from CD to USB stick by simply following the basic steps already mentioned. (NO REGISTRY CHANGES ARE NEEDED!)

You completely omitted to post details of your build and setup, and it is very hard for us to try and help you without knowing such details.

You may want to re-start from scratch, from here:
http://www.boot-land...?showtopic=4111

Read the part titled "Setting up an external USB HD" and follow it to the letter.

Report what happens.

jaclaz

Well, I'm pretty sure we've been down this path before. It requires those few files from the Server 2003 SP2 download, but I'm not quite ready to download 300MB just for a couple MBs, when there could still be a simple answer out there. And you're right, it is my personal perception, because no one has changed my perception regarding this error. Unless you're saying the error is a result of me trying to do all this.

And what "details" do you want? I'm willing and ready to give them out, all you need to do is ask

[was_jaclaz]

Well, I'm pretty sure we've been down this path before.

I am pretty sure you have NOT read what I suggested you to.

The NON-BootSDI needs NOT files from Server 2003 SP1 or R2.

And what "details" do you want? I'm willing and ready to give them out, all you need to do is ask

You might want to review the "common sense advice" attached to Rules:
http://www.boot-land...?act=boardrules
and expecially points #c., #d. and #f. (ALL of it, from #f1. to #f.5)

The whole Amendment #1 was added because of another new member behaving similarly as you are doing now, so you are also more than two years LATE.

Obviously "common sense advice" is just that, it is not compulsory , so we could go on forever , you failing to do what is suggested to you, and us keeping suggesting it, but it won't get "us" (please read as "you") very far.

I have unfortunately consummated my daily supply of patience for today, see you tomorrow, this should give you the time to actually READ the given Tutorial.



jaclaz

[TGP1994]

Ok, I'm following the instructions you linked me to step by step now. What I still don't understand is why it's saying

Also, if not checked already, check the option in the same script above for 'Add Win 2k3sp1 ...' files.

Since there are no files in the default directory to begin with, unless it's going to put the files there for me

And I can see you guys are suggesting that PEs and Windows are not the same, but from how I see it, copying files off of the installation cd makes it kind of the same . If someone could describe to me a little more what makes them so different that this task of mine would be impossible, that would great.

I'll continue on with the tutorial for making the bootable drive like you suggested, and I'll get back with the results.

Thanks.

EDIT: Just tried running the build again, (for some reason it doesn't make the ISO automatically,) so manually running the build ISO, a warning shows up in the log saying "You need SETUPLDR.BIN of W2003 SP1!" So, now I am very confused. You're saying that the Non-BootSDI build does not need Windows 2003 anything, yet Winbuilder seems to be contradicting you

[TGP1994]

I'm guessing this has been given up on? I have to, I reformatted the virtual drive and I'll be using Bart's way of putting a PE onto it. I guess this topic can be closed with the resolution of unfinished business.

[was_jaclaz]

I guess we failed to communicate.

Too bad.

jaclaz

[TGP1994]

Maybe it will work out next time :S

I was thinking on possibly learning the scripting for LiveXP... is that advisable?

[was_jaclaz]

Maybe it will work out next time :S

I was thinking on possibly learning the scripting for LiveXP... is that advisable?

If you want to develop .scripts, yes, of course.

But the whole "base philosophy" of a script or batch is to replicate autoamtically and in a convenientt way what you already succeeded with "manually".

At the moment you appear to have not yet the needed knowledge/experience to actually use a pre-made set of .scripts or make manually a build, so I would say that studying script syntax is a bit premature, right now.

If I were you, I would spend some time reading around the boards, here and on 911CD, to learn the basics of PE building, first.



jaclaz

[TGP1994]

If you want to develop .scripts, yes, of course.

But the whole "base philosophy" of a script or batch is to replicate autoamtically and in a convenientt way what you already succeeded with "manually".

At the moment you appear to have not yet the needed knowledge/experience to actually use a pre-made set of .scripts or make manually a build, so I would say that studying script syntax is a bit premature, right now.

If I were you, I would spend some time reading around the boards, here and on 911CD, to learn the basics of PE building, first.



jaclaz

Ok, will do.

Thanks for your patience