Search options (Page 23 of 99)

hmmmn, if we can do this in chips it is perfect, because chipset has to be installed to make intel ahci work.

@ adam,_W
Thanks.
U helped us help you, and made me think about things I never looked at before.

(an aside...IT specialists usually never explain. They fix. I am not an IT specialist. I know maybe 5 percent of what overflow knows about this great project. BUT, I have seen Jeff post the "extra mile" when I did not expect he would. I thank him for sticking to his principles and thank the people whom explain "truthfully", and not hide the mistakes they made. I once told Jeff I use the noobie principle. Hey, that's how I learned it. And how we all learn. I come from scratch, I should be able to explain this to a real noob. We assume our users are not noobs, but I will often find myself in "learning" mode when I read specialised IT guru's methods.)

We all learn. always.

unpruned, that means a list (excell) before we started searching for and looking at ways for filtering out conflicts.
When THAT does not have the specific, and 812 others showed up when we search for generic, YOU had better show us a link to the driver that works.

you can help us help you.
You may want to read the tutorials, they can help you understand pitfalls.
(these tuts do not explain where the logs are found..  duh)

Hi,

We do have to filter the collection and fix issues with conflicting drivers, and sound A and B have new testpacks with fixes.
A low level technician will know permutations, and without going in detail about the fixing I believe these testpacks remove hundreds of possible conflicts by fixing two files (one in A; one in B). Sound A and Sound B were long ago unified, and DriverPacks had to split them for bandwidth... after that members requested support which was added to sound B, and still later sound B was found to contain 'drivers that should work but didn't' and sound A and B had to be made to work together again.
This is what makes DriverPacks special.
YOU help us by telling us what you need, and what you used.
We help you by letting you test the packs.
here are the latest testpacks.
two files fixed, a couple hundred permutations for mismatch removed.

DP_Sound_A_wnt5_x86-32_804a

DP_Sound_B_wnt5_x86-32_804a

That LAN 804 has some good fixes, so I edited overflows post in news with this

EDIT JAAK; we again have issues on LAN 804 download. You can get it from JAAK DP_LAN_wnt5_x86-32_804.7z

The RAM drive size can be set.
it is, of course, obvious that you should not specify larger than what is there.

I used vistabootpro a few times (in vista x32 machines in which XP was loaded after vista.) but have not heard proof it can do vista x64 and vista x32 dualboot.
I will buy me a good testbed for that. I am no longer restricted to one machine of my own anyway..
I have to grin now.. Bigbrit? I have a few testplanks with "crap" feature, and crap helps find issues.

Vista unattended is new to me, and I have seen nothing yet that looks like a simple "how to" for noobies.
(the few "simple" guides I see on the web were wrong in some detail, or were about a detail only..)

@ alex, Thanks.

@adam_w
7zip is a great free tool. There is a small tool called createurSFX for making installers with 7z..
DriverPacks are not perfect in sysprep point of view (still a lot of same filenames, same service names) but a good deal of conflicting hardware ID was "judiciously" pruned so it has become easier to use DriverPacks.
LD? La Douce..

@ overflow
mentioning chipset did some good.
adam_w did not use it and it was part of the problem, so we all learned by my "noobie" comment.

hehe, I learned something too here.

sound 804a have a minor fix in a driver.
In sound A, an "all generic" inf is seen to cause grief time and time again, and its extention got renamed. (the driver has a dozen or so specific inf files..)
In sound B, one of the sigmatel had generic hwids competing with other models.

The chinese txt reads as: 80417rc Kb888111 patch could not be loaded, uaa sound card can not be installed automatically.

WELCOME to driverpacks.
I sent an email to you in which I explained we use English.
Many people here are NOT english. We use it because it is a well known language.

the error you report could be solved if you use a newer DriverPacks testpack.
http://forum.driverpacks.net/viewtopic. … 736#p19736

again?

further refinements in files found here.
http://forum.driverpacks.net/viewtopic. … 734#p19734

OH, met methode 1, eerst 2000 er op gezet..
de XP schijf laden, en 2000 upgrade laten starten gaf geen probleem.

daarna met zelfde schijfje overnieuw, (eerst 2000 er opnieuw op (herpartitioneren/snel formateren).)
dan die XP upgrade laten booten, en die deed ook een upgrade.
(beginschermen als je 2000 XP setup laat starten en wanneer je van XP schijf boot zijn enighzins anders, maar dat is normaal.)

In het kort, met methode 1 kan je 2000 upgraden (txtmode loopt als je van schijf boot, en de $OEM$ folder heeft ook die drivers..
Althans, hier werkte dat.

ik ga nu niet nof ff gauw methode 2 over een 2000 proberen gooien. (dat probeer ik ooit nog wel eens.)

(de txtmode drivers zitten in een methode 1 geslipte XP alsof ze van M$ zelf waren.. en de setup executable is origineel. Da was waarom ik onmiddellijk aan methode 1 dacht.)
Dat is gewoon een andere keuze voor slipstream.
Setup zelf loopt ongeveer even lang.