Search options (Page 159 of 213)

that darned revolving driverpack

based on your responses i belive you are prepared... and wish you luck...
there may still be a lurker who will chime in with a cheat sheet for you

We are all aware that the drivers are removable with nLite that needs no instructions.

If you are able to assemble a pack of Drivers that are equivilent to the included windows drivers then that would be a valid pack to submit to 3rd party DriverPack as a complete pack. just not the ones directly off the windows cd...
You could call it something obvious like  DP_XPDriverPackSoYouCanDeleteThemWithnLite.7zip LOL...

Welcome aboard...

ps i was telling you it was off topic not to get rid of you
but to tell you you may not get quality or timely help.

what you seek is contained in txtsetup.sif and dosnet.inf

i dare say if you were not able to come up with that on your own
then your biting off more than you can chew.

This is OFF Topic In that it is not related to DriverPacks at all
driver removal is not a supported feature of DriverPacks (obviously)

this IS a supported feature of nLite
you may find that you have excellent support there
Since it is within the scope of what they do.

although i will leave you with one thought
you could use nLite to remove them all
and then you could create a custom 3rd party DriverPack with your deleted drivers and call it
DP_XP_Drivers_that_I_didn't_really_want_deleted_after_all.7zip 

(i was teasing as i wrote this but i think it is valid to do what you want
however i don't think you will find better drivers than the included ones
and as you say they are licensed)

We try our very best to make no changes to the installation disk at all...
it is also a primary goal to operate within the spirit of the MS EULA
and as such we avoid entirely or given no alternative limit to a bare minimum any changes we make .

I do actually see the potential benefit of reducing the initial footprint of windows on the target machine.
at the same time i believe the installation that results would not be eligible for support
I believe it is OK for you to explain how to make your 3rd party DriverPack as long
as you don't package and distribute windows files
That certainly you could grow into a tool of some sort that an end user could use...
Giving back to the community is never a bad thing, it is self perpetuating...

again this is simply outside of our scope at DriverPacks...
Except for the part about instructions for a user created 3rd party DriverPack...
Those would be appropriate to that forum.
if you have any questions about creating one please ask.

have a nice day...

I am not positive without looking it up...
i think dpinst automatically creates a log

even if it doesnt i am quite certain  setupapi.log  IS updated
so there is a full log available if needed.
as far as a log of the script...
it logs to the active window so if it hangs, you know where...
(ummm unless you >null all the output! )

perhaps it would be easy enough to add somthing like...

@Echo off
REM Written by Jeff Herre AKA OverFlow rev08.05.27
REM A Script to use MicroSofts DPinst.exe with the DriverPacks.
REM Help and Support available at http://forum.DriverPacks.net  
TITLE DriverPacks Installation Tool
Color 9f
Set LOG=%SystemDrive%\DP_Install_Tool.log

Echo.
Echo Searching current drive for the DriverPacks...
Echo fast detect. (is it the current drive?) >> %LOG%
FOR /f "delims=: tokens=1" %%i in ("%~dp0") do SET CDDRIVE=%%i:
IF exist %CDDRIVE%\$OEM$\$1\D goto M1Found
IF exist %CDDRIVE%\OEM\bin\un7zip.exe GoTo M2Found

Echo.
Echo Searching all drives now...
Echo alternate detection. (is it any available drive?) >> %LOG% 
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:\$OEM$\$1\D" SET CDDRIVE=%%i:& GoTo M1Found 
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:\OEM\bin\un7zip.exe" SET CDDRIVE=%%i:& GoTo M2Found

Echo.
Echo The DriverPacks were not found ???
Echo The DriverPacks were not found ??? >> %LOG%
Pause
GoTo Done


:M2Found
Echo M2 Found >> %LOG%
Echo.
Echo Extracting the DriverPacks now...
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\DP*.7z %SystemDrive%\  %LOG%
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\bin\*.7z %SystemDrive%\ %LOG%
COPY /Y %CDDRIVE%\OEM\bin\DPsFnshr.ini %SystemDrive%\ >> %LOG%
IF EXIST %CDDRIVE%\OEM\*.ins COPY /Y %CDDRIVE%\OEM\*.ins %SystemDrive%\ >> %LOG%
COPY /Y %CDDRIVE%\OEM\DPINST.* %SystemDrive%\ >> %LOG%
GoTo Main


:M1Found
Echo M1 Found >> %LOG%
Echo.
Echo If you wish you may update drivers directly from the located M1 source
Echo Or you can use the DriverPacks and DP_Finisher with "Keep The Driver" option.
Echo If you choose Finisher and KTD then DriverPacks will be copied to "SystemDrive" 
Echo.
SET /p TPP=Only DriverPacks or Finisher and DriverPacks? (O or F) 
IF /I %TPP%==O Echo Running MicroSoft DPinst.exe without the DriverPacks Finisher now! >> %LOG%
IF /I %TPP%==O "%CDDRIVE%\$OEM$\$1\DPINST.exe" /c /s & GoTo Done 
XCOPY /S %CDDRIVE%\$OEM$\$1\. %SystemDrive% >> %LOG%


:Main
Echo.
Echo Running MicroSoft DPinst.exe now!
Echo Running MicroSoft DPinst.exe now! >> %LOG%
%SystemDrive%\DPINST.exe /c /s
Echo.
Echo Running the DriverPacks.net Finisher now!
Echo Running the DriverPacks.net Finisher now! >> %LOG%
%SystemDrive%\DPsFnshr.exe



:Done
EXIT

this is getting crazy... Nvidia has really missed the boat on PnP and seem oblivious to the fact.
i wonder if they are aware of it and don't care, or just don't understand how to fix it...

it has been fixed by them several times

it may be that you need to update your definitions in the installation package... or get a newer installer from them.

Glad your here... again!

please see read before you post in my signature and update your post please...

HWID's are always a good idea to include in a support request.
and most of the time DPs_BASE.log and DPs_BASE.ini are helpful.
the base log will tell us base versions and pack versions since you did not.
chipset version is not likely to cause mass storage issues. it is more likely mass storage...
we are unable to help you if you don't tell us basic info about your issue.

Welcome to DriverPacks and we hope to be able to help you.

Too funny !

yeah, i dont see this request having a down side and the advantages are obvious.

regarding difficulty, this is not.  but...
1) minimal time for my coding, error trapping, basic testing on all supported platforms
2) and medium level for the testing team
   i give this a medium to high difficulty rateing for feedback because;
   it requires manually checking the folders and file names and contents to verify it worked.
   normaly this takes weeks  - for a medium-high difficulty task maybe longer...
3) minimal time for RC release and final debug

I am sure this should be a feature - and i think timestamping the filenames is a great idea too...
I will credit both of you - excellent feedback on both the idea and suggestion.

which makes make think crazy thoughts for jaak to try like ...

[V3]
ms_count=2
ms_1_deviceName="VIA SATA/PATA IDE"
ms_1_tag="VIDEX32"
ms_1_sysFile="VIDEX32.sys"
ms_1_hwids="PCI\VEN_1106&DEV_3149&CC_0101"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k"
ms_2_deviceName="VIA SATA/PATA IDE"
ms_2_tag="VIDEX32"
ms_2_sysFile="VIDEX32.sys"
ms_2_hwids="PCI\VEN_1106&DEV_0571&CC_0101,PCI\VEN_1106&DEV_3149&CC_0101"
ms_2_isBusExtender=false
ms_2_exc_skipIfOS="wxp,w2k3"

I belive this resolves the issue for 2k and xp/2k3.
if in fact the HWID's list needing to be different for each OS an is a valid fix.
this could also extend to three different lists with -

ms_count=3
~ code for windows 2000 only
ms_1_exc_skipIfOS="wxp,w2k3"
~ code for windows 2003 only
ms_2_exc_skipIfOS="wxp,w2k"
~ code for windows XP only
ms_3_exc_skipIfOS="w2k,w2k3"

I have not tested this if this doesn't work i would consider that a bug

jeff

hmm it looks like you successfully added mass storage - textmode only
that should be perfect for testing... later you may want to add the rest of the packs.

the ICH chipset can emulate a standard IDE drive setup quite well.
it may be DriverPacks is forceing the raid driver when it is not needed?
you did not say if it was set in RAID mode or not...

if it is not in raid mode you may not need textmode driver at all
(but you will definatly want the mass storage pack selected - it will be used by setup later for PnP support)

Try it without the packs at all does that work? ? ? (i know it sounds silly)...

otherwise we may have to change the load order of some of our included drivers

tia