jtdoom
September 8th, 2006, 07:00 PM
Dear Gentlebeings,
Do YOU have to install windows XP on a regular basis?
Don't you hate it when you need that F6 FLOPPY?
Do you wish you could spend less time installing drivers on each installation?
After installing XPSp2, do you want to save an hour or longer with several restarts while doing windows update?
Well, spend a couple of hours on this, and save a couple hours each time you run setup.
a DVDRW is highly recommended.
---------------------
I knew a few things about unattended setup.
I knew about MsBatch, sysprep, and answerbuilder, but these tools are not the most convenient when one wants a bootable installation disc that sees your non-supported hard drive controller and has to be able to run a repair session.
One could do that with these tools and some geeky knowhow.
Adding the needed drivers is tedious, prone to error, and per type of machine...
Not really what I want to spend my time on...
So, my goal was to build a "setup" CD that can see hard drives in just about all machines, and NO floppy required.
Well, I learned there is a huge "filtered" collection of mass storage and chipset drivers available.
That took care of that F6 floppy need.
BUT, people whom are going to install on a regular basis need still better.
Graphics cards, Lan and wireless, and sound driver installation can be a pain.
And some Post service pack 2 hotfixes might be NEEDED to successfully install some drivers...
Well, I was not the only person looking for a convenient solution..
I found a few projects about Hotfix packs and driverpacks.
They get processed in such a form that including all of them can be done while still using a 700 or 800 Mb CDR.
When Unpacked, you find there is approx 1.25 Gigabyte of drivers not included in windows in there.
The Hotfixes are also taking room.
When one integrates all the hotfixes and all the driverpacks, and removes nothing, you will need a DVD.
(That's not a bad thing in itself... On a DVDRW one can really go for roll-outs.)
If you use Nlite to slim it down BEFORE you integrate hotfixes and slipstream the drivers, you can get it to fit on a CDR.
I spent some time at these guys hangouts and learned, and tested and learned.
When new releases were in the works, I ran a great many tests on a few "exotic" machines.
These programs improve over time, and I will watch their evolution.
But I ramble..
For those of us that regularly run setup on a variety of new machines, here is something that works.
Actually, after a few runs, you find they are SIMPLE steps.
to fit on CDR: Nlite (slimming it down/other functions) and RVM (hotfixes/addons)
After that, Slipstream the Driverpacks with DPs_Base.
Using a DVD: RVM to include hotfixes and addons, maybe you want to use Nlite for some of its other functions.
The last slipstream is adding the Driverpacks with DPs_Base.
common to CDR /DVD, when done streaming, create ISO (usable for burn, for RIS or for virtual PC) or just burn.
--------
let's get into detail
=====================
RVM for HOTFIX and ADDONS
http://www.ryanvm.net/msfn/updatepack.html
This is the page for Ryan Vander Meulen's integrator.
You want Hotfixes, so get his RVM POST SP2 hotfixes pack.
You should also get his RVM integrator and while you are at RVM's site, I can suggest you also look at the addons.
If you want them, download them into the same folder.
I selected some I wanted IN, and also DOTNETFX with its hotfixes (which is a 28Mb download)
my experience with addons is that you best do them in the same session.
Note, at first glance, you can also use Nlite to integrate RVM's hotfix pack and RVM's addons, but at the moment, I will NOT use Nuhi's Nlite to integrate these....
--------
the source
in this example I'll use a HOME edititon.
copy your OEM home sp2 CD to a folder
eg, oemsp2_HOME
--------
The RVM integrator.
Get to the folder you downloaded RVM integrator and the RVM packs into.
Run the integrator, and browse it to the selected source for this session.
IMPORTANT
For some windows source CD's OTHER than English, if you want HD-audio drivers load correctly, this is a required setting.
so, check into this, even when nowadays the default is ON..
hit the advanced flag
tick to ENABLE advanced
tick to convert UNICODE TO ANSI
go back to MAIN
In the integrator, you can have it make a copy to a new folder for the slipstreaming.
(You don't need to, but it's handy when you are going to make variants.)
eg, oemsp2_home_hotfixed
This oemsp2_home_hotfixed folder would have the rootfiles and 386 folder only.
I suggest you copy the SUPPORT folder to oemsp2_home_hotfixed folder.
And in HOME editions copy the VALUEADD\MSFT\NTBACKUP folder to SUPPORT folder.
This way, you would have these valuable tools when you need them.
You can let it work without making a copy too, though.
Browse for selecting the update pack and addons, and then let it integrate...
You can build an ISO in the same session, but since you will slipstream a cartload of drivers later on, you don't do that.
------
-----
NLITE NOTES -->
Slimming down to fit on a CDR.
If you are going to use NLite (http://www.nliteos.com/) to make a build fit on a 700Mb or 800 Mb CDR, then PLEASE do not do this after you slipstreamed the Driverpacks .
I will also advise to not use Nlite for integrating the RVM hotfix packs.
I ran into a bug in NLite when it integrates RVM's hotfixes.
(well... ?? ?? a txt file like svcpack.in_ contained like 1.2GB ?? ??)
RVM works for RVM.
You most definately do not want to use N-Lite for slipstreaming the driverpacks.
Anyway, for slimming the source.
The upgrade-migration tools in the 386 folder are usually not needed..
You could delete these folders. I did.
The dotnetFX folder is not needed. (The hotfixed dotnet is newer)
You could do away with the components folder altogether if you don't use tabletPC component.
Move NTbackup folder into support folder (if it is a Home edition).
Delete valueadd folder.
I do NOT delete support folder (the tools are too valuable).
Then you run Nlite on that already slimmed down source.
I would suggest you remove the unneeded languages and unneeded keyboards.
Music samples, and the guided tour are also things you don't need
With just this, you've slimmed it down enough to fit on 700Mb.
I prefer to use Nlite FIRST, then RVM, and then DPs_base
Other reliable folks tell me they do RVM first, then Nlite, and then DPs_base.
All experienced users do the driverpacks slipstream with DPs_Base and do that as LAST slipstream.
end notes <--
------
Now let's get those drivers into windows setup CD.
http://www.driverpacks.net/
The files are under driverpacks.
you need DPsBase to roll them into the hotfixed folder.
If you want to avoid F6, you definately need mass storage.
Chipsets sit on moboes..
CPU for an AMD fix
Sound has been split into two files by now
Graphics has been split to Three
and LAN and WLAN are also found on main download page.
(there are third party driverpacks found on the site, which are most probably much less tested.)
download the files you want to same folder you downloaded DPsBase_xxxx.exe to.
Now, since you will probably do this more than once, make a folder for DPsbase.
copy DPs_base_xxxx to that folder and run it.
It selfextracts.
You'll find an empty driverpacks folder in there.
Copy the driverpack files you want to it. (third party packs have to go to thirdparty folder)
run Dps_Base.exe, hit the arrow to get forward
select DISC (which is the default), and click Browse.
Browse and point it to the oemsp2_home (or oemsp2_home_hotfixed) folder
if you want all drivers, you must use method 2
(It's the default.)
click forward
>> Note;
Method 1 is NOT your choice if you do ALL, as the path statement would become way too long.
The $OEM$ path statement can be only so long (1024 characters in windows 2000, and 4096 in XP), and the drivers in paths exceeding this statement Limit would be skipped. The paths are kept really short, but you won't ever get ALL in your build by using method 1....
<<
Select the driverpacks, and for avoiding F6, you HAVE to use TEXTMODE.
(since you use method 2, just hit the select ALL button)
If you plan on adding/shuffling many different cards in that box later on, you might want to select KTD (keep the drivers).
The default is to NOT use it.
Pretty soon you walked the arrows through all the pages, and you hit the slipstream button.
A couple minutes later it's done. (a method one slipstream takes longer...)
Check the size of your hotfixed and driverslipped folder.
(if you slimmed down the source, you can use a 700 or 800Mb CDRW)
Note;
CDRW or DVDRW highly recommended if you want to test different versions before burning finals for your toolsbox.
You should test these builds on a non-production machine.
After a few tests with optimised/automated builds, I think you will run the integrator and driverpacks base builder on all the sources you want slipstreamed versions of.
eg, If you have to do Retail CD versions, why not?
OH, you may want to do this to gold releases or older service pack versions..
Then you will want to first slipstream the current service pack, and then do the hotfixes after latest servicepack.
(Nlite, RVM integrator and autostreamer can all help you with that.)
The older the version you have is, the more time you save when you have to use that build.
====== =======
Make ready to burn.
NOTE; If you use a DVD, one could copy or add some other stuff to the folder before you do that. Tools and programs you downloaded and will put on the new machine can be put in that DVD... Some people actually have the DVD run unattended installation of additional programs. << end note
Now you CAN make an ISO with the integrator or Nlite, and the ISO will have a bootsector.
run the integrator or Nlite, and hit ISO.
Tell it where the source is at, where to save the ISO, and the label you want to give it.
Then hit MAKE.
Then burn the ISO.
--OR--
If you want to use a burning suite with selection pane (like in Nero), you need a bootfile image.
Isobuster can get it off the source CD.
Save it as IMA if you plan on using NERO.
I used NERO...
In nero burning rom
bootable DVD
select the floppy image file
set options to NO EMULATION
set SECTORS to 4
drag the files into the selection pane.
burn
test it
I think you'll love it.
After using it a couple times, you probably saved yourself a few hours already.
For issues with these programs, visit the forums these guys have.
----
notes about UNattended.
For new machines, you can have it set to automatically format.
(in DATA, autopartition=1 and in unattended Repartition=YES)
(you will probably NOT want to put the key in the winnt.sif for OEM installs.)
Maybe you don't want to use FULL unattended.
A Winnt.sif you had created and use should be in the 386 folder before you run DPs_base
it makes a backup of it and it adds its entries to it.
If you didn't have a winnt.sif yet, a winnt.sif is created by DPs_Base...
This will still allow you to get to RECOVERY CONSOLE when you need it..
You CAN use a non-full unattended WINNT.SIF file.
You can make it NOT automatically go to the partition without windows
in DATA, autopartition=0
in [unattended] remove the line with "Repartition" or set it to Repartition=0
(in [unattended] you can also set it to leave filesystem alone... FileSystem=LeaveAlone).
Note; autopartition=1 is the default if that entry is not seen in the txtfile.
(That is how Windows can surprise you by ending up on another partition after an attempt at repair setup.)
I think that when you already rolled out a few and use your own winnt.sif files, you know more than I do.
----
----
NLite can help you make a WINNT.SIF for full unattended..
Oh, I have used Nlite to roll just the FEW drivers on the floppy into a disc a few times, but this driverpacks package has like 1500 different devices... and Nlite fails when it has to do all the packs.
It also breaks the driverpacks if it is run after BPsBase slipped in those driverpacks.
But I ramble.
so, having done several tests, I will go for what works.
in short;
after Nlite for slimming, RVM, and after RVM, DPs_Base.
Either make an ISO and burn it, or use NERO with a bootfile image.
TESTING.
Do not risk data, use a machine that can be formatted anytime for your tests.
The real tests are done on real machines, but one can use virtual machines too.
Virtual PC is a free Microsoft download.
-----------
-----------
If you just want to avoid the F6 floppy, mass storage and chipsets is all it takes.
If you have only these packs, you can use method 1, and textmode.
At the driverpacks site.
each download page has a changelog and supported drivers listing.
For instance, sound B
http://www.driverpacks.net/DriverPacks/DriverPack_Sound_B.htm
a last note; Vista recognised my raid chips in that exotic machine...
Do YOU have to install windows XP on a regular basis?
Don't you hate it when you need that F6 FLOPPY?
Do you wish you could spend less time installing drivers on each installation?
After installing XPSp2, do you want to save an hour or longer with several restarts while doing windows update?
Well, spend a couple of hours on this, and save a couple hours each time you run setup.
a DVDRW is highly recommended.
---------------------
I knew a few things about unattended setup.
I knew about MsBatch, sysprep, and answerbuilder, but these tools are not the most convenient when one wants a bootable installation disc that sees your non-supported hard drive controller and has to be able to run a repair session.
One could do that with these tools and some geeky knowhow.
Adding the needed drivers is tedious, prone to error, and per type of machine...
Not really what I want to spend my time on...
So, my goal was to build a "setup" CD that can see hard drives in just about all machines, and NO floppy required.
Well, I learned there is a huge "filtered" collection of mass storage and chipset drivers available.
That took care of that F6 floppy need.
BUT, people whom are going to install on a regular basis need still better.
Graphics cards, Lan and wireless, and sound driver installation can be a pain.
And some Post service pack 2 hotfixes might be NEEDED to successfully install some drivers...
Well, I was not the only person looking for a convenient solution..
I found a few projects about Hotfix packs and driverpacks.
They get processed in such a form that including all of them can be done while still using a 700 or 800 Mb CDR.
When Unpacked, you find there is approx 1.25 Gigabyte of drivers not included in windows in there.
The Hotfixes are also taking room.
When one integrates all the hotfixes and all the driverpacks, and removes nothing, you will need a DVD.
(That's not a bad thing in itself... On a DVDRW one can really go for roll-outs.)
If you use Nlite to slim it down BEFORE you integrate hotfixes and slipstream the drivers, you can get it to fit on a CDR.
I spent some time at these guys hangouts and learned, and tested and learned.
When new releases were in the works, I ran a great many tests on a few "exotic" machines.
These programs improve over time, and I will watch their evolution.
But I ramble..
For those of us that regularly run setup on a variety of new machines, here is something that works.
Actually, after a few runs, you find they are SIMPLE steps.
to fit on CDR: Nlite (slimming it down/other functions) and RVM (hotfixes/addons)
After that, Slipstream the Driverpacks with DPs_Base.
Using a DVD: RVM to include hotfixes and addons, maybe you want to use Nlite for some of its other functions.
The last slipstream is adding the Driverpacks with DPs_Base.
common to CDR /DVD, when done streaming, create ISO (usable for burn, for RIS or for virtual PC) or just burn.
--------
let's get into detail
=====================
RVM for HOTFIX and ADDONS
http://www.ryanvm.net/msfn/updatepack.html
This is the page for Ryan Vander Meulen's integrator.
You want Hotfixes, so get his RVM POST SP2 hotfixes pack.
You should also get his RVM integrator and while you are at RVM's site, I can suggest you also look at the addons.
If you want them, download them into the same folder.
I selected some I wanted IN, and also DOTNETFX with its hotfixes (which is a 28Mb download)
my experience with addons is that you best do them in the same session.
Note, at first glance, you can also use Nlite to integrate RVM's hotfix pack and RVM's addons, but at the moment, I will NOT use Nuhi's Nlite to integrate these....
--------
the source
in this example I'll use a HOME edititon.
copy your OEM home sp2 CD to a folder
eg, oemsp2_HOME
--------
The RVM integrator.
Get to the folder you downloaded RVM integrator and the RVM packs into.
Run the integrator, and browse it to the selected source for this session.
IMPORTANT
For some windows source CD's OTHER than English, if you want HD-audio drivers load correctly, this is a required setting.
so, check into this, even when nowadays the default is ON..
hit the advanced flag
tick to ENABLE advanced
tick to convert UNICODE TO ANSI
go back to MAIN
In the integrator, you can have it make a copy to a new folder for the slipstreaming.
(You don't need to, but it's handy when you are going to make variants.)
eg, oemsp2_home_hotfixed
This oemsp2_home_hotfixed folder would have the rootfiles and 386 folder only.
I suggest you copy the SUPPORT folder to oemsp2_home_hotfixed folder.
And in HOME editions copy the VALUEADD\MSFT\NTBACKUP folder to SUPPORT folder.
This way, you would have these valuable tools when you need them.
You can let it work without making a copy too, though.
Browse for selecting the update pack and addons, and then let it integrate...
You can build an ISO in the same session, but since you will slipstream a cartload of drivers later on, you don't do that.
------
-----
NLITE NOTES -->
Slimming down to fit on a CDR.
If you are going to use NLite (http://www.nliteos.com/) to make a build fit on a 700Mb or 800 Mb CDR, then PLEASE do not do this after you slipstreamed the Driverpacks .
I will also advise to not use Nlite for integrating the RVM hotfix packs.
I ran into a bug in NLite when it integrates RVM's hotfixes.
(well... ?? ?? a txt file like svcpack.in_ contained like 1.2GB ?? ??)
RVM works for RVM.
You most definately do not want to use N-Lite for slipstreaming the driverpacks.
Anyway, for slimming the source.
The upgrade-migration tools in the 386 folder are usually not needed..
You could delete these folders. I did.
The dotnetFX folder is not needed. (The hotfixed dotnet is newer)
You could do away with the components folder altogether if you don't use tabletPC component.
Move NTbackup folder into support folder (if it is a Home edition).
Delete valueadd folder.
I do NOT delete support folder (the tools are too valuable).
Then you run Nlite on that already slimmed down source.
I would suggest you remove the unneeded languages and unneeded keyboards.
Music samples, and the guided tour are also things you don't need
With just this, you've slimmed it down enough to fit on 700Mb.
I prefer to use Nlite FIRST, then RVM, and then DPs_base
Other reliable folks tell me they do RVM first, then Nlite, and then DPs_base.
All experienced users do the driverpacks slipstream with DPs_Base and do that as LAST slipstream.
end notes <--
------
Now let's get those drivers into windows setup CD.
http://www.driverpacks.net/
The files are under driverpacks.
you need DPsBase to roll them into the hotfixed folder.
If you want to avoid F6, you definately need mass storage.
Chipsets sit on moboes..
CPU for an AMD fix
Sound has been split into two files by now
Graphics has been split to Three
and LAN and WLAN are also found on main download page.
(there are third party driverpacks found on the site, which are most probably much less tested.)
download the files you want to same folder you downloaded DPsBase_xxxx.exe to.
Now, since you will probably do this more than once, make a folder for DPsbase.
copy DPs_base_xxxx to that folder and run it.
It selfextracts.
You'll find an empty driverpacks folder in there.
Copy the driverpack files you want to it. (third party packs have to go to thirdparty folder)
run Dps_Base.exe, hit the arrow to get forward
select DISC (which is the default), and click Browse.
Browse and point it to the oemsp2_home (or oemsp2_home_hotfixed) folder
if you want all drivers, you must use method 2
(It's the default.)
click forward
>> Note;
Method 1 is NOT your choice if you do ALL, as the path statement would become way too long.
The $OEM$ path statement can be only so long (1024 characters in windows 2000, and 4096 in XP), and the drivers in paths exceeding this statement Limit would be skipped. The paths are kept really short, but you won't ever get ALL in your build by using method 1....
<<
Select the driverpacks, and for avoiding F6, you HAVE to use TEXTMODE.
(since you use method 2, just hit the select ALL button)
If you plan on adding/shuffling many different cards in that box later on, you might want to select KTD (keep the drivers).
The default is to NOT use it.
Pretty soon you walked the arrows through all the pages, and you hit the slipstream button.
A couple minutes later it's done. (a method one slipstream takes longer...)
Check the size of your hotfixed and driverslipped folder.
(if you slimmed down the source, you can use a 700 or 800Mb CDRW)
Note;
CDRW or DVDRW highly recommended if you want to test different versions before burning finals for your toolsbox.
You should test these builds on a non-production machine.
After a few tests with optimised/automated builds, I think you will run the integrator and driverpacks base builder on all the sources you want slipstreamed versions of.
eg, If you have to do Retail CD versions, why not?
OH, you may want to do this to gold releases or older service pack versions..
Then you will want to first slipstream the current service pack, and then do the hotfixes after latest servicepack.
(Nlite, RVM integrator and autostreamer can all help you with that.)
The older the version you have is, the more time you save when you have to use that build.
====== =======
Make ready to burn.
NOTE; If you use a DVD, one could copy or add some other stuff to the folder before you do that. Tools and programs you downloaded and will put on the new machine can be put in that DVD... Some people actually have the DVD run unattended installation of additional programs. << end note
Now you CAN make an ISO with the integrator or Nlite, and the ISO will have a bootsector.
run the integrator or Nlite, and hit ISO.
Tell it where the source is at, where to save the ISO, and the label you want to give it.
Then hit MAKE.
Then burn the ISO.
--OR--
If you want to use a burning suite with selection pane (like in Nero), you need a bootfile image.
Isobuster can get it off the source CD.
Save it as IMA if you plan on using NERO.
I used NERO...
In nero burning rom
bootable DVD
select the floppy image file
set options to NO EMULATION
set SECTORS to 4
drag the files into the selection pane.
burn
test it
I think you'll love it.
After using it a couple times, you probably saved yourself a few hours already.
For issues with these programs, visit the forums these guys have.
----
notes about UNattended.
For new machines, you can have it set to automatically format.
(in DATA, autopartition=1 and in unattended Repartition=YES)
(you will probably NOT want to put the key in the winnt.sif for OEM installs.)
Maybe you don't want to use FULL unattended.
A Winnt.sif you had created and use should be in the 386 folder before you run DPs_base
it makes a backup of it and it adds its entries to it.
If you didn't have a winnt.sif yet, a winnt.sif is created by DPs_Base...
This will still allow you to get to RECOVERY CONSOLE when you need it..
You CAN use a non-full unattended WINNT.SIF file.
You can make it NOT automatically go to the partition without windows
in DATA, autopartition=0
in [unattended] remove the line with "Repartition" or set it to Repartition=0
(in [unattended] you can also set it to leave filesystem alone... FileSystem=LeaveAlone).
Note; autopartition=1 is the default if that entry is not seen in the txtfile.
(That is how Windows can surprise you by ending up on another partition after an attempt at repair setup.)
I think that when you already rolled out a few and use your own winnt.sif files, you know more than I do.
----
----
NLite can help you make a WINNT.SIF for full unattended..
Oh, I have used Nlite to roll just the FEW drivers on the floppy into a disc a few times, but this driverpacks package has like 1500 different devices... and Nlite fails when it has to do all the packs.
It also breaks the driverpacks if it is run after BPsBase slipped in those driverpacks.
But I ramble.
so, having done several tests, I will go for what works.
in short;
after Nlite for slimming, RVM, and after RVM, DPs_Base.
Either make an ISO and burn it, or use NERO with a bootfile image.
TESTING.
Do not risk data, use a machine that can be formatted anytime for your tests.
The real tests are done on real machines, but one can use virtual machines too.
Virtual PC is a free Microsoft download.
-----------
-----------
If you just want to avoid the F6 floppy, mass storage and chipsets is all it takes.
If you have only these packs, you can use method 1, and textmode.
At the driverpacks site.
each download page has a changelog and supported drivers listing.
For instance, sound B
http://www.driverpacks.net/DriverPacks/DriverPack_Sound_B.htm
a last note; Vista recognised my raid chips in that exotic machine...