Search options (Page 204 of 213)

you could run the finisher anytime you like... you dont have to let the base run it. (choose custom)

problem solved

if you want to know what the finisher does all you have to do is look at the respective packs PackName_wnt5_x86-32.ini
if a HWID matches it executes the instructions in the INI
after all the "exceptions" have been found and their actions(from the INI) applied it deletes the source files and creates a registry entry to delete the finisher istelf on the next reboot.

no big deal
and very few drivers even need it

IE if you did not run it your ati video card drivers would get installed but not the control panel which is handled by

DriverPack_Graphics_A_wnt5_x86-32.ini

[DriverPack]
platform	= "wnt5_x86-32"
name		= "Graphics A"
; version 709.2 
rootDir		= "D\G"
; OPTIONAL
classes		= "Display"
driverCount	= 2
decompSize	= 174
compSize	= 66.1


[A-1]
; REQUIRED
exc_count		= 2
; OPTIONAL
exc_1_tagFiles	= 3
exc_1_tagFile1	= "%SystemDrive%\ATICCC.ins"
exc_1_tagFile2	= "%DPSROOT%\D\G\A\1\ATICCC.exe"
exc_1_tagFile3	= "%SystemRoot%\system32\atidemgx.dll"
exc_1_+hwids	= 0
exc_1_-hwids	= 0
exc_1_+infFiles	= 1
exc_1_+infFile1	= "%DPSROOT%\D\G\A\1\*.inf"
exc_1_-infFiles	= 0
exc_1_commands	= 1
exc_1_command1  = "%DPSROOT%\D\G\A\1\ATICCC.exe"

exc_2_tagFiles	= 3
exc_2_tagFile1	= "%SystemDrive%\ATICCP.ins"
exc_2_tagFile2	= "%DPSROOT%\D\G\A\1\ATICCP.exe"
exc_2_tagFile3	= "%SystemRoot%\system32\atidemgx.dll"
exc_2_+hwids	= 0
exc_2_-hwids	= 0
exc_2_+infFiles	= 1
exc_2_+infFile1	= "%DPSROOT%\D\G\A\1\*.inf"
exc_2_-infFiles	= 0
exc_2_commands	= 1
exc_2_command1  = "%DPSROOT%\D\G\A\1\ATICCP.exe"

very nice work guys... i should be into my slow season soon (winter).
this is all very important and well done.

Can you say "BOOM!"

I'm not sure of everything that gets changed - its very complicated - I have only learned the certain aspects of it i needed to code the BartPE stuff.

helmi, Bâshrat the Sneaky, or one of the more veteran members may jump in here with a list and instructions.

I think it is easier to start over and if you are really curious use some software to compare the before and after folders of your driverpacks install all the files that are changed after the slipstream from the original are the ones you need to restore.

the best hint i can give you is i know the original files are backed up by the base. so if you sort the folder by date the most recently changed come to the top. like winnt.sif get renamed to WINNT.ORG
pretty much all the files changed are copied and the originals are renamed to .ORG

Again i really think its easier to start over (maybe if you used RyanVM integrator you would too.

There are several hundred lines (maybe a thousand) to remove from txtsetup.sif too
and other files -  you should be able to find the backed up originals. (sort by date hint hint)

i can fit my xp install with RVM nLite and driver packs on a CD - you should be able to as well.

It's MUCH easier to to start over than to back out all the changes.

(you could just hang a dvd on the system?)

Extra hint i make a new folder at each stage of the process.

i have my clean source folder. (OEM XP)
i have a SP2 Source folder (OEM XP + SP2)
I have a folder for after RVM (XPSP2 + RVM)
This is the main folder i copy to use for a source for nlite and driverpacks (yes i copy the whole thing)
the XPsp2-rvm-nLite folder is now copied to a new folder for the driverpacks slipstream.

This uses quite a bit of disk space but you can see how it would have saved your butt here.

shoot me an email. use my link to the left

well slipstreaming the driverpack into the source OS will not help you.  sorry.

if you wish to use the driverpacks with bartpe then you need to create a plugin and build PE with the plugin enabled.

Sorry there are not directions readily available.

you need to choose BartPE instead of Disk on the platform screen when you run the driverpacks.
then you need to build your bartpe checking in pe builder that the mass storage plugin is there and enabled.
build your bartpe.

test and BAM works like a charm or at least we havent heard of a single glitch in 6 months.

PS there is a thread started for this already.
http://forum.driverpacks.net/viewtopic.php?id=1436

We are all volunteers...

there is never enough time... I think most of us do this instead of sleeping at night.

I spent at least a hundred hours codeing the bartpe plugin this winter.

I am a computer consultant - self employed - and work full time (and definately not rich)
I think we are hard core users who reconize the need to work as a group to make life easier for us all.
commitment if you will.

good thing AAAAA is not an acronym...

Bigger Better Banners Briefly by the Boss!

rocket raid is included in the packs what is your HWID?

ummm SCSI and SAS? tee hee