You are not logged in. Please login or register.
It was my belief that the DriverPacks mass storage plugin was solid and working.
it theory it would already do everything neccessary to funtion in PE as well.
what are you refering to?
Hi
@ OverFlow and pack developers...
It adds some work, but it can be maintained.
We already look at the HWIDs when we are looking at adding REQuests.
Suppose you have a couple updates and new drivers on your "to be done" folder.
And, you already have the release's HWIDs excell sheet.
Then it is easy to use a copy of spotlight, and drag drop the to be done folder into the tool.
You open the old sheet, and open a new sheet.
You get the CSV in new sheet, and then paste it under old sheet.. viola..
You easily see which folder has the dupe HWIDs, and the driver version, and location... and filename.
Joshua plugin does not work with nForce2 400, it does work on nForce 680i and nForce 4 do.
The nForce drivers in the LAN DriverPack I posted should work in BartPE. I was unable to test this as I don't have a computer with nForce.
It was my belief that the DriverPacks mass storage plugin was solid and working.
it theory it would already do everything neccessary to funtion in PE as well.what are you refering to?
The WinPE version I had was already built (I was given the ISO), but it needed drivers, so I had to integrate them manually. What I had to do for this is the following:
I slipstreamed the MassStorage DriverPack into a BartPE session. I then took all of the SYS files from the plugin and copied them to the "Windows\System32\Drivers" folder on the WinPE ISO. I then went into the "MassStorage.inf" and "MassStorage.sif" and added all of the necessary information into the TXTSETUP.SIF file in the "Windows" folder on the WinPE ISO.
So, the MassStorage plugin is solid and working. It was just that I had an already built WinPE (ISO) that I had to integrate the drivers into.
Last edited by Echo_Platoon (2008-01-01 03:07:34)
good info... thanks for shareing!
No problem.
Congratulations on your promotion Corporal Echo_Platoon
Thanks for the promotion.
I will be uploading EchoPlatoon's LAN to nightly ftp
I mentione arcsas in a post here..
JakeLD told me about it, and later on, Jeff posted what was wrong with arcsas, and I uploaded a quickfix before I left for a new year's eve get-together.
@ echoplatoon, I will compare the changes against the existing nightlies, and can probably easily find out where JakeLD updates and additions fit in.. (if they are not in yet..)
@ JakeLD
today I found back the LAN pack you wanted to finalise.
I apologise for not getting that done, but I had somehow managed to compare the existing release with what I thought you wanted to release, and that was already released.
Sorry.. I wish I had not been that tired.
I bet 17,689 people died of anxiousness over that.
To the berieved, sorry.
%)
@Jaak: How is everything coming along with this?
I think I found an issue with some of the nvidia LAN drivers in BartPE
My brother-in-law was testing out his BartPE on an HP xw9300 workstation to see if the LAN drivers get picked up and the drivers didn't get picked up. I had him going into Windows and run the sav_HWID on the machine so I could search the drivers for the one that had the matching HWID for the LAN. I found the shortened version of the proper HWID (up to DEV_XXXX but containing anything after that such as &SUBSYS). I thought that it should have picked it up, but it didn't. What I did was took the full HWID, which ended with &REV_A3, and added it into the INF files. Then, I had my brother-in-law build BartPE, burn the ISO, and test it. This time it picked up the LAN driver.
Sorry if I don't have the HWID in this. I have it in my work e-mail at the moment and won't access it again until I go in on Monday. I will post the HWID on Monday so I could make my point clearer.
--Echo_Platoon
There is probably a duplicate or a generic HWID that overided the device. Btw, you can use the save_hwids in PE, I have a working plugin if you need one, just email em at jakeld@gmail.com or msn at jakeld_nt@hotmail.com.
Last edited by JakeLD (2008-01-05 14:44:41)
the Joshua plugin for nvidia will probably be teh way to go for nvidia until this is actually coded correctly as a plugin. ( in process atm)
@OverFlow: So, are we going to definitely use the Joshua plug-in for nvidia drivers for BartPE and eliminate the nvidia drivers we have in the LAN DriverPack just for BartPE? I actually had my brother-in-law try Joshua's plug-in and it still didn't work on this machine.
That is an excellent question.
The answer is NO... the Joshua plugin will become obsolete when I release DriverPacks LAN.
Be aware that we have not created a plugin for lan yet.
Copying the packs to the network folder is quite a bit different than createing a plugin.
I don't like to type so i will not elaborate on the many reasons.
Just belive me that the problems you are experiencing will not exist in a true plugin.
I didn't bring this up before because you were having fun with it and i saw no need to be a kill joy,
that and it beats a blank by a large margin.
i am codeing my butt off ATM on base
i have fixed the M1 double \d error
the bug where the $OEM$ folder was crerated when only masss storage was selected
the HJW pack is now recognized
SP3 support (beta is out on that)
the page profiles errors (base gets lost when the back button is pressed in gui mode)
removing hardcoded folders in Chipset. (there is a new approach to chipset.)
BartPE gets; new verify path code, chipset and cpu support will now precede LAN since you guys did this.
I hope to post the alpha on this as soon as today, but i won't put it up till i am happy with it and i am tough on myself.
I keep recomending the joshua plugin for two reasons one it has been out a long time two it is as close as we have to a universal driver
It has been out for some time and is bug free. I hoped that it would make it into the packs and reduce the total number of nvidia drivers. that will make my work easier having at least a known good starting point and i think would benifit the sysprep and disk users of base as a side effect.
I knew it wasn't going to be an official plugin. I don't mind you being a kill joy because I don't like acting all high and mighty.
it is nice work... it it's quick and easy and effective
that makes is a win in my book 
Oh man, I wish you guys would have talked to me a LONG time ago. When I created my first driver pack ( http://ubcd4win.com/forum/index.php?showtopic=1374 ) for the UBCD4Win back in 2005, everything that was stated here about the damn nVidia drivers I always ran into. At first it wasn't too big of a deal to copy and rename the files and such to make things work, but over time as the pack grew, it was a huge pain and it brought up more problems, as what OverFlow and others have already stated. Damn nVidia and all of their different driver versions having same names for files... I constantly ran into that issue and began to hate the nVidia drivers...
1.) Yes, you can copy the files and rename the copied files to get rid of the BartPE missing files errors, but then you have the problem where BartPE only copies the very last file of the same name and thus you'll only get working hardware which is based on that file and not all of them. Thus, this option wont work in the long run.
2.) Yes you can take each driver version, rename all files to something else and make sure inf references match, etc., but then you still have the issue of many duplicates HWIDs. To me, this still isn't the best way to go.
3.) Joshua's plugin/pack, which I think he originally made for the UBCD4Win to address the above two issues, for the most part works pretty well, but there are a few systems that may not work. I know he a ton of time into this but I don't know the specifics of how it all works. For now, this is the best bet for good nVidia driver support.
4.) Obviously, if we can find a way better than the first 3 above, then the new Bâshrat the Sneaky LAN driver pack for the BartPE community is born IMO.
Due to the issues above and the now excellent Bâshrat the Sneaky MassStorage BartPE support, I've only recently released some LAN only driver packs ( http://ubcd4win.com/forum/index.php?showtopic=9314 )where, I believe, I've completely left out the nVidia drivers and just rely on Joshua's plugin/pack instead. Much easier for me, as least until the real Bâshrat the Sneaky LAN BartPE pack becomes available. I've been doing my pack for over 2 years now and will just be so glad and happy once I can just rely on the Bâshrat the Sneaky packs from then on. I know the UBCD4Win and BartPE communities will be eternally grateful as well.
If you need any help with anything, though I'm limited on time, I'll do my best.
Well said...
I have fixed the M1 double \d error
the bug where the $OEM$ folder was created when only masss storage was selected
the HJW pack is now recognized
SP3 support (beta is out on that)
the page profiles errors (base gets lost when the back button is pressed in gui mode)
removing hardcoded folders in Chipset. (there is a new approach to chipset.)
BartPE gets; new verify path code, chipset and cpu support will now precede LAN since you guys did this.I hope to post the alpha on this as soon as today, but I won't put it up till I am happy with it and i am tough on myself.
I can confirm the method 1 D\D issue got eliminated in a IM session "team only" 'interim' test.
SP3 detection works
I hope to run tests on chipset coded folders "interim, team only" soon.
What Jeff did in the last version I recieved in a IM session was a great improvement, and that was a over a week ago. (I was scarce for a while but I had a good many personal excuses.)
What I see right now is that a lot of hard work is done, and nothing gets in the limelight.
Chips? Jeff recieved testfiles so he can test his code and If I know him at all, he will come up with something good for the end user, and will keep the pack developers in mind.
Mass? ditto.
Lan?
The PCI-HWIDS are easy (sorta).. but some of those other lines are mysterious.
What do lines with varying sections of underscores and hyphens do? They fight?
If anyone is interested some .sys files get omitted from the Intel gigbit dir, I\PRO1000 when adding it into Bart, I have just manually added them, (without overeriting e1000325.sys which was allready there but dated 2003) I will post what success this has [doesnt work on Dell 755's as it gets done without these]
Generally Net drivers does work at PE.
Of course there are exeptions. Some Net drivers behave different.
I know so far:
Broadcom NetXtreme II
http://www.broadcom.com/support/etherne … remeii.php
This driver use a Virtual Bus Device architecture.
D\L\B4: There are two inf and sys files for one nic device.
This driver dosn't work at RIS.
Maybe this could work at PE, a special plugin would be required.
Broadcom recommends the RIS driver for a Windows Preinstallation Environment.
There is one inf and sys files for one nic device.
PE community use this RIS driver.
Another major pain is nforce. There are a lot of driver versions.
And there are two inf and sys files for one nic device.
Nvidia dosn't offer RIS drivers to a end customer.
Some OEM offers nforce RIS drivers.
There is a pdf included: Nvidia recommend a RIS Driver for WinPE.
This RIS Driver is NOT recommended for normal windows.
http://support.fujitsu-siemens.com/Down … 5DCE8A753F
nForce Family Network Driver Date: 05.10.2006 Version: 65.3.4 RIS_PE
There are drivers 67.5.3 from 2007:
ftp://ftp.asus.com.tw/pub/ASUS/misc/uti … S_6753.zip
Some other exceptions:
Attensic use a strange subfolder: system32\Attansic\L1\atcInst.dll
http://www.911cd.net/forums//index.php? … p;p=122098
D-Link DGE-530T is similar: system32\wbem\mof\gewmi.mof
http://www.911cd.net/forums//index.php? … mp;p=87509
Unfortunately I don't have acess to above mentioned hardware.
I've to guess from user experiences.
You're right chud, that's why I use a plugin for Intel.
cdob, I will look into the RIS drivers and make sure they get added in the next nightlie. Thanks for the feedback.
Intel plugin:
[Version]
Signature= "$Windows NT$"[PEBuilder]
Name="Driver: Intel NIC 12.3"
;Help="nic_intelpro.htm"
Enable=1[SourceDisksFiles]
;PRO/100 Network Connection
files\PRO100\e100a325.inf=20,,1
files\PRO100\e100b325.inf=20,,1
files\PRO100\e100b325.sys=4,,1
files\PRO100\NicCo.dll=2,,1
files\PRO100\NicInst.dll=2,,1;PRO/1000 Network Connection Driver
files\PRO1000\e1000325.inf=20,,1
files\PRO1000\E1000325.sys=4,,1
files\PRO1000\NicCo.dll=2,,1
files\PRO1000\NicInstG.dll=2,,1;PCI Express Network Connection Driver
files\PRO1000\e1e5132.inf=20,,1
files\PRO1000\e1e5132.sys=4,,1
files\PRO1000\e1q5132.inf=20,,1
files\PRO1000\e1q5132.sys=4,,1
files\PRO1000\NicCo.dll=2,,1
files\PRO1000\NicInstE.dll=2,,1;PRO/10GbE Network Connection Driver
files\PROXGB\ixgb325.inf=20,,1
files\PROXGB\ixgb3251.sys=4,,1
files\PROXGB\NicCo.dll=2,,1
files\PROXGB\NicInst.dll=2,,1
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.022 seconds, 10 queries executed ]
