Batcher 1.20 - Application Source And .script Discussion Topic, Released as GNU and making 50Mb bartPE ISO's Options

[neue]

Batcher
http://batcher.pt.vu/


Batcher uses text files (with extension .script) to know wich actions to perform, using .script files is possible to copy,delete or edit files from one place to another. Registry manipulation, hive loading and using encoded files is also supported.

This program was designed with the purpose of making better PE bootable discs, using bart's PE builder as a support we are able to downsize the ISO size into much smaller dimensions.



There are a few projects developed by the community:


ScriptPack - Reduces bartPE and includes some freeware programs and the possibility to make RAM bootable CD's (using windows 2003 as source)- ISO sizes around 70Mb

microPE - The minimum sized WinXP/2003 bootable ISO - minimum size is around 17Mb (at the moment..)

miniBox - Mini-Windows on a Box - aims to provide a 16 bit shell to FreeDos based in files that come from windows 95/98/ME as a test platform



All the information regarding batcher .script files is available in http://scripts.pt.vu, where you'll find sintax examples and screenshots of the working programs and projects


At this moment the more recent .script interpreter used to make bootable ISO's in reduced size is WinBuilder, wich gives far more improved boot disk results.

[neue]

A few bugs have been fixed, and the list as increased.

Output directory has 179 files using 36,8Mb

[hilander999]

Thats pretty cool!!!

Did you leave basic net functions in this build, or are they deleted also?
How much functionality is left after the script?

[RvdH]

neue, This looks like a very usefull progie, allthough i guess it would be nicer to have standalone scripts for "Fonts", "(unused) Drivers" etc

Thanks!

[dennis123123]

neue, This looks like a very usefull progie, allthough i guess it would be nicer to have standalone scripts for "Fonts", "(unused) Drivers" etc

Thanks!

Yes the separate scripts would be a good idea. Great work

[neue]

It isn't dificult to include other scripts because they are just plain text files, but I don't know wich files have to be included in order to start the network. I'm still trying to get the minimum size possible. The main problem is that some files are loaded by registry. I'll try to load the registry hives and remove these entries.

Last time I tried to do this I used UPX to get 35Mb on my batch file, this time I still haven't compressed any file. I am starting to believe that it is easier to take the files straight from the windows cd, just a thought..


Thanks for the support!

[solara]

Does the program also remove the references to any removed files in the txtsetup.sif file?

My manual minimum build has a txtsetup.sif of 86k, whereas a regular build may be over 400k.

[neue]

@solara
Yes all references are erased, if you check the script you'll see:

[misc]INIdeletesection,1,"\i386\txtsetup.sif","SCSI.Load"
INIwritekey,1,"\i386\TXTSETUP.SIF","SCSI.Load","atapi","atapi.sys,4"
INIdeletekey,1,"\i386\TXTSETUP.SIF","BootBusExtenders.Load","ohci1394"
INIdeletekey,1,"\i386\TXTSETUP.SIF","BusExtenders.Load","sbp2port"
INIdeletekey,1,"\i386\TXTSETUP.SIF","InputDevicesSupport.Load","usbehci"
INIdeletekey,1,"\i386\TXTSETUP.SIF","InputDevicesSupport.Load","usbohci"
INIdeletekey,1,"\i386\TXTSETUP.SIF","InputDevicesSupport.Load","usbuhci"
INIdeletekey,1,"\i386\TXTSETUP.SIF","InputDevicesSupport.Load","usbhub"
INIdeletekey,1,"\i386\TXTSETUP.SIF","InputDevicesSupport.Load","usbccgp"
INIdeletekey,1,"\i386\TXTSETUP.SIF","InputDevicesSupport.Load","hidusb"
INIdeletekey,1,"\i386\TXTSETUP.SIF","InputDevicesSupport.Load","serial"
INIdeletekey,1,"\i386\TXTSETUP.SIF","InputDevicesSupport.Load","serenum"
INIdeletekey,1,"\i386\TXTSETUP.SIF","InputDevicesSupport.Load","usbstor"
INIdeletekey,1,"\i386\TXTSETUP.SIF","BusExtenders.Load","pcmcia"
INIdeletekey,1,"\i386\TXTSETUP.SIF","BusExtenders.Load","toside"
INIdeletekey,1,"\i386\TXTSETUP.SIF","BusExtenders.Load","lbrtfdc"

These keys remove the references to the drivers that are loaded at startup, and you are right about the size of txtsetup.sif file, there are many sections that are reduntant, I'll try to delete them in order to get a smaller file size.

[atomix]

what files do i need to leave to have explorer sheel fully working ?tnx
and is it possible to add plugins

[RvdH]

@atomix, plugins?

You can create your own customized "*.script" files

[DigiWiz]

Would love for Batcher to have the ability to create a log file of its own so I can see exactly what it has done. Then I can compare to my present batch file I use to delete files and see where improvements/addiotions or corrections can be made. Thanks for nice proggie.

DW

[neue]

@hilander999 So far I have removed all network and usb functions, I'm still trying to reach a minimum size, it basically has the same functions and looks much alike msdos 3.30 command prompt
On the serious side, I've not tested any other programs running in this ISO, but I am pretty sure that screen resolution can be increased to 1280x768, keyboards can be customized and native ntfs support is still working. Most console applications will run without problems and I've also kept marlett.ttf wich is responsable for keeping the windows fonts. On the next step I'll try to increase functionality.



@solara - The new script will reduce the size of txtsetup.sif from 400kb to about 66,7kb - if you manually delete the all "SourceDisksFiles.x86" sections (I think there are three in the file) it will be reduced to 32,1kb, I still haven't (yet) worked on a way to fully delete sections that are repeated in the same file.

@atomix - It is not easy to say wich files make the explorer shell work, but I can point you to other alternatives such as xoblite, geoshell or trog's xpelite, they all make your iso "slimmer", I personnaly think that a lite shell would be an important addition.

@digiwiz - there are many files that have been added to list since the batch file was released. Just take a look at the drivers folder. I have created a special option (on your request) that enables a log.txt file that reports all actions. This log.txt file can be found on the same directory as the application. I hope this was what you were expecting, enjoy!








In the meanwhile, a few more bugs were fixed, and a progress bar was added to increase processing speed. If you press "see details" button you can see all commands being processed, but it takes much longer to complete the script.





thanks for the feedback!

[philon]

@neue

Had to go back from 120 dpi (large) to 96 dpi (normal) in Properties of Desktop to see the output folder selector and the start button. Scalability problem I suppose.

Added keybord plugin with preselection german (unchecked kbdgr ofcourse) and added a plugin to see my sata hd (viasraid). Keyboard was ok then but no hd visible. Pressing "F6" during booting and installing the disk driver via floppy was ok.

As expected I got a command window with access to all partitions of the hd.

Tried also to enable the nu2menu plugin just for curiosity but got a reboot loop with an error message about lsass.exe.

Thanks a lot!

philon

[neue]

@philon - I've recompiled and uploaded the application. I think now it should work fine with in any resolution, will you let me know if this patch solved this issue?

[philon]

@neue

@philon - I've recompiled and uploaded the application.

Just downloaded new version. Must be newer than the version i used before because it has the third tab. It is still not perfect with large fonts: No change compared to previous version.

philon

[neue]

@philon - The problem is that the main form was trying to rescale itself. I disabled this, and changed the fonts to arial, you should be able to use the program in any scale now. Some controls may look a bit out of place, but they are all usable, I've always heard other programmers complaining about this type of problems, but I must admit this was a first time for me. I really appreciate your feedback, thanks!

[Former_hooovahh_post]

Maybe I'm just a newbie, but I couldn't boot bart pe after using your batcher. It would start the boot then say it was missing some file I think it was c_237 or some thing from the system32 folder. I deleated the line in your script that deleates that file and it booted fine.

I'm sorry if I'm an idiot but I tried adding some small programs like 7-zip and it wouldn't run, the command prompt version ran, but 7zfmn.exe, which is the UI version, wouldn't do any thing. Can this tiny version of bart pe run programs like that? or did I do some thing stupid, preventing graphical programs to run?

[neue]

@hooovahh - I think you did all the right steps to solve your problem and even explored some new options, such as trying gui and console programs - your experiences reminded me a famous quote:

“I am neither especially clever nor especially gifted. I am only very, very curious.”
Albert Einstein

You can use GUI programs, but you have to ensure that all necessary dll's are in your compilation. A good starting point would be dependency walker:

Dependency walker homepage

This program follows all resources that a program needs to function, including those who were erased by the batch script.

Good luck!

[bilou_gateux]

@neue
very usefull tool. can you post all supported syntax to accomplish various tasks:
can we use this syntax to delete one line in specified section (see the example i've posted):

CODE

INIdeletekey,1,"\i386\TXTSETUP.SIF","SourceDisksFiles","cpqarray.sys","1,,,,,,4_,4,1,,,1,4"

can the script be used to add some lines to txtsetup.sif or add some files to \i386\system32 or \i386\system32\drivers.
If i want to write a script to add display driver,which syntax to use:

CODE

addfile,1,"\i386\system32\nv4_disp.inf"
addfile,1,"\i386\system32\nv4_disp.dll"
addfile,1,"\i386\system32\drivers\nv4_mini.sys"

@all
Would anyone like to volunteer to write specific scripts. for example one script to:
remove NIC drivers \i386\inf and \i386\system32\drivers
remove ieee1394 (FireWire) support
remove USB support
in order not 3 or 4 911cd forum members write a script for the same purpose.

My first one is used to remove Mass storage device support (using windows Server 2003 SP1 as source for building BartPE). keep atapi for IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller support:

[main]title=Mass storage device support
description=Delete default Windows Server 2003 SP1 Mass storage device drivers, keep atapi. First, select the output directory where the files are placed, then press the "start" button.
workdir=

[process]
IniDeleteSection,1,"%TargetDir%\i386\txtsetup.sif","SCSI.Load"
IniDeleteSection,1,"%TargetDir%\i386\txtsetup.sif","SCSI"

IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","cpqarray.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","symc810.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","aic78xx.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","i2omp.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","iirsp.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","dac960nt.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","ql10wnt.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","lp6nds35.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","ql2100.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","ql2200.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","ql2300.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","mraid35x.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","cpqfcalm.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","ql1240.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","arc.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","aic78u2.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","ipsraidn.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","nfrd960.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","symc8xx.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","sym_hi.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","sym_u3.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","cd20xrnt.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","ultra.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","adpu160m.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","adpu320.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","dpti2o.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","ql1080.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","ql1280.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","ql12160.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","cpqarry2.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","symmpi.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","perc2.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","hpn.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","cbidf2k.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","dac2w2k.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","dellcerc.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","hpt3xx.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","cpqcissm.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","hpcisss.sys","1,,,,,,4_,4,1,,,1,4"
IniDeleteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SourceDisksFiles","afcnt.sys","1,,,,,,4_,4,1,,,1,4"

[process]
FileDelete,1,"%TargetDir%\I386\system32\drivers\cpqarray.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\symc810.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\aic78xx.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\i2omp.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\iirsp.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\dac960nt.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\ql10wnt.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\lp6nds35.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\ql2100.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\ql2200.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\ql2300.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\mraid35x.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\cpqfcalm.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\ql1240.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\arc.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\aic78u2.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\ipsraidn.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\nfrd960.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\symc8xx.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\sym_hi.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\sym_u3.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\cd20xrnt.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\ultra.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\adpu160m.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\adpu320.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\dpti2o.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\ql1080.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\ql1280.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\ql12160.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\cpqarry2.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\symmpi.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\perc2.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\hpn.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\cbidf2k.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\dac2w2k.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\dellcerc.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\hpt3xx.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\cpqcissm.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\hpcisss.sys"
FileDelete,1,"%TargetDir%\I386\system32\drivers\afcnt.sys"

IniAddSection,1,"%TargetDir%\I386\TXTSETUP.SIF","SCSI.Load"
IniWriteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SCSI.Load","atapi","atapi.sys,4"
IniAddSection,1,"%TargetDir%\I386\TXTSETUP.SIF","SCSI"
IniWriteKey,1,"%TargetDir%\I386\TXTSETUP.SIF","SCSI","atapi","#$qIDE CD-ROM (ATAPI 1.2)/PCI IDE Controller#$q"

This post has been edited by bilou_gateux: Apr 25 2006, 03:46 AM

[Former_hooovahh_post]

@hooovahh - I think you did all the right steps to solve your problem and even explored some new options, such as trying gui and console programs - your experiences reminded me a famous quote:
You can use GUI programs, but you have to ensure that all necessary dll's are in your compilation. A good starting point would be dependency walker:

Dependency walker homepage

This program follows all resources that a program needs to function, including those who were erased by the batch script.

Good luck!

Thanks you very much for your kind advice, and your encouraging words. Keep up the good work