Question asked "What is a bus extender" from TechDud post 35

Answering this question makes a good point
Damnation mentioned the fact that certain files error when added to mass storage because of entries in SCSI sections.

Simple Answer=
BusDrivers don't get entries in SCSI section... Mark files that error @SCSI entries as bus extenders and test big_smile



I am working on the chipset module as i write this and I am reviewing the related posts.
the more i look at these the more i am starting to belive they actually DO need to be in mass storage.

Long answer regarding BusExtenders:
Q:What does the entry "ms_1_isBusExtender" mean?
A:The "ms_1_isBusExtender" entry specifies wether the driver is a busextender or not.

Q:How can i find out if my driver is a busextender?
A:Open the .inf files which should be included in the driver.

Look for a line similar to the following:
LoadOrderGroup = System Bus Extender

If that line is present, your driver is a busextender.

My best guess is the framework drivers may be or behave similarly to Bus Extenders.
Please test and report using wdfldr.sys and wdf01000.sys or similar files.

Jeff

PS DLL files are not currently supported ... but that could change big_smile
cdob is usually on the money, the dll is probably not required at textmode.

here is the original thread
http://forum.driverpacks.net/viewtopic.php?id=5032

what he posted was a copy of my explanation of certain entries (or lack there of) in the mass storage INI file.

there was a special case where we had one updated driver in the pack that replaced THREE native drivers.

99% of the time an updated driver simply replaces an existing driver...

I had to write special code so that this one driver that actually replaced three native drivers would result in archiving all three of the native drivers. this was accomplished by adding a special entry containing no HWIDs. In this way DriverPacks BASE would archive the files but not replace them with any file. (because they are now covered by a different driver).

Took some creative juice on my part to make it work... and it looks unusual in the INI file.
If you read the INI and did not know what / why it was that way it would not be obvious what was going on.
Some guy was editing the pack and stumbled into it and got confused. That text was cut from the middle of my expanation of the "weird looking" entries.

That post was a copy of what i wrote three years ago...

it was not a question or a statement. that spambot simply stole my words from another post and pasted them here with that spam link wink

Damnation wrote:
OverFlow wrote:

is there any differnce if you don't load the file? Does it load it as a USB2?

If I don't have kmdf in the I386 folder, I get a "File not found!" error on flxhcic.sys

== is this when using a clean XP source?

Damnation wrote:
OverFlow wrote:

What is the speed vs a USB2 port ... Is it the same?

how much time is saved, if any?

for me, it was about 6 minutes more on USB2

==with or without the driver installed?  is it still faster using a clean xp source?

you are correct it is complex, but it is less complex now that it ever has been.

You have already found the sites, like this one, that simplify it as much as is currently possable.

there are no shortcuts in life.

If it were easy everyone would be doing it big_smile.

what you seek is a combination of driverpacks (You are here) and Microsoft SysPrep, plus your imaging software and a deployment method or methods.

your question is too general in nature to give you a specific answer.

Damnation wrote:

Hardware arrived,

It works! detected my usb drive in phase 1,

cdob, you were right txtsetup.sif entries for kmdf sys files need to be added else it BSODs at phase 2.


naturally. big_smile
----------------------------

is there any differnce if you don't load the file? Does it load it as a USB2?

What is the speed vs a USB2 port ... Is it the same?

how much time is saved, if any?

I believe BASE used to have a method to slipstream drivers that were not Mass Storage.
The method was for Chipset and would copy (and cab?) the drivers without the Mass sections being updated.
cdob is correct some entries are required to effect / legitimize the copy. big_smile.

This routine was deemed unneeded and disabled, it has not been missed in years. This routine could be reactivated, it only applies / applied to Chipset. I will only reactivate and debug this routine if it is proven at real hardware that it makes a difference.

much work has been spent on theories in the past that did not work as intended at real live testing. That is to say after all the work there was no benefit in terms of stability, functionality, speed or time.

I'm paying attention to this... Show your work and some actual results.

@cdob... still haven't forgotten about the PnP fix either.

http://forum.driverpacks.net/viewtopic.php?id=6269
We have been discussing that in a couple other forums.

Nothing is out of the question... i have not had time to work on BASE for a while but I could / can if need be big_smile.

anyone else who lands here can pop in over there and see if they have anything more to add

KTD is a legacy function, Basically retired.

It never did what it was intended to do, and we always recommend against its use.
SAD is the replacement for KTD.

In BartPE you need to select the "text mode drivers"

PE is Text mode.

the main mass storage pack is for PnP mode (normal windows)
and does not apply to BartPE or WinPE. Thus it is greyed out.

not automatically

CeEe4 wrote:

Thanks for your fast reply,

Thats great it will work in Windows 8.  So you wont have to change or add any more code for the OS build detection part in the script?

Will it just function as if it was Windows 7, after having a look at Win8 behind the new interface it seems very similar to 7.

Thanks again.


Win8 is NT6 based... Same as Win 7 and Vista (all NT6 kernel)
So for the most part they all use the same drivers

Win 2000, XP and Win 2003 are all NT5 Kernel
and pretty much use the same drivers.

yes you could use extracted drivers on a DVD i am pretty sure they are less than 8 gig.
However ODD like a DVD are very slow, typically extracting a large file is faster than accessing thousands of small ones... you could try it and let us know big_smile.

extracted drivers using SAD2 on a thumb drive would be the way to go..

490

(17 replies, posted in Software)

you guys are giving a rebuttal to a spambot tongue

that is why it looks cut and pasted and why the links are dead. Also why Mr_S removed his signature...

491

(5 replies, posted in Windows 8 Discussion)

Never use version "0" of anything tongue

492

(10 replies, posted in Software)

it does use less disk space on the target because at any one time only a single archive is extracted at a time.
On a system with limited HDD space this may be an advantage. HDDs with less than 3GB of space free are rare these days but i suppose they are still out there big_smile.

Sad2 can be made to run without any clicks at all. See post 5 by mr_smartepants.
create that file and put it in the root of your DVD, that will cause SAD to run when the disc is inserted.
We of course assume that AutoRun is enabled for the DVD drive on the system.
Also see here  http://forum.driverpacks.net/viewtopic.php?id=2264
It shows several options for DVD and Thumb drives for single and no click at all options.
the info is older but does still apply...

Jeff

PS SAD2 uses all or any of our packs.
http://forum.driverpacks.net/viewtopic.php?id=5336

PSS if you pre-extract all the packs (M1 or Method 1) on a thumb drive you can drastically speed up SAD2.
Create a runme.cmd file with one line in it "DP_Install_Tool.cmd /s" that will run SAD with a double click. big_smile

493

(10 replies, posted in Software)

lucaslopezld123 wrote:

SAD2 is great!, Although DPSU runs ahead as only extracts the necessary drives ...
there is any"js" or module that you can edit to launch the process unattended?

That is a misunderstanding on your part.

The archives are created using solid compression... that means they must be extracted completely to obtain even a single file. so even though it seems like they are only extracting the files you need in reality they are all extracted. Otherwise they could not retrive the files from the archive. big_smile

494

(30 replies, posted in Software)

bump

495

(10 replies, posted in Software)

you can try to ask him... Solution is not a DriverPacks project. He just uses our packs for his project big_smile.

Perhaps send him a message through forum email or post in his sub-forum here.

We support our own SAD2 here and will answer any questions related to that big_smile.

Have a great day.

496

(5 replies, posted in Windows 8 Discussion)

Anybody have a slab yet? AKA Surface.

497

(53 replies, posted in 3rd Party Vista / 7 DriverPacks)

Wow, Lots of the old gang here on this one.

Hey all!

that is with the packs right?

When you say 'bug' i think DriverPacks BASE... try almost three years. big_smile

We don't normally refer to conflicts or ommisions in the packs as bugs... wink

imagine that pants you were right wink

We haven't had a bug in how many years?

well 7b is HDD controller driver failure...

Bigfoot is correct drivers must be added with DISM.

I havent syspreped win7 ... I am not a fan of SysPrep
... In XP it was neccessary to set the HDD driver to standard IDE before sysprep. May be something similar in NT6.

There is not any clear guideance for Silent and self removing for SAD2 because DriverPacks is all about unattended installation. In fact we do not support ANY attended installation methods. So... it goes without saying that it IS unattended and self removing, since we do not support any other kinds of installs. Sorry that was not obvious. To those that have been with us or known about us for almost a decade now it is very well known. Sometimes it is difficult for us to see ourselfs as a first timer since it has been so long since we were. We can update the SAD2 pages to make sure that people who are unfamiliar with our project(s) get the full picture. thanks for pointing it out.

Jeff

PS you might look into Microsoft Deployment Toolkit