3,951 Reply by OverFlow

(14 replies, posted in Other)

this is a feature of DriverPacks.

you can create a driverpack (or modify an existing) and
use the INI in the DriverPack to launch an application
based on the presence of a specific HWID. or specific File name (like its driver file name).

the entry in the ini may look like this

[CR2]
; REQUIRED
exc_count    = 1
; OPTIONAL
exc_1_tagFiles    = 2
exc_1_tagFile1    = "%SystemRoot%\system32\drivers\P17.sys"
exc_1_tagFile2    = "%DPSROOT%\D\S\CR2\Ctzapxx.ini"
exc_1_+hwids    = 0
exc_1_-hwids    = 0
exc_1_+infFiles    = 1
exc_1_+infFile1    = "%DPSROOT%\D\S\CR2\Win2k_xp\*.inf"
exc_1_-infFiles    = 0
exc_1_commands    = 1
exc_1_command1    = "%DPSROOT%\D\S\CR2\ctzapxx.exe /S"



this says that if the file "%SystemRoot%\system32\drivers\P17.sys" is found
execute --> ctzapxx.exe /S


explained...
P17.sys will only exist if the device is present and its driver was successfully installed in the machine
if both of these things are true then we need to run the devices installer
to provide control panels and other features that compliment but are not part of the actual driver.

there is quite a bit of info already documented here on this topic -

Go to forum: Other

3,952 Reply by OverFlow

(13 replies, posted in DriverPack Graphics)

that darned revolving driverpack wink tongue

Go to forum: DriverPack Graphics

3,953 Reply by OverFlow

(1 replies, posted in Software)

what if i need a lan driver... wink

Go to forum: Software

3,954 Reply by OverFlow

(6 replies, posted in Other)

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 wink

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... wink

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. wink

Go to forum: Other

3,955 Reply by OverFlow

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

can you use the tool in my signature to give us the hwid?

probably it is in the lan pack
but it may be in the wlan pack

are you useing DriverPacks to install windows?

Go to forum: Feedback and Support - DriverPacks Base

3,956 Reply by OverFlow

(6 replies, posted in Other)

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  tongue

(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 wink
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...

Go to forum: Other

3,957 Reply by OverFlow

(14 replies, posted in Universal Imaging)

Jaak only reinforced Rules ONE and TWO. NEVER work on your original files -
let me put that a different way     NEVER  EVER  work on any original files for ANY reason  wink
Data is to IT   like   Life is to a Surgeon  big_smile       

1 always backup the users drive.
and if the machine will run
2 always virus scan.


I recommend you use DriverPacks with all the main packs plus a few like the monitor and modem packs from third party.
if you need to update drivers in a system you can simply drop the disk in and double click on DP_Install_Tool.cmd

Go to forum: Universal Imaging

3,958 Reply by OverFlow

(13 replies, posted in Feature Requests)

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... wink
(ummm unless you >null all the output! tongue )

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

Go to forum: Feature Requests

3,959 Reply by OverFlow

(8 replies, posted in DriverPack LAN)

Hee hee i feel that pain too wink

Go to forum: DriverPack LAN

3,960 Reply by OverFlow

(6 replies, posted in DriverPack LAN)

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...

Go to forum: DriverPack LAN

3,961 Reply by OverFlow

(5 replies, posted in Installation Platforms)

Awesome to see you Siginet!... have a great day!

Go to forum: Installation Platforms

3,962 Reply by OverFlow

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

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.

Go to forum: Feedback and Support - DriverPacks Base

3,963 Reply by OverFlow

(6 replies, posted in Other)

the drivers are only around 100 meg and they are all certified drivers for very popular hardware.
We depend on them being there... as these drivers are not in the packs and they never will be.

I see no benefit to this exercise the one hundred meg would just end up in a pack that needs downloading which is slly since they are included in windows. the time required to search them is seconds. so this will not save time or space and it will take many lhours of your time to accomplish.

so to review... huge time to implement and no benefits...
our goal is to support all hardware so removal of drivers is not the direction we are going.

Go to forum: Other

3,964 Reply by OverFlow

(9 replies, posted in DriverPack Graphics)

Glad your here... again!

Go to forum: DriverPack Graphics

3,965 Reply by OverFlow

(17 replies, posted in Software)

The short answer is no this is not possable.

Details...
well those cards were popular - 13 years ago when they were released in 1995...

they should be supported natively by windows 95 / 98.

from the S3 support page...

ViRGE (325) Drivers
ViRGE Graphics Drivers (DeviceID 5631)
Part Numbers
86C325 ViRGE (5631)

END OF SUPPORT ANNOUNCEMENT
S3 Graphics will no longer provide drivers for new operating systems or any other support for these devices.
The drivers provided below are the latest versions and will not be updated. 
http://www.s3graphics.com/en/resources/ … rchive.jsp

windows ME and NT4 were the last OS supported by the manufaturer,
thier most recent driver is dated may of 1999...

It is now ten years past the time for you to get a new video card wink

Since drivers are not available from an OEM source it is unlikely they will ever be included.
They have a very limited amount of ram, and The ViRGE was also unpopular for its lack of OpenGL support,
they really are not any good for use with modern NT OS's

so not possable and not desirable either.

Go to forum: Software

3,966 Reply by OverFlow

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

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.

Go to forum: Feedback and Support - DriverPacks Base

3,967 Reply by OverFlow

(40 replies, posted in DriverPack Mass Storage)

If it does not work the way i think it should i will make the required changes so it does.
(and it will like it!) wink

I am 90% sure it will work the way i outlined it above right out of the box...
I dont think this has ever been tried?...
IDK if this function was ever needed before now either?

i wonder if all caps translates differently??? tee hee

Go to forum: DriverPack Mass Storage

3,968 Reply by OverFlow

(6 replies, posted in Feature Requests)

Too funny wink tongue !

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... wink
I will credit both of you - excellent feedback on both the idea and suggestion.

Go to forum: Feature Requests

3,969 Reply by OverFlow

(40 replies, posted in DriverPack Mass Storage)

LOL

Go to forum: DriverPack Mass Storage

3,970 Reply by OverFlow

(40 replies, posted in DriverPack Mass Storage)

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 wink

jeff

Go to forum: DriverPack Mass Storage

3,971 Reply by OverFlow

(40 replies, posted in DriverPack Mass Storage)

in simple terms the first example will work most of the time

[V3]
ms_count=1
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

if needed this alternate version may work if the first one does not.

[V3]
ms_count=1
ms_1_deviceName="VIA SATA/PATA IDE"
ms_1_tag="VIDEX32"
ms_1_sysFile="VIDEX32.sys"
ms_1_hwids="PCI\VEN_1106&DEV_0571&CC_0101,PCI\VEN_1106&DEV_3149&CC_0101"
ms_1_isBusExtender=false

the second example has one additional HWID the first one does not.

Go to forum: DriverPack Mass Storage

3,972 Reply by OverFlow

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

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

Go to forum: Feedback and Support - DriverPacks Base

3,973 Reply by OverFlow

(14 replies, posted in Universal Imaging)

I belive that sp3 now allows an install without a PID...

however you will be prompted for your PID by genuine advantage and windows activation.
(when you visit Microsoft Updates for example)
so you should be able to input your clients PID after the install and have no licence issues.
this is intended by MS to eliminate the issue of the install CDs haveing different PID algorithims.

Go to forum: Universal Imaging

3,974 Reply by OverFlow

(13 replies, posted in Feature Requests)

I just noticed something else that made no sense to me....

%SystemDrive%\DPINST.exe /c /s > nul

/c means please log to console and would then seem to be in direct conflict with > null

so you should have written

%SystemDrive%\DPINST.exe /s > nul
or simply
%SystemDrive%\DPINST.exe /s

Go to forum: Feature Requests

3,975 Reply by OverFlow

(14 replies, posted in Universal Imaging)

um i wrote the DP_Install_Tool.cmd that gets copied to your OEM folder to search all available drive letters for your \OEM folder (the root folder of each drive letter only) {it also searches for the M1 folder $OEM$\$1\D\}

so you could call DP_Install_Tool.cmd after you are connected to the network drive.

PS see this thread here http://forum.driverpacks.net/viewtopic.php?id=2751


if you are a more hands on type see this...
http://forum.driverpacks.net/viewtopic.php?id=2264
I have copied the relevant info of the first post below.
(please note this post is in the FAQ section and it is stickied wink )

the first half of the post desribes how to extract or cab the drivers for use in the instructions below.
---------

OR for one click updateing...

If you do not wish to manually install the drivers you may, if you wish, use the following method
This is based on info from one of our members - Warm Snow (WsnoW)

Download http://3rdpartydriverpacks.thesneaky.co … /DPInst.7z

Extract DPINST.exe and DPInst.xml to the same folder as \D

--- both methods assume that D\ is a subfolder of the folder that contains the DPInst.* files ---

To use it simply double click on the DPInst.exe file and click the next button!

optional:
create a .CMD file with the following line --->  DPInst.exe /c /s
/c enables logging to the command window
/s enables silent mode (no GUI) 

For a "drivers only disk" simply copy to a CD, DVD, Thumbdrive or any removable media.
IE  Burn DPINST.exe and DPInst.xml and the D\ subfolder to disk

(if you wish to rename the D\ folder you will have to edit the XML file)
-------------

more...

--- advanced users only----
add
DPInst.exe /c /s
to your autorun.inf file wink the 'no click' updateing option - and only brought to you by Jeff  wink

please note;  wrote this tutorial before dpinst was included in base so the dwnload is not required if you have base version 8.x (or newer lol)

Go to forum: Universal Imaging