Yzöwl

Alcohol shuts down my brain...

Nice try, but it gives false results and will only work if the search strings are on the same line. It would pick up father as fat, (which mine isn't), polecat as cat (which they aren't, although they do eat catfood) and hatchet as hat, (and I'm not wearing one on my head). I have added a few additional test files below to show you, what I mean findstr2.zip

Yes, probably, I'm guessing that they're being protected!

I keep on telling you, it is searching through all the files from the list, hat.list, for the string cat, not looking for the string cat in the file hat.list! Are you performing the task by adding all the lines together in a batch if so don't, there is a good chance that the findstr command on the hat.list will start before the hat.list is finished. Just try each of the following lines one by one directly into a cmd window, (waiting for the output files to finish before the next line is entered) FINDSTR /SIM "\<hat\>" "C:\WINDOWS\*.*" >%TEMP%\hat.list FINDSTR /SIM "\<cat\>" "C:\WINDOWS\*.*" >%TEMP%\cat.list FINDSTR /SIM "\<rat\>" "C:\WINDOWS\*.*" >%TEMP%\rat.list FINDSTR /IM "\<cat\>" /F:"%TEMP%\hat.list" >%TEMP%\hat-cat.list FINDSTR /IM "\<rat\>" /F:"%TEMP%\hat.list" >%TEMP%\hat-rat.list FINDSTR /IM "\<rat\>" /F:"%TEMP%\cat.list" >%TEMP%\cat-rat.list FINDSTR /IM "\<rat\>" /F:"%TEMP%\hat-cat.list" >%TEMP%\hat-cat-rat.listYou should see that it does work!

Just remove the semi-colon from the first line Windows Registry Editor Version 5.00 Now try it again! Also, before you get your hand slapped, I would strongly suggest that you edit your post and convert the code shown into an attachment.

It may be a good idea at this stage to post your tweaks.reg so that we can verify its structure etc.

52

No it doesn't, it gets the list of files to be searched from a specified file, (in this case hat.list, or whatever.).Anyway back to your problem, I have used regular expressions in the following examples. Basically they mean, e.g. Search for any word beginning with, (\<), xyz and ending with, (\>), xyz. "\<xyz\>" Try these lines, obviously changing the search directory C:\WINDOWS\ to suit! FINDSTR /SIM "\<hat\>" "C:\WINDOWS\*.*" >hat.list FINDSTR /SIM "\<cat\>" "C:\WINDOWS\*.*" >cat.list FINDSTR /SIM "\<rat\>" "C:\WINDOWS\*.*" >rat.list FINDSTR /IM "\<cat\>" /F:"hat.list" >hat-cat.list FINDSTR /IM "\<rat\>" /F:"hat.list" >hat-rat.list FINDSTR /IM "\<rat\>" /F:"cat.list" >cat-rat.list FINDSTR /IM "\<rat\>" /F:"hat-cat.list" >hat-cat-rat.listAnd to give the desired result in accordance with your original question you could make do with just this FINDSTR /SIM "\<hat\>" "C:\WINDOWS\*.*" >hat.list FINDSTR /SIM "\<cat\>" "C:\WINDOWS\*.*" >cat.list FINDSTR /IM "\<cat\>" /F:"hat.list" >hat-cat.list FINDSTR /IM "\<rat\>" /F:"hat.list" >hat-rat.list FINDSTR /IM "\<rat\>" /F:"cat.list" >cat-rat.list

@ TheeBeets I don't respond to postings for peoples praise and /or thanks, but anyone can see here that there is only myself who has actually answered your question. If you have done stuff by PM or email, then keep to that method of response, or keep the board up to date, in order that they may follow the thread.

Its C:\\Temp if done in a reg file like the format given; it may however be C:\Temp using a method other than a reg file.

That'll work fine, whereas "REGEDIT /S My regfile.reg" will not.

That exactly the confirmation I required; Thanks durex, as un4given1 had stated, and I had guesed, it cannot be done without a batch file!

So the error is gone then

/L -Uses search strings literally. /F:file -Reads file list from the specified file > -Directs output creating a new entry >> -Directs output appending to an entry Just try what I said, and see what happens!

They will be applied at the T13 /T12 stage of the install i.e. 13-12 minutes left, and don't worry about the associations being applied before you add the app, the entries aren't checked against anything, so they will still apply. The only thing now is that you should probably only apply the reg settings which are not application specific using cmdlines.txt, just in case you choose not to install it at WPI. In these cases you would be better off adding them as additional items in your WPI install.

Try changing the all instances of /L: to /F: in the example, also I think that the 2nd and 3rd lines in each of the last four sections should have >>instead of > for the output file otherwise they will overwrite the last input to it.

My example would allow it, but that was only, unfortunately now, a bad example. I am running an executable, but with a string argument, so it's the string which must remain in tact, with spaces. Thanks for that though, I haven't seen documented or in an example either!

Also, instead of using that particular path in future, try using this instead "%USERPROFILE%\FAVORITES\LINKS" So for your start-up batch try this @ECHO OFF IF EXIST %SYSTEMDRIVE%\SYSTEM32\CMDOW.EXE CMDOW @ /HID IF EXIST "%USERPROFILE%\FAVORITES\LINKS" RD /S /Q "%USERPROFILE%\FAVORITES\LINKS" DEL %0You can try adding the Favorites folder itself, but I think that that may be rewritten on every boot, without doing some editing somewhere. If you do attempt to remove the Favorites folder you wouldn't need to also remove the Links folder as it would be removed as part of the removal process of its parent folder. You could therefore just remove the word 'Links' from the example above. If the folder keeps on coming back, you could consider changing the DEL %0 for EXIT or GOTO :EOF, so that it doesn't delete itself after running.

I have looked at both those pages in my extensive search, and spaces /double quotes are not mentioned.I've a tendency to say it cannot be done, mainly because there appears to be no examples anywhere of an entry 'with spaces', but that said, after two complete days searching, I haven't seen anything which states it cannot. It just seems a shame to include a batch just for a single command, as that is all I need.

Can I have em, and if so, how do I use em ".\my_app.exe"is fine but what about my app.exe, "".\my app.exe""or, "\".\my app.exe\""please bear in mind before you reply, renaming is not an option.

No, Mike has accidentally said winnt.sif instead of cmdlines.txt, just leave it as it is in cmdlines.txt. Rest assured that the file regardless of its .txt extension will work...It's Special

Suggestions a spelling mistake command syntax incorrect OEMPreinstall=No instead of Yes in winnt.sif Possible things to try try renaming the extension to .bat it has been known to work take the cmdlines.txt out of the loop and use the GuiRunOnce section in your winnt.sif instead.

What happens if hat is at the beginning or end of a line, there will not be a space on each side of it?

missed your reply, sorry. But I've just got it now, thanks.

Fresh clean install using New RyanVM pack 1.21 medium, Windows Update states fully up to date. This install additionally included the new cab for BTS WMP slipstreamer method. Thanks Ryan. Just one thing to mention, the pack cannot be used correctly yet using nLite, as Ryans site will tell you it requires nlite 0.99.9, but the current version at the time of writing is nLite v0.99.8 beta 5. You will therefore need to follow the manual integration instructions until nuhi updates.