Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Post
  • Reply
Laslow
Jul 18, 2007

astral posted:

Pretty much every install since Vista generates Windows.old if there was an old install detected. :shrug:
It does that in every version of Windows NT ever all the way back to 3.1. Although 2000 and older would be WINNT.old.
e: I’m actually misremembering, I did all that manually. It would just do that for the program files folder. I think you’re right, I think it was Vista and beyond where it wouldn’t just overwrite it like an idiot.

Laslow fucked around with this message at 21:42 on May 18, 2018

Adbot
ADBOT LOVES YOU

Laslow
Jul 18, 2007
I just installed Win 10 Workstation out of curiosity.

It’s running max all-core turbo at all times. Actually 200MHz above spec. It’s not even a CPU with XFR, it’s a Haswell E3. :question:

Laslow
Jul 18, 2007

Last Chance posted:

Let us know how it goes, brave beta testers
Not brave beta tester, but I've had the pulled 1809 RTM build for a while.

I checked for updates and there's new patches, so I just wanted to confirm that there's more to it than just the 17763.55 update version that MS had us marooned on the bad 1809 running for the past couple months.

Laslow
Jul 18, 2007

Last Chance posted:

You were absolutely correct in not wanting glitchy terrible updates on your machine. Even Microsoft encourages that "you to wait until the feature update is offered to your device automatically"

Don't try to skip the line, and in fact install the update as late as possible to allow for beta testing to take place amongst the install base.
If you're doing a fresh install, I'd recommend getting the latest version so you can get it out of the way and make sure your poo poo works. That way you can avoid having a good working 1803 or whatever system and have it all go to poo poo when MS pushes the new release on you in a few weeks/months or whenever they randomly decide to push it on you.

And I have to say this release cadence is ridiculous, by the time they got 1809 ready, it's not that long until 1903.

If they keep buttfumbling every six months, I think they might switch to annual major updates. As it stands right now, we're on up to Windows 10 Service Pack 6 using the old naming convention.

Laslow
Jul 18, 2007

SwissArmyDruid posted:

Does anyone know why WINDOWS itself would stop interacting with sound devices? For the longest time now, I thought that there was something wrong with my Realtek audio drivers that would keep re-loving themselves despite every reinstallation. I even consigned what was probably a perfectly good AT-2100 to the recycle because I thought IT had broken, and not Windows itself.

For the last six months plus, I've been blaming the Realtek drivers, blaming a Windows driver repository problem installing the wrong drivers over what I had installed, that kind of thing.

But I rubbed two neurons together earlier today and remembered that I owned a USB external sound card that I had picked up from a garage sale some years back. USB sound card was tested and found to be good on two other computers, one running win 8 and one running win 10, but plugged into the one that I want to use it on..... I got loving bupkis.

(I am 95% certain at this point that a full reinstall will fix the problem.... but I'm not about to install the October update, still.)

edit: In order, I thought the problem was:

the XLR cable
the USB cable
the microphone
the interface/DAC
the USB ports
the drivers

only to have been wrong each time, and each time I have been loving stymied by this windows install just refusing to accept any input.
Is the Windows audio service running at all when you look in services.msc?

Laslow
Jul 18, 2007
It’s all just making LTSC an increasingly compelling option by the week, despite their best efforts to bury it in various ways.

Laslow
Jul 18, 2007
*pop up message after a major update*

“The reason why your MICROSOFT SURFACE is an unstable piece of poo poo is because BROADCOM won’t get their goddamn act together! gently caress those incompetent lazy douchebags!”

[OK]

Laslow
Jul 18, 2007
1903 is out on MSDN. I went ahead a loaded it up to get it out of the way, nothing weird yet. You won’t miss anything by waiting though, there’s not really any new features that are jumping out at me.

I’m not surprised they played it safe with this one since the last two updates were such huge disasters.

Laslow
Jul 18, 2007

astral posted:

You could beta test Windows Sandbox for us!
It's okay I guess. It's just a Win 10 Enterprise Hyper-V instance with no persistence. That's fine and all, but it sucks if you need anything other than Edge or IE, you can't set a customized loadout/auto-restore point at all. No vGPU options either(or really any options at all).

VMWare Player/Workstation or Hyper-V proper with your own customized restore point works better, as Sandbox doesn't even have anything like unity mode, it's windowed or fullscreen or bust. Even Sandboxie, as hideous as it is is more convenient because of that too.

Since it's built in, it's handy for people who are too paranoid for incognito mode to browse for porn without having to spin up a VM or install Sandboxie, since that'd looks suspicious to nosy spouses. That's about it.

Laslow
Jul 18, 2007
I just read this:

"Intel Xeon, AMD Opteron, and AMD EPYC chips are still only supported for Windows 10 Pro for Workstations and Windows 10 Enterprise. There's no additional Enterprise-specific data shown, but when the Snapdragon 8cx does show up on the list, it should be the first ARM processor supported for that SKU."

From here: https://www.neowin.net/news/microsoft-updates-the-windows-10-cpu-requirements-for-the-may-2019-update

Is that remotely true? I have a Xeon E3 v3 and I'm running Workstation by lucky coincidence, but if they don't support a chip that's identical to a desktop i7 in regular Pro, that'd be supremely hosed up and lame. It's not multi-socket, or even HEDT. That'd barely be "Pro" at all.

e: That'd be the difference of between $300 or a $5 SA Mart/Ebay CD Key. :catstare:

If I didn't have a free copy, that'd be a $300 mistake because I wanted to save $15 and not have to buy a CPU fan separately when I built this computer essentially.

Laslow fucked around with this message at 20:35 on Apr 22, 2019

Laslow
Jul 18, 2007

wolrah posted:

Considering that the small-socket Xeons existed before Windows 10 Workstation was a thing and could be had in OEM entry level workstations shipping with Professional versions they have to a least have grandfathered in support for the older ones. Not sure how strictly they're enforcing the requirement on newer chips.

I do know though that when I've been looking at Dell Precision laptops speccing the Xeon CPU forces me to select Workstation Edition (and vice versa, you can't select Workstation without forcing a Xeon).
HP is doing that too, apparently. I think it's just rent-seeking from Microsoft. There's probably nothing preventing Joe Blow from installing Pro but for OEM's there's some new lovely and sneaky licensing verbiage keeping them from doing it.

Laslow
Jul 18, 2007
People would put off updates for months back in the day just to brag about uptime on their Windows 2000 box, since it was the first stable OS if you used 9x instead of NT. I think blaster worm changed everyone’s tune.

Also gently caress Microsoft, it was dumb luck that I didn’t have my X: Drive plugged in when I installed 1903 since I just moved and it’s still packed. Bastards.

e: it’s poo poo like this that makes me want to go back to LTSB/LTSC. I’ll keep using this dumpster fire and keep my backups up to date regularly until a hosed up update does finally get me.

Keep in mind 1903 isn’t generally available, and their new strategy of sitting on updates for a little while longer actually helped the catch bug before a wide release. I would withhold judgement until the release of WIN10_1903_x64_final(3)forrealthistime.iso hits general availability. Still kinda bad it hit MSDN with the bugs though.

Laslow fucked around with this message at 21:41 on Apr 25, 2019

Laslow
Jul 18, 2007

Lambert posted:

It's me, the person moaning about (and updating to) 1903 that hasn't even been released to the public yet and considering going for LTSB instead. Just accept pre-release software is going to contain some bugs and stop moaning.
If you see my edit, I came to that realization too, eventually.

It made it to MSDN, and MSDN customers are not beta testers/insiders, so I figured it wasn’t too risky. In fact, it works fine, even if only through dumb luck.

I even mentioned that it isn’t being pushed on the general public yet, so it’s not like a debacle with 1803/1809, unless a new bug comes up after that. We’ll see, I guess. But it seems pretty solid so far.

Laslow
Jul 18, 2007

Combat Pretzel posted:

--edit:
Whoops, it was Add-VMGpuPartitionAdapter. Now the guest VM automatically installs the Virtual Render Device like in Sandbox, but it fails with Code 43. :[
That’s normal if you’re using a GeForce card. You need an AMD or Quadro card to get around that usually.

Laslow
Jul 18, 2007
To all those people mentioning vfio and Linux as an alternative, it is perfectly viable if you’re like me and have 2 of everything (VGA cards/NICs/sound devices).

The problem is for me that Lutris with Wine-Staging and dxvk handles everything so well the only time I need to use Windows on QEMU/KVM is PS4 remote play which is the only program I’ve had problems with under WINE.

Other than that, I’ve got a NeXTSTEP clone as a window manager under X11 and I’m trucking along computering like it’s 1999 just fine. gently caress it.

e: I mean even Spotify and Discord and all that electron poo poo runs native fine too now. The worst part was circumventing Nvidia being cunty with error 43 under vfio, which took maybe an hour to figure out.

Laslow fucked around with this message at 23:25 on Jul 26, 2019

Laslow
Jul 18, 2007
I used Irfanview like it’s 2004. It’s crazy how little improvement there’s been on “opening a JPEG” in decades.

Laslow
Jul 18, 2007
See, if you’re properly paranoid then those are too popular. If you’re dodging MPAA copyright notices, sure. But if you’re selling massive amounts of supercomputers like Playstation 3’s to Iran on the deep web, then look elsewhere, pal.

Laslow
Jul 18, 2007

Last Chance posted:

Using win server as a gaming OS has always been possible even now, but it’s also always been a huge pain in the rear end and not worth it
Nah, you just need to go into services.msc and enable a couple things and a few things in the Programs and Features menu and it’s all the same as Enterprise, or LTSC. I don’t remember if they dumped UWP on it yet.

Also optimize for programs instead of background services is the advanced system dialog. I think that’s it.

Laslow
Jul 18, 2007

namlosh posted:

So, what's the best way to install Windows 10 Pro for Workstations? I have an MSDN Enterprise or whatever subscription, so I have a valid license key already. I'm about to flatten and re-install my machine.

Is it through the MCT? Is it just the key that makes the difference? Or do I have to do something else or download it from somewhere other than MSDN downloads?

Also, does it get updates like any other Pro version of Win10? I'd like to use the new Windows subsystem for Linux on it and run sandbox and all that other stuff. Just want to make sure it'll work. I turn my machine off when I'm not using it so the Power Usage doesn't bother me.
You can use the MCT, it might bitch about you having the wrong version of Pro and then prompt you to reboot to upgrade to Workstation, and you’re fine.

I think it does updates like regular Pro, but other than Workstation, I’ve only ever used LTSB/LTSC.

Laslow
Jul 18, 2007
If all else fails you could get a USB sound card for less than :10bux: on Prime. I used one for OOTB drivers on OSX, and now use it in VM’s, so it’s been handy. That’s for if/when you’re ready to give up, though.

Laslow
Jul 18, 2007

Klyith posted:

But I don't think the basic windows games changed between Vista & 7, so I think that installer will do ya just fine.
That game pack is a mandatory download for all my Windows installations. If anything just so I can type in “sol” in the run menu/NTVDM and it work as expected.

I found that those games have rumble support when I set off a mine in Minesweeper and my Xbox controller rumbled itself off my desk, startling me causing me to nearly poo poo my pants.

Adbot
ADBOT LOVES YOU

Laslow
Jul 18, 2007
Cool, I would bet that this isn’t the first time I inadvertently sniped a page with a whitenoise post about pants making GBS threads.

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply