Re: Repairing Windows System Files

[tbp1...@gmail.com]

You don't have to do each step separately first, but if you don't give the 
right leadin, you won't even see the help options.  E.g., if you type

dism  /?

then "/cleanup-image" will not be one of the options listed.  "/online" 
will be listed, and you have to know to ask for 

dism /online /?

and then "/cleanup-image" will be be listed.  If you want to discover 
"/checkhealth ", "/scanhealth", or "restorehealth" you have to include 
"/cleanup-image":

dism /online /cleanup-image  /?

On Sunday, June 12, 2022 at 4:08:54 PM UTC-4 David Szent-Györgyi wrote:

> On Sunday, June 12, 2022 at 3:35:17 PM UTC-4 tbp1...@gmail.com wrote:
>
>> You cannot get help on, e.g., "/cleanup-image", or even learn that it 
>> exists, unless you prefix the help command with the "/online" .  It seems 
>> that dism can do so many things that the help system had to become 
>> complicated, too.
>>
>
> You mean that one has to enter the command *dism /?*
>
> then 
> *dism /online /?*
> then 
>
> *dism /online /cleanup-image /?*The same is true of PowerShell's built-in 
> help: one has to drill down, one argument at a time. One must know which 
> argument to give at each step. That would be easier if Microsoft chose more 
> wisely when coining names!
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/dddec83d-e543-4e28-bd9a-64c40c6382f0n%40googlegroups.com.

Re: Repairing Windows System Files

[David Szent-Györgyi]

On Sunday, June 12, 2022 at 3:35:17 PM UTC-4 tbp1...@gmail.com wrote:

> You cannot get help on, e.g., "/cleanup-image", or even learn that it 
> exists, unless you prefix the help command with the "/online" .  It seems 
> that dism can do so many things that the help system had to become 
> complicated, too.
>

You mean that one has to enter the command *dism /?*

then 
*dism /online /?*
then 

*dism /online /cleanup-image /?*The same is true of PowerShell's built-in 
help: one has to drill down, one argument at a time. One must know which 
argument to give at each step. That would be easier if Microsoft chose more 
wisely when coining names!

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/304c92a8-5793-45cb-8af8-375b19c215d2n%40googlegroups.com.

Re: Repairing Windows System Files

[tbp1...@gmail.com]

On Sunday, June 12, 2022 at 3:14:06 PM UTC-4 David Szent-Györgyi wrote:

> On Sunday, June 12, 2022 at 10:03:54 AM UTC-4 tbp1...@gmail.com wrote:
>
>> The help text for dism is mostly unintelligible to ordinary computer 
>> users.  You would have to know a lot of Microsoft-specific OS details to 
>> make sense of most of it.  The only help command likely to be helpful for 
>> most of us is
>>
>> dism /online /cleanup-image /?
>>
>
> I am not in front a WIndows computer, so I cannot see the response to that 
> command. Am I correct that the response is display of the options for 
> performing cleanup or recovery operations on the operating system as 
> installed on the computer that is providing the command line?
>

Yes, that's right.  But there is another wrinkle. You cannot get help on, 
e.g., "/cleanup-image", or even learn that it exists, unless you prefix the 
help command with the "/online" .  It seems that dism can do so many things 
that the help system had to become complicated, too.

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/36f9cde8-496e-418f-a232-9942905bb43dn%40googlegroups.com.

Re: Repairing Windows System Files

[David Szent-Györgyi]

On Sunday, June 12, 2022 at 9:26:35 AM UTC-4 David Szent-Györgyi wrote:

Links of interest: 
> Repair a Windows Image 
> ;
>  
> includes dism usage for checking whether an image is repairable, for 
> detecting corruption as well as for making repairs
> Windows Imaging Format 
> , on Wikipedia 
> VHD (file format) , on 
> Wikipedia, covering VHDX as well
> DISM Overview 
> ,
>  
> Microsoft's documentation, not written for the general reader
>

I add another link, which should come first in the list: 

Use the System File Checker tool to repair missing or corrupted system files 
,
 
which covers Windows Vista through Windows 10. This is a task-centered 
procedure that explains just enough of the purpose of each command that one 
enters. The article makes no mention of Windows 11, alas.  

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/c9b31d84-8002-4e10-beb3-18a4fa243e61n%40googlegroups.com.

Re: Repairing Windows System Files

[David Szent-Györgyi]

On Sunday, June 12, 2022 at 10:03:54 AM UTC-4 tbp1...@gmail.com wrote:

> The help text for dism is mostly unintelligible to ordinary computer 
> users.  You would have to know a lot of Microsoft-specific OS details to 
> make sense of most of it.  The only help command likely to be helpful for 
> most of us is
>
> dism /online /cleanup-image /?
>

I am not in front a WIndows computer, so I cannot see the response to that 
command. Am I correct that the response is display of the options for 
performing cleanup or recovery operations on the operating system as 
installed on the computer that is providing the command line?

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/f764db0c-8c59-48df-9446-3594e96ccbden%40googlegroups.com.

Re: Please upvote Thomas's gf4 project

[David Szent-Györgyi]

>
> Youngsters have no idea what programming life was like in the "horse and 
> buggy" days 40 or 50 years ago:
>
> - Feeble hardware.
> - Feeble programming tools: We worked in assembler or C.
>   No git, python, numpy, matplotlib and leo.
> - No internet! No google, github and online communities!
> QQQ
>
> 40 or 50 years ago the challenges were way different, but we had the same 
> kind of engineering fun seeing what was possible.
>

In 1980 I was briefly involved in a project aimed at writing software to 
help in learning or reviewing trigonometry. The software was to run on the 
Atari 800 microcomputer, which offered sophisticated graphics for video 
displays, supporting mixing of text and graphics and offering hardware 
support for overlay of sprites along with hardware for detection of 
collisions between sprites and the rest of the displayed field. All that 
relied on custom chips built to run alongside the computer's 6502 
microprocessor; controlling it required careful programming. The machine 
featured a maximum of 48 KB of RAM and a floppy disk drive. 

The project's software was written in Forth, which provided a programming 
language, use of assembly language when needed, and a development 
environment that could fit on so small a machine. Forth had for many years 
an important niche in industrial control and embedded computing. 

Links of interest: 
Forth (programming language) 
, 
on Wikipedia. 
Gforth, GNU Project's implementation 
Win32Forth 
Documentation and books
Gforth user manual 

Starting Forth , by Leo Brodie, 
updated in 2003 by FORTH, Inc. 
Thinking Forth: A Language and Philosophy for Solving Problems 
, 
by Leo Brodie 

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/499730d0-403f-440b-94f5-3144177f80d7n%40googlegroups.com.

Re: Repairing Windows System Files

[tbp1...@gmail.com]

The help text for dism is mostly unintelligible to ordinary computer 
users.  You would have to know a lot of Microsoft-specific OS details to 
make sense of most of it.  The only help command likely to be helpful for 
most of us is

dism /online /cleanup-image /?


On Sunday, June 12, 2022 at 9:26:35 AM UTC-4 David Szent-Györgyi wrote:

> The terminology used with Microsoft's *dism* gives specific new meanings 
> to terms widely used in broader contexts. Keep in mind these specific 
> meanings: 
>
> WIM file a "Windows image" file, used for deployment of Windows Vista and 
> more recent versions of Windows; extension .wim
> VHD and VHDX files "Virtual hard disk", other types of file containing 
> disk images; extensions .vhd and .vhdx
> /Online targets the installation of Windows that is in use
> /Image targets a specified WIM file , VHD, or VHDX file. 
> store from British usage, a place in which items are routinely kept; 
> distinct from the North American usage for a shop)
>
> Links of interest: 
> Repair a Windows Image 
> ;
>  
> includes dism usage for checking whether an image is repairable, for 
> detecting corruption as well as for making repairs
> Windows Imaging Format 
> , on Wikipedia 
> VHD (file format) , on 
> Wikipedia, covering VHDX as well
> DISM Overview 
> ,
>  
> Microsoft's documentation, not written for the general reader
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/9f5ba602-208f-4f30-ade3-1dddb4e304c3n%40googlegroups.com.

Re: Repairing Windows System Files

[David Szent-Györgyi]

The terminology used with Microsoft's *dism* gives specific new meanings to 
terms widely used in broader contexts. Keep in mind these specific 
meanings: 

WIM file a "Windows image" file, used for deployment of Windows Vista and 
more recent versions of Windows; extension .wim
VHD and VHDX files "Virtual hard disk", other types of file containing disk 
images; extensions .vhd and .vhdx
/Online targets the installation of Windows that is in use
/Image targets a specified WIM file , VHD, or VHDX file. 
store from British usage, a place in which items are routinely kept; 
distinct from the North American usage for a shop)

Links of interest: 
Repair a Windows Image 
;
 
includes dism usage for checking whether an image is repairable, for 
detecting corruption as well as for making repairs
Windows Imaging Format 
, on Wikipedia 
VHD (file format) , on 
Wikipedia, covering VHDX as well
DISM Overview 
,
 
Microsoft's documentation, not written for the general reader

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/b40a7658-0a29-4448-8b2c-41db489fb24fn%40googlegroups.com.

Re: Repairing Windows System Files

[tbp1...@gmail.com]

I had one case where I had to run sfc several times before it reported no 
problems.  Then I ran dism and it found (and repaired) more.  That seems to 
be in line with what you wrote.  I haven't studied all the command line 
options for the tool.

On Sunday, June 12, 2022 at 8:13:44 AM UTC-4 David Szent-Györgyi wrote:

> On Saturday, June 4, 2022 at 5:57:21 PM UTC-4 tbp1...@gmail.com wrote:
>
>> I don't know when to prefer one over another.  I run sfc first, perhaps 
>> because it's easier to remember the command line.  If problems are found 
>> and claimed to be fixed, it's probably good to repeat the scan.
>>
>> I mention these utilities even though they are not Leo-specific, because 
>> it's hard to discover them online and I have found them helpful.
>>
>
> If my reading of the explanation below is correct, it is best to use 
> *dism* before using *sfc*. The following is an excerpt from Using the 
> Deployment Image Servicing and Management Tool (DISM) to repair the Windows 
> System Store 
> 
> .
>
> *The System File Checker tool can be used to repair corrupted system 
> files. For more information on how to use the tool, refer to the following 
> Microsoft article: Use the System File Checker tool to repair missing or 
> corrupted system files . The 
> System File Checker tool compares those files against the .wim store that 
> is saved on the system (not to be confused with the Windows Software Store 
> app where you can purchase software for Windows). If this store is 
> corrupted, the repairs may not resolve the problems that the system is 
> having. The DISM tool has some modifiers that can scan and repair the .wim 
> store based on parent copies stored on Microsoft’s update servers, making 
> it useful to run in conjunction with a system file check.*
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/027d868c-c78c-4c32-8486-b8aae627e3dbn%40googlegroups.com.

Re: Repairing Windows System Files

[David Szent-Györgyi]

On Saturday, June 4, 2022 at 5:57:21 PM UTC-4 tbp1...@gmail.com wrote:

> I don't know when to prefer one over another.  I run sfc first, perhaps 
> because it's easier to remember the command line.  If problems are found 
> and claimed to be fixed, it's probably good to repeat the scan.
>
> I mention these utilities even though they are not Leo-specific, because 
> it's hard to discover them online and I have found them helpful.
>

If my reading of the explanation below is correct, it is best to use *dism* 
before using *sfc*. The following is an excerpt from Using the Deployment 
Image Servicing and Management Tool (DISM) to repair the Windows System 
Store 

.

*The System File Checker tool can be used to repair corrupted system files. 
For more information on how to use the tool, refer to the following 
Microsoft article: Use the System File Checker tool to repair missing or 
corrupted system files . The 
System File Checker tool compares those files against the .wim store that 
is saved on the system (not to be confused with the Windows Software Store 
app where you can purchase software for Windows). If this store is 
corrupted, the repairs may not resolve the problems that the system is 
having. The DISM tool has some modifiers that can scan and repair the .wim 
store based on parent copies stored on Microsoft’s update servers, making 
it useful to run in conjunction with a system file check.*

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/25dc0b8d-08db-4ac1-8d63-3f45bfc7bdb3n%40googlegroups.com.