Search options (Page 205 of 213)

So Muiz got some freinds to vote
we knew it was happening
and had every opportunity to "Rally the Troups" 

It's all good fun!

if you slipstream the driverpacks most likely your f6 driver will fail its a known MS bug related to the oempreinstall=yes in winnt.sif

a setting which is necessary for driverpacks

Jaak Is working hard on mass. keep an eye out for for the next mass pack. and I will make sure he chimes in here

try resetting your bios ESCD table and freeing up some recources
Turn off sound on mb (free interupts) setting parrallel port to not use a DMA channel ect...

there are not as many resources to go around in text mode as there are when NT is running in apic

motaz i have seen a few issues of late that went away when QSC was turned on
can you test the install with qsc on?

clarifiying for helmi

Jig you stated:  all english, one updated, one not.

copy your entire OEM install CD (the one you currently install from) to your HDD (say C:\DP-temp\)
copy your entire updated OEM install CD (the one you currently install from) to your HDD (say C:\DP-temp-U\)

Run the DP_Base program in 'disk' mode with all packs selected, TextMode enabled, KTD disabled, QSC enabled, Method 2. pointing to C:\DP-temp\ as the 'location'. The same for C:\DP-temp-U\.

Then burn a bootable ISO useing the contents of C:\DP-temp\ and one for C:\DP-temp-U\ (easy).

This will not break any existing processes of your original CD -
It simply extends the driver library available to windows setup.
the KEY here is the drivers are available DURING the installation setup (the initial PnP discovery).
and it fits nicely on a 700 meg CD (and since you have no network connections you could skip wireless LAN and free more space.

Here is a GREAT source of reference in case you have not been there you
Will find a great many of your freinds from DriverPacks are in thier forum as well.
http://unattended.msfn.org/unattended.xp/

also: a DriverPacks Tutorial http://users.pandora.be/jtdoom/basetute/Eng_tut6b.htm

did you grab all the updates from the MS site or are you just useing nlite to slip the Ryan stuff?

NO it is preferable to have one CD that can be used in any system (OEM CD with only driverpacks added in your case)
furthermore some drivers require patches and we check for such things when we slipstream so you don't get hosed.
like the HDA update.
EVEN IF you have to create one per language.

an additional pickup here is not needing a "F6" floppy for the install.

Please check out RIS and DFS if you are worried about dated installs. on this forum there is a good thread on sysprep that gets into part of RIS. I cant remember the last time I visited a Server/client system to reinstall it i do that remotely from home. Helmi's WSUS Idea is outstanding! you can release only the updates you wish to all clients. (you set all the machines to use your server instead of MS Updates - great for no internet environments)

if you used driverpacks today you wouldn't have to update again until current hardware becomes obsolete
IE you will still be able to buy a similar system to the one you buy now, one year from now.
(so now were talking about a 15 minute update per language once a year[or mabey even just one!]).

What you want is kind of like hitting the brakes after the accident. opening your chute - after impact!
or
rather than create a big mess, and then have to clean it up, lets just not make a mess?

I would also like to point out ALL of us have said "These instructions assume you have started with a DriverPacks slipstreamed source." which you seem to indicate you haven't. This invalidates all our suggestions and probably will not give the expected results except for my 'two step' Drivers Only CD above.

The feedback of admins with many systems to maintain and years of work from several excellent people have culminated in this process and much goes on behind the scenes to avoid thousands of known issues. It works like a charm right out of the box sir!... I currently use this for dozens of companies some with 50 or more locations.

Try It! ... You'll Like it!  (and you will never look back)

nope it doesn't

I make a new DVD everytime Ryan VM comes out with a new update (say monthly)
so seemingly your method is not valid because not only do the drivers get updated quite frequently but so do the MS patches. So these install disks, do in fact, have a very short life.

I would make your new install disks as needed. Then you can slipstream all the latest microsoft patches for windows and office, and have all the latest drivers too. It costs ten cents to burn a disk and takes about 20 minutes. why take a process that is in place and working in a world class fashion and try and break it?

With your method it would be neccesary to watch the machine and manualy switch CD's.
The way the rest of us do it this becomes a totaly unattended process, and isn't that the goal?

I think you need to get more familiar with what is going on...

in order to create a drivers only disk

1. create a method 1 install and burn the $oem$ folder to a cd
2. You're Done.... its that simple. that cd IS a "drivers only disc"

that discusion has gotten way off topic ----  " [HOWTO] create a drivers-only disc "  (see above)

They are actually discussing trying to add KTD (Keep The Driver) functionality to an existing system.
Only a bench technician would find this useful - and a bench tech would have an extra drive laying around he could install with KTD enabled from the start. So very few people would need or want this if any at all. A drivers only disk (CD) and a KTD installation upgrade are not the same thing at all... not even close. so I am not suprized that you are confused.

many here have gotten the idea that the finisher magicaly will make unknown devices dissappear, and it wont.

an example of what the finisher does would be like the nvidia control panel shorcut and the taskbar icon.
that kind of stuff. the nvidia driver would be installed when you updated the device driver from device manager and told it to search your CD with the $OEM$ folder on it but non of the features would be available. (no control panel shortcut) [These types of things are normaly run from a hardware manufacurers driver installation program.] if you run the finisher it would see that you have the nvidia card installed and would associate the devices HWID with the exception that installs the stuff that is not part of the actual driver (the control panel icon and taskbar shortcut). Most of the drivers in the packs dont even have a single exception to be applied. As the name implies these are 'exceptions' both nvidia and ati are good examples of ones that do have exceptions. 

perhaps a simple way of putting this is "Many of the drivers in the packs don't even require the Finisher".

lets discuss why this could be a very bad thing. Suppose you installed without KTD and a Nvidia card and got the CPL icon and the Taskbar thing going on and switched to a ATI card then did the KTD upgrade with finisher now you would have the ati cpl and the nvidia cpl and both taskbar icons. if it doesn't crash. i belive you shouldn't run the finisher more than once per install -if you need to run the finisher again you probaly need to install again. lets say i were to upgrade a device or even two on a machine. If it were me i would just install the latest driver off the net rather than to fool with forceing the finisher to run on the entire driverpacks.

I have tried to explain this several times now without boring everyone to tears.

no it will never support the command line, it does exactly what it was written for - (which isn't what you think it does)
Im definately not going to code unneccessary garbage into it.
I am sure Bâshrat the Sneaky won't either. we cant eve get people to read simple instructions in the ini files ;P