Search options (Page 1 of 2)

Hi Siginet!

If you liked wb just wait for next stable release. On our beta testings the script processing speed has been reduced to half - which means that a huge project like uxp would take a little more than 10~20 minutes to complete a full boot disk.

Yes, we're doing this with wb scripts.

Each wb project has a server to download files from. On the root of the folder there is a text file that will list all files that are supposed to be present on the server along with their respective versions. If it's a binary file then we use MD5 for a quick checksum compare with the file on disk (if any).

Sure there is, Carfan from boot-land has become the UXP project manager and already began working on the next version since two weeks ago. Now it's the perfect time to add more tools such as yours.

If you get in contact with him, I'm sure you'll both get along quite well.
http://www.boot-land.net/forums/?showuser=5809

On my side, I'll be working on the winbuilder beta and stay around to explain whatever doubts you have regarding anything wb related.

UXP is one of my favorite projects so it would be a honor to see included some of your tools on this platform.

Good luck with the codings!

It's a true nightmare to support .NET inside Windows PE 1.x/2.x and when thinking about a tool to customize Vista it would be wise to think about portability.

Also the same applies for everyone else looking forward to run these tools on other OS's like reactOS or *nix's wine in the future.

Look at the discussion for the mentioned tool from AlbertS and read the amount of posts regarding people trying to run it let alone do some real work.

So many other coding languages available and I'd really prefer to see java being used as it is much easier to carry around and install.

-------------

Why should a person install a 200Mb framework to run a 200Kb program that could be coded using any open-souce or freeware available coding language like autoIt and such?

I say move away from MS claws to gain overall work efficiency.

These are excellent news!!

Welcome to the testing team!

Hi Jaak!

I completely subscribe your opinion, my laptop uses a Vista x64 and I guess that these installs are far more popular than XP x64 ever was.

I'd be happy to become just another beta tester but if you need additional hands to work on this goal then it would be honor to be your right hand!

These are good news!

So what should the first step be to start working on this?

Windows Post-Install Wizard is also in the process of being automated.

A tool to batch convert nLite addons into WPI packages was created to ease automated creation of a config.js file needed by WPI.

http://www.msfn.org/board/tool-addons2w … 13992.html

Please do sign me on the testing team - it would make really happy.

There are also a few suggestions by members on msfn that could be added so I'll work a bit longer to see them included on a newer version and also help out with any testings needed on driverpacks.

Also working well enough on most machines I've tested at my workplace

Used source:
XP PRO SP2 Portuguese
+ nlite and addons
+ updates from MS
+ All latest driverpacks available on the download page this monday

Hardware:
Pentium IV
256Mb~512Mb
---

Rebuilt several times in different configurations and also tested under Virtual Box emulator.

Only noticed a glitch when adding the graphic card driverpacks as it was needed to cancel the generic monitor display - nothing to do with mass storage anyways.

Hi Helmi!

Thanks for trying, I've finally managed to get some real hardware were I could properly test things.

It seems that xpsetuplauncher itself is not working well and needs some extra parameters when calling winnt32.exe

On this project you can install XP from command line using WINNT32.EXE /MAKELOCALSOURCE - this should be enough to launch the setup process and place all files on disk - do you know any way to workaround this limitation?

Also been having an error with DPSbldr.exe when installing windows and no driverpacks seems to get installed - looked up the forums and found no reference to this file, but was hoping you would have a better idea on why KTD is not being applied - is something needing to corrected on the scripts that add support to driverpacks?

-------------------------

We also use individual downloadable scripts/apps because each script can use it's own version and people might not need them all (some are too big sized to be included by default)

Would be really great if you or anyone else with more experience could help us correctly implement the driverpacks itself - as you see - it's possible to completely integrate it along with other tools in a automatic fashion but this still needs to be tested and improved and I lack a lot of experience installing windows (our boot land talks are mostly focused on PE based boot disks).

No changes need to be made on DriverPacks - and hopefully this sort of developments will become acessible to a whole lot more people that will also certainly contribute to keep this project alive and well.

We are however discussing a complete replacement of the windows install setup and directly install windows on a machine without fuzz - this would make windows install probably be complete under less than 10 minutes (no need to make local sources or text mode setup) with extra flexibility to apply this as we need and already running from ISO images or USB drives.

Look here: http://www.boot-land.net/forums/index.p … topic=2690

Windows Install is simply too limitative and we already know how to do it better..  :)