Bart PE All In One Options

[cmmehl]

Howdy all,

this project looks *very* interesting, and I'm just downloading (analog connection, will take some time). A short question before I even start testing it: will it be possible to create the RAM-based PE also on a USB stick, with the pe2usb tool?

Of course, if I understood that well, the idea of the RAM was to free the CD-drive, but I reckon it may also be faster than actually a CD or even a USB-stick is. Hence my interest.

Cheers
Chris

[neue]

Howdy all,

this project looks *very* interesting, and I'm just downloading (analog connection, will take some time). A short question before I even start testing it: will it be possible to create the RAM-based PE also on a USB stick, with the pe2usb tool?

Of course, if I understood that well, the idea of the RAM was to free the CD-drive, but I reckon it may also be faster than actually a CD or even a USB-stick is. Hence my interest.

Cheers
Chris

I am starting to check this possiblity too..

It would be great to have a standard .script to make usb boot a bit easier - I think jazclaz is an appropriate person to discuss it (not to mention dietmar also..)

[kimberlito]

Hooovahh, your AIO works like a charm.

1) After booting to AIO, in Task Manager, I couldn't find any tab/column that shows actual RAM usage. You could see that in BartPE's Task Manager. I can live with that, just curious if I missed something.

2) In the Batcher stage you have to set the path for ISO file but Batcher doesn't seem to create any (or at least I couldn't find it). However, if you leave this field blank the Batcher won't run. Again, not a big deal, just trying to understand how all this works.

PS: thanks for the link to 7-Zip, I didn't know RAR compression format.
:)

[philon]

Tested this really nice tool.

Here are my results: Everything went fine but CDIMAGE. It gave me an error message about a SxS file having more than 110 characters and stopped. I then used mkisofs for making the iso's without problem. I adeded a few things: German keyboard with toggle to US keyboard, local timezone, Drive Snapshot (not freeware), MBR Whisky. support of Via SATA hard drive and usb support and ended up with 60 MB. I did not write new scripts but made it via plugins as well as by copying over some files from an earlier 67 MB build (eg. txtsetup.sif). Finally I made a multiboot MiniCD with EasyBoot (not freeware) with the boot options to start MicroBartPE from CD or from Ram. Used the well known technique to rename one i386 folder and the pointers to it. Drive Snapshot is autostarted if the CD is inserted when running Windows.
I will use this CD to backup and restore images mainly.

Was surprised about the QUEMU GUI: Could not be easier and faster!

Thanks for this nice tool!

My wishlist: Regedit with runscanner or RegeditPE or RegistryLoaderPE ...

philon

PS. Does anybody know how to get rid of the Xobelite nag screen: "36 days have been passed since you last checked for updates"?

[Draugen]

PS. Does anybody know how to get rid of the Xobelite nag screen: "36 days have been passed since you last checked for updates"?

there's a string in extensions.rc:
"xoblite.checked.for.updates: #001 / 2005-01-01"

change it to:
"xoblite.checked.for.updates: #056 / 2106-02-25"

[Former_hooovahh_post]

Thank you everyone, I'm so thrilled people are actually using this.

@cmmehl
I'm not familiar with the usb utility you mentioned, but it might actually be useful, because when using a usb stick it gets writen over an over again as you change things and reboot. This dramatically reduces the life of the usb stick so going into ram would help alot. I'll look into it.

@kimberlito
sorry there's no real task manager, I simply used a pack of scripts posted by neue at his batcher thread. I realized having batcher create an iso would be stupid at that stage of the setup. Which is why I removed the mkisofs script. This is why it still asks for a location for the ISO but does nothing with it. I'll document that in the next version.

@philon
Thanks alot for taking what I made and running with it, it sounds like you've made alot of improvments. Just wondering, how did you get over 110 characters? I'll look into making a script for regedit, or equivelent of.

@Draugen
Thanks for that, I'll fix that in the next version.

[philon]

there's a string in extensions.rc:
"xoblite.checked.for.updates: #001 / 2005-01-01"

change it to:
"xoblite.checked.for.updates: #056 / 2106-02-25"

There is already this line in extensions.rc (two times):
"xoblite.checked.for.updates: #056 / 2106-02-25"

Xoblite seems to count the days from 2006-02-25 on. Btw. the nag screen is not a big issue, can live with it!

philon

[edborg]

New things in 1.2:
It now has two .ini files in it that remember your last sessions settings.
You can now have spaces in the file, or folder paths for every thing. I've tested it today and it worked, but I won't be surprised if there are problems.
I forgot to fix the typo...sorry.

I've tried 1.2, but it still gave problems to me ... unitl I learned how it was supposed to be used.
I ran "Boot into RAM" (without Help) and at the next run noticed that paths hadn't been remembered (no ini files added).
I then discovered that "Help" led to a new window (with its own RUN button!) which correctly created the ini files for the next run and copied paths to the "Boot into RAM" window. So there are two possible ways to do the task, one that creates the ini, the other that doesn't. Why not to eliminate one to avoid user's confusion?
Further, next time "Help" is used ini files are ignored, and the old default paths (hardcoded?) are reproposed.

It would be nice if only one window could be used and the paths were always read frome the same ini files, to limit configuration efforts to the first run only.

ADDED: Would it be possible to automatically delete the temporary RAM directory after building the ISO? It seems to me that if one forgets deleting it and changes his build, those changes are not reflected, as an ISO is already found in Temp\RAM.

Sorry for bothering you with all these details; it's not criticism at all, but only an attempt to facilitate the use of an already great tool.
edborg

P.S. I agree, RAM USB install would be very useful too. Pe2usb.cmd is Bart's script to do exactly that.
However, EWF (Enhanced Write Filter), the tool to protect against premature death of an USB stick is not necessary with BartPE (which is write protected on its own); it's only needed with full XP.

EDIT: neue (now Nuno Brito) has updated his Batcher/ScriptPack adding some tools AND changing name and paths. It therefore does no longer work with AIO, unless with some editing.

[hook88]

I adeded a few things: German keyboard with toggle to US keyboard, local timezone, Drive Snapshot (not freeware), MBR Whisky. support of Via SATA hard drive and usb support and ended up with 60 MB. I did not write new scripts but made it via plugins as well as by copying over some files from an earlier 67 MB build (eg. txtsetup.sif).

Can you explain more in details how to add usb support directly to bartpe directory? I've tried, but too many files in plugin (think not all are necessary) and rather big inf-file, so I have no success.

[hook88]

There is already this line in extensions.rc (two times):
"xoblite.checked.for.updates: #056 / 2106-02-25"

Xoblite seems to count the days from 2006-02-25 on. Btw. the nag screen is not a big issue, can live with it!

philon

I used #090 and have no nag screen. May be it appears in future.

[Nuno Brito]

neue (now Nuno Brito) has updated his Batcher/ScriptPack adding some tools AND changing name and paths. It therefore does no longer work with AIO, unless with some editing.

Oops..


I removed most script folders from the latest script pack and only left qEmu on a subfolder - this really eased my concern on updating new versions without crowding it with a lot of subfolders..

But all working paths withing batcher remain the same, I still haven't tested AIO, but what does this program relies in batcher to properly work?


The values to these paths depend only on an .ini file, perhaps once you upgrade to 1.17 I guess this file is overwritten - forcing to add the working paths again..


I will do my best to correct these problems..


As for USB boot using pe2usb, that looks a really interesting project..

[edborg]

Oops..
I removed most script folders from the latest script pack and only left qEmu on a subfolder - this really eased my concern on updating new versions without crowding it with a lot of subfolders..

But all working paths withing batcher remain the same, I still haven't tested AIO, but what does this program relies in batcher to properly work?
The values to these paths depend only on an .ini file, perhaps once you upgrade to 1.17 I guess this file is overwritten - forcing to add the working paths again..
I will do my best to correct these problems..
As for USB boot using pe2usb, that looks a really interesting project..

In fact the new tree structure of Batcher is much better, and works fine with BartAIO, provided the user (or hooovahh ) changes the name of the folder (ScriptPack/Batcher) and moves Qemu and mkISOfs to the "Other Scripts" folder, as the ISO creation is done in a separate step in BartAIO.
edborg

[Nuno Brito]

The new tree structure is much better, and works fine with AIO, provided the user (or hooovahh ) changes the name of the folder (ScriptPack/Batcher) and moves Qemu and mkISOfs to the "Other Scripts" folder. In fact the ISO creation is made in a separate step.
edborg

No I understand.. in previous versions all .script had to be placed under a "Scripts" sub-folder, with 1.17 any subfolder can be used - and no scripts subfolder available anymore..

Next pack will have a separate folder for qEmu and mkisofs scripts, if hooovahh updates his script paths to use scriptpack, next batcher versions will be fully compliant with AIO without worries..

[Former_hooovahh_post]

Wow there's so much activaty here I can only check this forum once a day at best. In any case I posted version 1.3

http://rapidshare.de/files/17199692/BartAIO1.3.zip.html

(I updated the first post)
This version made the taskmanger, and regedit apear in the menu of xoblite. I tried fixing the xoblite from naging you but it didn't work, I'll try the second post. I also added drive image xp to this. It was always there just not in the right directory. I also added the ability to now install PE to a USB device. It doesn' NOT load it into ram...I'll work on that. Also I couldn't test this part of the AIO because sadly I don't have a USB device I can test it on. And my bios doesn't like booting stuff like that. So some of you could test that for me.

It still uses the old batcher. I forgot what version exactly, I'll look into using the new one from now on. I'll also try to make the folder naming convention more universal.

@edborg
The reason why I had two places to perform the task, is because I wanted to show the user what to do in more detail. So I made a help page, which does the same as the normal page just explaining it a little more. I didn't realize that my writing the ini file worked in one and not the other I'll get right on that.

[micafili75]

hi,
i tried to download your tool, but isn't available... Could you provide me another link?
thanks

[cmmehl]

Philon,

I would be very interested to learn how exactly you manage to start MicroPE in RAM:

... with the boot options to start MicroBartPE from CD or from Ram.

Would be very nice if you could post the steps that brought you to this result.

Cheers
Chris

[edborg]

Wow there's so much activaty here I can only check this forum once a day at best. In any case I posted version 1.3

Nice job!

I tried fixing the xoblite from naging you but it didn't work, I'll try the second post.

It depends on the script. It works if you use the new ScriptPack from Nuno Brito (which is now called "Batcher")

I also added the ability to now install PE to a USB device. It doesn' NOT load it into ram...I'll work on that. Also I couldn't test this part of the AIO because sadly I don't have a USB device I can test it on. And my bios doesn't like booting stuff like that. So some of you could test that for me.

THIS IS GREAT! I don't have a spare USB stick either, but when I tested with Bart's pe2usb.cmd it worked fine, although some sticks may have format problem and require special efforts.

@edborg
The reason why I had two places to perform the task, is because I wanted to show the user what to do in more detail. So I made a help page, which does the same as the normal page just explaining it a little more. I didn't realize that my writing the ini file worked in one and not the other I'll get right on that.

I still think that one single page would be easier for the user. One would have to type in (or select) paths the first time and then find them as default the next times, unless he wants to change them again.
And what about deleting the temporary RAM folder?

Thanks for your contribution, that everybody appreciates here
edborg

[Nuno Brito]

I've mirrored your 1.3 version as well..

http://nunobrito.100free.com/BartAIO/BartAIO1.3.zip

(Copy and paste the link on your browser's adress bar to download the file..)

I didn't had time to update batcher to 1.17, but will do so soon.. keep up the good work!


Unlimited download bandwitdh here..

[Nuno Brito]

Also mentioned your program in my blog at http://nunobrito.pt.vu

[Former_hooovahh_post]

My work as temperarily layed me off so I've had a little time on my hand which is why I've created version 1.4

Here's the link I'll change the first post after this
http://rapidshare.de/files/17284378/BartAIO1.4.zip.html

Not a while lot changed, I tweaked the UI so that it's easier to understand. I also made tip strips all over places to help explain things, with out having a help page for every thing. Still have it for batcher and pebuilder cause the picture helps.

I also made it so you can have it delete the temp directory after creating the ISO.

I was able to borrow a USB drive and test the usb capabilites. And it works perfect. It loads pe into ram from the usb drive. Thanks Bart. I did make it a little better, you can now make any bartpe directory boot into ram, you no longer have to have the name be bartpe. Aside from that not much else changed. I didn't get to downloading batcher (the new one) I'll get it and try it out.

One thing I want to add is the ability to test the usb device with qemu, I'm pretty sure it can boot USB devices. For now it still only tests ISOs.

One last thing I fixed is I found the problem with not remembering your previous sessions settings. It now does. I'd explain what I did wrong but no one would understand without auto play media studio.