3,101

(5 replies, posted in Feedback and Support - DriverPacks Base)

Jaak wrote:

In our future, MSFT will take care of many things we did for free, and they may do it for free.

The tools MSFT develop(ed) to do this may be scripted to, or may be (made) distributable and (then) scripted to.

Well, DPINST.exe worked out great for us.  We'll just have to wait and see what M$ releases into the wild.

3,102

(20 replies, posted in DriverPack Sound)

Got them!  I'll be replacing SMC1 with these.  They're 2 months newer and have more HWIDs. 
I'll also prune the rest of DriverPack Sound B to make sure everything's clear.

I guess I'll just remove the empty sma9 dir eh?

3,103

(20 replies, posted in DriverPack Sound)

I took a deeper look at these.  They're a newer replacement for \SMC1\ and they add about a dozen more HWIDs we didn't have before.  Unfortunately, the archive King Cobra sent me is missing 3 files called in the .inf.  I've emailed him for the missing files.  If he mails them back, I can add them.

rdrown wrote:

Where are the setup*.log files located at?

%systemroot% (ie. C:\Windows\ )
They're named setupact.log (huge), setupapi.log, setuperr.log (should be empty), setuplog.txt (also large).
They'll give you insight where the problem was during setup.

3,105

(11 replies, posted in DriverPack Mass Storage)

I have that exact same HWID on my Gigabyte MB (different subsys): PCI\VEN_197B&DEV_2363
I have zero problems in AHCI, RAID and legacy (IDE).

3,106

(5 replies, posted in Software)

It's possible this 'copy' was burned at too high a speed.  Slower the speed, the more reliable the burn.

HWIDS?
Sounds like a driver hanging.  Check your setup*.log files.
I thought Hyper-V was only with W2k3 server with that feature, not XP.

I'm confused, is this a problem in live metal, or only VM?

3,108

(20 replies, posted in DriverPack Sound)

It's a soundmax audio driver.  Not really old, but old.  It's possible I can just put it in the empty folder.
Two birds with one stone... smile

Wow, I don't even have my w2k source anymore! sad

3,110

(20 replies, posted in DriverPack Sound)

I'm looking at the drivers he emailed me.  This one has a handful of HWIDs we can use.  I"ll just have to figure out where to put them for the next nightly.
The other drivers are all duplicated elsewhere.

Sigh...

q123 wrote:

actually the xp setup source was given by a friend of mine

That's software piracy.
You cannot "start over" with a preintegrated source without problems.
Start over with a "Clean" (as in hologramed legitimate XP CD).

3,112

(5 replies, posted in DriverPack Graphics)

Well, to be fair, Win7 is beta.  M$ themselves said that driver support at this stage is experimental.  Nvidia is quoted as saying their driver included with Win7 should be used instead of the 181.20 download.  I'm sure ATI is no better.
With that old hardware, ditch both Win7 and Vista and go back to XP, you'll be much happier.

3,113

(5 replies, posted in DriverPack Graphics)

Driver: http://ati.amd.com/support/drivers/xp/r … 00-xp.html
Mod tool: http://www.driverheaven.net/modtool.php

Can you post your DPs_BASE.log?  dpms 901 did add Nvidia.  To \NV6\nvgts.inf

I still don't understand why the HWIDs get jumbled in Cyrillic languages.

Renaming the .inf files should not break driver signing.  So you should be fine there.  Overall, it doesn't matter.  Just a further refinement of an already great dp. smile

How about changing the presetup.cmd line from:
SET TAGFILE=\OEM
to: SET TAGFILE=\OEM\bin\un7zip.exe

It's being called 6 lines later anyway.
Besides, \OEM isn't a 'tagfile', it's a 'tagdir'. wink

Very nice!  And an excellent first post!  Welcome to DriverPacks.net!

Bledi wrote:

where shall i find this unmodified (no driverpacks added) OEM windows XP cd ???

If you don't own it, we will not help you.
Warez discussion here is not tolerated.  Go legit or go home.
@Bledi, our support to you for DriverPacks ends now, unless you find your original LEGAL XP disc.  If you didn't pay for it, or it wasn't provided by your PC maker, is is NOT legal.

Feel free to come back for assistance once you've got your PC back within the confines of the law.
Here's the steps:
1. Read the tutorial.
2. Start with your original legal XP disc.
3. If your disc does not include SP3, integrate it.
4. Run DriverPacks BASE and follow the tutorial.
5. Build your ISO and test.

@Mods, should I close thread?  This problem was solved with the latest DriverPacks BASE correct?

The root of his problem is this line:

REM +==========================================================================+
REM |   Decompressing the DriverPacks to the harddisk - using un7zip.exe.      |
REM |--------------------------------------------------------------------------|
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\DRIVER.7z %SystemDrive%\

\oem\driver.7z does not exist therefore cannot be extracted.

OverFlow wrote:

If you are not part of the solution then you are part of the problem.

Or just part of the scenery tongue
I think my first post here was something like "Why haven't you updated the DriverPack Graphics A?"
I got slammed that time too.
big_smile

JakeLD wrote:

I want my life back. Thanks. big_smile

Don't we all! tongue

That scores a hit from PCI\VEN_10DE&DEV_037F&CC_0101 in dpms \NVTM\NVATABUSTM.inf but NOT NVRAIDTM.inf
Were you trying those SATA drives in RAID, AHCI, or IDE (compatibility) mode?

3,122

(15 replies, posted in DriverPack Mass Storage)

JakeLD wrote:

You remember Nick Burns from SNL ?

Yeah!  I miss the old episodes with Gilda Radner, John Candy, Dan Akeroyd, Chevy Chase, etc.
The new ones are just dumb.

I suggest you put back PCI\VEN_8086&DEV_2829 in the I3 section of the INI file and remove it from I4 and give a second try.

This fixes the VirtualBox problem. smile

3,123

(15 replies, posted in DriverPack Mass Storage)

I haven't had a chance to test this yet, but I will.
Thank you Jake! tongue

Fragbert wrote:

Updated to v6.14.10.5016.

OK, I have it in the latest nightly on my desk.  But I've got some serious cleanup in the nvidia sections.  Wow, what a mess with the duplicate HWIDs.
Give me a few days to fix before I upload OK?

OK, so maybe a statement was taken out of context, or maybe something was lost in the translation.
Whatever.
DriverPacks are not emailed to anybody.  We may email someone a link to a test dp for someone with specific hardware to test on.  Our DriverPacks do not get finalized without extensive testing!
Contrary to popular belief, we do not have an underground bunker with limitless supplies of PC hardware to conduct testing on. wink
We need everyone to help test new DriverPacks on all available hardware...even you.

Having said that, unwarranted personal attacks to/from members of staff are frowned upon.  Think of these forums as like a customer service counter.  We are here to help, but don't poke us in the eye either.
I firmly believe that "the customer is NOT always right, but should always have the right to be heard."

gvgb wrote:

At this point I'd like to ask from you to show some character and do the right thing as I'm sure that's what your conscience also tells you.

So what exactly are you asking for?