we may have to wait for MS to improve DPInst.exe for that to happen
it may be neccessary to run it twice with a reboot inbetween...
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
we may have to wait for MS to improve DPInst.exe for that to happen
it may be neccessary to run it twice with a reboot inbetween...
the normal M2 method is the best...
the t-39 method is flawed
- detached program runs parallel to setup.exe
not detached program first then setup afterwards they both run at the same time ![]()
that is why we use presetup
- it prevents setup from running until were ready
IE if setup runs before we are done extracting all the drivers it can't search all of them???
i still like the idea of useing wpi to update an existing system.
jsut not for UWXP
All good points ...
it still beats starting from zero.
a few edits is beter than manually createing hundreds of entrys ![]()
he is obviously not useing DriverPacks and he has given 0 info in four posts
(i deleted the other three identical cross posts)
he is about to run out of luck ![]()
@Galapo
There is not much i have to offer in the way of rewards...
but as a small token of my appreciation
Welcome to the DriverPacks Testing Team ! ![]()
you will find a previously hidden forum is now available to you.
never minds.
Re: Guess it is a good idea
I stickied it !
Welcome to DriverPacks,
Thank You for your fine contributions to the community.
What a great idea! adding drivers to a running copy of PE...
Not haveing to rebuild with pebuilder to support new hardware...
and useing DriverPacks as a source...
now that is a Great Combo~!
jeff
HWID's?
excellent... i will enable the option to select CP's if any DriverPacks graphics pack is selected
obviously it will only work if a CP is available in the pack that is used.
that is normal for the moment...
the control panel software selection in the GUI is dependent on the DriverPack Graphics A pack...
as a workaround for now we can create our image with DriverPack Graphics A selected
Then just delete the DriverPack Graphics A pack from the OEM folder after slipstreaming
IDK if mr_smartepants has the control panel in the graphics c pack ?
Note: I need to code...
DriverPacks BASE to check for control panels in DriverPack Graphics B and C
@mr_s This will likely require a new tag for the [DriverPacks] section of the graphics packs INI's
IE
[DriverPack]
platform = "wnt5_x86-32"
name = "Graphics A"
ControlPanel = "ATI,Nvidia"
perhaps not, i could just enable them if any graphics pack is selected... {shrugs}
teh second one is obviously easier and wont require extracting the inf from the pack during slipstreaming.
I am going to call that a [bug] if someone wants to report it over at the bugtracker ![]()
What are you talking about?
"Read Before You post"
link in my signature - please read it
then actually explain yourself
and check each item off the list in Read BEFORE you post.
We can't help if you don't make any sense...
having your app check for and remove that line when discovered is certainly the best option.
we will remove the ones that do not belong (like this jmicron) from the packs...
re: Special thanks to galapo, as usual
Yes... as ususal
Have a great day
and please accept our warm welcome, to both you and Kare
PS i am now following you that hostospe
can be read as "the currently booted Bartpe OS"
That is excellent to know and explains why my bartpe plugin works ![]()
(it is obvious registry entrys are not required for mass storage
the text mode drivers are used for PE and those do not require registry entries
[there is not even a registry available yet @ text mode
] )
this is intentional because loading the PnP driver resets the bus and most likely will BSOD ![]()
there are of course exceptions... ![]()
We still need to get this fixed ![]()
I belive the INF's should be as provided by the OEM...
If they have been changed then we need to change them back...
if that is the way they were provided then that is the way they should be...
there are cases where this is not possable... we can deal with that when we get there ![]()
Please let us know if any other strange problems occur...
We will be glad to either fix them, or help you to find a workaround.
In this case the issue is a bug in our pack... we will fix it!
if you find more we will fix those too! ![]()
so you guys don't need to do anything (you can tweak your pack for now)
we will include this fix in the next nightly and post here so you can test it ![]()
jeff
I belive there is a solution for this... at least it won't leave a mess... I think...
there is a command line switch for dpinst
/sa
Sets the suppressAddRemovePrograms flag to ON, which configures DPInst to suppress the addition of Add or Remove Programs entries that represent the driver packages and driver package groups that it installs.
it may be a good idea to add this switch if it just makes a mess in add remove programs... ![]()
moved to feature requests
try this instead...
http://driverpacks.sytes.net/driverpack … 1102RC.exe
it should be all fixed and ready for you to use in that RC ![]()
[thinking to self] call DriverPacks install tool from WPI... why didn't i think of that yet... i'm getting old... ![]()
that didn't take long... here you go
try dpinst /c /s /sh /lm /el
currently is dpinst /c /s
in the .cmd file
we have found a handful of bugs with dpinst...
it wont work at the root of a drive and it selectively ignores certain xml file entries
this will be fixed in teh next RC...
the path fix is already in the current RC 8.10.rc3
please report back to confirm or deny this fix... TIA
Welcome to DriverPacks and have a great day
Thank you for being one of the people who always keeps me motivated!
Well i may have figured this out...
It seems that there was a bug in the sortarray function of autoit i was useing for the 809/810 series releases
the Array that gets written to the massstorage.inf was being written raw instead of sorted.
the sort order of the entries is only an issue in certain cases and I belive yours may be one of those cases.
keep your eyes peeled for my next RC.
i had/have a bug in the finisher that needs to be confirmed as fixed first.
I was looking for a topic for your Offline sysprep and i did not see it in universal imageing or in software
Lets get a topic started for this under the software topic - after we get our bug fixed...
this sounds very cool... now that i understand what it is ![]()
I will be glad to assist you if i can
- what a great idea and i think your program will definately compliment DriverPacks
@Galapo, If you would please,
Start such a topic for us in "Software".
You understand better than anyone (who speaks english) what it is. LOL ![]()
I would certainly owe you one
thank you for being here you're "one of the good guys"!
PS Do you have a sticky here i didnt see it just now...
(maybe make that Two posts
)
take a look at this post please
http://forum.driverpacks.net/viewtopic.php?id=3208
Reported already ![]()
But thanks for playing! LOL ![]()
wow gigabyte with intel and a 8600GTS
that is very nice hardware sir...
GigaByte MBs are rock solid and GB is pleasant to deal with if the need arises.
my guess is fake setup may be the cause of this issue.
IDK why it only shows up on your rig though...
have you tried reseting BIOS settings to default (or clear CMOS jumper)
they allow you to tweak almost everything in the bios
some user settings can adversely affect your experience.
some of which you have to hit ctrl f1 to even view...
DriverPacks.net Forum » Posts by OverFlow
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.117 seconds, 5 queries executed ]