You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 113 of 213)
Topics by OverFlow User defined search
Posts found [ 2,801 to 2,825 of 5,302 ]
Driverpacks does not replace most of the drivers included with windows...
If you remove them then that hardware is most likely no longer supported by your Disc. 
It may, or may not, be broken... That depends on what you remove...
You more than likely have given up support for whatever hardware you chose to remove...
IMHO that is stupid. The point of DriverPacks is to support ALL hardware,
so removing drivers would be the Antithesis of that,
and if you remove the wrong ones you WILL break your installation.
You can lead a horse to water... but you can't make it drink.
You have been warned and that is all we can do.
Once it bites you in the butt...
perhaps then you will listen to the experts 
Please clear your temporary internet files and retry
I am SO Glad to see you sir!
Welcome home
you will not be able to use F6 drivers...
The entries BASE creates in your winnt.sif are mutualy exclusive to f6 drivers and repair options.
if you remove sections / entries from winnt.sif then you will not have a fully unattended install.
So you can have one or the other - fully unattended install or f6 drivers... not both...
Put another way...
if you remove the entries in your .sif you may then use f6 but your installation may/will stop for user input...
Jeff
if you discover we don't have a driver, just ask, we will add it... that is the best thing to do
it depends on weather you deleted the drivers or if you disabled them as outlined above...
You said you deleted them, if that is so then it is user error...
When i sliptream this pack i get 3112RX47.SY_ as expected...
if you deleted that folder without removeing it from the mass.ini file then you screwed the pooch yourself
the directions to edit the mass pack correctly are above... or you can wait fo rus to have time to fix it for you
Yes user error is a bug but not one we have any control over 
Don't sweat it too much we will fix it soon im sure 
I guess blue tooth first and Phone second...
I am going to have to take another look at those medals MSgt...
I really liked the look and warm feel...
not over done or understated... better than i could have done
I however will second Mr_smartepants motion of getting a tasteful host... please
one of our mods may decide to delete your links since you were already asked nicely once...
(I tried to not bring it up but you made me do it!)
jeff
just a couple of things...
1 We support
a Win2k Sp4
b WinXP SP2 and SP3
c Win2K3 Server SP1, SP2
If the finisher came up and said XPsp3 and it wasn't.
We would definately get BUG reports on that
The curved text is extremely hard to read.
buit it looks nice
For what you wish to do...
You only are required to select mass storage text mode...
but in certain instances also selecting the DriverPack MassStorage pack for slipstreaming will provide better support for your hardware.
since mass storage is only a few meg I can't think of a good reason not to include it
I am very excited to see contributions to DriverPacks from our new members.
That is the stuff DriverPacks is made of.
I would like to quote our good friend Jaak here.
Thanks for "helping us to help you" It is the spirit of what we do.
By giving back you have made yourselves part of our team
maybe you have three different versions of physx in your 3rd party DriverPack folder?
what is unpacker?
I think having established yourself here in some way would be important. I do not wish to give alpha products out to users who have not established thier skill set by provideing quality posts in the past. "Ohhh, pick me" doesn't count.
I dont't even know if the two of you even use DriverPacks BASE. and i certainly have no feel for either of your troubleshooting skills.
Alpha features are for advanced users. you have not even established that you are users, let alone advanced users
thank you for your interest and you can look forward to expanded testing as we have a more solid product to distribute.
Thanks again for your interest
Jeff
so it is not needed and therefore not an issue...
it depends what your personal desire is... KTD is not recomended...
KTD Keeps all the drivers permanently on the target. that is a waste.
if you want all hardware installed when you do an install then you must slipstream all the packs.
if you want KTD then jsut use a disk you have slipstreamed all the packs to and pop it in and run dp_ints_tool.cmd
this is better because it does not leave unneeded drivers behind on the HDD. and it is always current (assumeing you update your install disc)
SAD is instead of KTD. it is not a substitute for slipstreaming all the drivers to your disc.
dpinst.exe does not work as well as the windows setup.exe used during winpe phase of setup.
I though i said that "SAD replaces KTD" i dont think i was vague on that point.
to be absolutely clear - it does not replace the normal function of the DriverPacks.
It is however a 100 times better than KTD
without the HWID and you provideing a link to a known working driver it will not be added...
We can't / wont add a driver if we cannot verify it is working... that is up to you!
Wow... very cool!
It will have to be Bâshrat the Sneaky to add it, not even I have access to the root of our site
You can't use the mass storage driver pack with nLite.
We don't use or include the oemsetup files that nLite requires to add textmode drivers.
mr_smartepants is correct this is not the place to get support for nLite.
I would strongly recomend you not add DriverPacks drivers with nLite...
If you are only trying to add support for just your personal machine then nLite will work Great!
But, you will need to get the drivers you need from the OEM sources yourself.
DriverPacks is not nLite compatable unless you add the packs with DriverPacks BASE
if you're trying to add support for many or all machines DriverPacks is the best solution.
i can write the code in a few seconds... NBD... but thanks for the offer!
I am just not much of an artist... i just need someone to make the cool graphic!
It also occurs to me that the DSPD need not be a seperate app...
it could, and probably should, be part of the finisher itself.
although i think it is probably only neccessary with the finisher if KTD is enabled... not totaly positive on that one...
and KTD is now obsolete with the addition of SAD and DP_Inst_Tool
if those are the packs you selected for your slipstream... then yes.
With base 8.05 or newer KTD is no longer needed and is in fact a waste of 2 gig of HDD space.
KTD is considered an obsolite function... it has been replaced with SAD
SAD can be added / installed to your PC
or if you have a DriverPacks installation disk you can run the DP_Inst_tool.cmd right off the Disc.
TY
How are you integrateing the drivers?
mesh can be a verb the gears in the transmission meshed flawlessly
jaak is saying if the driver is not in the pack give us a link and we will add it
silicon hyll is a reference to the pain we all suffered with SI 3xxx series controllers
they conflicted with themselfs... the raid and non raid drivers would Kill each other and could not coexist...
we fought that battle for... it seemed like a year...
Posts found [ 2,801 to 2,825 of 5,302 ]
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.135 seconds, 5 queries executed ]