[DigiWiz]

No self-respecting geek would let PE Builder make their ISO for them - you'd use a batch file to perhaps get rid of unnecessary files, or maybe to eliminate duplicate files (I use CDIMAGE 2.52, but a special version of mkisofs accomplishes the same thing). Now you can use your batch file to perform one more useless thing...

Here's an offering that performs no useful purpose, other than to make your UBCD4Win build unique, and help regain your status as a full-fledged geek.

Download, then extract THIS file into your UBCD4Win system32 folder, then remake your ISO. Please note: this does NOT mean into your system32 folder of XP!!! Rather, place into the system32 folder that PE Builder constructed. Rebuild your ISO and voila!



DW

[SteelTrepid]

That is awesome!!!!

When I have some time I'll add it to the download page and provide instructions on how to use it also. That is just too cool!

You are the stuff Digi!

[stidyup]

Just remember to have a look at the previous discussion on this here, started by someone when he first joined

[DigiWiz]

This method was discovered/invented by the inimitable Sherpya, who also wrote PELoader that gets around the process limit of PE legally. He did not hack ntoskrnl.exe or any windows file - he used his own creation, and subsituted one file for another. No different than one finding a nice Notepad replacement, deleting the original, and subsituting your own find/creation. Since there is no hacking of Windows files, it remains legal - and easy to do too

Sherpya's thread may be read HERE for clarification.

DW

[stidyup]

And there's the case for the defence your honour

[LittlBUGer]

That's just plain awesome. Thanks DigiWiz!

[neonlys]

Quote

That is awesome!!!!

When I have some time I'll add it to the download page and provide instructions on how to use it also.  That is just too cool!

You are the stuff Digi!

Have this ever found its way into the project? AS of the date its been some time since this was posted.

Cheers!

This post has been edited by neonlys: 18 May 2005 - 12:11 PM

[SteelTrepid]

There is really no way for me to be able to add it to the project. Well, I have a few ideas but I do not want to attempt it. I've already had problems with MS and I don't want to take any chances. Digi has it outlined how to do it. I never said I was going to add it to the project. It would be pretty cool, but I just do not want anymore letters from MS.

[GiantWaffle]

DigiWiz, on Dec 8 2004, 11:30 PM, said:

No self-respecting geek would let PE Builder make their ISO for them - you'd use a batch file to perhaps get rid of unnecessary files, or maybe to eliminate duplicate files (I use CDIMAGE 2.52, but a special version of mkisofs accomplishes the same thing). Now you can use your batch file to perform one more useless thing...

Here's an offering that performs no useful purpose, other than to make your UBCD4Win build unique, and help regain your status as a full-fledged geek.

Download, then extract THIS file into your UBCD4Win system32 folder, then remake your ISO. Please note: this does NOT mean into your system32 folder of XP!!! Rather, place into the system32 folder that PE Builder constructed. Rebuild your ISO and voila!



DW

I'm a little confused. Of course, that's nothing new.

When I go to rebuild my ISO, it wants to delete the folders that it built first.
How can I put this file into that SYSTEM32 folder that it created, when it is
going to delete it before rebuilding? I would like to use this file, so if you
can help me, I would appreciate it.

Dave

[Joshua]

GiantWaffle, on Jun 27 2006, 02:40 PM, said:

When I go to rebuild my ISO, it wants to delete the folders that it built first.

press the F5 button in pebuilder.

Joshua

[GiantWaffle]

Joshua, on Jun 27 2006, 09:31 AM, said:

GiantWaffle, on Jun 27 2006, 02:40 PM, said:

When I go to rebuild my ISO, it wants to delete the folders that it built first.

press the F5 button in pebuilder.

Joshua

Okay, thanks, I will try that.

Dave

[DigiWiz]

There's another method which works well for including so-called "customized" files that you'll be including with every build that is very simple, and requires only slightly more than novice level to achieve, and is kinda slick... it goes a little something like this:

Say there are a group of files that you always want to include in your PE build, and these files will be overwriting files already processed by PE builder. You create a very simple "junk" plugin.

For example, I create my nu2menu ahead of time - it's highly structured, and NOT alphabetized, but rather in the order I want things to be - so it's premade, and I simply overwrite the one PE Builder makes with my own as the final step. As well, to save space, I overwrite a number of TrueType fonts from Windows 3.1 saving me around 4-5MB on the CD (new TTF are unicode and often orders of magnitude larger in size). There are a few Windows System files that can be compressed (this took meticulous trial and error, and is only for the CD space-freaks among us), so I again, overwrite these files as the final step. Also included in this relatively small list is BOOTVID.DLL, again overwriting so as to produce a nice custom bootscreen.

Almost in conclusion then, I used this so-called "junk" plugin to overwrite files that PE Builder has produced. You could go about it this way:

In your plugin directory create a plugin folder named zzzz-junk or whatever suitable name you'd like to use. Assuming you're building your PE disc on an NTFS drive (and you SHOULD), the zzzz-junk plugin will be processed last (or rename so that it WILL be last). To follow convention, I always include and use a files subfolder of the main plugin folder, so I have all my files (in this case BOOTVID.DLL for you) in zzzz-junk\files.

You junk.inf file might be as simple as:

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="!junk plugin"
Enable=1

[WinntDirectories]
a="Programs\Nu2Menu",3

[SourceDisksFiles]
files\BOOTVID.DLL=2

In my own plugin, which includes fonts you'd add similar to:

files\times.ttf=22, etc...

The table for knowing where certain filetypes go can be found by visiting HERE

This will either help you, or confuse you tremendously (hopefully the former after a few practice runs)

DW

[GiantWaffle]

DigiWiz, on Jun 27 2006, 08:52 PM, said:

There's another method which works well for including so-called "customized" files that you'll be including with every build that is very simple, and requires only slightly more than novice level to achieve, and is kinda slick... it goes a little something like this:

Say there are a group of files that you always want to include in your PE build, and these files will be overwriting files already processed by PE builder. You create a very simple "junk" plugin.

For example, I create my nu2menu ahead of time - it's highly structured, and NOT alphabetized, but rather in the order I want things to be - so it's premade, and I simply overwrite the one PE Builder makes with my own as the final step. As well, to save space, I overwrite a number of TrueType fonts from Windows 3.1 saving me around 4-5MB on the CD (new TTF are unicode and often orders of magnitude larger in size). There are a few Windows System files that can be compressed (this took meticulous trial and error, and is only for the CD space-freaks among us), so I again, overwrite these files as the final step. Also included in this relatively small list is BOOTVID.DLL, again overwriting so as to produce a nice custom bootscreen.

Almost in conclusion then, I used this so-called "junk" plugin to overwrite files that PE Builder has produced. You could go about it this way:

In your plugin directory create a plugin folder named zzzz-junk or whatever suitable name you'd like to use. Assuming you're building your PE disc on an NTFS drive (and you SHOULD), the zzzz-junk plugin will be processed last (or rename so that it WILL be last). To follow convention, I always include and use a files subfolder of the main plugin folder, so I have all my files (in this case BOOTVID.DLL for you) in zzzz-junk\files.

You junk.inf file might be as simple as:

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="!junk plugin"
Enable=1

[WinntDirectories]
a="Programs\Nu2Menu",3

[SourceDisksFiles]
files\BOOTVID.DLL=2

In my own plugin, which includes fonts you'd add similar to:

files\times.ttf=22, etc...

The table for knowing where certain filetypes go can be found by visiting HERE

This will either help you, or confuse you tremendously (hopefully the former after a few practice runs)

DW

Cool.

I was wondering if something like that could be done.

Dave

[grego1422]

The URL to download the bootscreen doesnt work anymore.
Can you please upload it to somewhere else?

[DigiWiz]

grego1422, on Jul 23 2007, 07:33 PM, said:

The URL to download the bootscreen doesnt work anymore. Can you please upload it to somewhere else?

I guess I don't throw anything away

http://rapidshare.com/files/44677586/ubcd4winboot.rar