226 replies to this topic

[danrevella]

Sure, you can put NaughtyPE on a HDD, just like you've done with BartPE.

Hi!!!
Please excuse me, I'm totally newbie....
Where may I find this procedure to get Bartpe/NaughtyPE bootable on a HDD?
Maybe is it enough add a script in the NaughtyPE project?
Thanks in advance... ;-)

Danrevella

[MedEvil]

Well, if you wanna put a plain NaughtyPE on a HDD, it can't be on the same partition as your other Windows, because the two will mesh. In that case you will need to put an image on the HDD.

You can read about it here:
http://www.boot-land...?...ost&p=37112
http://www.boot-land...?...ost&p=47006
http://www.boot-land...?...ost&p=41696

[smallhagrid]

BartPE is simplicity itself to get onto a HDD with a boot menu entry - see:
http://nu2.nu/pebuilder/faq/

Where you will find:
'Here is how to use peinst (PE Builder v3.1.3 and higher):

* Run PE-Builder and build as normal (no need to create an ISO image).
* After building, goto the <pebuilder>\plugin\peinst folder and run peinst.cmd <path> c:
Where <path> is the PE Builder output folder (default <pebuilder>\BartPE).
* Select option "5) Install BartPE to c:" and "2) Install PE-loader in c:\boot.ini".
This will add a line to your boot.ini for loading BartPE and is done is just a second. This action is only needed once, you can skip this next time.
* Select option "5) Install BartPE to c:" and "1) Install BartPE files to c:".
This will install the BartPE files in c:\minint and c:\programs. This will take a few minutes.
* When peinst.cmd has succesfully finished, reboot your system and select "Boot BartPE (by PE Builder)" from the boot.ini menu.'

So:

Where may I find this procedure to get Bartpe/NaughtyPE bootable on a HDD?

That answers the first part of your query - and building BartPE can be totally great too !

I see no such simple answer to getting NaughtyPE fully/easily/quickly onto HDD as with
the peinst procedure above though - and read the suggested posts with no further light
shed upon what should be a simple/clear procedure ?

[smallhagrid]

Cool.

Sure, you can put NaughtyPE on a HDD, just like you've done with BartPE.

And where might one exactly find the nice, easy, quick procedure for this, please ?
(Direct to HDD - not any fancy RAM booting/GRUB4DOS/imaging or whatever...)

[Lancelot]

smallhagrid

what you learned is always seems to you simpler than learning new things.
"copying 4-5 files to C:\"+"1iso file"+"1line" to boot.ini can not be too complex. .
also method you mentioned is not adviced, i guess medevil may write the reasons.


medevil

reminding (i believe you already know) "9 - ProgramFilesPE.Script" for livexp, now it is available for users like smallhagrid to install the method mentioned. But i dont have any desire to write a nice tutorial about this "not nice" method . Here is a short tutorial for smallhagrid with your lead: *change %programfiles% with "9 - ProgramFilesPE.Script", make a build, copy target to empty bartpe directory , than do peinst instructions smallhagrid wrote.)

good night to all.

[MedEvil]

There will be no more development of NaughtyPE or introduction of new functionality.
I will try to complete the few things that are still in the pipe. After that it's bye bye PE for me.

I've been patching and fixing the same bugs now for about 2 years and everytime i see the finishline, a new version of WB is released, which finaly has some annoying bugs fixed, but is also completely incompatoble with the old scripts.
So the whole thing starts over.

I had really high hopes for WB076 after WB074 was fully compatible to WB072. But no! Boot-Land stays Boot-Land!

[Lancelot]

There will be no more development of NaughtyPE or introduction of new functionality.

I will try to complete the few things that are still in the pipe. After that it's bye bye PE for me.

, I will save the "bye bye Naughty PE" when announced.

i agree with your comment about "incompatibility backward", and wrote detailed about my ideas....



Looking the full part of the half full glass, so now you have more time for LiveXP which can be used as a "Multimedia PE" for a long while

[MedEvil]

Update for NaughtyPE.

Mostly i changed just the default settings around again.
Then i fixed a bunch of bugs so that NaughtyPE, when build with WB076, reaches at least the Desktop.
All strings containing spaces will still get malformed though.
So WB072 is still recommended for building NaughtyPE!

Besides that, IE6.script was added and XPE.script learned a new trick. Or two?

[MedEvil]

Because of some complaints i did get and some own tests.
I have to stress: NaughtyPE build with WB076 manages to reach the desktop. This however does not imply in any way that things will work!!!

How far things do work, depends on your language or more precisely, if and how many folders have a space in their names.

If you want a usable NaughtyPE, only WB072 and WB074 will do!!!

[pscEx]

Because of some complaints i did get and some own tests.
I have to stress: NaughtyPE build with WB076 manages to reach the desktop. This however does not imply in any way that things will work!!!

How far things do work, depends on your language or more precisely, if and how many folders have a space in their names.

If you want a usable NaughtyPE, only WB072 and WB074 will do!!!

Can you explain some of the "things" which do not work?

Peter

EDIT: Add screen shoot of a build with 076

Edited by psc, 21 April 2009 - 08:22 AM.
Screen Shoot added

[MedEvil]

All Strings containg spaces get malformed.
This means links, registry...

With a souce which has no space in programFiles folder name, things mostly seem to work, except for 'Fish Radio' for instance which is one of the very few programs which has a space in its folder name in NaughtyPE. If i remember correctly there are also some applications, that disappear from the startmenu.

With a space, things take a turn for the worst. Error messages and strange behaviour of programs occur. Or with other words, more programs are affected. Why not all, i'm not quite sure, but guess the use of %programfiles% instead of the actual foldername protects some.

btw. Sound is not working in your NaughtyPE.

[pscEx]

All Strings containg spaces get malformed.
This means links, registry...

Please tell me at least one script with link failure and one script with wrong registry key.
I need to reproduce the issue.

btw. Sound is not working in your NaughtyPE.

Unfortunatewlly I do not have sound. Therefore I cannot reproduce.
Tell me the script and I'll try to compare.

Peter

[pscEx]

Please tell me at least one script with link failure and one script with wrong registry key.
I need to reproduce the issue.

Unfortunatewlly I do not have sound. Therefore I cannot reproduce.
Tell me the script and I'll try to compare.

Peter

MedEvil,

Maybe I have an unactual version of NaughtyPE (downloaded 2009_APR_19 12:49).
But the build with 074 (XP SP3 English) results in this boot:

When you do not have any troubles with 074, what's different on my system?
To prevent unnecessary questions: YES, i cleaned the complete Cache\Prebuild before.

Peter

[MedEvil]

Please tell me at least one script with link failure and one script with wrong registry key.
I need to reproduce the issue.

As already said FishRadio has malformed links.
To give you a script with malformed registry entries you will have to wait a bit, till after i published PrettyPacks, then i do a testbuild with WB076 for you.

Unfortunatewlly I do not have sound. Therefore I cannot reproduce.
Tell me the script and I'll try to compare.

Having no sound, is a very valid reason for NaughtyPE not having it too.

[MedEvil]

MedEvil,

Maybe I have an unactual version of NaughtyPE (downloaded 2009_APR_19 12:49).
But the build with 074 (XP SP3 English) results in this boot:

When you do not have any troubles with 074, what's different on my system?
To prevent unnecessary questions: YES, i cleaned the complete Cache\Prebuild before.

Peter

Since there is no dot3api.dll in my builds and i never got complaints about it missing, i guess the problem is not Wb074 but that you use as source XPSP3 while i still use XPSP2.

The curious thing is, why didn't you get that message when you've build with WB076?

[pscEx]

Since there is no dot3api.dll in my builds and i never got complaints about it missing, i guess the problem is not Wb074 but that you use as source XPSP3 while i still use XPSP2.

I'll try with SP2

The curious thing is, why didn't you get that message when you've build with WB076?

That one I did with German SP 2.

So we have to do a couple of 'serial investigations'.
I do not want to spend weeks on it. Therefore I would like to use a minimized project.

Can you post a project where all 'uncritical' and 'unneeded' scripts are unselected?

Just let remain only the scripts which in your experience create troubles.

Peter

BTW: I suggest that in the mean time you adapt the project (for 074) to SP3

[pscEx]

As already said FishRadio has malformed links.

I'll give it a trial.

Having no sound, is a very valid reason for NaughtyPE not having it too.

I suggest to continue with removing themes
Peter

[MedEvil]

BTW: I suggest that in the mean time you adapt the project (for 074) to SP3

As stated further above, with the exception of finishing a few things that i had already started (which is a statement i already regret to have ever made), there will be no updates or changes in NaughtyPE anymore.

The whole WB PE thing became nothing but a constant annoyance to me.
2 years and BartPE as a starting point and our PE are still crap. Even worst is, that there is no way to ever change this, because as soon as one turns around someone rips something, that used to work, up and changes - or at least breaks it again!

I will see, if something comes out from a little collaboration with fxscrpt, to build a PE completely independant from any other project or even WB.
Anyway NaughtyPE is history for me.

[MedEvil]

Warning!!!
At the last upload something must have broke. As a result Sound does not work with NaughtyPE.

I'm working now on finding the problem and will post back once the problem has been fixed.

[pscEx]

Does this mean,

If you want a usable NaughtyPE, only WB072 and WB074 will do!!!

should be read as

If you want a usable NaughtyPE, only WB072 and WB074 with German XP SP2 source CD will do!!!

?

Peter

[MedEvil]

should be read as

Nope shouldn't be read like that. Should work with all XPSP2, but W2k3Sp1 might make problems as i never tested it. But there too: all languages - same problems. I do not discriminate!

[pscEx]

Nope shouldn't be read like that. Should work with all XPSP2, but W2k3Sp1 might make problems as i never tested it. But there too: all languages - same problems. I do not discriminate!

So don't give up.
I just decided, for my own fun (and besides that for testing 077 beta 2 before publishing) , to create a project "NaughtyClone", which first gets all updated nativeEx core functions and internal apps like PENetwork.

I'm sure that after that the remaining issues are enumerable.

Peter

[MedEvil]

Regarding the Warining. It was just a glitch on my side not on the server.
NaughtyPE doesn't like it to be run from a folder path with spaces in it, like a lot of other projects.

[pscEx]

NaughtyPE doesn't like it to be run from a folder path with spaces in it, like a lot of other projects.

This space behaviour is one of my 'most hated' ones. And I'm sure that inside WinBuilder I did EVERYTHING(?) to allow this.

BTW: For this reason, the WB development team decided to have the development path as "???\WB Debug"

Peter

[MedEvil]

So don't give up.
I just decided, for my own fun (and besides that for testing 077 beta 2 before publishing) , to create a project "NaughtyClone", which first gets all updated nativeEx core functions and internal apps like PENetwork.

I tryed the same when Wb076 came out. Didn't went too well.
I clearly remember that the new registry was worst than the old one, despite fixing one major bug.
How good or bad things were all over, i unfortunately do not remember.

But i decided to stick with Wb072, despite that i had the intention to upgrade NaughtyPE to Wb076. So i guess it must have been pretty horrible.