851 Reply by Jaak

(41 replies, posted in DriverPack Mass Storage)

Thanks for the feedback.
I was hoping it would work with the HWID. I will undo that.
A link to the version you have to use (or to a dropshare with file from driver CD) would be nice.

Go to forum: DriverPack Mass Storage

852 Reply by Jaak

(12 replies, posted in DriverPack Mass Storage)

Hi
I thought cleanup did this.. but?
On clean source, NONE, M2, you get iLE's file in cab.
Now, the next? What is this is caused by?
When you next do M1, you find setupORG in cab. (wrong name).
(M1 adds finisher etc in $oem$\$1).

If you would next do another OS type (server2003 after 2000, for instance), M1, with the QSC cache created/used in previous M1, you get a bad install. File-not-found.
These are all good reasons to tell people to use clean source, and to clean cache.
--
Yes, I see many improvements in RC2 and hope to soon get a RC4.

Go to forum: DriverPack Mass Storage

853 Reply by Jaak

(41 replies, posted in DriverPack Mass Storage)

I hope it works, because we probably cannot have two similar drivers for nVidia 630.

Go to forum: DriverPack Mass Storage

854 Reply by Jaak

(12 replies, posted in DriverPack Mass Storage)

Hi,
When I select NONE in M2 to do cleanup, it leaves behind all the txtmode drivers in i386.
It does not restore the correct setup.exe. (the cab contains iLE )
edit; winnt.sif is not restored either.
-------
edit TWO; forget edit two.. it isn't cleanup doing this..
I didn't know about these things before.. We started looking hard this week and came across peculiarities like these.

Go to forum: DriverPack Mass Storage

855 Reply by Jaak

(41 replies, posted in DriverPack Mass Storage)

I thought I had removed a tag in nVidia but I was mistaken about that.
Maverickbna? I made a file YOU can test, because I added your HWID for TXTmode.
DP_MassStorage_wnt5_x86-32_8029_maverickbna.7z
edit> (link killed)

(others can try it too, I saw two other VIA HWIDS I suspect of causing grief, and removed them from TXTmode INI.. )

Go to forum: DriverPack Mass Storage

856 Reply by Jaak

(41 replies, posted in DriverPack Mass Storage)

http://users.pandora.be/jtdoom/save_hwids.cmd

this is the batch command script that gathers HWIDs and created a hwids.txt in same folder you doubleclicked it in.

Go to forum: DriverPack Mass Storage

857 Reply by Jaak

(41 replies, posted in DriverPack Mass Storage)

@ babyboy,
thanks for telling me.
I should have asked for the BSOD stop code. sad

I updated the link in my signature.
Please redownload the HWIDs tool, and try that.
(it is the same version Helmi uses)
We will want the output for sound.

it will pop a notepad window, and then you save as..
(bewaar als, en dan plak je die txt in een nieuwe topic in sound forum.)
Then post about the sound issue in sound forum, and paste the HWID txt.

@ skeptic.
have you tried with 8028nightly?

Go to forum: DriverPack Mass Storage

858 Reply by Jaak

(15 replies, posted in Feedback and Support - DriverPacks Base)

Norton should still allow you put DriverPacks.net in trusted sites, and when you do you look at its options for referrer.

Go to forum: Feedback and Support - DriverPacks Base

859 Reply by Jaak

(3 replies, posted in Feature Requests)

Hi,
the DriverPacks version is used for nightlies, but I agree about making it obvious that it is a nightly or testpack.

We know that 8029 is higher than 80211 and I most often cannot use the date.
These last few days I put together more than one testpacks in the same day, and I was going to use 8029A_txt after 8029_txt. (You should know we finally discovered why we was getting file-not-found reports when nothing looked wrong.)

On main site, When the current release is 8022 the new release gets 8023.
It could be the file that was tested in a 8023A_nightly (or a 8023C_test_a_fix)
When the current release is 801 and the month is 02 all its 802??** Versions are nightlies or for testing a particular fix.
I figure people will know what they are when they download them, and I hope they keep the releases and betas downloads separate, and that they use copies.
You can save downloads from the nightlies FTP in a betas folder, and save released downloads in DP_REL (or whatever).

I will keep this in mind, though.
Hmmm.
What if it wasn't in the name when you downloaded it?
It is easy to rename if you want to.
Add _nightly or _test_for_the_milkman when you rename the pack.
I think people realise that _nightly and _test_txt have a different goal in mind.
We can test several theories and when we get feedback we look at it, and then a new nightly gets built using the things that we was told worked.
Thank you for helping us help you.

Go to forum: Feature Requests

860 Reply by Jaak

(29 replies, posted in Feedback and Support - DriverPacks Base)

LOL...
Watsons use google.

Go to forum: Feedback and Support - DriverPacks Base

861 Reply by Jaak

(29 replies, posted in Feedback and Support - DriverPacks Base)

thanks.
We learn something new every day.

Go to forum: Feedback and Support - DriverPacks Base

862 Reply by Jaak

(4 replies, posted in Software)

Hi,
welcome to DriverPacks.
You discovered a bug but you were not the first to find this one.
OverFlow wrote about this not too long ago, and he is working on a fix.

Go to forum: Software

863 Reply by Jaak

(41 replies, posted in DriverPack Mass Storage)

one fix that will Come up has a correction in Nvidia.
I hope to finish tests before nightfall (GMT 20.00 today) and then you people get to test it.
I would like to get 802 released before monday.

Go to forum: DriverPack Mass Storage

864 Reply by Jaak

(29 replies, posted in Feedback and Support - DriverPacks Base)

I never had that gdiplus error and suggest you run a memory test tool.
I do know of a few reported bugs what affect VPC, but I cannot be your watson.
Most issues with VPC got reported and your issue should be reported too, but you had better do that report at a msft site.

Go to forum: Feedback and Support - DriverPacks Base

865 Reply by Jaak

(15 replies, posted in Feedback and Support - DriverPacks Base)

There was no PHP edit done I know of, and the link to chipset you wrote gave me a working file DL.
DriverPacks has a few people who know how to publish main DriverPacks.
They have a code of honour.
We admit mistakes.
I am not aware of any.

Go to forum: Feedback and Support - DriverPacks Base

866 Reply by Jaak

(8 replies, posted in DriverPack Mass Storage)

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.

Go to forum: DriverPack Mass Storage

867 Topic by Jaak

(12 replies, posted in DriverPack Mass Storage)

Dear Gentlebeings,

yesterday we was bughunting and we learned about some peculiarities.
I have the habit of slipstreaming DriverPacks into new copies of source.
When I didn't, it usually was with a newer testfile on the same OS, and I am in the habit of clearing QSC folder.

Now, without explaining all of the things we found out, I will advise all users that they clear QSC cache between slipstream, and that they use source copies that had no previous mass storage slipstreamed into them.

Of course, you can store copies of Nlited/RVM'd source on hard disk and we can call that the "clean source", but I will advise you slipstream DriverPacks into a new copy of that..

What is the issue?
Well, for instance; you have copies of the various sources without DriverPacks on hard disk, and you slipstream XP with QSC ON, and next you slipstream a copy of 2003 with QSC ON. Well, 2003 setup will come up with a file not found during TXTmode.
The file will get found when you slipstream a clean source of 2003 after you clearded QSC cache.
This happens when you do 2000 as second OS as well. If you do not clear QSC cache, then 2000 will halt on file not found. (different file)
It was like chasing ghosts. What we fixed unglued itself?
Anyway, the thing you should remember is that I advise, for the time being, that when you slipstream with QSC ON, that you do so with TXTmode folder removed from QSC folder. AND, that you should NOT slipstream mass storage into a source that was already slipstreamed with another version of Mass storage. Please use a new copy of source.

QSC ON does not add much time for TxTmode, and method one slipstream has a bug when you turn it OFF.
It usually works for you in Method two with QSC OFF.
(I will run a series of tests on M2 with QSC OFF tomorrow.)
I have to thank Jeff for the long sessions in which we discovered this peculiarity.
---------
OK, it is edit time.

The tests with method 2 and QSC OFF worked just fine.
When I started to advise to always turn QSC ON in Method Two, it was because we got reports about failed slipstreams.
When we told them to turn it ON, the user had success.
However, we have now learned that this advice is probably not the best advice.

It is still mandatory that you turn ON QSC in Method ONE.. So you better CLEAN that cache (remove mass/txtmode) when you next do another Operating System.
It is still best paractice to use a clean source.  This can already have SP and hotfixes and so on..
When you use another version of mass storage, you had better use a copy of the clean source that has no DriverPacks streamed in.
----------
Jeff is coding DpsBase, and we had many sessions in MSN where we banged heads together.
One of the reasons some people have a messed up 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 behind files 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 assumed 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.
(Textmode is same in M2 and M1.. The methods differ in how the drivers are made ready for Windows PnP.)
The Tut in my signature will get updated.

Go to forum: DriverPack Mass Storage

868 Reply by Jaak

(41 replies, posted in DriverPack Mass Storage)

als de uwe bijna explodeert, dan had je het geschreeuw in mijn hard disk daarnet moeten horen toen ik twee ISOs setup liet draaien in elk een van de VPC2007 vensters.

Ik ben bezig het nieuwe pack in verschillende windowsen te testen, want we leerden iets over enkele eigenaardigheden.

JA, als je kan, laat het ff koelen, en doe morgen een nieuwe.
-----
My hard disk screeched while I tested ISOs in two VPC boxes.
We learned about some peculiarities, and I am testing all windows versions before I upload what I tested.
(WE is Jeff and I. We was looking for peculiarities, and found some. We hope to fix the case sensitivity issue.)

Go to forum: DriverPack Mass Storage

869 Reply by Jaak

(41 replies, posted in DriverPack Mass Storage)

@ babyboy

Did you make a clean copy from the CD before you used a new testpack?
In the tutorial we do not say so, but a fresh clean copy of the CD works best.
We also advise to delete the QSC folder when you try a new testpack.

Je bent vrij nieuw, en je raakt het spoor kwijt.
If you can, put a clean copy of the CD in a folder, and make a second copy in a working folder.
Try 8028 with txtmode and mass storage selected, and use a CDRW to test the install.
If that works, tell us about it, and call it a day.

If it doesn't work, delete the working copy, and make a new copy of your stored CD-copy

move 8028 out of DriverPacks folder, and put 8026 in.
delete the QSC folder, and slipstream the working folder.
re-use the CDRW for the new burn.
test that.
If this also does not work.. then I don't know what will, but I will at least know that it was not some mixup between different packs that messes you up.

Go to forum: DriverPack Mass Storage

870 Reply by Jaak

(51 replies, posted in DriverPack Mass Storage)

A new testpack is in nightlies FTP.
http://dev.driverpacks.thesneaky.com/dr … nightly.7z

That pack includes Sil Image 3135 Helmi REQuested in new folder [S3] and the REQuested windows update version in [S7B] for 3114Raid5.

The Via [V4] section no longer has PCI\VEN_1106&DEV_0591
I also removed Mode tagging after subsys in a couple sections.
(we got proof that &CC_010* only works after DEV_* and not after SUBSYS_* )

Go to forum: DriverPack Mass Storage

871 Reply by Jaak

(41 replies, posted in DriverPack Mass Storage)

If skeptik and babybow can test this new testpack, we would find out if it was that 0591 messing it up.
8028nightly
http://dev.driverpacks.thesneaky.com/dr … nightly.7z

That pack includes Sil Image 3135 Helmi REQuested in new folder [S3] and the REQuested windows update version in [S7B] for 3114Raid5.

The Via [V4] section no longer has PCI\VEN_1106&DEV_0591
(I put the other HWIDs back in)

I also changed the modetags where they was wrong. (proof of that in other topic)

Babyboy can first test the 8028nightly version, and only if that fails he should try 8026nightly, because we MUST at least try with as many HWIDs as we can.
In other words, I will not move 8026nightly out of reach yet.

Go to forum: DriverPack Mass Storage

872 Reply by Jaak

(125 replies, posted in DriverPack Mass Storage)

so... now we will have to rush towards a release.. Because a fluke like this cannot stay in.

I will upload the latest build so you guys can TEST it.

Go to forum: DriverPack Mass Storage

873 Reply by Jaak

(125 replies, posted in DriverPack Mass Storage)

Hi
THANKS for that method of testing the theory.
I have just pulled the &CC_010*  from SUBSYS_*&CC_010* where we did that.

I wonder if you read it, but I once wrote I thought that SUBSYS_* would deal with the "mode", but yes, a few sections got  "mode-tagged" after a SUBSYS_* despite my doubts on that.
You just proved to me that this is invalid.
THANKS.

Go to forum: DriverPack Mass Storage

874 Reply by Jaak

(9 replies, posted in DriverPack Mass Storage)

Hi Helmi,
There is a nightly 8028 with the two drivers from WU.

Go to forum: DriverPack Mass Storage

875 Reply by Jaak

(41 replies, posted in DriverPack Mass Storage)

pulled

Go to forum: DriverPack Mass Storage