jaclaz

Well, redirection is for the output of a command, not for the command itself. Try running this: @SETLOCAL SET MyNum1=1 SET MyNum2=2 >NUL SET MyNum SET MyNum>NUL @ECHO. @ECHO Here start the @ @SET MyNum1=1 @SET MyNum2=2 @SET MyNum @SET MyNum>NUL jaclaz

Not really. You shouldn't redirect to NUL when you can "hide" that output by simply adding a "@" before that line. jaclaz

Sure , and now - through a moderate use of torture - I managed to have you document that reason. Sure it is a personal opinion, though exceptionally the fact that a number of drivers (most?) have the same file name for both architecture is not a (valid) reason, particularly if coming from someone that had the sensibility (and good idea) of renaming the drivers to avoid the possible update issue. Anyway my congratulations to you both for the idea/finding and for the mods that allow the use on Win2K. jaclaz

Given the "delims=<>:/|?*", what happens if the last character is a delimiter? I.e.: DIP=dfhkasldfjjalsdkj| or DIP=dfhkasldfjjalsdkj? About the "fun" code, some of the things that may happen can - as you did - be explained, some other things of what happens in batch has no real *rational reason* or explanation, some are quirks, and you need to learn to live with them. Rob van der Woude has a few pages documenting "strange" or "unexpected" things that may happen in batch (and how you can in some cases take advantage of those): https://www.robvanderwoude.com/altmsdosbatch.php https://www.robvanderwoude.com/useless.php https://www.robvanderwoude.com/clevertricks.php jaclaz

Well, in the meantime I checked, and seemingly you didn't change the .sys contents, but changed the .sys name (or at least I was able to find the same binaries in a supposedly original Asmedia driver set), then the 64 bit .dll is unchnaged but renamed, while the 32 bit .dll you patched/modified. If I may, not the smartest of the ideas to call the 32 bit and 64 bit drivers the same . I am attaching the original drivers (together with a copy of your drivers in a more convenient .zip format and with a filename slightly more readable than "f45t5753p100543n2_dQJtNfwo.rar" ) because - set apart the name change - it seems to me interesting for learning about the .inf and .oem changes you made . jaclaz ASM106x_ori_XP_sata_drivers.zip danielk_ASM106x_mod_XP_sata_drivers.zip

If suggestions are open, what about "The Nameless Browser" (TNB for short) which is accurate and vaguely reminds of H.P. Lovecraft : https://en.wikipedia.org/wiki/The_Nameless_City jaclaz

Is it modified or unmodified? Only for the record, I had to get unrar because it is compressed in a format that my 7-zip (of course dated) doesn't understand. A .7z or even better a .zip would be nicer (next time). particularly if the thingy is intended for 2K/XP users. jaclaz

Personally I would go for the PS2 keyboard. The USB 2.0 pci card (while a nice idea ) seems to me something that would be worth the time of an experiment, but there is a concrete risk that the install will fail, or - if you prefer - PS2 keyboard surely works, your USB 2.0 PCI card may. jaclaz

Anyway someone that took the pains to instal Win9x to a logical volume already should know that some issues may come with it. Just in case, good ol' XOSL FAQ's contain some good information about this (and various other "old OS" knowledge that is little by little being forgotten): http://www2.arnes.si/~fkomar/xosl.org/faqhow/faq.html jaclaz

Ok, I see where the issue arises from. I needed the Tomorrow and Naturally is on first as placeholders (to get the numbering right in the ADDRESS file) but they shouldn't be written to the actual Pitchers and Batters files, that are seemingly written sequentially without "gaps". So it is just a matter of putting an IF condition in the N column of the spreadsheet and regenerate the files, though now fsz it is also needed to add the 00 bytes at the end of the Batters and Pitchers file to match the original "total size". Try the new attachment. jaclaz Trip_Baseball_2.7z

Very good . jaclaz .

Try adding the FullName : https://www.windowscentral.com/how-add-your-full-name-local-account-windows-10 EDIT: found where I read about the issue: https://answers.microsoft.com/en-us/windows/forum/all/windows-10-1903-login-screen/ce270499-fa3f-4c6c-9e50-bdf852f05501 jaclaz

Cannot say what you want to do. I can suggest you to simply acknowledge that "modern" Windows built-in search tools are a lost cause and use a replacement. Namely (if you only have NTFS volumes) SwiftSearch or Everything: https://sourceforge.net/projects/swiftsearch/?source=dlp https://www.voidtools.com/ jaclaz

Why? in-situ (when it works) virtualizes the MBR, creating a new one with just the entry/partition/volume you mapped. ****************************************************************************** *** About the new map option --in-situ *** ****************************************************************************** --in-situ is used with hard drive images or hardrive partitions. With an in-situ map, we can typically use a logical partition as a primary partition. In-situ map is a whole drive map. It only virtualize the partition table and the number of hidden sectors in the BPB of the DOS Boot Record. While disk emulation may encounter various problems with win9x, the in-situ map works fine with win9x. Note that --in-situ will not change the real partition table. Example: map --in-situ (hd0,4)+1 (hd0) jaclaz

Check the "full name" against "user name". I have seen reports where the issue was created by having a "user name" different from "full name". Open a cmd window, in it run: wmic useraccount get /format:list or, if you want to better review the list: wmic useraccount get /format:list>C:\myaccounts.txt jaclaz

But if it only happens several weeks apart, most probably on wednesdays and fridays only, and if there is a full moon when you close Chrome, and only if you do so at the exact moment when the time hundreth seconds are odd, then it is a meta-para-pseudo connection , it has to do and it has nothing to do with the patch at the same time, hence should be classified primarily under the "voodoo" tag. jaclaz

I have not enough experience with Powerhell (please notice the correct spelling ) to give you any meaningful help, but it is a known issue (parameters) assuming you are correctly using the stupid leading "&" (ampersand): https://social.technet.microsoft.com/wiki/contents/articles/7703.powershell-running-executables.aspx#reCodeBlock https://social.technet.microsoft.com/wiki/contents/articles/7703.powershell-running-executables.aspx#The_Call_Operator_amp (but later vestions should not need it ) for parameters see here https://stackoverflow.com/questions/1673967/how-to-run-an-exe-file-in-powershell-with-parameters-with-spaces-and-quotes the staff is so stupidly complex that they made a dedicated program, echoargs, part of the: https://archive.codeplex.com/?p=pscx to check what Powershell actually "sees": https://rkeithhill.wordpress.com/2012/01/02/powershell-v3-ctp2-provides-better-argument-passing-to-exes/ and: https://web.archive.org/web/20170727144215/http://edgylogic.com/blog/powershell-and-external-commands-done-right/ And of course, if you take simplicity out of the equation you can try using this: https://www.mobzystems.com/code/7-zip-powershell-module/ https://gist.github.com/mobzystems/793007db28e3ffcc20e2 or this: https://www.powershellgallery.com/packages/7Zip4Powershell/1.9.0 jaclaz

The bootice/visualBCD are about the BOOTMGR menu (\boot\BCD). The .iso's, etc. should be on the grubdos menu (menu.lst). When you are shown the duplicate entry, try pressing "c". If you get to a prompt like "grub>" it is the menu.lst (or another .lst file). These can be edited with *any* text editor (please read as Notepad). jaclaz

1. Well, you can check it, of course. Something *like*: FOR /F "tokens=1 delims=ABCDEFGHIJHKLMNOPQRSTUVWZabcdefghijklmnopqrstuvwxyz" %%? IN ("!%1!") DO ( SET CMB=%%? IF NOT "!CMB:~0,1!"==":" (SET DlP=ERROR&ECHO !Dlp!&GOTO :EOF) ) would do. 2. Sure, use SET DlP=!%1:~2! instead of SET DlP=!%1:~2,254! the 254 was only an attempt to limit the length of the path, considering that maybe a backlash was needed and leaving a few characters for a sub-sub-sub ... directory. 3. That is the "clever" part , and you should think about it and answer yourself the question . 4. Not necessary a "fatal" error, one can change the code at will, as said it is a simple assumption that the path needs to start with a drive letter and a colon, the issue may be with those cases where you use relative paths (i.e. .\ or ..\) or - and this is one of the show stopper, UNC syntaxes and similar good examples might be: DIR \\?\C:\ or: DIR \\.\C:\ but if you want to recognize that, you will need to add complications and the simple backslash replacement won't work anymore "as is" (and of course introduces the ? as a valid character - in a fixed position - in a path) 5. As said the treating of double quotes is correct, double quotes cannot be inside a valid path AND can only be, matched, outside it and enclosing it, i.e. EITHER no quotes OR quotes enclosing it tertium non datur: https://en.wikipedia.org/wiki/Law_of_excluded_middle Having a path ending with a single backslash is correct. <last character is a full stop or period Looking for illegal characters, is - obviously - legal, if there is an illegal character, then the path is not valid (it is illegal), so yes, if any of the no-no characters is found the only possibility is to have a fatal error. Point being, what if all the checks performed till now are not enough? If the path is an existing path one could do, with the "as sanitized as possible" path variable a further check, *like* CALL :is_expanded_path !%1! GOTO :EOF :is_expanded_path IF %1=="%~dp1" ECHO Path %1 seems fine IF NOT %1=="%~dp1" SET DlP=ERROR&ECHO !Dlp!&GOTO :EOF that might help. And now, for the fun of it, try to visualize the results of the following batch before running it: @ECHO OFF SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION SET _Dir="C:\*" CALL :is_expanded_path !_Dir! SET _Dir="C:\/" CALL :is_expanded_path !_Dir! SET _Dir="C:\*/" CALL :is_expanded_path !_Dir! SET Head="C:\ SET Body= SET Tail= /" FOR /L %%? IN (1,1,12) DO ( SET Body=!Body!? SET _Dir=%Head%!Body!%Tail% CALL :is_expanded_path !_Dir! %%? ) ECHO . SET _Dir="C:\|/" CALL :is_expanded_path !_Dir! SET _Dir="C:\P*/" CALL :is_expanded_path !_Dir! SET _Dir="C:\*a?*/" CALL :is_expanded_path !_Dir! GOTO :EOF :is_expanded_path ECHO %2 "%~dp1" anything unexpected? jaclaz

I know , I was only pulling your leg a bit. Yep , you know, I tend to make the exact opposite, believing that simplicity is the ultimate sophistication: https://quoteinvestigator.com/2015/04/02/simple/ I try to remove as much as I can, and possibly even something more, so I am always on the brink of creating havoc because I omitted some checks . Since you like this kind of stuff, how to make sure that the "path" does not contain any non-legal characters? Let's decide which characters are not allowed in a path: https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file (of course the backslash is allowed in a path, it is not in a filename, and of course the colon is allowed in a path, but ONLY as second character) @ECHO OFF SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION SET _Dir=%* :: _Dir may be enclosed in quotes, or simply contain one or more quotes CALL :validate_dir _Dir ::Now _Dir is surely quoted with matched quotes SET _Dir GOTO :EOF :validate_dir ::make sure it contains no quotes SET %1=!%1:^"=! ::make sure it contains none of <>:/|?* ::let us assume that it begins with a drive letter followed by a colon IF "!%1:~1,1!"==":" (SET DlP=!%1:~2,254!) ELSE (SET DlP=ERROR&ECHO !Dlp!&GOTO :EOF) FOR /F "tokens=2 delims=<>:/|?*" %%? IN ("!DlP! ") DO (SET DlP=ERROR&ECHO !Dlp!&GOTO :EOF) :: make sure it ends with backslash SET %1=!%1!\ ::make sure it ends with only one backslash and enclose it in double quotes SET %1="!%1:\\=\!" GOTO :EOF jaclaz

Well, the subroutines I write don't generate errors , as said it is a case of writing style. Anyway, the ENDLOCAL is unneeded (there are very few cases when you need to NOT run the whole batch "LOCAL" and thus you need to exit the mode). The subroutine about MATCHED quotes is not relevant speaking of Paths. A path is EITHER enclosed in quotes OR it is not (you can't have a quote or any matched couple of quotes in a path), SO you can strip ALL quotes and reenclose the path in quotes (and this covers BOTH matched and UNmatched quotes) i.e.: @ECHO OFF SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION SET _Dir=%* :: _Dir may be enclosed in quotes, or simply contain one or more quotes CALL :validate_dir _Dir SET _Dir GOTO :EOF :validate_dir ::make sure it contains no quotes SET %1=!%1:^"=! :: make sure it ends with backslash SET %1=!%1!\ ::make sure it ends with only one backslash and enclose it in double quotes SET %1="!%1:\\=\!" GOTO :EOF It is much simpler (as it does a much simpler transformation). jaclaz

Naah, most of the time it is just one's own "writing style", or - if you prefer - there is more than one way to skin a cat (though none that the cat would appreciate ). Yep, adding them when missing AND removing duplicates when they are already there, and check (once and for all) if they are included in quotes (needed for paths with spaces) i.e. (example): @ECHO OFF SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION SET "_Dir=%~1" :: _Dir is not enclosed in quotes, stripped by the ~ CALL :validate_dir _Dir SET _Dir GOTO :EOF :validate_dir :: make sure it ends with backslash SET %1=!%1!\ ::make sure it ends with only one backslash and enclose it in double quotes SET %1="!%1:\\=\!" GOTO :EOF You are welcome , nothing missed that I can see, what I see unneeded is the ENDLOCAL&EXIT (the first can - should - be replaced by a GOTO :EOF, the last can - as well should - be replaced by a GOTO :EOF or, if it is the end of the batch, it's function is automatically performed by the actual EOF). But again it is probably a question of writing style, to me the "main" of the program must always end with a GOTO :EOF and as well each and every subroutine must begin with a :label and end with a GOTO :EOF. jaclaz

Some. "md5sum" is not a built-in batch command, so it must be an external program (and as such it should be always invoked as md5sum.exe, possibly even including its path to avoid possible issues when the batch is moved. This said, I would personally rather avoid the IF check and rather use a pipe to FIND, Also - surely you have your reasons but the /o-n parameter to dir doesn't seem like *needed*. As well, you surely have your reasons, but usually the setlocal is done globally on the whole batch and not within a function/subroutine, and without other information the EXIT /B seems superfluous. For the record, a directory should always ends with \. Anyway, provided that I got the whole idea behind correctly, I would personally write that stuff more *like*: @ECHO OFF SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION CALL :f_RecurseMd5 "%~dp0" GOTO :EOF :f_RecurseMd5 %_DirNames% SET "_Dir1=%~1" IF NOT "%_Dir1:~-1,1%"=="\" SET _Dir1=%_Dir1%\ FOR /F "tokens=* delims=" %%? IN ('DIR /-B/A-D "!_Dir1!"^|FIND /V /I "App.md5"') DO ECHO md5sum.exe "!_Dir1!%%?" REM FOR /F "tokens=* delims=" %%? IN ('DIR /-B/A-D "!_Dir1!"^|FIND /V /I "App.md5"') DO md5sum.exe "!_Dir1!%%?">>App.md5 FOR /F "tokens=* delims=" %%? IN ('dir /-B /AD "!_Dir1!"') DO IF EXIST "!_Dir1!%%?\" (CALL :f_RecurseMd5 "!_Dir1!%%?\") :f_CleanUp SET _Dir1= & ENDLOCAL&EXIT /B 0 Of course it still needs to be tested/validated. jaclaz

At first sight the Excel file looks good, what you have as "team 46 using 2019 files" should be team 39. Try checking the teams one by one against the Excel, most probably there is a "slip" somewhere". But the Batters2019 file is also fine, Chone Figgins, etc. are on team 46. :unsure: jaclaz

Just in case, Letter Assigner: jaclaz