1,776

(4 replies, posted in Universal Imaging)

A wise man learns from his own mistakes, but a wiser man learns from the mistakes of others. wink

Well first off you are correct.  There is no detailed guide on how to integrate the drivers easily.  But there is a sticky (in this section) on how to use DISM for Win7.  It's crude, and uses the command-line.   I feel comfortable with it, but not everyone will.
Next, you do NOT need all the DriverPacks.  This isn't documented anywhere but the more DriverPacks you integrate into your Win7 source, the more space is required on the hard drive during install.  It's an unfortunate truth.  Realistically, you would integrate only chipset, LAN, & Mass Storage.  Then use a SAD disc for the rest (or all) of the DriverPacks.  This is how I build mine, and works well.  Nobody really needs 3d graphics and HD audio DURING the install. wink
Your graphics card would work perfectly fine during the install by using the built in M$ driver.  Then update it afterwards with the newer drivers.

We are considering developing a new DriverPacks BASE specifically for Win7 (maybe Vista also), but we have neither the time, nor motivation ($$$) to do it right now.  Without a common utility, a detailed how-to is nearly impossible.

1,778

(12 replies, posted in Software)

brunetu wrote:

, but it would be useful to know if eg. DP Sound A is for dedicated sound boards and DP Sound B for integrated chips.

No, the sound DriverPacks don't follow that kind of pattern.  But I love the idea. smile
Sound A for "Add-in" cards and Sound B for "Built-in" chips.
Hmmm, I wonder what the file separation would be...

For now, DriverPack Sound A has Creative, Realtek & Via.  DriverPack Sound B supports all others.  It seemed appropriate at the time.

1,779

(8 replies, posted in Software)

I wouldn't bother using any nt6 OS, the hardware wouldn't handle it.
  Checking the spec sheet here the server came with a Pentium 4.  Which is not a 64-bit processor.
That's why there are no 64-bit drivers on the Dell site.  While the chipset supports 64-bit memory addressing, the CPU must also be 64-bit for the OS to work properly.

I think you're just asking for a world of hurt going this route.
Stick with W2k3 (32-bit) or XP.  You'll be much happier.

1,780

(1 replies, posted in Other)

I deleted the other 5 identical topics.  This behavior would constitute spamming the forums.  But I'm willing to let this infraction slide...for now.
Watch your self.

1,781

(20 replies, posted in 3rd Party Vista / 7 DriverPacks)

I don't see any problem with it.  It's a Third Party DriverPack, do what you think is right.
I created a new \nt6\x64 (& x86) directory on the Third Party DriverPack ftp server.

1,782

(2 replies, posted in DriverPack LAN)

The NV3 folder in your pack is identical in every way to the NV1 folder in the current release candidate.  The only exception to this is the .inf in your pack has the HWID PCI\VEN_10DE&DEV_0269 commented out, so I've done the same.
I've also added some of the functionality of your .ini exception.

1,783

(5 replies, posted in Other)

Welcome to DriverPacks.
This should get you started: http://tinyurl.com/39nhobm
It's the first link. wink

1,784

(1 replies, posted in DriverPack Sound)

Same here.  They're servers must have problems.

1,785

(20 replies, posted in 3rd Party Vista / 7 DriverPacks)

Why not just use the Third Party DriverPacks ftp server?

Glad it worked!  We may release dpms soon, so I may ask you to test a release candidate later.

1,787

(5 replies, posted in 3rd Party DriverPacks)

Updated to 10.11

Any update to this?  It's been nearly a week.
Still waiting for test results from the test packs.

I'm working this into a dpms release candidate...but I need test results!

1,789

(3 replies, posted in 3rd Party DriverPacks)

Yup, they're all there.  I made sure.

HWIDs please?
Which source are you using?  BPE?  WPE? UBCD4win?

1,791

(45 replies, posted in 3rd Party DriverPacks)

Uploaded 10.11

1,792

(25 replies, posted in 3rd Party DriverPacks)

10.11 uploaded

Please let us know.  Jmicron works fine on my PC, both in a live install and in virtualbox.
It's possible a rogue addon corrupted the txtsetup.sif file.

1,794

(3 replies, posted in 3rd Party DriverPacks)

I find it amazing that the Modem 10.10 didn't work for you when every single HWID in the driver you linked is contained in the modem Third Party DriverPack \M2\ folder, and folder \M2 is newer also.
Very strange.
If I add the driver you linked, it will never install because \M2 will over-ride it.

Sorry, Request denied. sad

1,795

(22 replies, posted in 3rd Party Vista / 7 DriverPacks)

I've uploaded the original from the first post.  Nobody uses this particular pack much.  So if you feel up to it, you can make an updated version.
http://www.mediafire.com/file/d4438rauw … x64_908.7z

Run the HWID tool linked in my signature.  Then follow the instructions in this FAQ post to find any compatible drivers.
The one you're referencing is VERY old. wink
But yes, that .inf appears to be broken.

I'm working on fixing dpms.  Would you be able to test a nightly build for us?  Your HWID was previously supported, but in the wrong place.
Test packs are in this thread: http://forum.driverpacks.net/viewtopic.php?id=4742
Please test pack #17 & #18 and let us know your results.

1,798

(1 replies, posted in Feature Requests)

Pirates are NOT supported.
Go legit or go home.
Distributing ANY version of Windows without a license from M$ is illegal (activators or not).
This is your one and only warning.
Banned for one day for soliciting warez (violation of Rule #1).  Read the "Read before you post" linked in my signature.
Follow the rules or your stay here will be brief.

1,799

(3 replies, posted in 3rd Party DriverPacks)

LOL, they already are in DriverPack Chipset.
Folders Ia thru Ie.  And I2\1-5 also.

jschafer wrote:

I've tried like 5 different copies of the amd ahci drivers.
Just can't figure it out.  are there some other drivers I have to integrate?

Umm, did you try the DriverPacks?
How are you building your image?  Sysprep, offline-sysprep, etc?  We have lots of stickies from folks who are pros at this stuff, I suggest you read them first.
Welcome to DriverPacks.