Ben N

@rahuldottech Busy! But it's been fun. Are you in college now?

@Burgi Not yet - currently in junior year :)

:D

@Burgi Hi! Good to see familiar faces (familiar icons?) still here after so long :)

I notice a Type property that seems to be set to "Local" for local printers (-Name set), maybe you could check that and put -Name or -ComputerName in the glob hash as appropriate?

@MichaelFrank Oh, it's globbing? The vast majority of the parameters in the output of Get-Printer only correspond to the complicated parameter sets of Add-Printer

You can just close the Bash window

Looks like -Name is for local printers and -ConnectionName is for connecting to a shared network printer?

I think the safest bet in terms of PowerShell being able to decide a single parameter set is -Name, but from skimming the documentation it looks like -ConnectionName and -Name don't mean the same thing

For which specifying -ConnectionName (first, simple set) or -Name (third, more featureful set) rather than passing the name as a positional parameter should work

One set (the second one listed) seems to require -PortName, so you probably need to disambiguate between the first and third

Hmm, do you know which parameters are needed?

Hi!

May I see the Param block that's giving you trouble?

Making an optional parameter mandatory for one set might help

If you've already rebooted the machine or reopened the command prompt, maybe the path is too long and getting truncated? Though I'm on Windows 10 and my path seems to be well over 2000 characters with no problems

Afraid not, sorry :/

Can confirm that stopping the beep driver removes that sound

Oh, I recognize that sound now - I heard it when I pressed too many keys at once in a video game

Beep is a user-mode function that seems to, at least in some Windows versions, rely on the beep driver

Is there a user-mode API that operates via the beep driver?

(that's total speculation, I'm not sure of the architecture related to delivering input to windows)

Maybe the window manager does this when it tries to enqueue an input message to a full message queue?

A Microsoft representative(?) seems to confirm that it does indeed indicate that the system is busy

That's... very interesting, I hadn't noticed that

(edited a bunch of times there, sorry)

You could have a variable that's initially $false and gets set to $true after one iteration of the loop, then pass -HideTableHeaders:$showedHeaders to Format-Table

Nice!

Does the Format-Table consistently fix it?

Without anything to explicitly say "put this stuff on the screen", we were relying on the default printing after the output eventually falls out the pipeline

foreach captures the output of the stuff inside it, so you can assign a whole foreach block to a variable

Ohhhhhh I think I see

Does adding [Console]::Out.Flush() after the Get-ADUser line also fix it?

Hm, maybe buffering-related? I've never encountered a problem with that in PowerShell before

Now that's interesting

Or if you do only the foreach without the enclosing while or the sleep in a fresh prompt, do you get AD data?

Like $users | Get-ADUser -Properties EmailAddress | select ...

Let's see if we can pipe $users directly into Get-ADUser, removing the need for a loop

Interesting

Is the ... a bunch of 2s and 3s?

Does the problem also appear if the wait time is short, like 5 seconds?

Hmm, if you sprinkle Write-Host lines around, do they execute in the expected order? Maybe put one before the for-each, one inside the for-each, and one before the sleep

Get-ADUser is probably finding nothing

I'm pretty sure that should be synchronous - what kind of values does $users hold?

Hi!

"DONG`n"*12

\o/

Pattern and context and attitude are more important

It's more a thing of "please don't" but I think instant suspension for it is a little excessive

@allquixotic Unsuspended