101

(4 replies, posted in Windows 7 Discussion)

http://forum.driverpacks.net/viewtopic.php?id=4422

check the drivers .INF file. The version, author, date, and intended platform(s) will be listed.

Just before first login network function should be available,
you need to have network card drivers installed of course,
(you cant network if your card isn't installed wink)
and the NIC settings appropriate for your environment are set.

- VM ware uses generic / native drivers and none need to be added... So it works

Most of the time live metal will need the network card drivers installed BEFORE you can get to the network... So it fails

You need drivers, to get to your drivers, as silly as that sounds.

Me too...

you know it's in there when your driver is installed big_smile. Odds are it is in there.

if it is not you add it, even better you report a missing driver and it gets added to the next release.

all of this is in the FAQ section of our site.

Welcome to DriverPacks.net

he lives!!!

We find it easier for everyone when you help us to help you.

Read BEFORE you post. as the name implies is to ensure you understand what that means.

In this case:
the HWIDs of the item(s) we are discussing.
the versions of the drivers we are discussing.
your install process.
is this win7 home, pro, ultimate, enterprise?


based on what content is there it sounds like you would like to force install a driver for a different device. That does not usually work out well. Add some meat (omitted details) to your query

108

(50 replies, posted in Software)

answer to second question.

DriverPacks are solid archives. Meaning that the entire stream must be extracted from start to finish. However if you are only extracting part of the archive (Let's say one driver) there is a huge pick up in not copying the unneeded files, they are "skipped". So even though the entire pack is processed only specified files are written / output during the process. Skipping is quicker than copying, go figure. big_smile

rename the file... test... report. big_smile

your guess is correct XP only supports drives up to 2TB. Since UBCD4Win is XP based it will not see a drive (partition) larger than 2TB

yup drivers only in the pack please

no these drivers have already been moved from the main packs to 3rd party DriverPack.

they are already removed... (don't use the 3rd party DriverPack, or only use it)

you are welcome to customize them to your tastes but the work has already been done.

Yes you can remove or disable them. Why do you want this?

You can disable them by editing the DriverPacks ini file for the corresponding folder
obviously from DriverPacks BASE this is an option.
this is also a finisher option.

Removing them... well sure you can, your results are not guaranteed to be stable. If you do remove them please also disable/remove them in the pack's ini file. HOW TO edit packs is discussed at length in the FAQ section of the forum. full detail is exposed in the mass storage section; which is, by far, the most difficult to understand and manipulate. All of the packs follow the same conventions but mass storage uses all of the options, some packs use none, graphics is the second hardest.

Techdud, since he is a clever guy, figured out how to move control panel items to 3rd party DriverPack - Impressive big_smile.

http://forum.driverpacks.net/viewtopic. … 538#p57538

yes last one...

With the NT6 DriverPacks it's really easy. It does not have conflict issues like NT5 did.

You could just keep adding drivers... But i don't think that is the best plan big_smile.

Simply replace old units with newer and add missing ones...

There is a special command line to compress files for release, requested by BadPointer.
(it puts the INF files separate for easy extraction.)

Simply 7zipping works fine for normal use.

There are instructions in the FAQ section, and questions are always welcome. big_smile

116

(24 replies, posted in BartPE - UBCD4Win - WinPE)

so you added it the "old way", i don't recommend that you add the DriverPack MassStorage BartPE plugin and the old way at the same time. One or the other is safer unless you know for a fact your HWID is not duplicated.

I was forced to move on with newer versions of PE because of UEFI bios but a good UBCD4Win ISO is still worth it's weight in gold.

117

(24 replies, posted in BartPE - UBCD4Win - WinPE)

Welcome to DriverPacks jmeile,

It's awesome that this fixed your issue and is why we don't close old topics.

I am duly impressed that you used search big_smile!

I am further impressed by the detailing of what worked for you. Your experience may help others.

did you use this driver for windows install or for BartPE Plugin?


Thanks for helping us to help you

118

(50 replies, posted in Software)

Welcome to DriverPacks hardware_failure,
So... was that a vote for, or against SDI? ... LOL

Thanks for taking the time to stop by, we do value the feedback.

Have you personally tested all of the features you listed above? That is not made clear except on installs which you admit is not yet tested.

It is more helpful to everyone if you can report on what you tested personally. Including an outline report of how you achieved success would definitely benefit others.

BP has been around a long time and I am cautiously optomistic about SDI.


Keep the feedback flowing people!

That is how I do it... I mount a known good ISO image... That i ahve slipstreamed with DriverPacks BASE.

then you don't need the E2B dpms routine, you are using the original DriverPacks BASE DriverPack MassStorage method that we know is rock solid.

Using a modified ntdetect file will give the advantage of loading more drivers. It's not really a modified file it's actually the one from 2k3 server. this normally is useful when doing sysprep because in that mode the amount of ram available is exactly half the normal amount. We have not had any issues during installation with memory limits, when using DriverPacks BASE to add drivers to source. Same goes for DriverPacks BASE BartPE plugins. There are times this is useful... I don't think you have found one of them big_smile.

Note to self, follow your gut not what someone else says.

Yes... Listen closely, consider carefully, maybe even test the waters, but always make your own decision.

Those are standard Intel HWIDs, I didn't look but I am sure they are already included.

You are likely correct that since E2B log does not show the HWIDs it would not be able to match the proper driver.

you could try a different version of dpms but i don't think that will fix your issue.

You must figure out why HWID detection fails in order for you to succeed.
I install XP from E2B on USB so I know it works big_smile.

yes it does work with our DriverPacks...
In fact we even changed our method of archiving the packs to help his program run faster big_smile.

122

(50 replies, posted in Software)

Always nice to see one of our veterans give a big thumbs up.

an excellent suggestion, from the author no less. Please try that too and report your experience, good or bad, in that thread. We need some feedback there big_smile.

JoDP wrote:

Hello  all,

new here - and don't know where and for what exactly to ask ;-)
It's OK, if you move this posting to the correct forum or if you tell me for which topic to search

I have an ASUS EeeBox B202.
With the current Easy&Boot and the newest DriverPacks I installed WinXP_SP2 flawless in IDE mode. But I want SATA.
Should not be a problem:
PCI IDs  ICH7M-Family
27c3     82801GR/GDH (ICH7R/ICH7DH) SATA Controller [RAID mode]   

27c4     82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode]   
27c5     82801GBM/GHM (ICH7-M Family) SATA Controller [AHCI mode]
   
27c6     82801GHM (ICH7-M DH) SATA Controller [RAID mode]

But this Board has no BIOS switch for IDE / SATA mode. On istallation the reported PCI ID 8086:27C4 leads allways to the installation of IDE drivers for the SATA Controller. Windows works, but I need SATA AHCI.

With many changes in Drivepack.ini I tried to replace / override the reported PCI ID 8086:27C4 with 8086:27C5, but no luck. I guess I understand to little of the PDMS system

You can't cheat by substituting HWIDs. The driver only works for the mode the controller is in. When the controller is in SATA mode it reports a different HWID than the one it reports in IDE mode and the matching driver (SATA or IDE) installs and works. Installing a SATA driver if the device is in IDE mode WILL fail. YOU MUST change the mode of the controller at the hardware level, In BIOS for example.  What you are doing is analogous to painting the outside of your car because you don't like the color of the interior.

JoDP wrote:

I understand: On boards with fixed SATA mode or after switching to SATA mode would DPMS add the needed F6 drivers for the WinXP installation.

If the driver is included in the driverpack then yes

JoDP wrote:

As a quick solution for me, I would like to modify dpms2.g4b somehow like
... if the now received/processed PCI ID is "8086:27C4" ( IDE-mode ) then replace it / process it as "8086:27C5" ( SATA mode ) ...

Has someone this code-snippet for me and can tell me where to place it in dpms2.g4b?

As I stated this is not possable. YOU MUST at a hardware level put the controller in SATA mode FIRST.
IDK how to set this on your hardware. sorry.
When your device reports the SATA HWID then the SATA driver will install automagically
Further i would like to point out that any speed benefits will be lame, We are in PE mode... not in windows. PE mode, think DOS. no high level functions are available with DOS drivers (the F6 drivers). They are for reasons of explanation like 16 bit versions of the 32 and 64 bit versions. Limp in mode. PE or Preinstallation Environment is a simple install tool, not a replacement for windows. Even if you figure this out there may be very little, or none, performance improvement in PE...

The answer is the same for XP_SP2 (why don't you have SP3 or SP4?) when the device reports its SATA HWID then you will get SATA drivers. Simply changing the driver will not switch the hardware to a different mode. that is a function of the hardware, it's a firmware / BIOS setting.

I have tried BOTH of my keys and the battery is still dead... i don't understand???

No we will not release code that alters bios or firmware ... that would be too dangerous for our tastes.

Cuttlas wrote:

Another question, Can I delete All Setup files (Exe files) from Drivers' Folders?
I think they will install by .inf file so there is no need for setup exe files. Am I right?

If that would work we would have deleted them ourselves tongue

- - - - - - - - -
Sure it's only ONE step, how could that get messed up, LOL.

Agreed that there are not very many steps... Totally true. 
But there are a thousand ways to fail to complete them, shall I list them?
The devil is in the details, i dotting and t crossing is critical.