5,001 Reply by OverFlow

(8 replies, posted in DriverPack Sound)

I attempt to avoid OEM drivers and instead opt for Reference drivers.

I have seen cases where an Nvidia reference driver failed on a dell and the actual dell driver was needed. this is rare.
It is more likey that a driver that has been tweaked for a Dell would not work on a non dell card.

can we find the reference driver from the chipset manufacturer ?

if you have a machine that has special needs then make a special disk for it - but generaly not good for the masses.

a reference driver will also support a larger HWID and re-manufactuer base

so i would check IDT (formerly sigmatel) or realtek

strange that it says it is a cmajor audio (sigmatel) when the Dell technical specs say it should be an AC97 (Realtek)

There are a lot of dell PCs out there so we are bound to have  Some  dell drivers in the packs - no problem.
Lets just attempt to find reference drivers when we can...

(larger lists of supported HWIDS and less likely to have issues)

Go to forum: DriverPack Sound

5,002 Reply by OverFlow

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

@freinds
Where did you get that means that the version is not verifyable to the server list
this may mean the server was unavailable when you requested. it may mean you have a bunch iof test packs too... ;-)
 
@ben
the rest of the section is just to make the finisher run the exe since the exe is not there no finishing required.
therefore section not required - you may also notice most of the driversw don't have any entries. if a driver has a section it is by my definition an "exception"

please remember that the finisher does not install drivers... (so yes it will still be installed) it adds things that are not installed by the drivers inf file (it adds control panels and start menu shortcuts that kind of stuff)

@All
for the 1000 th time the finisher DOES NOT INSTALL DRIVERS!

Go to forum: Feedback and Support - DriverPacks Base

5,003 Reply by OverFlow

(4 replies, posted in Translations Team)

please put it up ... thank you... welcome!

Go to forum: Translations Team

5,004 Reply by OverFlow

(15 replies, posted in Frequently Asked Questions)

jaak checkout benjamminzIS other thread i found the problem its in sound b can we get that in the nightly...

Go to forum: Frequently Asked Questions

5,005 Reply by OverFlow

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

I NEED the rest of your LOGS!!!!  - ignored completely jeeezz... i can only ask nice so many times sorry...
and you just kept replying with a number of scripts we didnt write.
I had every reason to belive you never tried a clean install so where was i to start troubleshooting?
you gave me one log to go on... in your 15 posts about this.

Your Logs allow me to see why things happen, that is why we log...
the log would have told me what was different about your system - everyone else has no problem

your HWID's from the one log you provided put me there.

Had that been in your first post instead of two weeks later...   then you wouldnt feel like you do about me.

please check our "read before you post" in my sig below and see how many you can check off the list. ?

i know exactly what your problem is now...

i am assumeing you have DP_Sound_B_wnt5_x86-32_7102.7z even though your post indicates an older version

[T-5]
; REQUIRED
exc_count    = 1
; OPTIONAL
exc_1_tagFiles    = 1
exc_1_tagFile1    = "%SystemRoot%\system32\drivers\dmxsens.sys"
exc_1_+hwids    = 0
exc_1_-hwids    = 0
exc_1_+infFiles    = 1
exc_1_+infFile1    = "%DPSROOT%\D\S\T\5\*.inf"
exc_1_-infFiles    = 0
exc_1_commands    = 1
exc_1_command1    = "%DPSROOT%\D\S\T\5\T_DMX.exe"

refers to a removed exe in the pack

delete this section from the DriverPack_Sound_B_wnt5_x86-32.ini and repack

done

Go to forum: Feedback and Support - DriverPacks Base

5,006 Reply by OverFlow

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

doesn't get any faster than that...

Go to forum: Feedback and Support - DriverPacks Base

5,007 Reply by OverFlow

(15 replies, posted in Frequently Asked Questions)

ristech wrote:

Here's what I have done so far by following your posts:
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD        = "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation    = "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC        = "yes"

KTD=false will remove your drivers when finisher runs. Since you did not rerun windows setup it wont update existing devices in your machine you have to do that by hand.

i dont' know how many times i have to say this the DriverPacks Finisher DOES NOT INSTALL DRIVERS. - - - PERIOD!

it adds SOFTWARE to PREVIOUSLY INSTALLED drivers (like control panel files or raid management GUI, ect... things that are normaly installed by running an executable installer program)


example i run an install without the driverpacks on a machine that has an ATI card
it gets added to device manager as a standard VGA card
i run a KTD script like above and run the finisher since the ati card is not installed the finisher will not install the ATI control panel and why should it since there is not ATI card in the system per device manager???

Do you see why this cannot work???

Go to forum: Frequently Asked Questions

5,008 Reply by OverFlow

(15 replies, posted in Frequently Asked Questions)

@all adding drivers to an existing system is not tough at all.
KTD is designed for what i call an air system its a MB, hdd and powersupply on a workbench. If i think i have a bad sound card i pull it out of the client machine and drop it on my "air system" since i have never had this device in my sytem before pnp searches and finds the driver.

perfect...

KTD is not practical for a regular install say i add a device 6 months from now do i really want to auto install a 6 month old driver? No.
KTD is only useful for a test machine that gets reloaded often. that being the case why add it afterwards just reload it . Done.

KTD will not enable you to magicaly make all those devices with yellow exclamation points disappear.
this is because windows setup has already enumerated all the devices in your system. and added them to device manager as unsupported devices  and its not going to check again setup is overwith...

now you can add a folder to the pnp search path and manually remove the devices from device manger and then search for new hardware.

but there is now way from base to clean up the mess made by not making the drivers available to setup.

That is the key they have to be there to begin with or there is not much point

Go to forum: Frequently Asked Questions

5,009 Reply by OverFlow

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

Welcome to DriverPacks.net solata10,

the $oem$ folders are only copied if oempreinstall is set to yes in winnt.sif...

this problem is an issue created when IE7 is not slipstreamed properly and therefore should not be DP related... but ya never know.

how are you adding IE7?

Go to forum: Feedback and Support - DriverPacks Base

5,010 Reply by OverFlow

(1 replies, posted in Installation Platforms)

welcome to driverpacks

its called method 2 it slipstreams all drivers and has no known limit.

method one has this limit because the drivers are added in text mode instead of in GUI mode.

only method one has this limit (in text mode setup) and method one is considered obsolete by many including Bâshrat the Sneaky

based on the title of your post you may be wanting to use KTD (Keep The Driver) search for that if so...
or create a drivers only cd search for that if so

both subjects are coverd extensively and have stickies

if you truely are wanting a "master drivers cd" (and not a slipstream) windows would be running in GUI mode and have no limit on the search path.

if you are wanting a cd you can just pop in and use as a master drivers cd then just create a method one disk and copy all the files from

$OEM$\$1\D  to a CD this CD can be used for the search removable media option in add new hardware. no limit...

Go to forum: Installation Platforms

5,011 Reply by OverFlow

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

You have written a lot of code to to fail to do a process that is built in to the base...

and the built in version works flawlessly.

if you insist it doesnt - then run it normaly (no custom scripts) and produce your logs

cmdlines.txt
Runonceex.cmd
DPs_BASE.log
DPs_BASE.ini
DPsFnshr.log
DPsFnshr.ini

the ONLY reason it would not run is if you overwrite the registry entry for finisher with another registry entry like this

overwriteing a registry entry example DON'T DO THIS:
SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx
REG ADD %KEY%\996 /V 1 /D "%SystemDrive%\DPsFnshr.exe"
REG ADD %KEY%\996 /V 1 /D "%drive%\WPI\WPI.hta"


this is VALID
SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx
REG ADD %KEY%\996 /V 1 /D "%SystemDrive%\DPsFnshr.exe"
REG ADD %KEY%\996 /V 2 /D "%drive%\WPI\WPI.hta"


that is why i suggested GUI runonce instead of runonceexe to rule this out... however you seemingly ignored this advice.

your not the first / only one here who installs on dual boot platforms

Go to forum: Feedback and Support - DriverPacks Base

5,012 Reply by OverFlow

(15 replies, posted in Frequently Asked Questions)

This forum is for adding driverpacks after the installation
IE it was installed without driverpacks KTD and we wish to upgrade it.

Slipstream ALL Latest Packs except for Graphics B & C and Sound A. Using method 2 with QSC enabled and KTD disabled (but I want to KTD so I modified the FINI.cmd will post it below).

WHY? what a silly thing to do...  " i want KTD so i disabled it " [and now it doesnt work - DUH!]

Did you read Jaaks post???

Jaak wrote:

hmmm

fini.cmd proved to be a no good useless bit of experimental work.

you are trying to manually duplicate this process needlessly since the DP base already provides teh functionality you want and why should we help you when we have provided a simple way to get the result you desire.

If you are able to get something useful working by all means let us know. If it doesnt work it's not much help is it?

since you are installing clean you can just enable KTD from base and your done. 

it's that simple.  please post in the appropriate threads.

Go to forum: Frequently Asked Questions

5,013 Reply by OverFlow

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

Hello ibliss,
Welcome to DriverPacks.net Glad your here...

Please edit your title and preceed it with [PROB] so it gets noticed by the team.
Since this is a Sound issue you might have put it there, but this feedback forum is fine.

We will get it back in there for you since you indicated replaceing the file was a valid fix.

Go to forum: Feedback and Support - DriverPacks Base

5,014 Reply by OverFlow

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

hidden feature? you mean like mapping it that way? or useing subst command...

Go to forum: Feedback and Support - DriverPacks Base

5,015 Reply by OverFlow

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

nlite also has the same limit it just doesnt tell you you have exceeded it like we do ;-)

its a microsoft limit not a driverpacks limit that is why we came up with M2

but for this to work your I386 folder must be in the root or it wont find setup.exe.

yes  \\share\i386

no   \\share\clients\MS\xp\I386

(same configuration as an OEM disk)

Go to forum: Feedback and Support - DriverPacks Base

5,016 Reply by OverFlow

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

AVG Free v7.5 Did indeed report it as a trojan...

But it's not it disables the beep for the driversigning popup window (very annoying if KTD is on.)

Either create an exception or report it as a false positive to AVG

you can delete it if you want its not mission critical

Go to forum: Feedback and Support - DriverPacks Base

5,017 Reply by OverFlow

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

that file hasnt been touched in 6 months (we log)

its a false positve did you verify the hash on your download ?

i have avg on a UBCD4win disk im loading it now... which engine and definition dates?

Go to forum: Feedback and Support - DriverPacks Base

5,018 Reply by OverFlow

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

from a clean system redownload base from us and verify the hash... then scan
(not the same machine as before unless you format)

thousands of other users have not reported anything...

what virus scanner / version / definition dates supplied this positive...
what is the SARC or other description of this payload

Go to forum: Feedback and Support - DriverPacks Base

5,019 Reply by OverFlow

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

Jaak why don't you use that as a rough draft for thread and well get it stickied for multi OS disks and Multi OS UnAttended Windows DVD
which i furthermore will refer to as      (are you ready)

MOSUWDVD 

- Pronounced    Moo-Sue-DVD

LOL

Go to forum: Feedback and Support - DriverPacks Base

5,020 Reply by OverFlow

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

Simply disableing a drive in the bios is not enough to keep windows from finding a drive... you may have to completely remove it
or you may have to use systemroot\..\ instead of systemdrive which may become muddled on a dual boot system. since the system drive is the boot drive not the installation drive. in theory this would not matter and should proceed normaly. send us your logs (see below)


1  try just running base on a clean source (no nlite  no ryanvm no nothing) select custom for the finisher. and dont run it at all...

take a good look ath the source disk folders and then do a VMware install and look at the folders particularly SystemDrive and systemdrive\d\

2  run base on a clean source (no nlite  no ryanvm no nothing) select guirunonce for the finisher.

if this dose not work show us your DPs_BASE.ini and DPs_BASE.log and \WINDOWS\dpsFnshr.log

i for one dont really care to trouble shoot / syntax check your code - that is not our niche. this isnt the script kiddie forum.
that said... you code is doomed to fail

:DOPNFCHECK1
if exist "%systemroot%\DriverPacks\D\C" (
    GOTO :CHECK2
    ) ELSE (
        GOTO :DOPNF

refers to a missing location :CHECK2 therefore anytime chipset was included your script would crash... and i assume you did no error trapping when you call this command? or you would have known this already.

use it the way is was intended first (out of the box if you will)  before you try to reinvent the wheel.


the three stooges go out and get a station wagon with the wood side panels they take it home an proceed to tear all the paneling off...
They stand back and take a look at it afterwards and one looks at the other and says "I liked it better in the box"

Go to forum: Feedback and Support - DriverPacks Base

5,021 Reply by OverFlow

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

got rid of your dup posts for ya jaak

Did you get this to work Mike?

Go to forum: Feedback and Support - DriverPacks Base

5,022 Reply by OverFlow

(1 replies, posted in Feature Requests)

can you ask a specific question?

when your done with hfslip run base... seems to be the short answer.
adding driverpacks useing DPs_Base.exe is the last step... always.

Go to forum: Feature Requests

5,023 Reply by OverFlow

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

Welcome to driverpacks.net

Let us know how this works out for you... this is not a supported setup but im intrigued...

Go to forum: Feedback and Support - DriverPacks Base

5,024 Reply by OverFlow

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

that is an issue because we intercept the call to setup.exe and then recall the original in method 2
see \i386\PRESETUP.CMD and i think you will discover your issue...
it is very possable that you dont need all the packs (Wlan is a path monster for example)
and i would hate to think you were pushing an install wireless. wink

so you amy be able to switch back to method one and make it work if you must have all the packs consider KTD and then you could jsut check device manager for devices that didnt make the txtmodepnp path cut (ktd / gui-pnp does not have this limit which is why m2 is prefered)

Go to forum: Feedback and Support - DriverPacks Base

5,025 Reply by OverFlow

(97 replies, posted in DriverPack Sound)

We are all working on different pieces that will all come together. The things that get tested and prove effective will be in a final release.
Not all of our test packs make it. most do. We can release (main team members) at any time we wish. We choose not to release garbage and look foolish if we can help it.  we don't always win that battle due to shortages of active testers and the broad base of hardware they bring to the table. You can take advantage of the fact that Muiz has pronounced it a final. that implies he is done with his peice of the pie.
Download his test version to see if it is broken by testing it. Once you realize its not broken add your fix and put it up as  test pack 71122
and can be the next release. i assure you no ones work will be abandoned if it is needed and effective. I had that happen to me when i signed on here and before it was open source.


I can add your fix right now if i want... lets proceed slowly and with due caution.

Go to forum: DriverPack Sound