Does it show up when YOU did that?
IF SO, then I think I have installed a program what changed core settings.
I'd like to know if it brings up txtsetup.sif in the list of files with such txt in it.
Otherwise, it is (imo) a bug.

Have you tried adding a wildcard (*) at the end of VMS (--> VMS*)?
Generally, search should not just search for the lone phrase you entered, but who knows.
Maybe another bug to be reported to Redmond

but, after a slipstream... when I put VMS in that search for TXT dialog box, and let it look for VMS (which ought be in txtsetup.SIF because slipstream added VMSCSI to it.) then it won't show me that txtsetup.sif has that bit of txt..

strange.

well, folder options are set to show all extentions, hidden maps and files, system files, and yet file-manager's file search (for txtstring in files) will not show matches (which I know exist) in that file.

if your XP does show reults, I may have to do a re-install.
(I've been messing on main rig too often lately since the test machines are in overhaul. (read, gutted))

Yes, I can find that one by simply searching for "txt" in the root of my UWXPCD folder.
Pressing [T] once will actually jump to this search entry (there's a plethora of them so it was hard to spot it with the naked eye ).

if your XP does show reults, I may have to do a re-install.
(I've been messing on main rig too often lately since the test machines are in overhaul. (read, gutted))

CAN ANYONE TELL ME WHY SEARCH (For Txt) DOES NOT BRING UP Txtsetup.sif IN THE RESULTS.

That was with caps-lock ON on purpose.

Hidden file attribute maybe?
I think there's a setting in search that omits results in hidden files, even though you can (and should, lol) enable the display of such...

Echo_Platoon wrote:

jtdoom,

Would you like me to be a tester?

HOOT, HOOT.

you are now officially ours, and first errant is about BSOD.

BSOD will mean 'bring sushi or dumplings' when we are done.

Thanks,  jtdoom.  Now, where do I go to download the beta versions of the DriverPacks, so I could look through the files and test them.

jtdoom,

Would you like me to be a tester?

HOOT, HOOT.

you are now officially ours, and first errant is about BSOD.

BSOD will mean 'bring sushi or dumplings' when we are done.

That was with caps-lock ON on purpose.

Really, the recent reducing of BSOD was because Overlap was reduced.
During TXTmode, it it really has to be avoided.
[D-3] is therefore gone.

BSOD... I want it to mean "Bring Sushi Or Dumplings".
The observations we put in that learning pains txt will be a useful basis for future helpers.

When I did the recent Silicon Image update, I looked at ALL the HWIDs these two updates supported.
Every single one was searched for and no overlap was allowed.
That is tedious work, since we still have no database.

This would be a wet dream.
Dbase 1; what HWIDs do we support in the released packs.
2, what is in those new drivers.
3, find overlap.
Then, use your brains and advanced comparison tools..
Common sense tells me that people make errors.
Peer review is a good way to correct errors.
Don't shoot the pianist. Next tune played gets you your honey .

It tells a story.
http://forum.driverpacks.net/viewtopic.php?id=1688

It's amazing that a single comma or carriage return can break this.. But that is what can happen.
Any small typo can break this.
Like an underscore that goes missing (it is a a mystery how that happened). 
Some people take the time to figure out what went wrong when it goes critically wrong, and detailed reports do help. We do need some extra testers, and people who already make their own modifictions can tell us how  to make better modifications.
We need Dr Watsons too.. Yesterday proved this, don't you think?

I know what you mean WRT typos, the number of times I have shouted at my AutoIt scripts saying they are right before clearing my eyes, seeing the missing bracket or quote and then quietly fixing it goes into high double digits.

I have just rebuilt my disc and it works perfectly, thank you. Regarding testing I only have 3 machines, all Nvidia gfx, one with RAID array, one laptop (always have probs with the DP Nvidia gfx so use the OEMs), when the DriverPacks are released a rebuild is done and tested on all 3 and if there are any problems I try to sort of post on the forums.

I do sometimes have the time to spend (on a 4 on 4 off shift pattern), but will take some time to understand the ini, unless there is a readme somewhere. If there is anything I can do that fits my setup, let me know and I will try, this is the type of project that needs to stay alive and if more people help it lessens the burden of others.

just did some tests, and the answer to the twoliner you metioned is that they can co-exist, and do what they must do. (of course, if dac960nt is needed during TXTmode because 2000 cannot see the hard drive, then it has to be enabled for 2000.. (and possibly disable another, to avoid having it bounce a memory boundary.))

Would you like me to be a tester?