This is what a I want ;)

Alright, I'm so tired of searching I'm just going to throw this out there and hope somebody can help me:

I need a Windows based bootable distro with the following features:

1. Finished image close to 100MB or less
2. Bootable from a USB flash drive
3. Network support for modern Dell desktops and laptops
4. USB keyboard and mouse support
5. SATA drive support
6. Some type of GUI
7. Possibility of hacking in WinBatch support

That's it! Can anybody help me/suggest something?

1. Finished image close to 100MB or less

All projects end up in less than 60Mb, so this should be easy..

2. Bootable from a USB flash drive
3. Network support for modern Dell desktops and laptops

This is a bit trickier, it's possible but I haven't looked much into it yet..

Draugen has added network support for his microPE project (http://batcher.pt.vu), but I still haven't looked at it. Regarding USB boot, edborg was working on this some time ago. You should look for bartAIO in the old forums, it's meant to include all tools to make your PE USB drive..

4. USB keyboard and mouse support
5. SATA drive support

Philon has already done this here, I'll add it as soon as he makes it available..

6. Some type of GUI

On the next build (048) you'll be able to use either xoblite or explorer as shell, both sizing around 50Mb ISO's

7. Possibility of hacking in WinBatch support

It would be a very good tool to add, but Winbatch is not free and cannot be included inside the distribution..

even tho winbatch isn't free, it should still be possible to add support for it. we just can't distribute the program binaries

even tho winbatch isn't free, it should still be possible to add support for it. we just can't distribute the program binaries

I somewhat disagree, completely!

The more we use Freeware/Open Source apps only, the wider the possible "audience" is.

I think we have already determined, by experience, that members of this board are more or less the same ones that took interest in Nuno's ideas on the 911CD forum.

So, with a theoretically VERY wide audience, potentially everyone that has to deal with Windows 2K/XP/Server 2003 equipped PC's, people actively contributing to our little projects can be counted on the fingers without taking one's shoes off.

Troubleshooting and solving "generic" problems already take some of these good guys' time.

If we start supporting applications that need a bought license, most probably some more time will have to be given to these apps, with a quite limited targeted audience.

Of course, if one has to develop a script or a support file for a particular Commercial app for his/her own use, making it public will be very much appreciated, but it would be a pity if such activities would lead to less time dedicated to the core chores (pardon me the pun) related to the main development.

jaclaz

I agree. I didn't actually want Winbatch support implemented. I just wanted to be able to hack it in myself. I've done it before and it's fairly simple with .script.

Within some time it's possible to add new features and new commands, I'm actually dedicating my time to it right now, feel free to give suggestions from your experience on winbatch..

I agree. I didn't actually want Winbatch support implemented. I just wanted to be able to hack it in myself. I've done it before and it's fairly simple with .script.

Hm. I misread your post it seems. Sorry!

*hides under desk*

@jaclaz: good point. I actually agree I make a point of using as much F/OSS as is practical (note: not POSSIBLE ). And valuable development time (which I seem to have next to nothing of these days) should not be spent on niche requirements. If $ProprietarySoftware matters so much, they can hack it in themselves (and then share )

@nuno: your beer-glass-clinking avatar reminded me of the beers i have in my fridge. Mmmm... honey ale (which tastes somewhat like beer spiced with mead. Mmmmm... [home brewed] mead, for that matter).

-- Martin

that just reminds me how good european beer tastes, I really miss it around here..