Search options (Page 12 of 213)

It is going to be inevitable that providers will drop support for XP in their drivers. How many drivers today include support for win98?

Haswell is NT6 platform oriented hardware, run Win7 on it. IF you are really really tied to software that is locked to winXP then Run Win7 with XPmode. It's specifically for that reason.

If a driver supports an OS then we gleefully add it.
We can't put square pegs in round holes, find the round peg and it's all good.

we had a heck of a time with HDAudio until MS came out with the KB888111 (i think that was the number)  HDAudio  patch. there won't be any new patches so... we will have to see what develops.

if they're on-board they may still not release them. the "reset" of the BIOS will re-enumerate the resources .

MSFN.org is the place to find what you seek

that's what i did, but mine is very specialized, we use the output to populate the fields for publishing a pack. That is all it does. but... if very efficiently extracts (99.3%) all the correct HWIDs and categorizes by OS, and skips non entries. Only for one very specific task, that has a user base of two.

We have a forum for UBCD4Win if you need us

I'm moving this over there too

That's exactly what we need to know

all we need to do is move the matching HWID from I\A to I\9 or add the matching HWID to I\9... What is the BEST matching HWID to add (or move) ???

it's not an easy thing to deal with as you well know !
No easy way to keep is short and sweet.

Love your Easy 2 Boot - I use it all the time!

I am so glad you are here!

Jeff

Let me put it another way, originally we had mass storage packs with sub folders. At some point the pack became flat, with no sub folders. Now it has sub folders again. The program and features have not changed. Sub folders were always supported and still are. That has not changed.

You simply picked a version that didn't have any and so you were surprised when they reappeared.

And yes I can see that the "current version" would make sense to use.

But we didn't change anything, you simply did not pick the best example to use to write your code . And i am certainly not saying that is your fault either. the current version at that time simply did not demonstrate that convention.

you just needed to learn a bit more about whet is supported, since that scenario did not exist in your example you could not have known about it. But we didn't change our rules. if anything we reverted to our old style.

Also when people have issues many times we recommend that they try an older version. Some times we break things in newer versions and the older version will work when the latest greatest does not. Now there is an advantage to everyone... your code will now work with our older packs too .

you don't strip anything out, just use a "clean" source. One that has not been added to.
Clean sp2 source is recommended by bartpe but xp sp3 works fine.

When you run Base make sure it's in BartPE mode and NOT in Windows mode.
Any drivers you select will have plugins built. Just because the plugins are built does not mean they will work. Sound will fail for sure, but BASE will build the plugin. This is because BartPE does not have the proper structure to support the sound drivers. (a short-coming of HWPNP) other drivers are simply not needed, like video. Typically all you need are Mass, LAN and WLAN.

if you select them in DriverPacks BASE BartPE mode it will make the plugins. then simply make sure the plugins are enabled when you run PEBuilder.

not simple but it's  not complicated either .

do those files exist in the mass storage plugin folder?
Which mass storage pack did you use? (version)
Which BASE version?
It may also help to see the DriverPacks BASE-log (in case it failed to create the plugin correctly - and would mean it's not your fault )

This should actually be in the BartPE forum, we may move it at some point

Welcome to DriverPacks.net!

Welcome to DriverPacks.net smc1979,

Thanks for all the help, looks great! Feel free to contribute as much or as little as you wish. This tool has been here a while and we have had zero feedback on it for some time. Until you showed up . If changes will benefit you then they may help others too. Please share both the why and the results as often as you llike .

We actually use a different tool here on the team, one that I wrote that is very specific to our needs. His has a lot more features. Mine does a much better job of returning the HWIDs contained in the files. Some of his changes were the direct result of us pointing out errors / omissions as a result of my scripts output. one of the big ones was hitting the max array size in AutoIt. .

I'm so glad you joined, again, welcome aboard.

Jeff