Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

  • Days Won


Everything posted by jaclaz

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. Yep, whenever the error is "this is not a valid Win32 applicarion" it is worth to try this, though sometimes it is needed to change also the "Minor" OperatingSystem and Sybsystem fields though 5 0 5 0 is OK, jaclaz
  14. To be picky (as I am BTW) the "normal" WinPE from MS does not have it, but it is entirely possible to have it in a PE build created by one of the common tools, i.e. Winbuilder or PEbakery. Win10PE SE has a script "WOW64 Basic" (written by our friend JFX) that does exactly that, i.e. "WoW64 (Windows on Windows64) provides support for running 32bit programs in a 64bit environment.". jaclaz
  15. In other words, if ain't broken, don't fix it. jaclaz
  16. Well, this is bordering with conspiracy theories, that would mean that VmWare paid Microsoft to force their (VmWares) users to update to a new version of VmWare, and that Microsoft took the money and did that knowing that everyone will blame them (Microsoft) for the issue. I would attribute the problem more to the usual stupidity (or rather increasing sloppyness/lack of quality control) of the good MS guys, with VmWare "innocent", so that there is not anything "planned". jaclaz
  17. That issue is with Windows 3.1/3.11 (and - similar but different - with any DOS earlier than 7.0). It was released in times on par with DOS 5 and 6. Last "real" DOS (6.22) only understood FAT12/16 volumes AND CHS mapped only, (partition types 01, 04, 06). Windows 3.1/3.11 having been developed in the same period, and being actually a graphical shell over DOS. uses the same data. Windows 95 and conversely DOS 7.x was, starting with 2nd release, extended with the LBA mapping for "BIG" FAT 16 volumes and FAT32 (partition types 0B, 0C and 0E). To be exact 7.0 introduced LBA FAT16 (0E) and 7.1 FAT 32 CHS and LBA (0B and 0C). More or less *any* tool before Win95 2nd version (DOS 7.1) came out only understood 06 and created only 06 FAT partitions, while later tools, depending on the case, may create either 06 or 0E partitions, more likely 0E. Even if it is not "common" it is perfectly possible to run 3.1/3.11 over DOS 7.0/7.1, but the FAT16 partition needs to be 01, 04 or 06 or Windows 3.x will throw a fit (in protected mode) if it finds a 0E partition. The grub4dos map feature (BOTH the map --in-situ used in that referenced thread and when you map a volume to a whole disk like you do here) creates on the fly a new MBR partition table and for FAT 16 it creates it with an ID of 0E, that Windows 3.1/3.11 cannot fully understand, so the underlying DOS 7/7.1 boots fine, but when the protected mode (and some related drivers) kick in it will error out. Dos 7.x/8 (standalone) and Win9x/Me won't be affected as they understand 0E just fine, besides 0B and 0C, what happens when grub4dos through the map command creates the new MBR partition table entry is seen here: http://reboot.pro/topic/21732-windows-for-workgroups-311-grub4dos-and-protected-mode/?p=206527 In more detail the automatic "conversion" of partition ID is: 01->0E 04->0E 06->0E 0B->0C 0C->0C So I wrote the small batch to allow changing (when/if needed) the partition ID (which may in itself be useful for some other "crazy" experiments) and YaYa (one of the grub4dos Authors/Maintainers) added the feature through the --in-situ=FLAGS. (,both cover and are tested for the "map --in-situ" option only), Some tests would be needed to see if my batch works "as is" or needs to be modified in the case of a map --,mem (hdm,n)+1 (hdm) case (your case) but there is no need for this since you are using Win 9x and a 0C partition ID already. jaclaz
  18. ... and get (additionally/besides Serpent) QTweb, For "simple" sites it is faster and leaner than anything else. jaclaz
  19. They do have a tendency to stop working, particularly on desktops/tower, in my experience laptops (kept properly) are less prone to this, I personally attribute this to three main factors: the drives (common desktops units) themselves are cheap (and as such they are cheaply made) they are used less and less, and lubricants tend to stick up as they dry up very often a lot of air (and dust) is blown through them by the PC internal fan(s), which makes lubricant dry and hardened by dust ciontamination Usually (on desktop units) all is needed is to disassemble and clean the inside accurately, particularly the lens, of course and in some cases cleaning the sliding parts and putting on them a tiny drop/bit of lubricant and move them manually is needed. You'll need both a vacuum cleaner and some source of compressed air. If you need some lubricant, you want to use Molykote EM-30L (which is a specific grease "safe" for plastic parts) for slides and gear teeths and sewing machine oil for metal rods and gear pins, if you cannot find (or afford) the Molycote (or even better "Superlube") any "white", silicon based grease would do, rule of the thumb i to use the least possible quantity of lubricant, (and that much is already too much, you should have used less ). Of course it is well possible that the unit is simply defective/worn-out, but it costs very little to try and clean/lubricate them. jaclaz
  20. http://reboot.pro/topic/22191-how-to-make-a-multiboot-usb-stick-supporting-gpt-and-mbr-targets/ jaclaz
  21. NONE. Read latest dencorso's post to understand why (even if personally I run XP SP2, and - just in case - yes, I know, thanks for telling me that SP3 and unofficial SP4 are available ) I doubt it will work, unless you have Windows File Protection Service disabled, read the instructions: https://www.win-raid.com/t4035f45-Windows-XP-Bit-and-Server-Bit-on-Modern-Hardware-242.html#msg96981 jaclaz
  22. It depends on what you want it to do: The options available are: So, if you type: winxppae.exe /4GB [ENTER] you will have the needed files patched to support a maximum of 4 GB AND a backup of them (before the patch is applied) if you type: winxppae.exe /ALL [ENTER] you will have the needed files patched to support unlimited RAM AND a backup of them (before the patch is applied) if you add after EITHER the /4GB OR the /ALL the /NB or /NOBACKUP (DO NOT do this) switch, you will have NOT the backup. jaclaz
  23. Well, that is much later (like three years later, a different age, it has colours) and it is essentially a Sinclair Spectrum: https://www.old-computers.com/museum/computer.asp?st=1&c=935 See: https://www.youtube.com/watch?v=1Jr7Q1yJOUM jaclaz
  24. @dibya Isn't this the second (or maybe third) Christmas that you create some expectations for something that you never delivered? @caliber OK. Start -> All Programs -> Accessories -> Command Prompt You now have a black window open and you have a command prompt in the form of a line, probably *like*: C:\Documents and Settings\username>_ with the underscore flashing, right? Now you should know where exactly you have extracted the file, you can use windows explorer to get the right path. Let's say the file is in D:\IronPortable\Download\WinXPPAE.exe At the prompt (in the command promp window) you type: cd /d D:\IronPortable\download and press [ENTER]. Please note that if for any reason the path has one or more spaces in it, you need to enclose it in double quotes, example: cd /d "D:\Path with spaces\download" Now the prompt has changed to the path you just typed. Verify that it is the right place: DIR WinXPPAE.exe and press [ENTER] it should show you the file, its date and time. Now type: WinXPPAE.EXE and press [ENTER] You should see the following: jaclaz
  • Create New...