Search options (Page 71 of 159)

Can you post your HWIDs?  I'm not sure your post belongs here if you're using BartPE.
BTW, DriverPack LAN 10.11.1 is the latest.

Added to 10.11r2 (not online yet)

Yup, we know all about it.  We're busy updating DriverPacks BASE...please be patient.

We may not wait that long...

Since you already know where the nightlies are hiding...Can you test 10.11r2?

When you integrate DriverPacks into an XP source, key files are backed up so that DriverPacks may later be "uninstalled".
The original txtsetup.sif was backed up to txtsetup.org.  When you "updated" your DriverPacks, DriverPacks BASE removed the now modified txtsetup.sif and replaced it with the .org (now renamed).
This is why we ALWAYS say "use DriverPacks last", because any modifications AFTER DriverPacks are integrated will be lost when the DriverPacks are updated or removed by DriverPacks BASE.

I'll look into it.
*Edit
Not a valid file.  There are no drivers in the .exe, only .msi files.

Good find.  I'll update DriverPack LAN.
Welcome to DriverPacks!

Sure, but there's no guarantee they'll work with those newer drivers in there.

*Edit
Nope, the drivers you linked are 3 yrs older than the ones in DriverPack Sound B and will not install even if I add them to the pack.  Also the older drivers contain less than half the HWIDs of the current DriverPack Sound B \I\ folder, and would be a significant downgrade if implemented.
If the current DriverPack Sound B doesn't work for you, then your only option would be for you to manually remove the \I\ folder and replace it with your older drivers.

I think that was requested years ago because the app would appear to hang during the txtsetup.sif/dosnet.inf update phase with no feedback to the user what was happening.
Having the window "focus" as top-level could be annoying if you're doing other work and it's in the way.  But on my machine, integrations only last about 90 sec, so it's relatively minor IMHO.

I used to own a Socket 478 P4 (2.8GHz) and it was not x64 capable (even with the extensions, which only allow for more RAM).  IIRC, the only Socket 478 CPU that supported 64-bit was the xeon.
Your system uses Socket-T, so it's possible.

Well, every document I can find at Dell states 64-bit OS are not supported (by omission). XP64 wouldn't install at all if the system didn't support it.  You'd get a cryptic error at the end of txtsetup "not supported".  So if it installed at all, then I guess it's supported.

Indeed.  I installed XP64 on exactly 3 machines and they have collectively been a support nightmare far surpassing all other machines combined!  Migrating them to Vista 64 was the best move for me (Win7 is 1000% better).

I don't think it's a driver problem.  It's hard to tell.  Do you modify the Win7 source in any way?  Is it a legitimate hologramed disc or did you "acquire" it from somewhere else. 
I don't think I've ever seen that happen with a plain, untouched disc before (I have an HD3450).  But if it's a tainted pirated source, then you never know what you're going to get.