QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
If you mention that picoXP only cmd.exe that is true - the goal of that project was to remove everything as possible from a running OS and leave only the command line working - and it surely taught a lot about could be removed to XP based boot disk.
It is possible that Windows XP can be reduced to 5MB while leaving a bare Win32 console. Mark proved that. I do not compress my applications for forced compatibility.
My MS Project consists of 560 files(in 28 folders
) that can effectively run any application with the exception of the .NET Framework. I am currently geared towards integrating service tools, the .NET Framework and then integrating things like PowerShell and my own applications.
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
It would help if you posted your log.html after running a project that isn't working as you expect otherwise I can't point you on the right direction.
I would if I can find it. Last time I had VS installed this program keeps crashing in the middle of the build process and JIT catches it. This needs to be addressed.
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
Which windows source and service pack are you using?
Windows XP Professional SP2b VOLUME
Windows Server 2003 SP2 VOLUME
Windows Longhorn Professional OEM
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
Have you used nlite/modified or is it original?
NO.Don't even bother asking me about applications like nLite or vLite or whatever the hell it has grown into now. nLite is a disgusting program that modifies the Windows installations with a method less than favorable to developers such as myself and the BartPE, Reatogo and WinBuilder communities. Since you're the leader of the later, you already knew that.
Ever since I first saw what it had done in early 2003, I have refused to use it on any OS CD. Use of nLite is a serious disservice to my production environment.
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
One detail: your batch file that will only remove files and nothing more..
Meaning that:
- You'd need to install windows PE tools on your machine
Noted. I only posted this script as an example. I couldn't get the delete command working in a cross-scripted environment so I needed to start forcing commands.
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
- Start from scratch and learn how to create a windows PE with the provided tools
Done. Several times. I still base my prime examples from Longhorn.
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
- Adding programs also need to be done manually, checking dependencies and adding registry keys, etc..
Done.
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
- Aditional features and drivers also need to be tested over and over again until they work (if possible)
I can worry about that later. Tools like vmware aid that.
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
This was mainly the reason why
batcher was first coded, nowadays followed by winbuilder - a good tool to tweak and automate these actions really saves time.
I'm really interested as to how you build the Windows registry without using bldhives. I have command scripts that create, open and punch entries into the PE Registry and seal them in order to create a working system. I don't like extracting a hardset config.inf anymore.
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
And when these results are automated and studied we can spend time going forward to new directions rather than repeating the same old manual steps over and over again.
Assuming nothing can go wrong. Which it usually does anyway.
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
Believe me that this isn't a very efficient way of doing things.
I prefer effectiveness over efficiency. When an automated method is deemed "efficient" and then constantly fails to do what it's intended for, we have a problem.
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
If you don't believe me, then take a look here:
http://www.911cd.net/forums//index.php?showtopic=12067 - I've posted that batch script in 2005 and it would reduce any vanilla bartPE to a 35Mb ISO.
I have archived that thread on my server. It's a good read.
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
And things have kept being improved since that topic, passing from automated file removal to completely build a new and efficient OS structure from scratch as you see today on nativeEx.
...
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
WinBuilder shouldn't honestly be compared to bartPE since wb is only an script engine which will carry out whatever project you wish without even needing to be related to PE boot disks.
Agreed. Deos the OP have anything further to add?
QUOTE (Nuno Brito @ Sep 21 2007, 07:53 AM)
Please be more specific and compare against any of the currently available wb projects:
Please don't. If I see another thread like this I'm going to be diagnosed with a permanent case of stupid. =/
) while less than half of them understand where the dependencies are. In the end they get frustrated and come here to ask someone to post an edit of a file. WinBuilder is relative to PE Builder with the exception that it isn't married to constant access of the source disc for every little thing you do. Likewise, WinBuilder can be freely customized with the .script files but it runs into the same joint problem of possible conflicts caused by numerous INFs. That's where WinBuilder wins. The script writers are willing to change the scripts and edit them in order to stay free of conflicts. While the source can be edited in plain view, most of the data for building the primary target is encrypted so the end user just sees gibberish.
)
The perfect PE is an open one. I'm likely to drop this entire project and all my years working on it when ReactOS goes epic. 
Seriously, what's the point of having a PicoPE if all you can do successfully is run the exit command? Annouce that you have the smallest and most useless PE. Poof. 
