jaclaz Posted August 10, 2011 Share Posted August 10, 2011 The script stops after doing DIR if the directory is empty ("File Not Found").Well, the idea was to give you the hints, not doing your tests.... What happens with:FOR /F %%I IN ('^>nul DIR/A-D/B HFMER 2^>^&1') DO (jaclaz Link to comment Share on other sites More sharing options...
tomasz86 Posted August 10, 2011 Author Share Posted August 10, 2011 "^" was necessary Doing like this is enough for my scriptFOR /F %%I IN ('DIR/A-D/B HFMER ^2^>NUL')Thank you once again. Link to comment Share on other sites More sharing options...
tomasz86 Posted August 13, 2011 Author Share Posted August 13, 2011 (edited) Using COPY /B serves no purpose when used in that manner, in fact it is the default mode when copying single files.I'm asking about this once again as I'd like to be sure. If COPY/B has no use when copying single files, when do you actually have to use it? Edited March 3, 2013 by tomasz86 Link to comment Share on other sites More sharing options...
Yzöwl Posted August 13, 2011 Share Posted August 13, 2011 Basically, you should only require to use it when merging files into one.Read more about it, (Notes: 3.). Link to comment Share on other sites More sharing options...
jaclaz Posted August 13, 2011 Share Posted August 13, 2011 Basically, you should only require to use it when merging files into one.Read more about it, (Notes: 3.).Well, that seems to apply to MS-DOS 7.The MS resource seen before:http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/copy.mspx?mfr=trueis about XP.The one I cited seems like being NT4 and 2K "oriented":http://ss64.com/nt/copy.html(though as said it is possible that is alltogether "wrong", it does look similar to an actual output of a "COPY /?" ) Since it is not the first time that a "common" program syntax changes dramatically between one version of the OS and the other, it is still possible that NT4/2K behave differently.I have found another "hits" for " /A : ASCII text file (default)":http://www.bat-to-exe.com/batchcommands/copy.htmlthat seem like not coming from the same SS64 source.@tomasz86Why don't you simply try with a few files?jaclaz Link to comment Share on other sites More sharing options...
Yzöwl Posted August 13, 2011 Share Posted August 13, 2011 Well, that seems to apply to MS-DOS 7.The MS resource seen before:http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/copy.mspx?mfr=trueis about XP.The one I cited seems like being NT4 and 2K "oriented":http://ss64.com/nt/copy.html(though as said it is possible that is alltogether "wrong", it does look similar to an actual output of a "COPY /?" ) Since it is not the first time that a "common" program syntax changes dramatically between one version of the OS and the other, it is still possible that NT4/2K behave differently.I have found another "hits" for " /A : ASCII text file (default)":http://www.bat-to-exe.com/batchcommands/copy.htmlthat seem like not coming from the same SS64 source.@tomasz86Why don't you simply try with a few files?jaclazSummary from Windows XP and DOS 7 (above)In Windows XP/b is the default value for copy, unless copy combines files.In Dos 7By default: When copying files from one location to another, COPY assumes binary mode;When concatenating files, COPY assumes ASCII mode;They dont appear to be contradictory so why would NT4 2000 have changed in between them Link to comment Share on other sites More sharing options...
jaclaz Posted August 13, 2011 Share Posted August 13, 2011 They dont appear to be contradictory so why would NT4 2000 have changed in between themIt is a possibility, only trying to find a reason for the mentioned "/A (default)", BTW DOS 7 comes AFTER NT and before 2K.jaclaz Link to comment Share on other sites More sharing options...
Yzöwl Posted August 13, 2011 Share Posted August 13, 2011 Typing error, NT5 2000 Link to comment Share on other sites More sharing options...
tomasz86 Posted August 23, 2011 Author Share Posted August 23, 2011 I managed to get the UpdateInis working but is there any way to prevent moving the edited section to the end of the file?I change some entries under [Version] and after that the whole [Version] section is moved to the end of the update.inf file. Link to comment Share on other sites More sharing options...
jaclaz Posted August 23, 2011 Share Posted August 23, 2011 I managed to get the UpdateInis working but is there any way to prevent moving the edited section to the end of the file?I change some entries under [Version] and after that the whole [Version] section is moved to the end of the update.inf file.And again, no crystall ball available at the moment. Standard litany:http://homepages.tesco.net/J.deBoynePollard/FGA/problem-report-standard-litany.htmlAdditionally post the actual file that gives you problems (before and after the whatever steps you took into changing it).jaclaz Link to comment Share on other sites More sharing options...
tomasz86 Posted August 25, 2011 Author Share Posted August 25, 2011 (edited) http://www.mediafire.com/file/1p82vz13vomc0g9/updateinis.7zupdate-org - the original update.infupdateinis.inf - the Update INIs fileupdate.inf - after running Update INIs (rundll32.exe advpack.dll,LaunchINFSection updateinis.inf,,1) Edited August 25, 2011 by tomasz86 Link to comment Share on other sites More sharing options...
jaclaz Posted August 25, 2011 Share Posted August 25, 2011 http://www.mediafire.com/file/1p82vz13vomc0g9/updateinis.7zupdate-org - the original update.infupdateinis.inf - the Update INIs fileupdate.inf - after running Update INIs (rundll32.exe advpack.dll,LaunchINFSection updateinis.inf,,1)Are you talking of these?[update.Version]"D:\HFMER\SP\update.inf","Version","MaxNtServicePackVersion=1024","MaxNtServicePackVersion=1560""D:\HFMER\SP\update.inf","Version","ThisServicePackVersion=1024","ThisServicePackVersion=1560""D:\HFMER\SP\update.inf","Version",,"ThisServicePackBuild=1"What if you use INSTEAD "Update .ini Fields sections (UpdateIniFields)":http://technet.microsoft.com/en-us/library/dd346763.aspxjaclaz Link to comment Share on other sites More sharing options...
tomasz86 Posted August 25, 2011 Author Share Posted August 25, 2011 I can't get it to work with UpdateIniFields. I've tried many different combinations but the best result I can get is:UpdateIniFields[DefaultInstall]UpdateIniFields=Update.Version[Update.Version]"D:\HFMER\SP\update.inf","Version","MaxNtServicePackVersion","1024","1536"ResultMaxNtServicePackVersion=MaxNtServicePackVersion= 1536 Link to comment Share on other sites More sharing options...
jaclaz Posted August 26, 2011 Share Posted August 26, 2011 I can't get it to work with UpdateIniFields. I've tried many different combinations but the best result I can get is:You are right, it simply does not work , and anyway re-orders the sections as well.jaclaz Link to comment Share on other sites More sharing options...
tomasz86 Posted August 26, 2011 Author Share Posted August 26, 2011 I guess I'll have to stick to Update Inis as reordering the sections in this case doesn't have any influence on how update.inf works... and what's more important is that Update Inis seems to work smoothly. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now