Jump to content

My Quest for the Perfect Unattended CD/DVD


Recommended Posts

I'm just really confused. I've got 19 years of IT under my belt, but it seems like there are always 2 or 6 or even 10 ways to do something. But in the area of building customized Windows CD/DVD routines, it seems there are QUITE a lot more ways to do this old game.

Let's review:

If I wanted to build an Unattended CD/DVD to install Windows on a PC, I have these options to squeeze, modify and re-configure the standard stuff that goes into a CD/DVD:

-> Microsoft [http://support.microsoft.com/kb/216258]

-> NLite

-> PowerPacker

-> Windows Unattended CD Creator [http://www.vitaligraf.de/en/]

-> SysAngel Software Windows CD/DVD Creator [http://ping.windowsdream.com/index.html]

-> Other Options (I swear to god there are like 4 others, I promise I'll find them and post them here)

Now, if I wanted to bring the system up-to-date with respect to patches, updates, etc. we have:

-> RyanVM

-> AutoPatcher

-> Nlite

-> Powerpacker

-> Windows Updates Downloaders

-> Driverpacks [http://driverpacks.net/DriverPacks/]

-> (Again, there's got to be 15 other ways to do this)

Sweet Mary on a Bike!!

Can anyone, authoritatively, describe a system where you can review the BEST options available and figure out what components to patch together to get a system working?

Here are my own personal goals:

(1) Install Windows XP (I have a specific edition, XP PRO SP2)

(2) Install with preset options (unattended including formatting, partition sizing, windows components)

(3) Customize the install before first-user (new users created, registry settings imported)

(4) Have the Windows installation updated with patches (from Microsoft)

(5) Have customized software installed automatically (base software) and then options to choose additional 3rd party packages

I think, with some study, sweat and blood, I can probably get #1 and #2 figured out with NLite, Powerpacker, or (other) similar. But #3, #4 and especially #5 worry me.

First, with #3: Many registry 'options' only apply to certain users, so the logical necessity is to apply those to all. I'd have to figure out which ones they are and figure out how to apply them to other registry trees, or just use 'default user' and so when they log in it's applied (first time).

Then, with #4: This seems like a never ending battle. You almost need a daily, or weekly build to incorporate Microsoft's Tuesday patch days into this process, and rebuild/reburn your custom CD/DVD. That doesn't bother me. The bothersome part is understanding which method is superior for 'slipstreaming' them. In reality, if it's just a big arsed pain, I'm going to put Autopatcher and it's updated components into the CD and trigger it after first boot, etc. That seems most logical. Why re-invent the wheel?

Finally with #5, it's probably the least worrisome -- but then again, I'm going to have to figure out how the per-user installation options are applied, etc. Finally, I'll have to have a wget-incorporated build system which goes out to the various sites, downloads the newest releases, and rebuilds them into the custom discs on a semi-periodic basis. Hoping, of course, that functionality and switchology hasn't changed for the package or the installer.

FINALLY and MOST IMPORTANTLY, there lies the issue that, with all of the above, it would seem that a 'typical' unattended install will jump to an hour or more. Here's my question -- that's A LONG time for some things I just don't want to mess with, especially on many computers.

Here's my final question and big point:

Has ANYONE figured out the DEFINITIVE, MASTER method for sysprepping an existing Windows XP PRO installation so that it can go onto just about any hardware? If not, and that's what I think, then we're stuck with the actual installation process (and necessary F6 pressing) for that hardware which is just too new and cutting edge to be supported by any kind of Ghost/Sysprep method described.

With that being said, wouldn't it be possible do to a completely customized unattended install, and GHOST the machine AT THE POINT where it reboots from the first blue screen setup (after partitioning, formatting and copying files). Granted, we'd have to PRESTAGE some stuff (like the various install things), or put that back onto the ghost DVD so that after installation, #5 can pull back from the DVD.

But -- thinking aloud -- wouldn't this allow for the unambiguous installation of XP onto many different hardware sources and shave some time of the already long install (possibly 10-15 minutes)??

Thanks all for reading this far...

Link to comment
Share on other sites


Wow! I can't ever remember seeing this question phrased like this before? Sounds like you have done your research but, you forgot to mention the most important site of all!? http://unattended.msfn.org/ :blink:

While there are many ways to do this? They are all error prone or limited for one reason or another. The final solution depends mostly on your knowlege of Windowz install routeen, and update process. Program setup routeens and their installers. Familerarity of windows command line and/or scripting languages like perl/rexx.

If you are or want to be experienced at this http://unattended.msfn.org/ is an exellent resource that will walk you threw all of this.

A much easier way and the most popular method on this forum is to use the combined work RyanVM, NliteOS, BTS_DriverPack, WPI in that order with exceptions. This method provides for a reletivly intergrated solution that is easy to duplicate on a monthly basis. The biggest problems of this system is the individual pieces of software are not mature and will have variouse major issues most of which can be overcum along with signifigant changes between versions. I also don't like having to download all the files needed over and over again since neither RyanVM or BTS_DPs provide any way of updating and existing set of files.

Historically I prefrered to use automated batch files, pre-patched files and misc assortment of utilities. Recently this has become more difficult and time consuming as changes in the process of files and conflicts have been more difficult to overcum.

Installing software is a whole other process for me. Some here like to intergrate other software into windows I386 folder. I to create silent installers that can be installed after the registry is created so I can install later on other machines of choice without install and still keep the itegrety of the softwares uninstall/repair procedure. For silent installs I use a custom batch file that takes advantage of NirSoft zipinstaller and NirCMD, 7zip, iexpress and USSF. This works for the majority of installs and for everything else I dissaseble the install or use Autoit. Then the software installs can be managed with WPI (Windowz Post Install Utillity) This is the easiest way to have default and custom choices in what software is installed and still have it automated.

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

Going after your questions.

#3 Updating Registry:

This is a trivial matter. There are a couple of ways of doing it with the biggest decision being when to apply so you affect the right users. Nlite uses the hive*.inf but, you may also use a batch file and then you can make that batch file a silent install. Regestry commands can be in either format: (REG IMPORT "settings.reg") and\or (REG ADD "HKLM\Software" /ve "" /t "REG_SZ" /d "Data of Value" /f) and then used at T-39 for all users or T-11 for current user (Administrator)

#4 Windowz Updates:

There are two basic popular methods:

1.) The simplist and most efficiant is RyanVM Update Pack and Addons.

2.) Download the Windowz "Bulk Update" .iso package compilations from MS. http://support.microsoft.com/kb/913086

I haven't had much luck with autopatcher programs? Somethings to keep in mind about MS_Updates is that they sometimes nullify each other. They must also be installed in the order of release and old versions must not be used if a newer one is available.

#5 Sofware install:

This is not an issue again, like the registry is the choice of install time is the most important. Silent installs are will documented on this forum.

Time?:

The time of install can vary widely depending on what you have done. Here are some personal examples:

Windows 2000 minimal with no driver or software on P4 800mhz === 12 minutes.

Windows XPSP2_PRO with no drivers and minimal software with 1CD on AMD64 3000+ === 18 minutes

Windows XPSP2_PRO basic workstation with drivers and programs with 1CD AMD64 3000+ === 35 minutes

Windows 2003 Server with Drivers and 3GB of programs and DATA with 1DVD Intel Optron Quad Core === 100 minutes

These times can be lowered if you reduce the compression of source files.

Finnaly?:

An unattend install is just that and totally possable with Windowz 2k and newer. A unatended install and immediate GhostBU would be silly since the install alone is more flexable with the MS way of things.

If you use the BTS_DP then you will not need or be able to press F6 for install of extras drivers for just about all primary hardware devices.

After creating my unattend DVD the only step needed to install a different configuration on variouse machines is to put the appropriate winnt.sif file on a floppy, boot the machine and come back an hour later to a fully setup machine ready to go. Including all updates, servicepacks, drivers, software including users and various settings.

Start by downloading the appropriate software and have fun.

- RyanVM Update pack and addon pack

- NliteOS

- BTS_DP

- MS Virtual Machine

For Software Installs

- WPI

- 7zip or WinRAR

- Universal Extractor

- NirCMD and ZipInstaller nirsoft.com

You now have enough info just to get started let us know if we can further help.

Link to comment
Share on other sites

Wow! I can't ever remember seeing this question phrased like this before?

Wow! I cannot remember the last time someone took so much time and effort to help someone. I *really* appreciate your effort here.

Sounds like you have done your research but, you forgot to mention the most important site of all!? http://unattended.msfn.org/

lolz... yeah, I figured I would be pointed back to this. I consider unattended.msfn.org the best way too, it's just that I thought it was still all a bit outdated. I remember combing through that about a year or two ago, and it was all great info. The one thing that p!$$ed me off was the fact that Microsoft made you use a winnt.sif from a floppy. How double-stupid is that?

While there are many ways to do this? They are all error prone or limited for one reason or another. The final solution depends mostly on your knowlege of Windowz install routeen, and update process. Program setup routeens and their installers. Familerarity of windows command line and/or scripting languages like perl/rexx.

I know enough to know what I don't know. But the bottom line is, whatever is required, I can learn in a very short amount of time. Nothing really scares me, whether it's perl, vb or (gulp) Windows powershell. But, to be honest (don't laugh), my favorite scripting environment is good old Windows CMD shell.

...and the most popular method on this forum is to use the combined work RyanVM, NliteOS, BTS_DriverPack, WPI in that order with exceptions.

Sigh, I figured. It's just that, well, there seems to be no SINGLE high level guide to do this. Maybe I haven't searched and looked enough. I will. I like all of this information, it's just that sometimes, you really have to read, read and re-read everything to make sense of it. Maybe I'll be the person that will put it all together in one, comprehensive guide, etc.. who knows?

For silent installs I use a custom batch file that takes advantage of NirSoft zipinstaller and NirCMD, 7zip, iexpress and USSF. This works for the majority of installs and for everything else I dissaseble the install or use Autoit. Then the software installs can be managed with WPI (Windowz Post Install Utillity) This is the easiest way to have default and custom choices in what software is installed and still have it automated.

I use the FREEWARE (hard to find now) version of WinInstall LE 2003 -- not the crippled one that shipped with Windows 2003, but the ORIGINAL full Freeware one that shipped with Windows 2000. It's actually fully functional, and still works to this very day on most stuff I package. I can do that, Nullsoft Scriptable Installer System (NSIS) or any of the plethora of others (heard of InnoSetup v 5)? They're all good, and I can package my butt off - no problems here. Sorry, that was a stupid question on my part. It's just the registry stuff (which you mentioned later) which worried me.

#3 Updating Registry: This is a trivial matter.

Lol! Trivial to those who have done it 15 times. I need practice. I'm very familiar with the registry (reg.exe) tool included in XP and 2003, so that's no issue.

There are a couple of ways of doing it with the biggest decision being when to apply so you affect the right users. Nlite uses the hive*.inf but, you may also use a batch file and then you can make that batch file a silent install. Regestry commands can be in either format: (REG IMPORT "settings.reg") and\or (REG ADD "HKLM\Software" /ve "" /t "REG_SZ" /d "Data of Value" /f) and then used at T-39 for all users or T-11 for current user (Administrator)

Ok, I'm lost there. I need to review the unattended.msfn.org for more detail on the T-39 and T-11 phases, I suppose.

#4 Windowz Updates:

There are two basic popular methods:

1.) The simplist and most efficiant is RyanVM Update Pack and Addons.

I hate to say it, but 'simple' is a term I cannot relate to. Until I find a high level comprehensive guide to WHAT RyanVM, Update 'Packs' and 'Addons' are, it's like the days of compiling custom linux kernels for IPCop. It's just darned confusing until you've done it 15 times, as I mentioned earlier. I guess it's just alot of hard work is required before I can really understand it. Shame.

2.) Download the Windowz "Bulk Update" .iso package compilations from MS. ... 913086...

:( This is security updates only, right? My point is that I wanted ALL Windows updates (security, critical, patch, component update, etc) POST SP2 possible, up to date.

Again, I've heard things like "Oh, use MBSACLI.CMD and it will XML out a listing of what you need." But again, I fear this is SECURITY only. And again, SECURITY is only part of the patch universe, right? Point being, if there were a utility which could list every patch on a given day post-SP2, I wouldn't mind downloading the delta-changes of those patches and putting them into a directory and rebuilding with (choose one: nLite, etc). But, sigh, sadly, I don't think we're going to find that out anytime soon. I asked the guys in the Autopatcher forum, btw, and that (above) was the response I received (use MBSACLI).

This is not an issue again, like the registry is the choice of install time is the most important. Silent installs are will documented on this forum.

Thanks, homework ahead.

Time?

Is money. Lol, couldn't resist. But seriously?

I had an admin on my team once that found a way to use the Compaq Smart Start scripting toolkit, but he was able to ghost the process at the first blue-screen text-mode portion reboot, saving about 15 minutes per install.

If that kind of time isn't worth it (and I suppose there could be issues), then I'm just going to skip this part of my question and say, thanks, you're right.

Start by downloading the appropriate software and have fun.

- RyanVM Update pack and addon pack

- NliteOS

- BTS_DP

- MS Virtual Machine

For Software Installs

- WPI

- 7zip or WinRAR

- Universal Extractor

- NirCMD and ZipInstaller nirsoft.com

Yeah. I've got my weekends cut out for me for the next several months, huh? :)

Link to comment
Share on other sites

2.) Download the Windowz "Bulk Update" .iso package compilations from MS. ... 913086...

:( This is security updates only, right? My point is that I wanted ALL Windows updates (security, critical, patch, component update, etc) POST SP2 possible, up to date.

Again, I've heard things like "Oh, use MBSACLI.CMD and it will XML out a listing of what you need." But again, I fear this is SECURITY only. And again, SECURITY is only part of the patch universe, right? Point being, if there were a utility which could list every patch on a given day post-SP2, I wouldn't mind downloading the delta-changes of those patches and putting them into a directory and rebuilding with (choose one: nLite, etc). But, sigh, sadly, I don't think we're going to find that out anytime soon. I asked the guys in the Autopatcher forum, btw, and that (above) was the response I received (use MBSACLI).

I don't have all the answers for you, and yes, I also seek them.

Working with this professionally you have deadlines and you want it to save you time, as time is limited.

But regarding updates, you really should take a look at this little amazing app.

http://www.msfn.org/board/index.php?showforum=147

Link to comment
Share on other sites

lolz... yeah, I figured I would be pointed back to this. I consider unattended.msfn.org the best way too, it's just that I thought it was still all a bit outdated. I remember combing through that about a year or two ago, and it was all great info. The one thing that p!$$ed me off was the fact that Microsoft made you use a winnt.sif from a floppy. How double-stupid is that?

unattended.msfn.org is a little outdated but some things may never change although MSVista is a different animal. The winnt.sif may also be placed in the I386 Folder or you may use a floppy. I use a floppy because it allows me to change the install per-machine. Although I do wish the install would look for USB drive instead.

I know enough to know what I don't know. But the bottom line is, whatever is required, I can learn in a very short amount of time. Nothing really scares me, whether it's perl, vb or (gulp) Windows powershell. But, to be honest (don't laugh), my favorite scripting environment is good old Windows CMD shell.

No laughing here it is what MS would prefer i'm sure? It is good for most things except reading databases or even Comma Delimited files? I prefer perl because I work on many types of machines including linux and Apple so using a cross platform language is more convenient. Recently I ran across Rexx and it is too easy not to use.

Sigh, I figured. It's just that, well, there seems to be no SINGLE high level guide to do this. Maybe I haven't searched and looked enough. I will. I like all of this information, it's just that sometimes, you really have to read, read and re-read everything to make sense of it. Maybe I'll be the person that will put it all together in one, comprehensive guide, etc.. who knows?

It's really not needed if you use the RyanVM, Nlite, BTS_DP combo-method and you are conservative with your choices with nlite and don't push the envelope by removing the apps MS intends to be used for evil? Like IE, OE and WMP. I ran into msfn.org years after my first unattended windows98 install and I have not seen anything that compaires. You won't find some of the info here on the MSDN. The only trick I can think of is "TIMING"! The order of everything is very important. Everything you need to know about the install is in the MS Deployment Tools Help File (Deploy.cab)

I use the FREEWARE (hard to find now) version of WinInstall LE 2003 -- not the crippled one that shipped with Windows 2003, but the ORIGINAL full Freeware one that shipped with Windows 2000. It's actually fully functional, and still works to this very day on most stuff I package. I can do that, Nullsoft Scriptable Installer System (NSIS) or any of the plethora of others (heard of InnoSetup v 5)? They're all good, and I can package my butt off - no problems here. Sorry, that was a stupid question on my part. It's just the registry stuff (which you mentioned later) which worried me.

I like WinInstall but, it is not common freeware so I did not recommend. And most of the others are too complex for use by most people? My personal needs require something faster and what is faster then answering a couple of basic questions from a batch file and waiting for the silent exe and a decription file including hash sums? I sounds like you also have a system you like and if you use MS_RIS then .MSI files are the only way to go.

Lol! Trivial to those who have done it 15 times. I need practice. I'm very familiar with the registry (reg.exe) tool included in XP and 2003, so that's no issue.

Officially I think the number is close to 300 times? Feels like 1,000,000. :wacko:

You are right? MS treats the registy like an unsupported feature or power toy? Instead of the essential location of most settings??? (Ba$terds) It just so happens that secrecy was the reason the registry was my first real knowlege of windows internal workings. You can avoid allot of headache by backing up the Registry before ANY editing. (REGEDIT.EXE /E %SYSTEMDRIVE%\RegBU.reg) Along with a windows restore disk or something like PE or Winternals ERD.

Ok, I'm lost there. I need to review the unattended.msfn.org for more detail on the T-39 and T-11 phases, I suppose.

http://unattended.msfn.org/unattended.xp/view/web/13/

I hate to say it, but 'simple' is a term I cannot relate to. Until I find a high level comprehensive guide to WHAT RyanVM, Update 'Packs' and 'Addons' are, it's like the days of compiling custom linux kernels for IPCop. It's just darned confusing until you've done it 15 times, as I mentioned earlier. I guess it's just alot of hard work is required before I can really understand it. Shame.

Lol! IPCop and its Kernel... that used to be painfull when is was a offshoot of smoothwall? Now that it is LFS things are a bit simpler now. The process as described is allot easier then you are making it sound. There are many users of this forum that have limited PC knowlege with their own sucessfull builds. RyanVM update pack are very straight forward. The process he uses is identical to the way MS would have done it, if you were to have done it manually one by one only he just combines all the files together. You should just try it and then ask questions when you have problems? Everything you want can be easily enough accomplished.

:( This is security updates only, right? My point is that I wanted ALL Windows updates (security, critical, patch, component update, etc) POST SP2 possible, up to date.

Here is the current list from all the CDs for winXP and IE

MDAC28-KB911562-X86-ENU.EXE
MSXML4-KB927978-ENU.EXE
MSXML6-KB927977-ENU-X86.EXE
NDP20-KB917283-X86.exe
NDP20-KB922770-X86.EXE
OE6.0SP1-KB911567-WINDOWS-2000-XP-X86-ENU.EXE
WINDOWS-KB913433-X86-ENU.EXE
WINDOWSMEDIA-KB911564-X86-ENU.EXE
WINDOWSMEDIA10-KB911565-V2-X86-ENU.EXE
WINDOWSMEDIA10-KB917734-X86-ENU.EXE
WINDOWSMEDIA8-KB917734-X86-ENU.EXE
WINDOWSMEDIA9-KB911565-X86-ENU.EXE
WINDOWSMEDIA9-KB917734-X86-ENU.EXE
WINDOWSXP-KB901190-X86-ENU.EXE
WINDOWSXP-KB908519-X86-ENU.EXE
WINDOWSXP-KB908531-X86-ENU.EXE
WINDOWSXP-KB911280-V2-X86-ENU.EXE
WINDOWSXP-KB911562-X86-ENU.EXE
WINDOWSXP-KB911567-X86-ENU.EXE
WINDOWSXP-KB911927-X86-ENU.EXE
WINDOWSXP-KB912919-X86-ENU.EXE
WINDOWSXP-KB913446-X86-ENU.EXE
WINDOWSXP-KB913580-X86-ENU.EXE
WINDOWSXP-KB914388-X86-ENU.EXE
WINDOWSXP-KB914389-X86-ENU.EXE
WINDOWSXP-KB914798-V2-X86-ENU.EXE
WINDOWSXP-KB917159-X86-ENU.EXE
WINDOWSXP-KB917344-X86-ENU.EXE
WINDOWSXP-KB917422-X86-ENU.EXE
WINDOWSXP-KB917537-X86-ENU.EXE
WINDOWSXP-KB917953-X86-ENU.EXE
WINDOWSXP-KB918439-X86-ENU.EXE
WINDOWSXP-KB919007-X86-ENU.EXE
WINDOWSXP-KB920213-X86-ENU.EXE
WINDOWSXP-KB920214-X86-ENU.EXE
WINDOWSXP-KB920670-X86-ENU.EXE
WINDOWSXP-KB920683-X86-ENU.EXE
WINDOWSXP-KB920685-X86-ENU.EXE
WINDOWSXP-KB921398-X86-ENU.EXE
WINDOWSXP-KB921883-X86-ENU.EXE
WINDOWSXP-KB922616-X86-ENU.EXE
WINDOWSXP-KB922819-X86-ENU.EXE
WINDOWSXP-KB923191-X86-ENU.EXE
WINDOWSXP-KB923414-X86-ENU.EXE
WINDOWSXP-KB923789-X86-ENU.EXE
WINDOWSXP-KB923980-X86-ENU.EXE
WINDOWSXP-KB924191-X86-ENU.EXE
WINDOWSXP-KB924270-X86-ENU.EXE
WINDOWSXP-KB924496-X86-ENU.EXE

IE:
IE6.0SP1-KB912812-WINDOWS-2000-XP-X86-ENU.EXE
IE6.0SP1-KB916281-WINDOWS-2000-XP-X86-ENU.EXE
IE6.0SP1-KB918439-WINDOWS-2000-XP-X86-ENU.EXE
IE6.0SP1-KB918899-WINDOWS-2000-XP-V3-X86-ENU.EXE
WINDOWSXP-KB912812-X86-ENU.EXE
WINDOWSXP-KB916281-X86-ENU.EXE
WINDOWSXP-KB922760-X86-ENU.EXE

I understand you want the same thing most people here at MSFN want and have. A current and fully upto date unattended XPSP2 Pro CD with current drivers for modern mainstream hardware including any needed software and settings with minimal user effort at install and much more! Perfect is reletive to the use and the software company we are dealing with? The perfect install looks allot more like Ubuntu? IMHO.

Well that will take care of all your security, critical updates for WINDOWZ 2K, 2K3, XP and Vista in all languages. In other words everything that matters. As far as hardware drives go that is where the BTS DriverPacks shine. This guy accomplished what many said was not possable and you can still use a CD. The only problem I have had was with the soundcard drivers that was overcum by temporary disabeling the sound untill install was finished. Everything else will have to be indevidually fetched and silently installed or intergrated.

Again, I've heard things like "Oh, use MBSACLI.CMD and it will XML out a listing of what you need." But again, I fear this is SECURITY only. And again, SECURITY is only part of the patch universe, right? Point being, if there were a utility which could list every patch on a given day post-SP2, I wouldn't mind downloading the delta-changes of those patches and putting them into a directory and rebuilding with (choose one: nLite, etc). But, sigh, sadly, I don't think we're going to find that out anytime soon. I asked the guys in the Autopatcher forum, btw, and that (above) was the response I received (use MBSACLI).

Like I mentioned before since Jan-2006 this has been done with the MS .iso files. Although it sounds like you got some good info? The MBSACLI.CMD does contain what you need? This is what it is based on. (http://support.microsoft.com/kb/894193) RyanVM also has a list of all the packages you need in his pack. or just install XPSP2 and goto Windows Update? They will all take you to the same place? For XP RyanVM has taken all the guess work out.

I had an admin on my team once that found a way to use the Compaq Smart Start scripting toolkit, but he was able to ghost the process at the first blue-screen text-mode portion reboot, saving about 15 minutes per install.

If that kind of time isn't worth it (and I suppose there could be issues), then I'm just going to skip this part of my question and say, thanks, you're right.

I am not familier with that Compaq app. I am not sure what that would save you in the end? Hey its all "1's and 0's" so I suppose anything is possable? Although I have learnt the hard way, when MS has a system for you to use, It is in your best interest just to play along unless you have a really good reason otherwise... Like I said the biggest thing you can do is to not install any more then nessasary and use the lowest (store) compression on all files.

Yeah. I've got my weekends cut out for me for the next several months, huh? :)

I almost forgot about the official help files! (START HERE -- Almost everything you need to know in a .chm file)

Windows Support Tools

Windows Deploy Kit

Several months will only be the case if you try to understand everything before trying. Thanks to the hard work of Ryan, Nlite and the BTS_DP this madness of allways reinstalling windows is very simple and should take less then one weekend on your first dry run and it will get much faster the more you do. Take it one step at a time and you will get there? My DL-DVD includes every version of MS Operating System since DOS2.0 all installed unattended after choice and partitioning. Google "Windows AllinOne DVD".

Stop Reading! :) and get downloading. Test on a virtual machine while reading about what you are going to do to the next disk you make. Rince and Repeat... :hello:

Edited by mywindow
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...