Forum Replies Created
-
Posts
-
There’s an interesting thread here on Redit, but doesn’t seem to fly for me, or the guy that started the thread…
yes I’ve done this on previous versions of Server, Server 2008R2 and it worked — doesn’t seem to fly with Server 2019 or the current issue of AMD drivers.
Considering what a telemetry nightmare Windows 10 has become, how flaky the LTSB/C edition of Windows 10 can be — I’m surprised there isn’t greater interest in Server 2019 as a Workstation, as it’s so much more performant for so many workloads.
I’d encourage you to post more info about your system, so when someone does drop by that might be able to help you they know what hardware (Intel, AMD, NVIDIA) and drivers you’re using.
As well if you do a web search for “oculus virtual desktop not working” it turns up a surprising number of results from forums to videos from people that have the same issue on Windows 10 apparently since a recent update to the Oculus software and drivers.
Thanks CakeLancelot next time around I’ll give this a try. I remember having to do something similar long ago on Server 2003 and what were at the time ATI drivers — if that doesn’t date my long term interest in more robust Workstation Operating Systems, I don’t know what would. Interestingly you can still find “ATI” referenced in AMD’s driver and software installations.
Glad to see the forums back up! Have been running Server 2009 for a over a month now (forum dates are wrong from refresh), and really like it! Seems slightly more responsive then Server 2016, slightly less latency in running audio post processing applications, and every bit as well behaved.
Haven’t done any benchmarks, but probably will at some point to see if there’s any performance difference between it and W10, and Server 2016. One thing that also interests (and concerns) me is the amount of telemetry Sever 2019 transmits, so will at some point run Wire Shark and have a look, and see if Blackbird works on 2019 as well…
Thank you for keeping us updated, and all you do to keep the forum current! While there’s a lot to like in Microsoft’s new operating systems, there’s just as much if not more I don’t like making the future of which Microsoft OS sill satisfy me more of a quandary then ever before…
I’d bet file associations can be fixed to register manually again; apparently a lot of stuff can be done via PowerShell from what I’m reading…
Some of the things I wonder include (in rough order of importance):
· does audio work?
· will it properly identify and install Intel network adapters?
· does DirectX install and work?
· can you install WSL like you can on WS 2016 now with PowerShell?
· Edge Browser?In general is it as solid as other WS builds, editions and kernel versions, or is the new junk they’ve been adding like the ‘Immersive Control Panel’ making things flaky and sluggish like it does on the consumer/desktop version of the OS?
I also wonder with Microsoft’s aggressive ‘feature’ additions of telemetry, even to WS 2016, if they’ve added still more of this type of thing to WS 2019… Soon or later, I’ll have to have a look for myself — and while I’m sure feature wise it’s a very modern and capable OS, in general I’m liking the direction Microsoft is going less and less…
Lotusisrael wrote:
WS 2019 seems less bloated and less stuffed with spyware then W10 RS 5, as WS 2016 was less bloated and less stuffed with spyware then W10 RS1.But is it less bloated and stuffed then Sever 2016? 😕
Lotusisrael wrote:
Desktop Experience, although enabled by default on Server a GUI, has some components moved out into other places. The requirement of enabling Fax Server to get printing to work properly (this was the case in WS 2016 as well) and not including this into Desktop Experience causes some issues.Yeah they’ve been moving stuff around and shuffling stuff to the Metro Modern UI since WS 2016, I don’t think it’s a problem, in fact setting up Sever 2016 as a Workstation, even doing every step manually to get it to feature parity with Windows 8.1 or 10 was less work them managing all the bloat and spy-ware on the desktop version of the OS and setting those up not to be such a pain and so awkward to use…
Lotusisrael wrote:
What audio editing software do you use? Pro Tools? Fruity Loops?Literally everything, it just depends on the project I’m working on and who I’m working with — I do mostly post-processing and editing so it’s more to tools like SoundForge, and WaveLab — but has included everything from Nuendo, and propritary mixing console software, game engines, and and all the DX and VST plug-in applications these can use.
I also use some architectural CAD software (mostly for learning) and game so it’s nice to have 3D render performance that’s at close to parity with the consumer OS, to be able to do more things on one system — curranty I multi-boot several OS’s (Windows 8.1, 10 & Sever 15, and BSD UNIX) across several machines to get things done, and it’s tiresome…
Thanks for the update Lotusisrael — I’ve been wondering if 2019 is any good as a Workstation. I’d really like to get around to benchmarking all the Servers that are still updated for some of the stuff I do; 3D render, audio production, and just compare general performance — I remember as far back as Windows Server 2003 even with same kernel version numbers there were some surprising measurable performance differences between Windows Server and the consumer desktop OS. Unfortunately Microsoft’s desktop OS has become such an onerous mess of telemetry, spyware, disparate interfaces — and is as much or more work to setup than a Server OS conversion that I really don’t see a future for it. Also glad to see the forums are back, it looked like they were down for a while!
Tihiy has moved most of his most recent discussion about his Explorer 7 Shell Wrapper to this thread on MSFN; there have been a lot of updates, compatibility fixes, and features added to the wrapper; and he’s still working on it.
Also Stardock’s Start8 has seen a lot of updates, and now offers a standard Windows 7 Start Menu interface, a new compressed Metro interface, and its original twist on the Start Metro interface.
Lastly but not in last place by any means Classic Shell‘s Classic Start has also seen several Windows 8 compatibility and feature updates — that might be worth a look if this is still your favorite.
Right now I’d put Classic Shell and Start8 in a dead heat tie, that can probably be best decided based on which is the least invasive, uses the least resources, and behaves the best if you just want to add a Start Menu to Windows 8 at no cost.
Tihiy’s Windows 7 Explorer Shell Wrapper is a different animal, that can offer some enormous resource savings, totally obviates the Metro/Modern interface, and even allows disabling the OpenGL compositer which Windows 8 Explorer with any flavor of Start Menu won’t allow, and can easily be swapped with the native Windows 8 Shell…
🙂
And another update with news that may not be so good; this time from Paul Thurrott in this blog post, the important quote here:
@Paul Thurrott wrote:
Related to this second point is information I’ve received that Microsoft has been furiously ripping out legacy code in Windows 8 that would have enabled third parties to bring back the Start button, Start Menu, and other software bits that could have made this new OS look and work like its predecessor. In fact, I’ve seen that several well-known UI hacks that worked fine with the Windows 8 Consumer Preview are no longer functional in the coming Release Preview. And those with hopes that Microsoft would allow businesses, at least, to boot directly to the desktop should prepare for disappointment. That feature not only isn’t happening, it’s being removed from Windows Server 12 (Windows 8’s stable mate) as well.
There’s a new build of Windows Server 2012 that was released today 31 May 2012 in parallel with the Windows 8 Release Preview that can be downloaded through the Windows Server 2012 Portal Page…
It will be interesting to learn if the code changes Paul mentions will break the Classic Shell and virtually all the Start Menu hacks like those I’ve mentioned above. If so it may be possible to import the missing files from an earlier RC to sustain comparability — but things reach a point where the work involved is too onerous and the results perhaps not worth the effort…
Update: I just learned second hand that Start8 still works with the new build of Windows 8 and apparently the new build of Server 2012 so if Micosoft has indeed succeeded in blocking other alternatives this may yet offer some hope…
:geek:
Hey ExpertUser! I just found another article, here that apparently restores the Start Menu in Windows 8… This was on an older Windows 8 Developer’s Preview, not the new Windows 8 Release Preview and obviously not Windows Server 2012 — but if it does work it would probably be a preferable option for some than the Classic Shell…
😉
LOL, well I wasn’t entirely joking; consider: Windows Server 8, and to a lesser extent Windows 8 will get deployed in mission critical applications, and as you’ve seen for yourself, certain parts of the Windows 8 interface do not allow the Administrator/User to multi-task when some parts and features UI are being used… That will be a ‘deal breaker’ of epic proportions, just getting kicked out of the Desktop to Metro could literally be a life and death situation where critical data can not be monitored and administered concurrently with configuring some system settings…
:ugeek:
Wow that looks pretty neat! Is it well behaved? Does it still allow you to launch Metro stuff should that ever be needed? Just from your initial reaction alone I have a feeling if Microsoft doesn’t change direction (which seems likely this late in the game) on the Windows 8 and Server 8 DesktopWorkstation interface design — you and the Classic Shell Developers are going to be quite popular with the Server 8 and Windows 8 Administrators and Users…
😀
Cool!
Hey I just noticed this on the Classic Shell FAQ, so it does appear to at least superficially support Windows 8… It may not be an ideal solution but it is a FOSS project that may at least offer some resources (and hope) for a direction to explore (no pun intended)…
Next time I try Windows 8 I’ll certainly give the Classic Shell a try as well as a few other alternative Windows Shell projects that might work to see if they offer more practical Workstation UI that’s also well behaved and robust…
Love your work ExpertUser!
:ugeek:
