Nuno Brito

Hi Damian! I meant both types of unattended install. Use a switch to install silently on my system Have the option to use as nlite addon (for example) btw: I've noticed that some details were only modified after rebooting my machine for the second time (for some reason, don't know why) - after this everything (including title bar as described above) worked really good. There are of course a few glitches but in overall this has worked very good right from the start and now it should only be a matter of perfecting things. I like the icons updates - do makes XP look better. Let me know if there's something I can test and give feedback - I'd like to help somehow.

This is very good work! Feedback: - As mentioned - the disabled tabs are deceiving - they should at least be kept hidden to avoid confusions - You should warn people that reboot is needed after patching is complete - I use the task in vertical mode at the left of my screen and after clicking the "orb" button there is "ghost shadow" left. Request: Can this procedure be slipstreamed on a windows install? Thanks. I like it

Good work - I've also presented your project on boot land --> http://www.boot-land.net/forums/index.php?showtopic=3628 This might be useful for some of the projects regarding XP offline sysprep and install.

AeroXP is already going on a 2.88Mb sized XP disk.. http://blog.boot-land.net/xp-in-a-288mb-fl...isk/2007-12-08/

Thank you for this effort - it's a very good package.

If no file is associated the icon should be visible anyhow even with no app associated - but when you install 7zip then it might overwrite your energize settings. Thanks for replying - but have you downloaded the latest beta?

*BUMP* It's been a few days and no replies - nobody uses energize?

Look on the VistaPE forum discussion and see how explorer is implemented under WinPE 2.0 using all versions of Vista Install DVD. It would be good to create a tutorial explaining all the steps but this process has already been completely automated over an year ago and people there are even moving to much more extensive functionality without requiring manual steps.

I had exactly the same issue mentioned on this thread when starting up with xpize last week - no point in creating a new thread requesting command line support so I add my opinion and (hopefully) one day it can be added back. In the meanwhile it's good that new xpize users can understand that there is no command line support at the present time and that some older threads retrieved by google can induce in error. http://www.google.com/search?hl=pt-BR&...+Google&lr= http://unattended.msfn.org/unattended.xp/v...e3446f8f103420/

Hi, Is the download package corrupted? I've tried downloading using a few download managers and I keep seeing the message - "This Installer is corrupt" (in french) Or am I the only person getting this message? Thanks..

Kykc, here's the error outputed - hope it helps: EventType : clr20r3 P1 : updater.exe P2 : 0.6.5.0 P3 : 47501f56 P4 : updater P5 : 0.6.5.0 P6 : 47501f56 P7 : 24 P8 : 13 P9 : system.nullreferenceexception I've uninstalled your program, restarted the machine and installed fresh again - same result. ---------------------- I'm using a Windows XP Home Edition x86 Portuguese with SP2 on Dual Core CPU with 1Gb RAM machine .NET on my machine Framework 1.1 Framework 1.1 hotfix (KB928366) Framework 1.1 Portuguese Language Pack Framework 2.0 Other .NET apps are running correctly. ------------------------ On my humble opinion I'd say that .NET is the future of Windows Programming because it was declared as standard.. With other coding platforms this Updater app would still run on Win9x, XP, ReactOS and Vista without these issues/dependencies.

WinRoot is a very small project meant to produce a 5Mb bootable operative system based on Windows XP. It will boot this modified Windows OS into the Native Command Line Interface using a modified SMSS.EXE based on the TinyKrnl project research. This project is completely based on the excellent work by "Windows OCManage" from the BETA Archive forums - you can find the latest improvements to this development on the respective discussion page here: http://betaarchive.co.uk/forum/viewtopic.php?t=2772 http://winbuilder.net/download.php?view.6 This project is created under 11 seconds.. (also being discussed on boot land --> http://www.boot-land.net/forums/project-WinRoot-t3537.html)

Please post this question on the VistaPE forum were the author or a member might help solve this question. Based on my experience I'd say that you need to adapt VistaPE to avoid any links to CD locations. WinPE 2.0 boots completely into RAM by default but VistaPE will link back to the removable media to save RAM usage on very big sized apps (like openoffice for example). Remove all apps included on your build and try again.

Tried both versions you have available for download on your site and none started - both gave error. nLite works ok on my machine and I thought .NET 2.0 was working well too. If you're just starting out this app - please consider using another platform - very little advantages in using a heavy .NET since delphi, autoIt and Visual C produce very small and standalone exe's that work on both old and new machines well enough. (just an opinion thought) Thanks for this app!

Thanks for the quick reply! I've done some extra work yesterday and I'm testing automated integration with nLite. So far things are looking good enough and I can write the registry to match the selected download folder. Only one detail noticed by other members - some files don't seem prepared to be directly integrated, would be good to have some nlite aware options. Good luck with your programming.

Hi, Just introducing myself to WUD and I'm surprised to see such a nifty little tool - will surely give it a lot of good use to build install CD's I've read the topic about unattended builds but it could still use a few more options (if possible). The ideal configuration would be using a standard INI file instead of the windows registry. This would help in two things 1 - Make WUD portable (put on a pendisk or any other folder) 2 - Let other apps configure all possible options inside WUD and run it with these customizations -------------------------- A possible INI file could perhaps be similar to this: [options] default_update_list=Windows XP aAbBcCdD download_folder=c:\XP-Unattended\Addons Product_as_subfolder=False Category_as_subfolder=True Show_Publish_dates=False Show_description_tooltips=True Minimize_to_tray=False Remove_unlisted_files=False [proxy] username= password= address= port= use_proxy=False use_authentication=False authentication= ------------------------ Would also be good to define a location for placing all the UL files instead of the root folder or it can get a bit difficult to organize the folder. Hope this feedback helps - good work with WUD!

Support for command line parameters would be a nice welcome back..

Try VistaPE - it will create your WinPE 2.0 boot disk along with support to explorer as shell - you'll need to use your Windows Vista as source to copy needed files. You find the direct download link here: http://vistape.boot-land.net/eng/index.html And respective project discussion: http://www.boot-land.net/forums/VistaPE-f51.html Good luck!

You can create a PE boot disk as small as 30 Mb and use it launch the windows install process if you wish (launch the setup files from another folder not as I386) - I've never tried to use the same folder as both source and target at the same time (mostly for fear of corrupting the source while testing) This is a good question, I wonder how possible it can be? About liveXP and PE environments - there's a lot of things that can be added and customized, and this is done trying to meet your expectative of functionality/ISO size/speed. Which USB devices wouldn't autorun? At this moment there is very good support for removable media USB devices, and you can add more drivers as needed. There is also a full blown live XP project that can be found here: http://www.boot-land.net/forums/MobileOS-t1218.html Boots from USB and the image is very light. Unfortunatelly the process to build it is somewhat complicated at this moment, so I recommend if you the PE environments as mobile platform while this newer project gets further improved. If you post which programs you were trying to run, maybe it would be easier to make them work than going for all this sort of effort. In most cases you only need to add a few missing dependencies/services or registry keys.

Try asking in the VistaPE forum - maybe Nightman can clear you doubts: http://www.boot-land.net/forums/VistaPE-f51.html

Hi Fly! It's been over a year since batcher on 911cd.net and we're all pretty much alive and still having fun with boot disk projects that grown quite a lot in usability. I do remember you very well, thanks for all the help back on those days!

Boot discs can and should be reduced if needed. You can build a PE based on XP / 2003 sized from 14Mb up to an ISO with explorer as shell using as low as 31Mb. These are boot disks completely stripped from unneeded features. WinPE 2.0 can also be reduced removing the unneeded components that come by default, if needed it will boot sized under 50Mb. Look here: http://vistape.boot-land.net Where you can find more details on how to tweak WinPE 2.0 from WAIK and Vista DVD's - this is valid not just for removing but also for adding extra programs and customizing things to work as you expect. If you're still looking for manual ways to decrease even more the size of your WinPE 2.0 could you please be more specific on how you plan to use this boot disk?

Partition magic won't work because it will need a writable (temporary) folder. You should run it from a ramdisk and point the %temp% variable onto it. Read here: http://www.bootcd.us/BartPE_Plugin_Details...oot-CD-Rom.html It's been a long while since I've last used partition magic, but you should google a bit and I'm sure that a lot of solutions will come up to solve your matter. For adding sound support you will need to use XPE under bartPE - there is the reatogo project (bartpe derivated) wich will automatically add your driver support - but it is not the only solution just google around and you should quickly find solutions for all your doubts. Let me know how this works out for you, good luck!

Nightman has already succeeded on creating an automated creation/modification process for building these PE 2.0 images using explorer as shell from ISO's that go from 60 Mb to 200Mb depending on what you need to add. Here's a list of scripts already available to add: http://vistape.boot-land.net/eng/plugins.html And the support forum for vistaPE where more information can be found regarding PXE: http://www.boot-land.net/forums/VistaPE-f51.html http://www.boot-land.net/forums/boot-WinPE...-PXE-t1220.html Good luck and have fun!

Thank your for these great replies, I've learnt quite a lot from them!