Poll: Why don't you use Linux?

[revelator]

this article might help, it seems to touch on the same problem with the xonar and linux.

https://delightlylinux.wordpress.com/2017/01/13/experience-better-sound-in-linux-with-the-asus-xonar-dx-sound-card/

[revelator]

i hope it helped , my x-fi sadly is no longer supported by windows so im stuck using it with linux but luckily i had no problems with it.

[SeriousToni]

9 hours ago, revelator said:

i hope it helped , my x-fi sadly is no longer supported by windows so im stuck using it with linux but luckily i had no problems with it.

I will test some more and get back here after it. Thank you for your help so far -it's always a good thing having someone to talk to with knowledge instead of random Google searches. 

[revelator]

Allways happy to help . Hope it gets sorted

[taffernicus]

Not for non-enterprise use: I hope I’ll get the chance to set up and maintain Rocky or Almalinux for corporate needs someday.I’m tired of the proliferation of RedHat. I want to compare it with centOS

 

 

[revelator]

redhat is one of the oldest players in the linux world which is why i guess most proliferate them.

redhat is also the developer who took over cygwin from cygnus solutions and further promoted it as a way to build linux software for use on windows and spawned multiple subprojects like msys and rtems who were used as frontends for building pure windows and other OS based binaries using native compilers (mingw gcc for msys and a mix of both msvc and gcc with rtems). cygwin itself relies on the cygwin dll as a dependency for running linux applications on windows by creating a minimal shim based on a subset of the linux runtime environment via newlib.

unfortunatly while it works it is also rather slow because of the emulation so some people created a neutered version of cygwin as a frontend for driving the mingw compiler (msys or minimal system). this allowed users to build software from the linux world as native windows binaries but it did take quite a lot of patching because some of the software relied heavily on the linux api so these parts had to be rewritten to work with the windows api.

Rtems was used heavily by the firefox team before they changed the engine. Mostly because of hurdles with gcc's windows incompatible exception models (dwarf and sjlj) C code was still handled by gcc but for C++ they used msvc so that exceptions were still compatible.

in the end developers started doing most of the gruntwork to make things work on both but it took close to 30 years before we got that far.

the original msys is now dead and replaced with msys2 which collaborates tightly with the cygwin developers and is much closer to the original cygwin code than msys was, in fact you only need to set a few environment varables to turn msys2 into cygwin.

it has even been discussed to add X11 like cygwin does but as a real windows based desktop system for applications that only have gui's compatible with the X system like many of the gnome gtk packages. 

The old msys can still be downloaded and used with both 32 and 64 bit mingw, but it a bit buggy and uses a very old package manager that is incompatible with 64 bit mingw. Might be possible with a lot of work to port the msys2 pacman to it if anyone wanted to. The biggest problem is the instability of the old versions fork implementations and the fact that old msys is 32 bit so it has problems with large memory footprints.