Recent content by WildWilly

Oh geez. Single quotes. The one thing I didn't think to try. Anyway, the point is moot now, at least for me, since I renamed the interface. But your advice is probably now just hiding here in the weeds for some other lost soul to use to get found. The background, which I thought was...

Well over a year ago, my close friend :D @garlin gave me a Power Shell script upthread here for displaying the network status dialog. Things have changed & now I have this: C:\Users\WildWilly2>ipconfig Windows IP Configuration Ethernet adapter Ethernet: Media State . . . . . . . . . . ...

By the way, to follow up my posts earlier in this thread, it turned out I had 4 DIMMs of 32G each go bad. I suspect there was something fishy about the LEDs on the spines of the DIMMs. I have replaced all 4 DIMMs with DIMMs that do not have LEDs on them. In addition, I had to change some...

It occurs to me that this might be informative. At a command prompt, execute this: set >"Q:\Useful Files\Environment Variables.txt" Now, maybe you don't have a Q-drive. Pick a drive letter that you actually have. Maybe you don't have a directory named "Useful Files" on your Q-drive. Pick a...

I had reason to get into my BIOS & I do believe I disabled secure boot at some point in the past. I don't remember doing it. There's a setting somewhere in the BIOS that says it's set for other operating systems. I think that's the flag that says secure boot is disabled. I don't recall why...

Oh no. I'm not having any problems. This system is working fine. I don't have Bit Locker turned on & that's how I intend to keep it. I was just adding my experience to the soup here. I'm curious now about secure boot. I need to check that in my BIOS next time I go to boot. News . . ...

Well . . . I'm not so sure about secure boot. I found this: https://support.microsoft.com/en-us/windows/windows-11-and-secure-boot-a8ff1202-c0d9-42f5-940f-843abef64fad They talk about: Go to Settings > Update & Security > Recovery Ain't no such thing. It appears to be Go to Settings >...

@zbook Local account I'm pretty sure secure boot is off. That's a BIOS thing, right? I'll have to look that up. I assume it's supported. It completed successfully. Doesn't that mean it's supported?

I can say that a simple update from W11 23H2 to 24H2 did NOT turn on Bit Locker on my system. The posts in this thread got me a shade alarmed, so I hunted around in my Settings for the relevant information. I have never turned Bit Locker on & it's still not on. On a faintly related topic, the...

In my third .bat file above I have a Type command. That's wrong. The script actually works anyway because the redirection on the command creates the file. But contrary to what I said above, it doesn't contain anything. The error message generated by the Type goes to the bit bucket because...

Got it. I think I'm remembering that if you're coding 1> or 2> or something like that, you can't have a space between the number & the >. A space would set off the number so that the command interpreter would think the number is a parameter for the command. But if you don't have the number...

Oooohhhhh . . . I see what you mean. I told you I'm slow. As of now, I'm running like this: TimeOut /t 60 /nobreak 1>nul Are you saying I could code it like this? TimeOut /t 60 /nobreak >nul Or would it have to be like this? TimeOut /t 60 /nobreak>nul That's without the space before the...

Why? Because I'm slow, and contrary to popular belief, I don't know everything. By the way it's not Dir>null. It's 1>nul. But I do thank you for the inspiration.

As for named pipes, I looked that up once & I got the impression that it's something you can access in C++ but not in simple .bat files. I also got the impression that named pipes is essentially the mechanism I'm describing above with my 3 scripts, where I create a semaphore file in one task &...

Thanks. I guess as long as I use Waitfor but not Waitfor /si, I'll be good. If that stops working, I guess I'll have to come up with some other evasive maneuver . . . like I did when I discovered Waitfor /si was no longer working.