won't do him any good - he doesn't have the hardware smile

use the 3rd party DriverPack FTP if you like or rapid share or whatever...
A link to the file on OEM's site would be the best wink

Is it the same version he is pointing too?

When you installed windows 2000 did you use a win 2000 source that had DriverPacks slipstreamed?
this provides the mass storage support

DON'T run makePNF... if you are useing skinlayers method...

It is probably easier to run SAD from runonce or guirunonce than to use the skinlayers method. wink

I am going to move this to feature requests

these both are problematic...

SetupParams executes from winnt.sif at T-9 minute stage  - Before the reboot.
Some drivers may not finish if the reboot does not occur before running it... wink


Detached program cannot be used to run DriverPacks... if it could we would not have a fake setup.

The problem with detached program is it runs in parrallel with setup.exe. (not before it, but at the same time)
so the system will start installing devices before DriverPacks will have finished extracting the drivers LOL
that would make for some really cool support issues - sometimes it works, sometimes it doesn't LOL

That is why fakesetup exists, it waits till the DriverPacks are fully extracted before calling the original setup.exe (which installs the drivers)

Simple explanation
we rename ms's setup.exe to setuporg.exe
put in our own setup.exe (we refer to it as "fake setup")
Our setup.exe calls presetup.cmd then calls setuporg.exe
thus we can pause windows setup long enough to put the DriverPacks in place for setup to find.

the alternative is to manipulate the files during textmode (Uggg)

I appreciate the input!

ping -n 20 IPaddress

might work nicely...
use the built in timeout feature as a delay wink
you could even use a bigger number or longer timeout (-w 9999 is about ten seconds)

so  "start /wait ping -n 20 -w 9999 192.168.1.1" would pause execution and wait up to 200 seconds for the connection to become live.

once the connection is live the replys will come quickly and the timeout will automaticaly end smile


Bashrat is not the only sneaky one wink tongue

2,331

(6 replies, posted in DriverPack Chipset)

DriverPacks mass storage can not be integrated with nLite.
it is not a good idea to install any of the DriverPacks with nLite

If you could do that we would not provide DriverPacks BASE wink

DriverPacks doesn't ever use drivers provided by third parties

and we do not encourage our users to do so either. (no worrys about us hosting it, or even recomending it for that matter) I don't think we have a rule against it either... so it can stay unless a mod disagrees with me wink

Thank you for responding to the OP with an offer of help.
We always like that... It is in the spirit of what we do.

Welcome both of you to DriverPacks and have a great day.

http://www.google.com/search?q=Sysprep+ … 1I7GGLL_en

http://www.microsoft.com/downloads/deta … layLang=en

http://technet.microsoft.com/en-us/libr … 77113.aspx
http://technet.microsoft.com/en-us/libr … 77109.aspx
http://technet.microsoft.com/en-us/libr … 77159.aspx

DriverPacks SAD feature can be used to update drivers post install...

If your sysprep image was installed with a windows 2k source slipstreamed with DriverPack MassStorage.
Then you should be able to set your HDD controller to standard IDE (or simply remove it) before you shut down to create your image.
when the PC first boots the HDD controler type should be detected automaticaly.

useing Skinlayers guide skip the mass storage, MakePNF and KTD parts...

Creating the \D\folders and running devpath works fine...

Why don't you try it and see how far you get and then ask us some specific questions as you encounter Issues...

Thanks

and the voting begins...

Ideas?

the DP_ part is and the platform id is currently hard coded...
so other anything other than that it would be easy wink

DP_3P-PackName_x86-32_Version.7z  is a good idea

Welcome to DriverPacks JOHANSEN... SkinLayers may not get back to you right away he stops by now and then... wink

were you having a specific problem?

Is it possable to check the firmware / BIOS and flash/update...

Sometimes newer drivers drop support for old firmware versions

Jake put the update out to the team a few minutes ago

mass 9.05r1

the ink is not even dry yet wink. But it looks like the 'L8' update (the 'Late' update hee hee) was included.

Thanks a Million JakeLD
- I hope your trip was Pleasant and educational! Welcome back.

Chad Andrew Syphrett, looking for help with Windows XP drivers... on a Linux forum! 
http://ubuntuforums.org/showthread.php?p=7248601
I knew something that funny just could not be made up... ROFL

He also seems to be active on the Warez Scene...

At this rate he will be getting a Darwin award too...

smile now that I know he is 25 and not 15 (at least physically)
We will allow his post / thread to be a top google hit on his name and his alias...
That should help him to bite his tongue and show due respect in the future.

Thanks for bringing us into the fold... (Now I know why they call you NewsPoster)

We will notify the company that their services are no longer required wink

I will dial it back another notch since he has such well known issues...
I was trying to not get to carried away with it realizing he was immature.

Thanks again!

Jeff

Welcome to the DriverPacks.net forums!

Below are a list of guidelines we have provided in order to help ensure everyone has a favorable visit here at DriverPacks.net.

Remember … we have only one "rule":

Less is more: no extensive rules. Simply act responsible.
~
Wim Leers

This is how the team interprets 'responsible':

Forum Rules

0. Read this before posting a request for our help.

1. This is not a warez site! Links to or requests for warez and/or illegal material (OS discs, porn, cracks, serials, etc.) will not be tolerated. Discussion of circumventing WGA/activation/timebombs/keygens or any other illegal activity will not be tolerated. Advertising is also forbidden. If you violate any of the aforementioned you will be banned from this site without further notice.
Consider this the one and only warning for the above list of egregious items
  1a.  We do not support warez or pirated installs.  Our definition of this is:  Did you obtain your license from Microsoft or an authorized OEM vendor?  Do you have a legal hologram-ed disc?  If the answers to both of those questions is "Yes", please continue.  Otherwise, go legit or go home.  Warez is a support nightmare for the DriverPacks staff.  99% of the DriverPacks failures are caused by the idiot who modified/released the pirated OS source in the first place because they didn't know what they were doing. 

2. Topics devoted to political or religious debate, unless technology related, are prohibited. DriverPacks.net is a driver support forum and political debates are just too far off topic. Political links in signatures, and any polite and courteous comments, in otherwise non-political topics are allowed, but we will not allow and may remove any topics where the content is solely a debate of politics.

3. No user shall by any means of the forum: sell, trade or give away; hardware, software, or any other non consumer or electronic related material. DriverPacks.net does not support any type of trade, sale or gifting, and shall not be held accountable.

4. Please do not post large screenshots within threads. (exceeding 300x200 px in resolution and/or 150 KB in size.) Provide a link to any large images and please host on your own web space if possible. If you do not have personal web space try imageshack.us or tinypic.com.

5. Spamming will not be tolerated. [Duh] We have provided an "Other" section for those members who wish to share their personal websites or off topic discussions, but not commercial ones. Please use that section only. We do log all IP traffic on this site and will simply block you, so don't even bother trying.

6. Images in signatures should NOT exceed a total of 260x80 px and 80 KB in size. Flash and animated sigs are discouraged. You can enter max 5 lines of text and 650 characters in a signature or signature image. Advertising and/or affiliates are not allowed in signatures nor avatars. (With the exception of one small link in addition to your signature, just NO overt advertising). If your signature link leads to a site with a shopping cart it will be deleted. If your avatar or signature seems to us to have exceeded the above guidelines it will be edited without any additional notice required from us. Members with slow connection can disable other members signatures when reading posts by going to: Profile -> Display -> Set options.

7. If you need to attach something, it'd be great if you could find a host for the file. Please only email something if you absolutely have no other option.

8. You are expected to be mature when discussing in threads. Racism, pornography, threatening, profanity, personal attacks, or excessive vulgarity are not tolerated. You will be promptly banned … or worse. No exceptions. This community is built upon mutual respect. You are not allowed to wage personal attacks against other members. People who do not respect personal opinions and/or personal work will be warned in first instance. If you ignore the warning and keep on flaming, you will be banned (or worse) without any notice.

9. Has the thread you started or participated in been moved, closed or deleted? We might have just been bored. Check with the forum moderator via forum email. Under no circumstances should a thread be started asking why other threads were moderated. Forum moderation is not up for public debate, such threads will be deleted and the thread starter warned. DriverPacks.net reserves the right to edit, delete or move posts made on this site. The previous also goes for signatures that have been modified or removed. All decisions of the DriverPacks team are final and non negotiable. So say we all...

10. We do not encourage the raising of post counts or creating threads that state you have reached a post count milestone, unlike other forums that do. Please remember there's no prizes in store for those with a very high number of posts! (except for the coveted DriverPacks Maniac title we will award for  the first one reaching 1 million posts wink - LOL)

11. Please refrain from using CAPITALIZATION in the topic title or when participating in threads because they will not attract attention - instead it will annoy many of DriverPacks.net members.  POSTING IN ALL CAPS is equivalent to shouting.  Please don't, it hurts our ears.

12. Please do not bash old topics when a member has made it active again, it's been made active for a good reason; to answer an unanswered question, or to bring new information. It does not need to be closed or deleted. In fact we like it when our users can find related material to their issue. We encourage this behavior.

13. (see rule 0) Use some common sense. Don't post your question under multiple forums. Remember to engage brain first, then post. Take a minute and be thoughtful when creating the topic title for a new thread. People do judge a book by its cover. When posting, have something to say, not just "My First post!" or "Cool site!!!" We already know it's your first post and sort of have the idea how this site looks by now :-). Poor judgment when posting will result in a demerit, and we wouldn't want that would we? wink

14. (see rule 0) Very often we see meaningless subjects in topic title giving absolutely no clue what the post / thread is about.

Good examples of a Bad Title:
- Oh no!
- Help
- I'm mad
- Please help
- Question
- I need your help
- Hmmmm ....
- Whoa Dude!
These and similar bad titles can and should be avoided! Simply enter something more specific and descriptive in the topic title. It's easier for us to help if you do!

A few good examples of a Good Title:
- [BUG] BSOD with DriverPack Graphics A 9.04 on ATI Radeon 9800Pro
- RunOnceEx install problem (double installation)
- [REQ]uest - add driver for Toshiba modem model xxxx
- [HELP] BASE 8.12.4 3rd party DriverPack for Game controller
- BartPE HDD not found BASE 8.12.4, MassStorage 9.03r1

15. (see rule 0.) Use the correct tags for a new topic
- Available tags for members:
[BUG] - If you are getting a Windows error message, program error message, or any other type of error.
[REQ] - Request to add a feature or driver
[HELP] - If you need help changing settings or configuring a feature.
[How-to] - If you have a guide on how to do something.
[Question] - If you have a question that doesn't fall under any of the above categories. No errors or help requests.
[Misc] - If your topic doesn't fit into anything else here.
- Additional tags for moderators:
[IMPL] - Request was implemented in current DriverPacks. 
[SLVD] - Problem/bug was solved in current DriverPacks.  Also used to indicate where a question was answered.
[CLSD] - Topic closed or locked.  Either because the issue was resolved, or because of rule violations.

We would like to make everyone's visit here a pleasant one,
and if you have observed the above guide you should be safe tongue wink


Posting Guidelines


How To Ask Questions The Smart Way is a good read for any user, especially if you think any of the following is harsh. 

Although quite easy to use, the DriverPacks and the accompanying software form a toolset that is designed for use by advanced level users. 
If you have not used the search feature of this forum, or Google. AKA, STFW
If you do not include basic details (See rule #0)
If you have not read the FAQ's or documentation BartPE Tutorial   DP_Base Tutorial
If you did not include your HWID's or DPs_BASE.log in your post

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 it's obvious that you failed to read this post and 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 perceived 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)
    You are expected to already be familiar with everything in this guide.
    http://unattended.msfn.org/unattended.xp/
    If you ask a question that is covered in that manual then you will receive a demerit. roll

If you will expect us to take our personal time to support you, then we can likewise expect:
a) You will take a minute to include good details in your post.
b) You will have already read our documentation and tutorials.

If one of the team seems to have been short with you...
Perhaps you should make sure you have been respectful / appreciative.
We are working for free.

Think to yourself: "Could I reproduce my issue with just the info I have provided in my post and title?"
This does not need to be a wordy or involved task.   In Example (IE)

Title "[BUG] Finisher - Base 8.12.4 - Sound A 9.01 & Sound B 9.01"
I used RVM to add SP3 and updates to my XP, then nLite to automate it, I run DriverPacks BASE with all packs and mass textmode, then create ISO with nLite.
Sound drivers are installed but the Control panel is not.
The relevant part of the finisher log is included below.
the HWID for the sound card is PCI/VenxxxxSubxxxRev12

LOG here

If the answer to "Could I reproduce..." is 'yes',
and you have double checked "Read BEFORE you post" (AKA rule 0.)
Then you should be welcomed with open arms - and possibly breakfast.


Enjoy your stay at DriverPacks.net!

Regards,
The DriverPacks.net Administration Team

===================================================
The original of the above guide was donated to Mr_smartepants
and once again he did most of the work editing it to work for DriverPacks…
I simply plagiarized it here and added a few lines big_smile tongue wink
It is considered to be open for review, comments and suggested edits, to the entire team.
(If you are a member... then you are part of our team too.)
Mods of course can help themselves to adding any omissions, removing, correcting, rewording for clarity etc...

Off Topic...

Does it work if you select BusLogic... ? ? ?

NewsAndHistory wrote:

I admit, you've proven 1 thing: you're a complete idiot. You've failed to answer simple questions, once again.

I'm sad for your mom. She could have done a lot better. I hope she doesn't have anymore children (including grandchildren). You & her are from a bad gene pool, obviously.

My mom died an agonizing death from cancer at age 67...
and her grand children (my kids) have 4.0 GPAs (as did I)

So, now we know you are a teenager. wink
- I could be your daddy - whats your moms name?

We are not here to cater to your educational needs... sorry about your luck


DriverPacks is for advanced users only...
We don't tolerate or answer newbie questions.
I will print it really large so you can read it this time

NOBODY HERE IS GOING TO HELP YOU.
XP x64 is NOT SUPPORTED
XP x64 is JUNK if you want proof try google (you may have heard of it)

No help will be offered to anyone for noob level issues at DriverPacks...
Our 'members in good standing' do not need their little hands held, like you obviously do.

I did not 'fail' to answer your questions
- We have no obligation to you or your questions, at all...
   Why do you feel we OWE you an answer?
   (To prove we are smarter than you... Nope we covered that already. LOL)
   (Because you donated... mmm... Nope. You didn't.)
   (Because the info is not available anywhere else... Nope, It's readily available)
- I told you your questions are inappropriate here and we are not going to answer them.
          (The above line is describing what NOT SUPPORTED means.
          Since you don't seem to understand english very well I thought I should spell it out.)
     There is a huge difference between failing to answer,
     and deliberately not answering questions you were Clearly Told were Unsupported .
- Let this fact sink in...     we don't owe you anything... you are not entitled to sh*t...
     you however do owe us... we are owed respect, in return for your membership. 
     Failure to meet this expectation is dealt with harshly.
- Why is it simple ideas like "Not Supported" or "Chipset driver" just do not register in your brain?
- You assumed I was a teenager, YET AGAIN failing to do any research (or thinking) on your own.

Dell doesn't support it, we don't support it, MS doesn't support it... Notice a pattern developing here...
Ask yourself...
Q  Why doesn't anyone support it...
A  Because it is garbage, and can't be properly supported
- not even by Dell... and especialy not on that particular machine. (POS)

HINT: Feature Requests forum (this is and naming your chipset are the only help you are getting...)
  - One demerit awarded -

---- edit

NewsAndHistory wrote:

Where exactly, in that person's message does she/he say, nVidia? Did you know I did search your forum for answers to my driver-related questions before I posted (above)? Obviously, you're not thinking straight.

You have not shown anything to prove your assumptions are worth 2 cents. You claimed that XP 64-bit is "junk", but where's your evidence to prove that? Do you think you're 1 of the leading experts on Dell computers or Microsoft operating systems?

You've made many assumptions, but you've failed to show me facts.

You assume too much. That's why you're a moron. Tell me the truth, and stop lying out of your ass. Your forum is almost as shitty as your mind. Your ignorance shines. It's hard to miss, when your head isn't stuck up your ass, and you have no idea which direction leads to the exit. You're lost in your own asshole.

Your proof was provided by you... (would you like a link to that?)
Dell doesn't support it... (Can we assume Dell is a leading expert on Dell computers?)
That is proof enough for an intelligent person.

Do you think you're 1 of the leading experts on Dell computers or Microsoft operating systems?

Since I have been into computers since 1968 and started my MicroSoft education with the release of DOS 1...
Have a college degree in programming. Have personally serviced many thousands of Dells with every imaginable MS OS on them, over a period of several decades. (I think a Compaq even managed to slip in there once. wink)

- I would say YES I am - One of many thousands of leading experts...
- The ENTIRE DriverPacks Team has credentials that are just as good, or better...
- this ain't the 'kiddy korner' buddy
- DriverPacks is downloaded at the rate of a million times a day (note there are no support issues)
- We all have already earned our reputations, many times over.

The members of the DriverPacks Team ARE the leading experts on drivers for MS OS's. (and install, maint, repair of) 
At least everyone who publishes DriverPacks in all of the many magazine guides, Blogs, and our hundreds of millions of users all think and say so.
---- edit

LOL - I am a moron... LOL

Where exactly, in that person's message does she/he say, nVidia?

UM... 
You gave me that info yourself. . .  (Moron)
- I ask Google,  Dell Inspiron 531S has What Chipset? - Answer:  Nvidia
I know this must seem like brain surgery to someone with your skill level... (Skill level ID ten T)
let me write it in big letters for you  HTTP://GOOGLE.COM  (unlike the Dell rep I gave you a link wink)
I'm truly sorry for your complete ignorance and total lack of initiative.
   Obviously one of us is not thinking straight (Or at all for that matter)... (hint: it is not me)
   I do not assume... you are just obtuse.  That just makes it seem like I assumed.
   Because you are not smart enough to connect the dots yourself does not automatically make my answer an assumption.
   I Researched the facts you gave me... Something you should have done yourself, but are obviously incapable.
   (so you are either too ignorant or too lazy... you pick - but the answer given is valid and not assumed at all)
If you can't figure out on your own what chipset YOU have on YOUR PC then you are in WAY OVER your head. (blatant fact)
- you need to face facts,
1 You're not even capable of discovering your personal PCs chipset without someone else looking it up for you...
     (I was able to come up with the chipset info in less than a minute... and I don't even have the PC to look at wink 
2 Dell support stuck the answer(s) right under your nose... and still you were (are) clueless.
    The Dell support answer was flawless...
    You're just bitter because they did not spoon feed you.
    They are not allowed to help you if your issue is unsupported. (DUH)
    He even gave you a good hint, and he probably had to stick his neck out to give that much to you, yet you are bitter. You should be thankful since he did give you the answer even though it was unsupported, and I am sure his boss would say he is told to turn you away empty handed. I consider that "Value Added Service" Cudos to the person who took your request.
   
Will the moron please stand up! (yes you)

I stick by my previous statements and add this...
you are not only a Bonehead, you are a very lazy ill-mannered Bonehead... (don't make me use the t word)

Plus you can't even find the x64 thread here at DriverPacks... and it is stickied...   That is major lame dude.


Go away now little one...
PS nobody here is going to spoon feed you info or hold your little hand.
--- edit
We are not your mom and this is not your room. temper tantrums are not tolerated.
DriverPacks is for big boys wink
--- edit

XP x64 is junk and it is WELL documented here, and elsewhere.
Just because you are unable to use a search engine does not mean the info is not out there big_smile

DriverPacks does not now nor have we in the past catered to noobs.

2,345

(35 replies, posted in Windows 7 Discussion)

Wow this is exciting stuff... I am seeing light at the end of the tunnel - and i don't hear a train!

We do not support XP x64...

Even the lamest attempt at a search of our forum would have yielded you that answer...
since you were also unable to find the reference drivers I assume this is a little over your head.

You just want it, you don't even know why you want it,
or how it works, or what the disadvantages are.
You are probably determined to do this because
someone who probably knows even less about it than you do told you it was a good thing...
It is not a good thing

The Short story is XP x64 is Junk... It is at least as much garbage as Vista is.
MS doesn't even support it... it was / is a poor attempt at 2k3 workstation.

If you want a decent x64 support win7 is your best option ATM

PS - The Dell guy DID tell you where to get drivers...
Key Word "ChipSet"...  IE Nvidia wink
He also tried to tell you XP x64 was a bad plan...
- Do you think Dell does not have the resources to support any 'viable' OS?
     * It is not supported for a reason tongue (perhaps many reasons wink)
you were (are?) not listening...

Too funny...
There is a Screen there Titled "Device Type"
but the IDE and SCSI choice's are not presented... LOL
I guess ESX 4 is not as much like VMWare 4 as I assumed

Thanks for educating me.

Um... we are going to need to look at this further...

Will you please subscribe to this thread so you can test a fix for us when one is available?

you could... but they would still collide...
RunOnce and GUIRunOnce do not wait for a program to finish before calling the next command yikes
and if you have auto login enabled then GUIRunOnce will start running while RunOnceEx is still executing wink
You have to use Start /Wait - and that may not always work either wink (Programs that use a launcher / extractor app)

you can select runonce from DriverPacks BASE too... rather than doing it manually wink
the default 937 should not interfere with anything... (looks like you used 000)

Simple solution:
If you Create a New HDD you will be offered IDE or SCSI
- no real benefit to selecting SCSI in a VM that I know of?
- Create an IDE / default volume instead

Almost as simple solution:
I can get you a copy of the nightly (The testing teams version.) of the DriverPacks mass storage pack big_smile !
( offering pack blatantly this time... )
If you accept the nightly offer then you are obligated to report your results good or bad... tongue


We already know an older Mass storage pack works - ( [8.05] and that is  Good Info  thank you)


PS
It occurred to me that, it may not be obvious to non team members,
there is almost always a newer version of most of our Packs that are only available to the DriverPacks team.
- Just because we haven't released a new version
  does not mean there is not a newer version of a DriverPack.
    - Sadly every day one or more of our nightly packs die...
      We receive many reports of horrible and agonizing deaths at the hands of our team.
      Only those packs that can survive multiple reincarnation / DriverPacks Team thrashings,
        ( including SamLab - Who can break anything wink LOL ),
        and are "-Inspector 13-" approved,
        will ever see a "final status" and get a release date.
  - You cant just dump a bunch of drivers into a folder structure and call it a DriverPack (I WISH) big_smile



Our best testers are people like you , who can expose a repeatable failure sad, and hopefully prove a fix.

Jaak calls that "Help us to Help You.", and we like that a lot.

2,350

(17 replies, posted in Hardware)

try this just for giggles

Make a UBCD4Win CD and test to see if it finds your HDD... ???
(no need to make any custom changes just go with the default settings wink)

Since by default UBCD4Win uses DriverPacks drivers
if the UBCD4Win CD works (finds the HDD)
then so should a DriverPacks slipstreamed OS install wink big_smile

If nothing else  you will be able to run the HWID's tool from UBCD4Win and get the translated HWID's. LOL
- oops sorry one small change, you need to add HWID's tool to your disk wink