http://forum.driverpacks.net/viewtopic. … 710#p29710
read that post... I will again tell you SAD is the answer to your question.
If the drivers are available, then the wizard is not displayed
Simple
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
http://forum.driverpacks.net/viewtopic. … 710#p29710
read that post... I will again tell you SAD is the answer to your question.
If the drivers are available, then the wizard is not displayed
Simple
the driversigning things normaly only pop up when KTD is enabled...
we should not need KTD, and it may cause issues too.
Sad can be run at any time. what is the HWID for the soundcard that is at issue
Sometimes the order in which you add IE can have adverse effects...
Did you try running teh SAD tool after the install... that may clean up the strays...
That is what i call teamwork - Well Done!
here is a sneak preview... it's an alpha so keep a close eye on it
extract to the BASE folder (with dps_base.exe)
Create a SAD M2 folder...
run the prep tool on the SAD folder...
now the SAD folder has a new executable
HID Installer.exe
will only extract needed drivers from the packs and install only them.
This is being tested right now to see if it is effective,
in that if it is not any faster than extracting the full set of drivers,
then it is not really worth pursuing
PS this alpha does not call the finisher - this must be done manually ATM
I did this intentionally to prevent the files from all being deleted by the finisher
(makes it hard to troubleshoot when all the files get deleted )
so Copy the \D\ folder before you run the finisher and you will have all the drivers that match your machine
I don't see how that benifits you in any way... but there you have it.
Please report success or failure sir!
Excellent details ef... that is the minumum I need to offer support
BASE ver, OS ver, Pack ver, and in this case also the Platform ver (UBCD4Win).
I am so glad all three of you reported
However - please note ef's clear, complete and consise details for future reference. That's how it's done...
the problem is obviously in the Mass Storage INI file... should be able to fix it in a jiffy.
SAD works nicely for this... alternately you could use DSPdsblr.exe whyich is included with base in the finisher archive.
did you run driverpacks after nLite? (it is very important that DriverPacks is the last step...)
will the shutdown command work? http://www.ss64.com/nt/shutdown.html
yeah... I like waffles. Waffles are never off topic as far as im concerned
We can deal with that in the mass storae pack i belive.
We will take a look at it ...
I second the Win7 vote
I'm running a 64bit version on a test machine
I have just been abusing it... It's solid
All vista drivers i installed worked fine. As advertized
I installed apps and games dual booted it with the OEM Vista - repartitioned with the Vista disk manager.
It's fast and its stable and it has a more tolerable footprint in RAM.
We will have to see where they go with it but.. since the beta is strong we have high hopes
I'd like to see tehm make it even leaner
code tags added for you
If it were supported... Then i am sure we could...
Neither RIS nor Attended installs are supported (Repair is an attended install)
Saying we broke somthing that is not supported is not encoraging though and in fact is quite the opposite.
So saying we broke something that is not supported on multiple levels is... well... antagonistic...
Providing no details about your process, (which neither helps us or someone else who may stumble on this thread) and being antagonistict at the same time is really not condusive to leading us to support of it, nor helpful to someone else who may wish to do the same thing. (your posts have been anything but helpful either to us or anyone else)
contradicting MS documentation is also not helpful...
- IE proper $OEM$ folder fucntions depend on it being and OEM installation.
So you were able to force a Repair to work for RIS, two unsupported issues, Yay,
and you have shared the 'how to make it work' results with no one, Boo...
We can't create problems with unsupported platforms. {think about it} To accuse us of such is short sighted.
I equate this to you complaining that DriverPacks BASE used to make toast and now we have broken the toast feature.
- But since you have been able to make the toast feature work again so should we! - {HUH}
We do not now nor have we ever supported the use of DriverPacks BASE to make toast... toast is not supported (still) sorry...
now waffles... that we can talk about
Hatred is a bit strong.
I just don't have patience for things that are terribly gimped
I have always found easier ways to accomplish the same things with less of my time through alternate means...
it aggravates me i don't hate it - i just don't like it
Error code 10 is a hardware error - IE this device cant start... i don't think drivers are going to fix it.
If we are going to play the guessing game i guess he hooked upboth power connectors at the same time
Sorry cant help you... RIS is not supported.
bye bye now...
well i would need to know which executable minisetup is ... is it just setup with a parameter after it? or winnt32... ect. then i write a fake setup... autoit will fail at PE so it will need to be vb or something else... nbd
perhaps a large bit in your favorite drill...
bore several holes through the case until it stops sputtering & smokeing..
the answer is simple...
DriverPacks with RIS must have OemPreinstall=Yes or it will not work...
If you don't have OemPreinstall=Yes then the $OEM$ folders are not used (copied).
--- OEM folders depends on OemPreinstall ---
and the driverpacks will then not be copied to the target machine... and then don't get installed.
Repair or $OEM$ folders - not both - one or the other...
Ah... 'Ping'... the lightbulb comes on...
So we have some awsome building blocks for a DriverPacks solution.
the DriverPacks solution (as always) would be depoyable as an unattended platform
- and OSP is an attended solution...
- i belived that after an OSP was performed on each type of machine in your envirionment
that it would then be complete / deployable without user intervention...
I don't think anyone is working on that pack right now... Thanks for bumping the topic so we don't forget!
last question first...
M1 all files are copied uncompressed to the destination during txtmode. (2gig transfer)
M2 (normal not RIS) the files are extracted during Presetup Environment (PE is after the first reboot)
- Both methods have the files in place before Setup.exe runs... _ M1 raw copy in text mode _ M2 extraction in PE.
I am not positive about RogueSpears method here but that CMD window should be extracting the M2 packs.
My belief is they should have been copied localy during the txtmode portion as compressed files.
If i am remembering/guessing correctly then there is probably a folder I386\$OEM$\$1\OEM\[DriverPacks.files] that should be copied to the local hdd as SystemRoot\OEM\ and extracted to SystemRoot\D\ just before setup.exe is called (extracted when that CMD window is displayed) M2 would be faster (moving a 2gig source wouth thousands of files, takes longer than moving a 350 meg source with a dozen large archives. )
In as much as RogueSpear is a genius there has not been much call for support for RIS here in our forum So although i am delighted that you did take the time to search this is one of the few times that you may not find much here to help. Is RS's forum still up... I belive he is either getting (or did get) out of windows support entirely... SAD, I know. He does still frequesnt here and may drop us a lifeline!...
Thanks for your kind words and for taking the time to attempt to help yourself. Since you are running RIS off a Linux box i am quite certain that you exhausted every other avenue before posting. This is something Linux guys seem to have in common, they will try everything before asking for help .
Jeff
i did not realize that offlinesysprep was such a complete tool...
It sounds like i would just be reinventing the wheel by pursuing this...
Wow... you are a mind reader...
This is something that is in testing ATM by our dedicated testing team...
DriverPacks.net Forum » Posts by OverFlow
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.146 seconds, 5 queries executed ]