No problem.

OverFlow wrote:

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.

JakeLD wrote:

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 took about a day's time to get everything renamed and all the references in the INFs updated.  I'll tell you one thing, though,..."Replace All" in Notepad saved me a lot of time when updating the references in the INFs. 

Note:  The names of the files are longer since I added on to the end of the name to give each file a unique name.

Additional Note:  I also got the LAN DriverPack, I posted a link to, working on the XP SP2 version of WinPE as well as got the MassStorage DriverPack working on that version of WinPE.  If you want me to post how I did that, please let me know and I will post my steps.

I have something even better for BartPE.  I went through the latest LAN DriverPack.  I changed filenames of all files so that no two files have the same exact name.  Also, I edited the INFs to reflect these changes.  I have tested my changes by using pebuilder and I had no errors.  I also edited "DriverPack_LAN_wnt5_x86-32.ini" to reflect the filename changes.  I put everything back into a .7z file and uploaded it to my Rapidshare account.

Here is the LAN DriverPack that I edited:

http://rapidshare.com/files/80202113/DP_LAN_wnt5_x86-32_7121.7z

I hope this helps with creating the BartPE version of the LAN DriverPack.

106

(26 replies, posted in DriverPack Mass Storage)

G1 servers aren't supported by HP anymore.  I know this from my job last year working on servers.

The DLLs that have "ins" in the names are referenced in the INF files as a co DLL file.  I didn't get a chance to look in the INF for the SYS files, though.

I got message back from the user and he said that he is all set now.  Thanks for the help everyone.

@dolivas:  I would not be able to post any of that.  I was helping out a remote user with this issue.  I am having him try the new drivers in general to make sure they work for him.  I'm waiting to hear back from him.  I think he may have done something wrong somewhere if the very last part of the HWID shouldn't make a difference.  I'll let him know that the drivers should have worked for him.

I also did not see anything in the new INF that would make a difference.

Here is the newest driver from VIA Arena for VIA Rhine II.  It is version 6.0 and dated 14 November 2007.

http://www.viaarena.com/default.aspx?Pa … bCatID=147

@JakeLD:  I'm helping out someone who said the current driver in the LAN DriverPack doesn't install for his VIA Rhine II.  I was able to have him get                   HWID for me so I could post it on here to help resolve the issue quicker.

PCI\VEN_1106&DEV_3065&SUBSYS_80ED1043&REV_78\3&267A616A&0&90: VIA Rhine II Fast Ethernet Adapter

I checked the current driver in the LAN DriverPack and the new driver I posted the link to and both have the HWID of PCI\VEN_1106&DEV_3065&SUBSYS_80ED1043.  Does the "&REV_78" part matter for HWIDs?

111

(3 replies, posted in Other)

OverFlow wrote:

OEMSETUP= yes in winntsif is mutually exclusive to hit f6 if the machine has a floopy you could put a floppy in with a winnt.sif file on it that file on the floppy superceeds the one in the i386 folder on the cd

Thanks for the help, Overflow.  I let the guy in my other forum know about this already.

112

(3 replies, posted in Other)

I know that pressing F6 to install additional drivers is disabled when integrating the DriverPacks.  A guy in another forum that I'm part of was asking me if there is a way to enable the pressing of F6 to install additional drivers.  Is there a way to do this so I could let the guy in the other forum know?  Thanks in advance.

Echo_Platoon if you just select the file and press CTRL C (copy) and then CTRL V (paste) this will create a copy in the same folder prefixed with Copy of <filename>.  Then all you need to do is rename the copy to what you want.

Oh, yeah.  I forgot about that.  Thanks for reminding me.  Man, I need to start playing around with the little stuff in Window XP, again.  LOL

Jaak wrote:

Hi
I can do this for a future LAN DP.
I actually did this for a testpack which is not in testing yet.
I did not drag/drop, tho. I select file, copy in same folder, rename the copy.

You can do that as well.  It would be quicker.  I don't have that option when I click on File after selecting a file.

I'm glad I could help.  Is this a good way to come back from my long absence?  LOL

Jaak,

I will e-mail you everything I did for this to get it working.

--Echo_Platoon

117

(26 replies, posted in DriverPack Mass Storage)

Jaak,

Sorry about my absence.  I have been VERY busy between work and family stuff.  I'm going to try to be around more often on here.  So, if you need help with anything with the DriverPacks, just let me know.

--Echo_Platoon

At my work, my brother-in-law was building a BartPE disc and I suggested to him to use the DriverPacks.  MassStorage was easy to put in due to the BASE slipstream method.  I, then, went to work on getting the LAN DriverPack working.  I extracted the LAN DriverPack and put the folder in the LAN drivers folder for BartPE.  Then, I had pebuilder build the disc but I came across some errors during the build process.  All of the errors during the build process were with the nVidia LAN drivers.  The errors were about missing files, such as DLLs that the INF file has listed as a co-DLL-file that is needed.  I was able to do a workaround for this.  I got it to have no errors in the build process.  I also helped test the BartPE on several different types of machines.  My tests were successful.  If you want to know how I got everything to work, just let me know and I'll explain in further detail

--Echo_Platoon

Jaak,

If you want, I will take a look at this tonight.

Jaak,

I'm currently working on this one.  I'll e-mail you my results.

I'm getting a 404 Not Found when trying to download the Monitor, Misc, and TV DriverPacks.

If the topics for the Monitor and Misc DriverPacks from the links JakeLD are up-to-date, the download links for each should be:

Monitor:  http://3rdpartydriverpacks.thesneaky.co … _070827.7z

Misc:  http://3rdpartydriverpacks.thesneaky.co … -32_708.7z

I was able to download from those links.  I don't know where the DriverPack TV topic is located.

tenchi103 wrote:

Just a heads up if interested:
The drivers for the IT8211F, IT8211AF, and IT8212F Raid controller are all found here on ITE's website: http://www.ite.com.tw/software_download … nload2.asp

Thanks, tenchi103.  I already downloaded the drivers from the first link in this topic, made everything to go for the DriversPack, and sent everything to Jaak.  Are the drivers in the link you posted newer than the drivers found in the first link posted in this topic?

Jaak,

I'm currently working on this.  I will e-mail you when I'm done.

Jaak,

I did everything for this already and e-mailed the finished product to you.

Jaak wrote:

Okay,
FAIK, it is an update.

I figured that.  I will compare the HWIDs of the current driver in the DriverPack to HWIDs of this updated driver.  I will let you know my results.