Search options (Page 42 of 213)

Um they have environment variables just for that reason... bonehead...

Stickied...

I trust SamLab... But I am not OK with a third party driver

I would love to be able to answer that...

We are always working on the DriverPacks 24-7...

but the truth is your guess is as good as ours.

It is not a simple thing... IE You can't just drop a driver into the packs and have it work (I wish).

We have to add it test it FAIL, start over... FAIL, add a different version, test, FAIL start over... Until eventually we find a method / Driver combination that works most of teh time. then we have to find a combination that works all the time... It's a HUGE amount of work, although it does / would not seem like it to the casual observer.

Stay susbscribed to this topic and well ask you to test a nightly pack after we have some good reports from the testing team.

AGAIN... posting your HWIDs will help solve the issue *(HWID tool in my signature)

looks like we are all in agreement...

I will re offer MDT - it makes 7lite unneccessary

tutorial linked in my signature

There are no stupid questions. the only stupid question is the one that is never asked.

the windows seven packs are not designed for any specific tool...

they are perfect for DISM. They can be used with SAD but you will have to create a SAD folder and then add them manually (IE use the CPU Pack with M1 to create the folders and file structure then extract the Win7 packs where the CPU pack was extracted ).

I would get the DMT (Deployment Management Tool) from MS and install the WAIK (which includes DISM) from the DMT.

Have a great day.

Jeff

So... following along. There would be no reason or need to use a ram disc? (except if we could, man it would be soooo fast!)

One could simply use \\?\%SystemDrive%\D\...

I don't think we can reliably create a 3GB ram disc that would be required to hold the full set of DriverPacks. Not all machines would have a sufficient amount of ram. It is even more likely that having enough ram would be an issue with a Win 2K machine, which would need it the most.

This does not help, and is in fact a hinderence, with the max size of a registry entry. (DevicePath)
I wish i could find the documentation on how to use a file to store a registry entry. (A Hive file)

\\?\%SystemDrive%\D\ Has merit as a solution. But we would need to use an environment variable to keep the path short enough to store in the registry. IE

Setx P =  \\?\%SystemDrive%\D\

then store paths in devpath registry entry as %P%G\... and %P%CPU\... and so on.

you can't reuse the same source when you integrate 901... Start with a fresh source.

It would be VERY easy to include .din files as part of the plugins... I would like to not include exe files. (or any other files that are not needed)

hmmm... It's not really a "bug".  It is an exception...

All other drivers work just fine without their supporting files in BartPE. In most all cases (99%) only the .INF and the .SYS file are required for BartPE.  I don't see any reason to bloat the PE footprint past the 700k CD limit without a valid reason. I am absolutely not going to globaly include all files for all drivers, that would make the final BartPE disc well over 3 gig.

If certain drivers need support files included then we need to simply/only include those specific files for those specific drivers... So far we are only talking about certain Intel LAN drivers. I am also not convinced at this time that the EXE file is required. It is likely that the .DIN files alone are the issue. Anyone care to test that theory?

mr_s - I think all files are excluded except INF, DLL and SYS