please read this
(Rightclick, open in new window)
http://forum.driverpacks.net/viewtopic.php?id=2374
Jeff is coding Base at the moment, and we had many sessions in MSN where we banged sherlock's and watson's heads together.
One of the reasons some people have a messed up an install source is that many users were led to believe that Base cleans up previous slipstreams quite nicely.
Well, that is NOT a fact. To the contrary. It left files behind from the old slipstream which can mess up the new slipstream and most often this is undetected because it still works.
The people reporting issues and many (if not all) experienced testers would start fresh when they felt that they needed a clean fresh source, and I assume all experienced users know that it is not a good idea to repeatedly slipstream different packs to a previously slipstreamed source.
Base is not bad when it is used with prudence.
Mass storage has seen drastic changes, and we all learned.
What I learned yesterday has had me make new test files.
The latest I have was extensively tested in method 2.
The advisory post I linked to tells you what not to do.
The Tut in my signature will soon get updated.
fixes in this new testpack are like this.
I removed &CC_0101 (and 104) mode tags where they would cause a BSOD.
(YEP... I thank the poster whom proved to us that mode-tagging cannot be done after subsys_*)
Note to Frequenzy; One of the affected HWIDs was a Nvidia.
Note to myself, I probably did that to avoid a duplicate.. I have to again CHECK dupes.
Via drivers have issue too.
Hey, they usually had. It worked fairly well until we had updates available..
I have to get to bed.
I will upload a 8029 tomorrow.
Last edited by Jaak (2008-02-10 10:39:52)
The answer was 42?
Kind regards, Jaak.