You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
editing the inf will break signing. We try not to do that because signing is our freind.
put another way you cant update an included windows driver (automaticaly) unless the upgraded driver is signed.
that is a very old card - does the new driver make it any faster 
the latest volley of drivers from intel nvidia and ati was just awful... by far the worst we have ever seen...
Mr_smartepants busted his tail to get the graphics packs out and we are feverisshly working on mass... i assume chipset and sound will follow. again the boys have just done their worst this time around and we get left with junk to try and make work...
We only have a handful of guys to sort through the hundreds of new releases and try to add them.
So it takes time and patience and motivation. thanks for helping with the motivation part!
jeff
if you really wish for a silent install you must also set the GUI= line to NO in the ini
PS don't use the default INI name
RUN AS could be used too
How can M2 setup.ex_ exist in your source if you have not run base on it previously?
some of the drivers we are discovering do not support legacy mode...
these drivers will need PnP entries seeded into in the Hive files.
this has been noted by cdob and little bugger and verified by some others.
so far only only Nvidia and Jmicro have been positively identified as failing if this is not done...
It may be that SAS and other Server drivers also need this to be addressed and could be why we were stumped.
- how can a registry entry be required at textmode... HUH? apparently a hive entry will acomplish this.
many txtsetup.oem files contain registry info but only the few drivers that have discontinued (or never had) support for legacy mode will fail.
Yes there are bound to be a few bugs...
most of the packs are not yet ready for PE...
I opened the selection of the other packs in this RC series to see if it would even work at all
And is why there was no anouncement about it I just kinda snuck it out there for those of you who pay attention
if you can post your HWIDs that may yeild a few clues... thanks for checking in. we will see what we can do
have a great day
yup... and should lead us to a driver
well your mac outputs them in hex...
Vendor ID: 0x106b
Device ID: 0x008a
Subsystem Vendor ID: 0x0004
Subsystem ID: 0x0000
Revision ID: 0x0064
but i could not find any info useing those or their decimal equivilents...
my controler for example outputs
PCI\VEN_1095&DEV_3112&SUBSYS_61121095&REV_02\4&1F7DBC9F&0&58F0: Silicon Image SiI 3112 SATARaid Controller
Newsposter is correct pirates get to 'walk the plank' here.
you should start with a clean OEM/Retail copy and do your own work...
that way you know what you have. We don't recomend you trust warez, at all...
haveing made that clear... we will help you create your own UXP
you only need three simple tools RVM Integrator, nLite, DriverPacks. in that order.
your first time may take you a couple hours but most of us can do it in about twenty minutes after you get the hang of it.
the only way we can tell if your hardware is supported would be if you can you post your hwids? (tool in my signature)
Say no to warez... go legit or walk the plank
yes and those files should be found when base is rerun on that same source but your log indicates that they are missing... are you deleting them? is your source disk an OEM or retail. are you useing a source that was modified already?
set autologon in the registry
set the logon count to 1
use an account specifically permissioned to install in your environment. (custom account)
call the DriverPacks Finisher
remove / overwrite the registry entries (for security)
call shutdown -r -t 30
i could think of more but that is simple and effective
I am glad it worked for you! it is always nice to hear that. 
Welcome to DriverPacks and have a great day
you are running base version 8.05 you will need the newer version here... (release candidate)
http://forum.driverpacks.net/viewtopic.php?id=3092
see if that helps...
link to tutorials are in my signature... but a tutorial for SAD (to be renamed SoFI, Software First Installer) is not yet written.
the post you referenced is leading up to a tutorial...
Yeah... It's a Great question. One I am sure many people are asking themselfs.
I think once the new mass pack hits the streets then sound will be next...
Thanks for posting it's good to keep the lurkers in the loop too
added to your title - and stickied this for now
Sure... that is good too
we need to find the conflict...
any process of elimination gets us closer to the cause and ultimately the fix.
I must point out again that your source is corrupted...
If 'Method 2' setup is found then txtsetup.org and dosnet.org MUST exist.
(since they are backed up when 'Method 2' is installed and you log indicates M2 was installed)
What are you doing to your source? If m2 is installed then txtsetup.org and dosnet.org MUST exist!
( I will have to assume the following since i still don't know what you did - you could tell us... that might be nice )
If they don't then you have DESTROYED your source and must start over... (didn't i say this already in an earlier post)
your freeze at t-34 is then assumed to be because your source is corrupted.
Can you please tell us how you are manageing to delete the backup files every time?
this may be the key to why you are not successful...
Note to self- next version; create critical error if backups are not found and m2 setup is... kidding
Sure this is the perfect place to mention it.
We are working the mass storage pack every day trying to get an update out.
we are currently working on test revision 12 (i think) of the mass storage pack...
JakeLD indicates that our three current VIA drivers have been updated to a single driver in the latest test pack...
'[V1],[V2] and [V3] updated to Hyperion 5.21a'
Looks like we are already on it
Welcome to DriverPacks
Stay tuned and thanks for stopping by.
That makes sense... stay tuned for our next packs... we will have this resolved soon
Thanks for getting back to us
We are always looking for a few enthusiastic people for the testing team.
Welcome and thanks for your interest in helping us out.
the guys have been beating thier brains out on graphics and mass... 
you have access to the testing forum... everything is posted there that is in process...
DPs_BASE.log (since you did not provide versions)
the answer is pack extraction takes three minutes and since we target UNATTENDED installs we don't care
(we arn't watching, (that would be an attended install))
It is possable it just is not neccessary... if all the drivers get extracted then we won't miss any
It is also possable that determining which drivers we need and only extracting those might take longer.
PS Windows does not always pick the driver we think it will
which newest base... official, alpha, beta, RC, Head...
the newest mass storage is DP_MassStorage_wnt5_x86-32_811B2 (not 805 - that is 6 months old)
there have been many mass packs since 805 (none that were stable enough for official release)
post your log since you can't understand my simple request above...
you only provided one of the three things i specificaly asked for.
Please see the "Read BEFORE you post" link in my signature to help you provide 'useful' info.
base and mass storage versions you are useing and on what OS...
the versions in those folders are the versions that are included with those drivers...
We don't modify them... if they are not correct report it to the OEM provider. When they update thier drivers ro the current verson of GDIplus then we will include thier newer drivers in the packs.
Again, we don't mod drivers... you get what we get from them... if it is wrong tell them...
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.116 seconds, 5 queries executed ]