You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
I install windows from BartPE all the time... it works fine.
Start with a clean source.
Never add drivers with nLite.
always add DriverPacks as the last step in your process.
DriverPacks works fine with all MS supported languages.
If you follow the tutorial it WILL work...
If after you start with a clean source and then you are still having trouble please include your entire DPs_BASE.log...
ROFL...
And that's what you get if you can't (or won't) read the clear, consise and readily available info we post...
on each download page there is a "Details" button
Sound A -> http://driverpacks.net/driverpacks/wind … 06/drivers
Sound B -> http://driverpacks.net/driverpacks/wind … 06/drivers
there are also change-logs for each pack...
99% of our users include both (for that matter most people add all the main packs) ... and never give it a second thought.
Murphys Law must be applied here...
Whichever pack you didn't include will be the one you need for the computer you are currently working on.
Our goal has always been to include ALL drivers so they will be available for your installation... With that in mind the logical thing to do is to include ALL our packs... Then you will always have the drivers you need... If you really want to know what is in a pack that info is provided on the download pages 
.
thought it sounded like a bad reader or burn... Thanks for following up with your results!
Jeff
Welcome to DriverPacks!
reported to Wim!
Thanks for pointing it out
YIKES!!!!
Well number one the DP_Install_Tool.cmd has been modified by someone...
IE There are no errors like "Ho. is not recognized" in the main window with an unmodified DP_Install_Tool.cmd
It is REALLY hard to help if you don't tell us what you did 
.
number two you failed to read "read BEFORE you post"...
Otherwise you would have included your
DPs_BASE.log and
DPsFnshr.log and
HWIDs and
provided a description of what you did and
told us which version of the BT DriverPacks you used.
From Read BEFORE you post rule #6:
"6. Tell us what you did - Could we try to reproduce your issue ourselves just based on your first post?"
We look forward to assisting you, but you must first help us to help you.
Twig!!!! WAzzappppp! Third Party DriverPacks have not been the same in over a year!
So glad to see you!
Best wishes sir!
HDD controller drivers are the Mass Storage pack...
most likely the blue screen is due to a failure to include the proper mass storage driver
chipset is different ... (and a good idea)
HAL is built into the OS and not part of a driverpack...
IE single processor or multiprocessor support is built in to vista, not an add on.
Extremely long integration times are usually related to virus scanning software.
the post you linked to is not related ... you are not useing KTD...
It sounds like a bad disc or reader... have you tried to reburn the disc?
did you make ANY changes after you run DriverPacks BASE?
does the OEM folder exist at the root of your disc?
does OEM\bin\un7zip.exe exist? can you run it manually (on your disc)?
does \OEM\bin\DPsFnshr.7z exist? can you open it (on your disc)?
I have bolded it in the app and noted it in the app download page. Your feedback was acted upon, at least in BASE (Which I have the ability to change). Do you have the latest version?
I don't have access to the website to make changes there, but I have brought it to Wims attention.
On the website it is very clear which packs are for NT5.
Agreed... there is no indication that BASE will NOT do NT6 OS's until after it is downloaded.
bump
there it is!!!! I'll work on it!
KTD does not and will not do what you think it will...
you must run SAD for a software first installation (like Ghost), and even then it will only be 90% effective. KTD is more like a 50/50 proposition. KTD works well for monitors, modems, printers and like kind external devices. It absolutely will not, and can not, work for installations that will install chipset drivers, because a reboot is required after installing chipset and before installing drivers that depend on chipset. You can with pretty good success run SAD reboot run SAD again reboot and run SAD a third time.
The above instructions you referenced have been taken out of context and are to be used with SysPrep and are fairly effective when run with MiniSetup.
please review the stickied posts in universal imaging. It is not documented because it will NOT work. (at least not well)
hit and miss functionality is not encouraged or documented and supported.
Since what you want will not work *(reliably) it will not be documented into a tutorial
SAD is the replacement for KTD. KTD does not (and never did) do what most people mistakenly belive it will. Again it works fairly good for some monitors and a few modems and printers that do not require a setup.exe file to be run, and not much else.
If you are looking for KTD to be used to install an OS from one machine onto a different machine ... Forget IT!
I know what the differnce is cdob has posted it a couple times. I can never find it when i need it, like now. it has to do with hex editing the Hive files. since registy entries can not be created before the registy exists. I have not had time to integrate this into base... It only affects three or four poorly written drivers. more specifically the driver is not written to support legacy mode (dos).
I thought that i had stickied the CDOB posts about the fix but i can't find it (again).
Where did you get your source (a hologramed CD)?
did you make any changes to your source?
did you slipstream the driverpacks or install them by some other means?
is this sound device on the MB?
have you checked the CPU fan and heatsink for good airflow and proper seat?
overheating can cause strange issues. is the power supply fan running?
Nvidia is just a huge PITA...
Thanks for the feedback, We'll keep working on it!
Well the one thing we did not discuss was solid archive...
with a solid archive the entire pack must be extracted to get one file...
if we do not do this then apps which wish to only extract a single file will benefit greatly...
What is the negative impact of that on archive size
and do any of these apps do this (i belive they do)
We are always open to ideas... we don't always agree
Improved speed of indexing driverpacks(DriverPack Solution, Drivers Installer Assistant).
seems reasonable, and worth doing. this would also help other apps like WarmSnows and our own SAD platform.
how long it takes us to compress them is of little issue. We only have to do it once .
i find it hard to belive that increasing the dictionary size to 256 only increases the compression 3% (32, 64, 128, 256, = 3%?)
main questions not addressed...
How much does this increas the size of the (main) DriverPacks?
How much time is saved; @256mb ram, @384mb ram, @512mb ram, >512mb ram?
We discussed this years ago... I don't remember where the thread is now.
Erik used to use a huge dictionary size and we had people who were not even able to extract them on machines with 128 meg of ram... at that time he reduced the size of the dictionary.
The higher dictionary size means the better compression, but it is slower and needs more memory. Memory usage for LZMA compressing is about 10 times more than dictionary size. Memory usage for LZMA decompressing is close to value of dictionary size.
the command line presented is
..\7za.exe a ..\out\%1 -mmt=off -m0=BCJ2 -m1=LZMA:d%2m:fb273 -m2=LZMA:d512k -m3=LZMA:d512k -mb0:1 -mb0s1:2 -mb0s2:3 *.ini -ir!*.inf
note -mmt=off Seems odd.
If a machine supports hyperthreading then why disable it?
This will drastically reduce performance when creating the archive on a PC that supports hyperthreading. (like mine)
I too am curious how much time we are talking about...
Since the max dictionary size on the version of 7zip we use is 256 - I have a hard time beliving that there are really that many machines that have less than 256 meg of free ram... If someone is running on a machine with less than 256 meg of free ram then shame on them. We should not penalize everyone else with a viable system to cater to a few people whos machines aren't even valid for windows xp anyway. (less than 256 meg of free ram is not valid in my opinion). IE the base system ram should be at least 384 meg, 512 prefered.
It is my belief that this recomendation will only help machines that are not viable for XP anyway.
A machine with less than 512 meg of RAM is going to be painfully slow, period.
I belive that xp boxes with less than 512 meg of ram are a very small percentage of the total machines running XP.
if a machine only has 256 meg of ram (total)... then load win98se on it and call it a day .
If a machine has 512 meg of ram or more on it (and the vast majority do) it is my belief this will have little or no effect at all... am i wrong?
How much does this increas the size of the (main) DriverPacks?
How much time is saved; @256mb ram, @384mb ram, @512mb ram, >512mb ram?
Again...
Use a proxy that is not close to your location and you will recieve the content from a different "mirror"
Simple CDN has hundreds of "mirrors", but they don't have a feature to allow someone to manually choose one of them from a list. The selection is automated based on your location. by useing a proxy that is not close to you (IE it will cause the CDN to select a different "mirror".
this same issue IS posted in several places...
IN fact it is stickied in both "feedback and support" and in "site and forum issues" (which are the obvious places to look) and a few other places...
- our search feature works too 
-
here is the meat of it
We use a Content Delivery Network (CDN) which automagically mirrors for us, and and auto-selects the closest / fastest server / mirror for you.
It is my guess that the problems are isolated to one (or a few) server clusters.
We have millions of downloads successful. I assume one post represents thousands or tens of thousands of users. That being true we have a small percentage of failures.
Please include your IP or Geographic region so we can lean on simple CDN.
Those of you needing an alternate download location:
The problem is isolated to certain servers, each providing service to a local region.
The workaround is then obvious.
Use a proxy that is not in your geographic region. you can Google for open proxies.
By using a proxy that is not close to you it will fool the CDN to supply the content from another server. (the CDN will think you are close to a different server cluster) Simple.
code 10 "usually" means that the device is not functioning properly (hardware failure... IE "is it plugged in").
Sometimes this error will show up on old MBs where interrupt conflicts prevented a device from communicating properly.
It may be the driver... but that specific error makes the device itself (hardware) suspect.
thanks for reporting
I'm moving this to Feedback and support BASE... requests...
From the MS documentation
"/q or /s
Sets the quietInstall flag to ON, which suppresses the display of wizard pages, user dialog boxes, and other user messages that DPInst and Windows generate. The quietInstall flag works with the presence of an end-user license agreement (EULA) page and the suppressEulaPage flag."
so our DPInst.exe /c /s is the equivelent of useing the xml entry <quietMode/>
Perhaps we should try
<?xml version="1.0" ?>
<dpinst>
<search>
<subDirectory>*</subDirectory>
</search>
<scanHardware/>
<suppressWizard/>
<legacyMode/>
<enableNotListedLanguages/>
<suppressAddRemovePrograms/>
</dpinst>Start "MicroSoft Driver Pack Installer Tool Running" /wait /separate /realtime /min CMD /C DPInst.exe /cand see if that is better
Thanks for your feedback SEOTool, it helps make DriverPacks better for everyone!!!!
Jeff
Apple supports thier own drivers... mr_smartepants has pointed out their archive a few times.
Win 7 drivers are already provided... they are listed as "Vista" (both are Win NT 6.x platforms) Wim intends to make that more clear on the site. We had originaly planned on having them separate... but it was not neccessary and was in fact going to be more dificult, since most providers bundle the Vista and WIn 7 drivers together anyway.
Can you tell us where you downloaded (region / country) and what time? So we can forward that to support at our download provider (Simple CDN).
If you use a proxy you can easily get the file off of a different simple CDN server cluster. (Google "open proxy") By using a proxy in another country location you can fool the CDN into providing the content from a server close to the proxy instead of close to you . simple cdn's network automatically provides the content from the closest / least loaded server.
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.126 seconds, 5 queries executed ]