Search options (Page 34 of 99)

Hi
Somebody posted this for bj2tall, and I mistook it for spam.
http://forum.driverpacks.net/viewtopic.php?id=2402

Hi Kevin, you can become a donator

A comment on having all the packs together.

The recommendation to not use all at the same time they posted in other fora must have had a reason, and today that reason has little or no foundation because we groomed duplicated competing Hardware ID we found across different drivers pretty well now.
An example in Sound Packs; A Realtek driver could compete with an nVidia. We made a choice because we had to, and removed some competing files. When Sound A and B are used together, there is not a single competing HWID.. We may have made a wrong choice, or we may be missing a driver, but it is better than having the wrong driver chosen by windows.
In graphics, the packs complement another. Mr Smartepants and the other graphics pack gurus know what they are doing.

B...Y H...LL

I was not subscribed to this topic and just found it back.
You guys must have thought I was nuts?
I put together a Lan nightly 8022 pruned_test and I admit I forgot about this topic.
The LAN8022nightly_pruned test is based on last released LAN 802.1

The changelog is in testing forum, and worksheet are in nightly FTP.

Off the top of my head; in LAN we have NV7 replacing HWIDS in NV4* and NV5*
ALL NV\12 look obsolete, have no unique HWIDs. NV3 has all of its HWIDs, and I removed NV\12.
3 and renamed subfolders stayed
4 had a cleanup, some went in the bin.
5 and 6 stayed.
7 stayed.

I will have to look at this topic again (reread when I look at LAN), and see what I/we can do to make this thing go like "a goldmine"
I can hope for a smart helper whom will look at that nightly, and know test-Packs are in a turbulent flux, so I don't mind it one bit if what I did gets corrected, as long as I hear where I went wrong.
I am getting feebleminded, and think I used a "fresh view" when I started pruning in LAN.
((fretting about one merge))
I know I saw that original excell worksheet and hazed. "before" had over 15,500 HWIDS.

When I finished that build, I knew there are still duplicate HWIDS, and there is a  file I am fretting about has only three.. (there are more than three dupes left in there.)

Anyway, THANKS.
I had forgotten what was written here but some of it must have stayed recessed in an overworked mecanic's duffy brain..
I present my doodles in that nightly, and with what I see you can do I say it's your pot of lead you can turn to gold.

8022  is all yours.

Hi,
couple months ago when DriverPacks sound A and B got looked at for duplicate hardware IDs we saw that Realtek and Nvidia claim same HWIDs, and their versioning system is disparative.
Woow. A 2008 driver could claim a 2005 HWID and be dead wrong, and the pruning I spent many hours on was (is) not perfect.

I hope that team members look at the worksheets, and find problem HWID of yours.
If we had it in an older pack, and current pack uses same version systemfiles, then we can fix this quite easily.

If we never had the HWID, then we must at least take notice of this helpful post.

Goede dag, en welkom bij DriverPacks.

Als je in DriverPacks mass storage kijkt, dan zie je meer dan een folder met VIA txtmode drivers en die moeten wij allemaal tesamen met elkaar maken werken.
De meest recente update heeft enkele commentaren over VIA opgeleverd, en de consensus is eigenlijk dat die laaste update alle hard drives die in BIOS op IDE-modus staan, aanstuurt in RAID.

De mensen die dan wel een RAID array hebben (of die hun BIOS op RAID selectie hebben staan, ook als ze er een enkele hard disk aan hangen hebben.) vallen uit de boot als we die driver er uit doen, en die vorige versie was er in en had klaarblijkelijk geen probleem..

Je kan alle VIA folders die niet overeen stemmen met je floppy en alle niet corresponderende VIA secties in het INI bestand er uithalen, en het mass storage pack (D) met het edited INI terug 7zippen.
Geef het een hoger nummer. 8021 wordt 8022
Gebruik je fixed bestand.
Ik wil wel weten welke VIA driver dat mobo heeft.
Ik kan googlen, maar jij zou een link naar deze die voor jou werkt beter moeten kennen dan ik.
----
Je kan ook een andere instelling gebruiken in je BIOS.

I hate to admit this, but group talk IM in systems like paltalk are not "my" thing. IM in itself is usually shut.
IMs kill concentration. (in MSN, I talk to Jeff, and anybody else can disturb me..)
I like public dissections in fora.
The advantage of fora is that what was written in a moderated forum is moderated.
In IM, it is out of public.
In fora it usually stays public but it can get collected, can get summarised, can get deleted/moved.
(if inappropriate/wrong/insubstantial/abusive/spam.)
In forum, a smart user can use "search" which can bring a big hit discovery for all to read long after.

EDIT
whomever had a good idea discussed in an IM session and does not find DriverPacks relevant discussions in our fora should not hesitate to write about the discussion in a post. YOU could think that I will sit on it. He could think you will sit on it, and the entire community does not find the solution because you all sat on it. See what I mean?

hi, top post has link to other topic.
That topic has the link and extra information.

edit; OOPS.. SORRY
I forgot the testing forum is not accessible to everybody.
It is accesible to applicants for testing team and all team members, and to donators.

Since OverFlow intended that this gets tested, the link to a working RC might be put back in public.
On the other hand, RC2 has been tested, RC3alpha was tested (and the work done in that RC3alpha shows us that new features are not easily implemented, that old flaws are not easily worked around.)
RC2 and RC3alpha is the basis of still newer work main team members have not yet pre-viewed..
So, I wonder. Should I link to a "old" version?
When a new Release candidate can be tested in a wider audience, I think OverFlow will put it up in public for testing. This could be in an existing public forum, a new "public testfiles" forum (Name not fixed, it does not exist yet), or here. He will decide.

Hi.
The link above was killed because that particular file was to test a solution for maverick, and it did not work.
The other fixes we discussed here are included in the 802 release.
For 802.1 release the mass storage INI re-introduced a load order for silicon RAID what we used before and it apparently worked best. However, when a user trying to remove a section to replave the folder and INI section with files he got in a SFXMinipack told me he did not find the section, I put them in alphanumerical sequence again. (That seemed possible because we was then thinking the &CC_010* tagging would fix that sort of misery.)
I thought of this after I put 802 up, and did not want to update this without people knowing there was a INI load order change. (Wouldn't want to do a silent update because of issue mentioned in the post about TXTmode file not found post.)

OH, and the maverick testfile gave no problem for you, that is good news.
That means I did not completely break the VIA Txtmode by editing the pack's INI.

sam1sam
http://driverpacks.net/DriverPacks/changelog.php?pag=m

hehe, well, roughly thirty hours to find dupe weeds and prune them(some dupe HWIDs still exist)
(that includes roughly four hours to write changes in the PHP changelog/supported device file.)

Adding this one was fairly easy. And it had only two dupes in it..
Of course, I did NOT include the utility setup.
Most owners of such stuff would not have it attached during setup, and if they do, it will probably function without installing the utility.

And THAT, that is something ygor.almeida  can find out for us.

Well, I at least learned how to test the solution when it comes available