Nuno Brito

Cool!! Great work, will be included on the next version for sure!

haha.. that was easy.. For a moment I thought in practising some voodoo! I'll clean up the first topic with the recent changes and attach the source code in case someone else needs it. Thank you!

I think this tool has reached a stable state. Kelsenellenelvian, do you think this topic could be posted as stickie? Otherwise I fear it will soon fall into oblivion as more posts get added. I can also release this tool as open source if you wish, guess my goal to create a converter can now be considered complete and will carry on with my work on UXP.

I'll explain some of the steps that are done on UXP. Copy the source windows install files to a target folder Create a liveXP based on the source windows install files Run nLite on the windows install files placed on the target folder UXP will create a copy of your original source files to a target and will let nLite modify the target files. LiveXP is built using the source files and won't modify them. I advice you to use UXP to automate this step otherwise you need to manually rename the I386 folder created by LiveXP as "myXP" and copy all files inside the target folder of liveXP onto the target folder of UXP. The script that automates these steps is here: http://xp.winbuilder.net/uxp/MultiBoot/xp-liveCD.script You rename the liveXP I386 folder to avoid overwritting the Windows Install files on the UXP target. ---- Personally, I think that the cleanest way to do this action is simply overwriting your liveXP project inside UXP with the new one that you're using and prefer. You find your old LiveXP files inside the %basedir%\Projects\MultiBoot\LiveXP %basedir% is the folder where winbuilder.exe is placed. -------- benxhi: thank you!!

Hi kwikshere, I don't have a all-in-one solution but I'm working on platform to combine all possible steps of building and customizing a Windows Install CD/DVD At the moment it already contains WUD to download all possible MS updates, DriverPacks for hardware support and launches nLite for customization and including addons. Benxhi has requested support for WPI (Windows Post Install wizard) and I've spent some time doing an app to convert the nlite addons into the WPI format: http://www.msfn.org/board/tool-addons2wpi-...er-t113992.html I think this might be a good tool for automating the process of creating your DVD with Office, WMP and such. http://www.msfn.org/board/project-uxp-t113249.html The goal is automating all the separate parts of the build process and save time to see the results.

Glad you've found the solution! Modified XP sources are known for erratic behavior as it is a bit unpredictable to know exactly what has been removed or added to them. It should be possible to test the new service pack. Post a request for SP3 support here: http://www.boot-land.net/forums/nativeEx-and-LiveXP-f52.html

hmm.. So I'm assuming that UXP is built fine but LiveXP is not. The files inside that LiveXP version have grow outdated as Galapo has been introducing a lot of modifications and improvements to that project. Do like this: Download the latest WinBuilder.exe binary --> http://winbuilder.net/download.php?list.3 Place it on a empty folder and run WinBuilder.exe Go to the Download Center and uncheck all servers except LiveXP (to only download LiveXP project files) After dowload is concluded, wb should restart itself and you should press the Play button (big blue button) This should give you a good LiveXP project - if you wish - replace the old LiveXP files inside the c:\uxp\Projects\MultiBoot\LiveXP folder with your newer version. If something is still not working as expected, do mention it and we'll figure it out..

Some options: - Disable the UAC and try again - Mount the reg hives from another OS (WinPE/VistaPE) - Use a raw reg hive viewer: http://nunobrito.eu/download.php?view.5 (example)

I think few people expect a stable and ready OS to be delivered from the ReactOS team. This has been done for ages under Linux and there are even DOS driver support. The documentation produced along the way is more than enough to understand what needs to be done and *nix OS's can add good support for working with this filesystem then it would be logical to see this as a much easier task for ReactOS. They simply don't see it as priority and keep ReactOS from being used on real hardware situations. Seriously doubt it would bring a bad reputation as people willing to use it are aware of the limitations and would likely find good ways to use this OS. Also worth mentioning that some developers have already used NTFS.sys driver from Microsoft to add this support but it would pretty much defeat the point of using open source developments if we enclosed a MS file and I never saw this option available ever again. -- Drivers for hardware aren´t a complication - look on driverpacks.net to find support for nearly about every vital piece of hardware.

New 1.2 version made avaialable! Log of changes: - Added new tabs for Help, Paths and Options - Improved progress listing - Added option to use GUI instead of just command line switches - Options to customize default category and paths for WPI, option to keep Temp files - Added a better help text - All settings are saved to addons2wpi.ini to avoid repeating the same actions Download here: http://nunobrito.eu/download.php?view.8 Added all previously requested options and also improved the overall file progress to make it look more smooth. ----------------------------------- I still need more feedback regarding the best way to create config.js - can the line pn=xx be ignored when using pn++ ? This was tested with my list of Addons, if there is any addon that you notice that isn't working, please post the download link so that I can get the same files you're using and see what is wrong. Thank you for all the feedback so far, hope the missing 20% to get this tool completed are getting near to be reached..

Hi! What is the path where your UXP project is placed? In case of doubt, please post the log.html file.

Hi benxhi! Please try placing the UXP project on a shorter folder like "c:\UXP" Looking on the log it also seems that you have disabled the last scripts on your project that used nLite and also the scripts on the "Finish" folder which would build the ISO image.

Olá! The code can't be recycled that easily. I also follow ReactOS for some time and the current development status is nowhere stable nor efficient enough to run apps as we'd like it and this is something that simply makes me sad as I don't want to switch over to linux nor continue opressed by MS licensing and EULA's. -- If you're really interested in pursuing this goal then you might however have better luck with the WINE files since they intend to emulate Win9x behavior and will likely allow replace much of the DLL's with other 32 bit equivalents. The ReactOS team doesn't seem very interested to go anywhere and refuse any suggestion to add slight improvements that would at least make it a minimally usuable OS as NTFS support and care more about finishing the driver support area to use the same Windows drivers. If more people used ReactOS as a work OS then it would surely increase the popularity and feedback. Just sad to see no better alternatives (or "ReactOS") to run common MS based applications.

I like the new logo, could you make the UXP title a bit bigger? Hmm.. What are the paths you're using? Can you post your log.html file here? (Open the log tab after building the projects and click on save log) This might help to understand why it isn't copying the I386 folder correctly. Thank you for this artwork!

Thank you for taking them into consideration. I'm using WPI (also discussed on MSFN) and would like to use your program to apply a customized group of settings on the newly installed Vista. Have you ever thought about adding performance profiles regarding the services that are launched with Vista? There are several registry tweaks that many users find extremely valuable. Look here: http://www.speedyvista.com/registry.html One other suggestion, if could use the forum signature space to include a direct link to the page of Winbubble and this way it would be easier to for other members to visit your site.

Permission? You have my blessing! Funny you mention this as I've already asked a member on boot land a few days ago if he would be available to make a small logo for uxp. Look here: http://www.boot-land.net/forums/Artwork-lo...-UXP-t4141.html Would be really nice to replace the winbuilder logo by an UXP one.

Hi Lawrence, this looks like an interesting program : One of my favourite hobbies is modifying windows installs and I have a few requests: - Can you make it possible to apply the tweaks on external registry hives? - Would it possible to save a profile to a file on disk and then launch winbubble to apply these settings in unattended mode from a batch file?

hello again! This sounds neat, where can I read more about them? ---------- Will look on the scripts for the graphics driverpacks and see what techniques were used after debugging the things posted earlier today that need to be corrected on the next version. I thought it was working good, why do you say this?

Hi Scott, sorry for skipping your comments but I was replying to the previous questions. Hmm.. Version 1.1 should be cleaning up the temp folder for a clean operation when running in unattended mode, will do more testings and try to reproduce the same bug as it should be copying all these files to "%WPIpath%\Install\SVCPACK" and removing the temp folder along the way. But since you found this "feature" usefull, what do you think about adding a small options panel where you would be able to customize this behavior and choose what to do with the extracted files? Maybe I could also add a few more buttons and other users wouldn't need to use the command line to convert addons. Thanks for reporting these annoying bugs, will correct them right away. I'm really happy that you like it, thank you for the feedback!

Thank you for testing, you can use a subfolder without mentioning the full path but I wasn't counting on folders using relative paths like ..\ Is this an important feature to be added? No problem, we can also add support for running the Build_AddOn.cmd and people can decide to run them or not when batch converting a package like this. Another doubt: Is the config.js outputed by this tool being well created under your opinion? Are there any sort of details needed to take into account when adding several dozens of addons together?

New version was uploaded. program now removes all runtime temporary folders added support for unpacking .7z .zip and .rar nlite addons (requires 7za.exe and unrar.exe on the same folder as addons2wpi) Please download the new package as it already contains 7za.exe and unrar.exe which are used for handling other archive formats. http://nunobrito.eu/download.php?view.8 -------- There is no chance of converting the livemessenger with some reliability as it is not (yet) a addon. But after the user runs the initial batch file that will build the addon it will be possible to convert it just like any other addon.

7z is now well supported whenever 7za.exe is placed on the same folder as addons2wpi rar is not being decompressed for some strange reason - anyone knows why this happens with the console app 7za.exe? --- A doubt: Regarding the live Messenger addon you've posted - is it really working with nlite out of the box? Looking at the forum discussion I see people have to manually run Build_AddOn.cmd prior to integrate this addon. Should this step be automated by this tool?

Hi jtdoom! Thank you benxhi, will download right away and check them out. ------- edit: The file structure is identical, will start adding 7z and rar support!

Somehow missed reading your request. I can use the 7zip command line version to add support for all other archive formats and whenever 7z.exe is available on the same folder as addons2wpi then it use this extract tool as default for all supported extensions. http://www.7-zip.org/ But one question: addons in other compressed formats still have the exact same structure as cab ones?

zorphnog, please re-test as it should be corrected now.