mjc

I would suggest PortableFirebird and Bookmarks Synchronizer if you're going to be doing any serious amount of moving =)

service packs first, one thing at a time my friend =)

Bâshrat: Any thoughts on VMware drivers, printers, and/or 64bit?

looks more like it has a space in it ("Documents and") and needs to be a quoted string.

you could certainly do that, but if you want it to be solid(reliable?) you should use raid 1. you cannot make a raid0 in software in windows, you need to use hardware or "hard"ware raid. ("hard"ware being the stuff that usually comes on motherboards or costs less than $100)

most likely spyware. could you run HijackThis and post a log to a pastebin?

takes me a click of a mouse to start vmware, and it gets a whole CPU core to itself. Oh, and I boot it off ISO images, so no need to burn a CD either.

what tells you that you have a prescott? just curious. Try WCPUID from http://www.h-oda.com/ to be sure.

I've decided to use XML to describe all of the hand-made AIOG addons. Here is a Sample Silent Install Description File. Any suggestions? Code-wise I'm currently working on a slipstreamer. I've managed to implement cabinet , 7zip, and rar extraction via the appropriate DLLs. As soon as it's actually usable I will post the source and a binary for testing.

SF's got some funky clauses in their licensing, last I checked. I'm on 100mbit unmetered anyways, so no big deal.

if you putz around with the TSWeb client's javascript (or use rdesktop in cygwin) it will let you specify your resolution (resWidth by resHeight). A 16:9 aspect ratio is achievable but you cannot go higher than 1600x1200. (1600x1024 is the closest 16:9 aspect to this)

404 on sound a =/

awesome; I'm working on giving this beast some structure at the moment. side note, anyone want to design a gui for this thing? I'm terrible at that stuff. I've set up a homepage here: http://325i.org/projects/allinoneguru Write access to it is open to anyone that wants it, assuming they can help of course =) and as soon as there's some feasible code I'll be posting nightly binaries and source.

FALSE alarm I was trying to add a 32bit driver to a 64bit OS. doh!

netbooting support (for testing RIS) fast formatting in 2k/xp setup (due to sparse file creation on ntfs) officially (and unofficially) supports a lot more operating systems than VPC (appears to emulate more hardware...) Has a lot of enhancements to speed up things that are traditionally slow on a real pc (such as fdisk.exe in dos if you decide to use it for whatever ungodly reason) some versions of it will emulate more than one CPU Personally I use Virtutech Simics for all of my non-x86 simulation needs. the x86-64 simulator is really helpful for testing x86-64 nlite. Well worth the price, IMO.

Cooperation meaning help of any kind (programming, docs, source, candy...) of course. By no means do I expect anyone to just sit back and watch if they do not want to.

I would by no means consider writing such an app stealing. After all, credit will be given where credit is due... Without the help of everyone that's ever put work into this stuff I certainly would never have dreamed up such an app.

I plan on implementing this tool, as there is a need at the company I work for, regardless of whether I have aid from others or not. As far as discussion, that's what this thread is for =) Developers can choose to support me or do their own thing, whatever works. I'm not forcing anyone to do anything. As far as rethinking, if you mean because it would obsolete a lot of work, I feel that this is the best path to producing the product we've all been waiting for =) if you feel otherwise please explain how and why.

To clarify, we need a RIS tool, I'm creating one. No commercial fishiness involved. I own the copyright to my own code, so I'm free to release it under the GPL.

if nLite is in C#, porting it to C is trivial. Most of the code in most of these applications is actually very straightforward, and with some thinking and access to the source, it would be very easy to port and/or integrate all the features. I'm trying to reduce the amount of work done in the future by unifying all these tools. If it takes a lot of porting, rethinking, retooling, or whatnot, so what? Also, as I'm being paid to create this, I have all the time in the world to crank out updates, fixes, manuals, and whatnot. The only licensing restrictions that would prevent me from publishing the whole or part of the tool would be restrictions by the creators of the current toolset, as well as restrictions on Microsoft or other vendors' code (for example the driversets...)

the problem with using other peoples' software is speed. Hand-crafted and hand-optimized C can be tons faster than simply launching a bunch of separate tools. If I am able to release it (in whole or part) under the GPL, not only would it be faster, but the source would be modifiable by all. (think: no need to create another tool when you can just extend AIOG)

I'm in the design stage of creating an unattend app to demolish all other unattend apps. It will contain each of the unique features of nLite, RyanVM's updates, BTS's driver packs, XPize, PowerPacker, MiniPE, and any other tools people can recommend. I'm being paid to do this as part of my 9-5 because we need such a tool internally, but I will make the program freely available, under the GPL if licensing allows. It is evolving out of a script that I've been working on for a few weeks. I've decided that 100% of the process beyond selecting what is needed and not needed can be automated and therefore should. Current features include: Accepts any Windows XP or 2003 version set (will do more than one version at a time soon) Downloads and slipstreams the appropriate service pack Downloads and installs the latest RyanVM pack (this should instead be downloading and installing the latest hotfixes directly from MS in the future) Applies nLite tweaks (nLite is currently used for slipstreaming and ryanvm anyways, but I'd like to roll all of these functionalities into one giant app) Applies BTS driver packs (should download all the drivers separately in parallel from each manufacturer) Creates RIS installs (with license key management to come.. different .sif files for each key, permissions set to the user, computer, or group policy that is allotted the keys) Creates a WinPE disk (to come; with preferred tools only as an option) The app will be written in C, because it is the language I am most comfortable in, and because it is the fastest for such things. I plan on including the functionality of burnatonce and cdimage.exe as well. cdimage.exe's important function (optimization) is very easy to implement. If you are interested in working on this project with me, let me know. I would appreciate keeping feature requests and whatnot to a separate thread as I expect this one to grow fast.

group policy install would be the best way to handle this methinks, but I'm not sure what scan you're talking about. perhaps this? http://service1.symantec.com/SUPPORT/ent-s...src=bar_sch_nam

I am using RIS and am in the process of developing a database system that would incorporate RyanVM's pack, BTS driver packs, and nlite into an auto-updating system complete with license management ( user X gets license Y for version ABC ) as well as DigiWiz's MiniPE. It would be trivial to allow this to also create all windows dvd sets. So far, the ryanvm & nlite parts are done, and minipe boots via RIS. If anyone's interested, please reply or start a new thread or something.

I can host your files as well if you'd like, 100mbit server in Washington, DC, USA.