Sure, kick-mute exists. And there's almost never a good reason to use it.
@JourneymanGeek Most people respond well enough to a verbal warning. And kicking without said warning/notice seems kinda pointless - it doesn't tell them what they're doing wrong.
A persistent offender can't be dealt with via kick-mute, since it's so short...
it seems like they focus a lot on obsessively high quality features whenever they do anything, which means when we get new stuff it generally scales well, performs well, but takes forever and a day to come for fairly small changes
But you can only have so many full-fledged moderators. Too many diamond mods and the community may no longer be able to function in a democratic fashion.
The answer as it is, does not answer my question (i.e. how do I do X). Instead the answer links to a bug report with a solution. I've just imported the solution to the answer.
@BardiHarborow agreed, but my next follow-up is, well, if they're going to have a non-answer, flag it as a non-answer and it'll get deleted, then post your own
having crap content on the site isn't an acceptable alternative just because people have such irrational protectivism over their "own content" (IMO we should be more like Wikipedia so I apologize for my fairly disdainful tone about rejected edits)
I am looking to start a PowerShell ISE sessions as a domain user.
runas.exe /netonly /user:domain.local\username "powershell ise"
I am prompted for the password and the ISE environment launches. However, running whoami gives the following results:
win-machine\user
which is the local machine ...
Well... it would be great if VirtualBox had proper nested virtualization support. Not sure if the improved AMD-V features in Zen allow for better performance running nested VMs, but it would really be useful for more ambitious projects.
Things have improved greatly with the latest versions.
Perhaps a good motivator would be to tell myself, "we spent $4K on Astaroth for a reason, take advantage of that investment to learn skills for your career!"
And with my mother starting to give me more agency to do things on my own, I should no longer feel stuck in a rut.
(e.g. I'm now allowed to make more significant financial decisions on my own, without clearing her)
It was mostly compute-bound on both systems, but having an NVMe SSD works wonders even when it's not obviously I/O-bound, since the NVMe protocol inherently requires less compute than SATA AHCI.
Which is why I got 10m 45s on the desktop. (POST is oddly long on this motherboard FWIW.)
Windows 10 version 1803 appears to have greatly improved the memory compression feature. I'm seeing less paging under memory pressure and more memory saved from compression as reported by Task Manager.
This is a huge deal on a netbook with 2 GB of RAM.
@Bob my main beef is even fiber to the home has an uptime around 95-97% instead of the 99.99% or better that you get in a DC... they install it so cheaply and without caring about the quality of their workmanship and you get line issues and reliability issues, and the hardware is cheap buggy crap, it's just faster ADSL basically
I'd pay a $1000 setup fee just to have enterprise-grade installation that will actually work reliably for a decade at least
these residential ISPs seem to take a special pleasure in saving every last quarter of a penny to figure out the best way to deliver a service that'll work fine on Day 1 of service without regard for how many support calls it's going to cost later down the line when the shoddy service just randomly cuts out or gets misconfigured on the service end, etc.
> Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server.
NTLM is a weaker authentication mechanism. Please check:
Which applications are using NTLM authentication? Are there configuration issues preventing the use of stronger authentication such as Kerberos authentication? If NTLM must be supported, is Extended Protection configured?
@Bob I saw a couple and put them on the list... for completeness and to suit the many different definitions of "simple"
"simple" depends far too much on end user skill and in some cases "press two key at the same time" could be beyond the end user. Sometimes the simplest method could be "check the box the computer came in"
IIRC my search was literally "Windows 32 or 64" to find a whole bunch of dupes. Granted there's a lot of the kind of questions he didn't want... but there were enough of the ones he did.
I wasn't meaning to imply anything about bad searching, the search tool is fickle and a bit quirky at the best of times. I just get vaguely miffed by HNQs repeating old questions.
In short, this is a mixture of limitations. One is in how many "address lines" the CPU itself supports (different from the 64/32-bit address space/register size), 32 lines would allow 4GiB of RAM, having a 33rd line connected would allow 8GiB of ram and so on.
The other problem is in how many...
@djsmiley2k depends on the CPU implementation. Entirely possible to have a 32-bit internal bus fetching data from a 64-bit external bus, you'd just need special instructions that know how to access it. It's not entirely practical and is a lot simpler for programmers if you don't though...
The modularity of CPU and memory is exactly what allows us to tailor computers to suit specific needs. We already have memory "on CPU" and putting more of it just makes it more expensive, not less.
The way I see it, you can't really remove the external memory interface... but you can put more cache onto the processor package. Intel has done this before. It makes a huge difference.
It saddens me to see that Intel has not deployed this technology on any new desktop processors. They still have it for mobile chips, primarily to boost processor graphics performance, but a small group of people fortunate enough to have an i7-5775C know just how underrated the eDRAM is.
@FMLCat there are some benchmarks that show otherwise - if you're very regularly dealing with a common set of data whose size is greater than your L3 but not more than slightly larger than your L4, it'll be faster than going to system memory all the time
@allquixotic A few, very specific benchmarks and/or workloads, yes, which is why I said "pretty much all"
More typical benchmarks show practically no difference
Here they tested Cinebench with no eDRAM, then 128MB of eDRAM clocked all the way from 1400Mhz to 2200Mhz.
Then Anandtech tested performance with a bunch of applications with DDR4 memory all the way from 2400 to 3067MT/s
The biggest difference they got going from 2400 to 3067 was around 1%, whereas close to half the benchmarks saw RAM with tighter timings at 2400 outperform the 3067 stuff
Also note the laptop with DDR4-2133 and no eDRAM outperforming a desktop with the same CPU with 128MB eDRAM and DDR2800
Yeah, that's just one benchmark, but it's hard to find direct comparisons across a ton of benchmarks. The closest you get is them testing a 6770HQ NUC in one review and a 6700HQ laptop in another
@FMLCat NUCs are getting special treatment somehow, I think. What I mean is they're currently the only hardware platform receiving Vega M GH (though it may eventually find use in cheap HP/Dell AIOs in 2 years as a way to use up their stock)
@FMLCat annoyingly they take the middle tier of them (presumably to save power/space, which I like, but still, I want it all :D)
like Skylake 13" MBP gets Intel Iris but not Iris Pro
Kaby Lake gets Iris Plus but still no Iris Pro, no 48 EUs
to be precise they seem to be taking GT3 chips
not GT4e
so if their power budget only supports GT3 I highly doubt they'd take M GH. Maybe in the 15" MBP, but I dunno what Vega M GH perf is like compared to the Radeon Pro 560 dGPU already in those
I am looking to start a PowerShell ISE sessions as a domain user.
runas.exe /netonly /user:domain.local\username "powershell ise"
I am prompted for the password and the ISE environment launches. However, running whoami gives the following results:
win-machine\user
which is the local machine ...
In short, this is a mixture of limitations. One is in how many "address lines" the CPU itself supports (different from the 64/32-bit address space/register size), 32 lines would allow 4GiB of RAM, having a 33rd line connected would allow 8GiB of ram and so on.
The other problem is in how many...
