You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
hmm you may have found a bug in Bâshrat the Sneaky code
they are not mutually exclusive one is for plug and play drivers and one is for text mode (they are complementary)
the winnt.sof is not required for text mode only i am almost certain can you test that and get back to me?
whoa whoa whoa...
now were talkin apples and oranges.
I thought you wanted a "do it all disk" which you could accomplish with a multiboot disk (with multiple configs pointing to a single installation file set). one disk that will install AND repair.
if you just want a disk that doesn't require you to hit f6 and provide a driver. Just only check textmode mass storage and unselect all other packs. (if you simply delete folders you will create problems. We don't add stuff that is not needed 
)
Sorry i was not thorough in my advise.
mass storage text mode drivers are slipstreamed directly to windows installation and will work regardless of any settings in winnt.sif
the difference being text mode drivers vs. PNP drivers all pnp drivers would be unavailable but not the text mode ones
No, this line is not what you think it is
but you are more than welcome to create a third party driverpack - which will acomplish the same thing
It's all good! 
I am sorry if this request is a PITA
Does this issue occour if the DriverPacks are installed normaly from a CD / DVD?
PS you accidentally put this in the wrong forum (since RIS sysprep is not supported - technicaly) software is where most of the ris stuff is and "Other" is the correct place.
try the new 3rd party DriverPack for monitors and see where you land. Since it seems as though the monitor driver is the issue doesn't it?
and it looks like it is trying to use a 7 year old driver on your brand new monitor.
im guessing here but this is a wide screen flat panel and you are attempting to install a standard graphics monitor driver which certainly does not support the correct screen resolutions for a wide screen monitor. can you say boom!
sorry if i guessed wrong but you were vague.
you rock!!!
close topic please!
two things.
First this is not well documented and your being a DriverPacks newbie there is no way you would be expected to know this.
DriverPacks doesn't replace all of the OEM drivers so DON'T DELETE them. You definately still need them.
@Jaak and mr_smartepants lets get this in the tutorial?
Second DriverPacks will not function if OemPreinstall=Yes is not present in winnt.sif. OemPreinstall=Yes specifically excludes the menus you want.
two workarounds
One put in a floppy with a blank winnt.sif - The winnt.sif on the floppy superceeds the one on the CD / DVD.
Two create a multiboot CD /DVD here is a guide from our very best friends over at MSFN Multi Boot Guide
Thanks for helping us to help you
and pointing out some info that is not readily available.
we need you to "keep your wits about you" sir!
Hello basilirwin,
Welcome to Driverpacks.net were glad your here and thanks so much for posting.
Please read the "read before you post" in my signature below. Especially the part about useing the search feature.
this issue has already been posted by someone else ---> http://forum.driverpacks.net/viewtopic.php?id=2180
have a great day and we look forward to seeing you here!
if you look the driver was accepted (its not a signing issue) it was a bad inf or the inf references a bad file
"" NWADIEnum.inf" will be installed (Policy=Ignore). ""
i actually broke out the code last night... i'm started at least
its all good !
i have discovered that you can remove or even add a pack without any ill effect
Provided you are useing the latest base and packs (the ones with the INF's included)
on older versions (below 7.x) of the base and packs this will blow you up. because the inf info for the finisher is in the pack. delete the pack delete the finisher info related to the pack as well. so it works.
with the older base and packs the info was not in the packs and would have DOOMed you (yay!)
thanks for the idea TigerC10
@tiger stop misleading people
the finisher files are extracted at the same time the drivers are unpacked. (during the WinPE segment and before setup.exe is called.) if your drivers get unpacked then your finisher files should be unpacked too. (If not see me! because you have changed something - you are the only one who has this issue) please stop telling people to do things manually. that just make things worse. the problem only exists for you PERIOD. i will be glad to help you figure out how you are breaking the process. but not here start your own thread and i'll help you - gladly. and post your dp DPs_BASE.log and DPs_BASE.ini and PRESETUP.CMD from your i386 folder
@hicountryrider
yes you can assume all the files are there if you follow the tutorial in my sig. it works flawlessly (ignore tiger)
We had updates for Soundpack A and Mass storage in late November
Mass Storage Pack
Debugger had suggested a workaround for issues where a RAID driver got the upperhand when the chip was set for Base-Mode. The Paths in the pack were shortend to help make Method one more viable and some SI drivers were added - Jaak put a lot of work into this.
Sound A Pack
mr_smartepants fixed an issue with the soundblaster driver where the Audigy control panel was installed for the Xfi driver. lucky2007 posted this issue and was a HUGE help in testing and providing the fix and getting it resolved - (it's not just 'lucky' it's hard work) HWID's were trimmed from some of the INF's to address driver conflicts. Jaak continued with my vision of keeping method One alive and shortened the paths in Sound A too. Dolivas, Major, and corytk all helped and deserve a round of applause. Thanks guys, this was a true TEAM effort.
Muiz Released a third party driverpack (3rd party DriverPack) for Monitor that Bons helped with.
Dolivas Updated the 3rd party DriverPack for modem
Overflow finaly wrote the help file for BartPE Tutorial link
We already have updated packs for December - LAN, Graphics A & B, Sound A & B, and WLAN
Folder structures were optimized for Method 1 by Jaak
Driverpacks is opensource and freeware. Our team members donate their personal time to make this project happen.
Members Like Bâshrat the Sneaky, Helmi, Muiz, Jaak, Overflow, JakeLD, debugger, Chud, Twig123, maxximum, RougeSpear, mr_smartepants, fragbert, Ricktendo64, Ruudboek, TigerC10, Lightsout, McStarfighter, Major, Signet, Dolivas and BigBrit.
We always need people with access to a variety hardware for our test packs - If this sounds like you then become a team member and help make DriverPacks all it can be! we need YOU! or as Jaak is fond of saying
"You need us - We need you"
have a great holiday season and thanks to all.
---- Jeff Herre AKA OverFlow
and now there is more to the story - and Jaak accuses me of never sleeping....
Dear Gentlebeings,
Jeff mentioned the folder structures are changing to get Method 1 more viable.
When we compared the old Mass storage driverPack with the new one, we found that we had added 14 drivers, and despite that we have been able to shorten Path length by approximately 200 characters.
The additions were actually older driver versions we needed to be able to support several Silicon Image Mass storage chip BIOS versions.
Today, Sound A, Sound B, and Graphics B have all had their folder structures changed as well.
The new structures will take getting used to, I guess.
It is something we wanted to do long ago, and now we are at it..
Jeff also mentioned that we trimmed HWIDs from several INF files in the Sound DriverPacks.
Approximately 2050 duplicated HWIDs were found in Sound A and B.
The testers were patient, and we added some new people to the team.
They earned their place, let me tell you that.
It would not be possible without you.
Thank you for helping us help you.
---Jaak
for those of you who don't know there is a MS path limit on method one of 4096. The path for method one was 6895 last month. Jaak has trimmed that to 6090. That is a total pickup of 805, and a lot of work. My hat is off to you my friend...
Your Welcome! and thanks for being here.
this info is well documented over at msfn. Keep reading
OEM disk means a XP installation CD not a restore cd
driverpacks will not allow you to continue if it is not a valid source.
driverpacks is always last in your disk preparation
1 you can use rvm to integrate sp2 (look at the file menu)
2 driverpacks is the last step always. then burn.
3 all the files are at the location you selected - in the OEM and $OEM$ folders.
4 an ISO is nice for testing in a virtual machine.
HWID pruning will not work why? since it only has one HWID cant it just be added?
or will driver signing be an issue...
try disableing base / mass storage plugin and adding the driver manually.
It sounds like this is within your ability.
Does it work? if it doesnt work by itself the problem may not be the plugin but a problem with the driver itself.
we will do our best to meet your deadline.
@jaak -he said the new driver didnt work - however we dont know HOW he added it.
what you are trying to do may be percieved as leeching by our servers. Leaching is blocked.
Could it be the help file is in the wrong language??? I don't see others haveing this same issue...
that whid matches with \D\L\AT\2 yes it is in the pack
Is it not installing for you... DPsFnshr.log please
we use referers if you block these with your firewall you will be denied access.
(leech warning)
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.113 seconds, 8 queries executed ]