You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
please use code tags (updated your post for you)
RU using Galapos OffLineSysprep for mass storage?
If not you should be. (and it makes your request unneccessary)
You also forgot to mention that Devcon must be in your C:\lng folder for your script to work.
PS If you hate Dell then it is a good thing you were not around in the old days and having to deploy to compaqs. 
It was (is) a bug on the server due to adding NT6 drivers to the download page
- I belive it is fixed now
Pardon our dust!
Edit Nope still broken...
I reported it to Wim. We will have to wait for a resolution from him!
Thanks for reporting it makes DriverPacks better for everyone!!!
PS Those packs ARE still in use.
There ar not any updates for them yet either so you haven't missed anything .
You can go to http://driverpacks.net/driverpacks (home page) to get / verify them manually if you wish .
Awesome!
Please put them on the nightly server
Use this naming convention
[DP_blah_blah_wnt6-x86_version.7z] for Vista/7 32-bit
[DP_blah_blah_wnt6-x64_version.7z] for Vista/7 64-bit
Thanks for the help... please post testing team related stuff in the testing team forum
Thanks again!!!!
He was using Muiz direct links from the forum rather than the links from http://driverpacks.net/downloads
Since Muiz and I were working on the packs only the links on the downloads page were working. (since they are automatic)
Muiz had to go back manually and update all the direct links. 
Sure no problem... I'll take a good hard look at it...
I am not exactly sure how to attack that though... it looks like it worked 313 out of 314 times 
.
Thanks a million for reminding me or I would certainly forgotten!
Have an awesome day!
PS fixed this bug in my testing copy - look forward to an email any day. I have to go through and make sure I have not broken anything in other changes i have made to the source.
Jeff
Sure we are open to having DriverPacks for linux. The real question is "do you have any volunteers to create and maintain these packs?".
No your users do not have to buy XP... MS has downgrade rights for their OS's.
In MOST cases If you have a license for Vista / Win 7 you can install XP as a substitute.
This is clearly outlined in their EULA. Please read it / them for specifics.
You may also have to read specific OEM licenses as they can differ from Retail and Site license.
http://oem.microsoft.com/script/Content … eid=553075 - Skip down to "Downgrade Rights" and you will find this...
Q. What are downgrade rights and how would my customer benefit from downgrade rights?
A. Downgrade rights refer to the ability of your customers to acquire the most recent version of Microsoft software but continue to run a previous version until they are ready to upgrade. Downgrade rights are an end-user right and are documented in the product End-user license agreement.Q. Where can I find out more information on downgrade rights?
A. Please visit http://oem.microsoft.com/downgrade for more information.Q. Who can install the downgrade software or reinstall the original software?
A. A System Builder (when authorized by end user), or the end user. Because downgrade rights are an end user right granted in the end user license agreement (EULA), the end-user must first be able to accept the (EULA) associated with Windows Vista Business, Windows Vista Ultimate, Windows XP Professional, Windows Server 2003 or Windows Small Business Server 2003 software, so this software must be installed first before the downgrade software is installed.Q. Where do customers get the CD/media to install the Downgrade Software?
A. End users must use a legally licensed version of the specified previous version of the Windows desktop or server operating system to install the Downgrade Software. The Downgrade Software may be from the retail, OEM/System Builder, or volume licensing channels.
Follow the link http://oem.microsoft.com/script/content … eID=552836 and a convenient chart is supplied to outline the options.
Thanks for your thoughts and ideas and please let us know if you are volunteering to help with this .
Have an awesome day!
Jeff
PS I belive it is only a matter of time before reference drivers are available for these chips. (That is if they are not already)
Please use the links on the home page instead http://driverpacks.net/driverpacks
Please use the links on the home page instead http://driverpacks.net/driverpacks
Please use the links on the home page instead http://driverpacks.net/driverpacks
Please use the links on the home page instead http://driverpacks.net/driverpacks
Read this similar post
http://forum.driverpacks.net/viewtopic. … 080#p36080
and this one
http://forum.driverpacks.net/viewtopic. … 056#p36056
and this one
http://forum.driverpacks.net/viewtopic. … 053#p36053
Since you did STFF no demerits have been awarded
summary
Read posting guidelines in the rules section...
Take special note of the first rule (#0) AKA 'Read BEFORE you post'
(Linked to in my signature below and It's in every main team members signatures for that matter.)
When asking for help on DriverPacks.net one must first be a DriverPacks user, and you're not, and you did not read the rules.
Hint: DriverPacks support forum means we support DriverPacks . (Dell support supports Dell )
Woo Hoo,
I got a second report of a similar issue and it put me over the top on finding the culprit code!!!!
I posted my findings in the other thread here http://forum.driverpacks.net/viewtopic. … 093#p36093
Good news!!!
OK i have figured out HOW the problem occurs you and Dumpydooby are both victims of the exact same issue...
when we Replace an existing driver in the pack We must remove all entries related to that driver from the Dosnet and Txtsetup files...
A "replacement" is what we call it when we upgrade a driver that exists natively in windows....
UNFORTUNATLY we replace a driver called ULTRA
[P8]
ms_count=1
ms_1_deviceName="Promise SATAII150 TX2plus"
ms_1_tag="ultra"
ms_1_sysFile="ultra.sys"
ms_1_hwids="PCI\VEN_105A&DEV_4d33,PCI\VEN_105A&DEV_4D69,PCI\VEN_105A&DEV_4D68,PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A,PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A,PCI\VEN_105A&DEV_4D38&SUBSYS_4D33105A"
ms_1_isBusExtender=false
ms_1_exc_replaceIfOS="wxp,w2k3"
Notice the replaceIfOS tag
Now
Notice the lines that get deleted in your txtsetup.sif file (both of you) that are also very similar in name IE ultra*.*
ultradf3.cab = 100,,,,,,_x,,3,3
ultradf3.inf = 100,,,,,,,20,0,0
ultradfg.sif = 100,,,,,,_x,,3,3
ultradfg.sys = 100,,,,,,,4,0,0,,1,4
UltraISO.CAB = 1,,,,,,_x,,3,3
UltraISO.inf = 1,,,,,,,20,0,0
dfrg.exe = 100,,,,,,,2,0,0,ultradefrag.exe
Working on it now. I belive it has to do with nested quotation marks in the Fedit.exe routines
Obviously this only happens in 'ultra' rare cases.
IE Only if an addon Starts with same name as the replacement mass storage driver
So at least now I know:
How it happens.
What part of the code is doing it.
What triggers it.
I belive the problem is related to a really ugly set of nested quotes in a line similar to this
_runDos("""""" & @scriptDir & "\bin\Fedit.exe"" -rem -f """ & $_I386 & "\txtsetup.sif"" -s:c ""SourceDisksFiles"" -l:o """ & $NameOfDriverToReplace & """""")working on a fix I will email you two for testing when I think i have it
Highlander999 is working on an update to BartPE that will fix most of the issues with sound video and oddball devices that require advanced PnP support. Most of the issues are related to missing registry entries. It is WAY over my head or I would try and explain it to you so your issue can be solved to . (It is my belief that missing registry entries are your obstacle)
"0. Read this before posting a request for our help."
"If you create a post that says "I am looking for a driver for"
(Especially if you have not used the DriverPacks at all.)"
Then your welcome here may not be as warm and fuzzy as you might like.
The above mistakes are considered Noob like behaviors...
We are not and have never been a noob friendly site.
- Note to Newbies:
The label Noob is not assigned based on a percieved level of experience,
but rather for showing a lack of resourcefulness, (Did you try to help yourself?)
or failing to demonstrate some effort was made to help us to help you. (omission of key details)
This is the support forum for DriverPacks. Not dell support, Nor BCL easyPDF conversion software support.
If you need support for your Dell... Contact Dell (Duh)
Dell support is GREAT! Try it...
If you need support for BCL easyPDF conversion software then contact them...
Only questions related to DriverPacks are appropriate at DriverPacks.net.
Instructions to install that driver are on the Dell download page click " Installation Instructions " and follow the directions.
If that does not work Read the Drivers help page or Call them!
PS Your Security software said not to trust Dell? Use some common sense... silly boy!
I am moving this to the BartPE forum - Thanks again for all the feedback!
Now that is what i expected to see in windows...
PCI\VEN_14E4&DEV_164C&SUBSYS_7038103C is a valid HWID and exists in bxvbd.inf for platform HPQ.ntx86. That means it is for NT5 all versions of 32 bit OSs IE Win2k XP and 2K3. (64 bit versions are specifically excluded.) install requires bxvbdx.sys and bxvbd.inf and it seems as though WdfCoInstaller01007.dll is also required.
try adding the folowing lines to [SourceDisksFiles] in the LAN.inf if they are not already
wnt5\WdfCoInstaller01007.dll=2,,1
wnt5\bxvbd.inf=20,,1
wnt5\bxvbdx.sys=4,,1
and adding the WdfCoInstaller01007.dll to the wnt5 folder if it is not...
and make sure that the bxvbdx.sys and bxvbd.inf files are in the wnt5 folder too
Obviously all from the Download you pointed to for me
Just guessing here I have asked two of the UBCD4Win guys to drop by...
I'm sure they will know exactly what to do, but perhaps they want me to figure it out on my own this time lol
yes the hwids reported in device manager in UBCD4Win must appear in the INF we used. (or a compatable ID)
"0. Read this before posting a request for our help."
"If you create a post that says "I am looking for a driver for"
(Especially if you have not used the DriverPacks at all.)"
Then your welcome here may not be as warm and fuzzy as you might like.
The above mistakes are considered Noob like behaviors...
We are not and have never been a noob friendly site.
- Note to Newbies:
The label Noob is not assigned based on a percieved level of experience,
but rather for showing a lack of resourcefulness, (Did you try to help yourself?)
or failing to demonstrate some effort was made to help us to help you. (omission of key details)
Wow... this is indeed a rare bug! reported here Dumpydooby's Report at the bugtracker too.
I thought it was isolated to the certain file names dumpydooby reported... It seems it is not.
I am working on code this week so I'll switch gears and see if i can figure it out. Having two examples should make it MUCH easier to nail down!
Thanks for reporting it makes DriverPacks better for everyone! I second the motion... Outstanding first post!
Welcome to DriverPacks, we're glad your here.
Jeff
PS Feel free to Add a BUG report and reference DD's report. (there is a field for that.)
DriverPacks BASE tutorial in my signature...
Read "Read BEFORE you post" also in my signature. (Rule #0)
Read posting guidelines in the rules section...
TWO Demerits have been awarded.
One for your title, and one for asking for a driver...
That may be a new record for someones first post... lol
(please note the difference between a Noob and a Newbie as outlined in the rules 
.)
Ah ha!...
You are installing XP and you do not have SP3 installed yet, therefore you do not have KB888111 installed and therefore HDA (High Definition Audio) is not supported. You must either install KB888111 or SP3 first before you can install your sound driver. (SP3 includes KB888111)
This is not a driver issue it is a Microsoft issue! and is why you can't find that HWID.
It is not a driver it's an OS patch / update.
NOTE: once you install sp3 or KB888111 then your actual sound hardware will show up and need drivers
- more: KB888111 is a "Bus" driver and the devices connected to the Bus are not visible until the Bus is installed...
just like PCI devices would not show up if PCI were not supported
they did try to tell you... "HDA audio bus driver is not found"
Driverforge is supplied by our good friend Kickarse who is a member in good standing at DriverPacks and a respected friend.
However we (the DriverPacks team) do not support driverforge...
If Kickarse sees this or a related issue he may offer help... but we don't see him everyday.
You could always send him an email using the forum mail feature .
DriverPacks BASE is designed to be used by IT people but it is not terribly difficult to use.
the tutorial (linked in our signatures) will explain how to add drivers to an install disc.
That is the primary function of BASE is to add drivers to the install media so finding drivers is never necessary again.
- had you used DriverPacks BASE to slipstream your drivers to XP SP2 BASE would have also added KB888111 for you automatically .
We do have a feature in DriverPacks BASE called SAD (Stand Alone Drivers)
That feature is described in the Frequently Asked Questions forum. (well yeah...)
The description in the FAQ assumes you have already read the tutorial...
SAD is supported by our forum !
SAD will also fail if your OS is not properly patched (IE you still have to install KB888111 first)
Source means...
We support lots of source OS's windows 2000, windows XP, Windows 2003 Server, Windows Vista, windows Server 2008, Windows 7, and multiple Service packs for each of those OS's....
So the question "What is your source?" means "please tell us what you are doing because we are not psychic"
If we assume you are installing Windows 7 but you are installing windows 2000 then you will get the wrong answers.
If you are installing windows XP then you must say so, or we don't know. If we don't know then we can't help!
If you are installing windows XP then it MATTERS if it is plain XP or XP with Service Pack 1 (SP1), or Service Pack 2 (SP2), or Service Pack 3 (SP3). Again we are not psychic, If you are updating XP (SP0) the answer is different than if you are installing XP SP3. Same thing for the other OS's. We include the link to "Read Before you post" in our signatures to make sure that these details are provided to us so we can offer useful answers... if you read the Rules and Posting Guidelines almost every rule references Rule #0 AKA "Read before you post". #6 is kind of a sleeper... but please consider, I cant reproduce your issue if I don't know what source / OS you are using...
We often refer to this as "help us to help you" details are the key .
To put it another way... what if I asked you "Why does my ford escort not start" How could you possibly answer that question? There is simply not enough details for you to provide me a useful answer... best you can do is start playing 20 questions. We don't like that game .
Help us to help you!
"read before you post" Will help / guide you to provide us good details in the future...
Like:
What pack versions did you use?
What is your OS? Including the service pack level installed. (AKA your Source.)
What are the HWIDs of the device? (HWIDs tool in my signature) [I do realize you supplied a partial HWID]
What was your process? did you format the machine? Are you attempting a repair? ? ? ?
We do like to help you - but you have to help us first!
( Your issue is solved if you install sp3 or KB888111)
how about the win7 folder... on his site is best place... he has excelent bandwidth
sorry about that i lept before i looked
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.216 seconds, 5 queries executed ]