Just curious - since React OS is supposed to be a Win XP clone, is it structured modularly like XP, so that by using a product line Nlite, could React OS be stripped down and turned into an Embedded OS for use in various dedicated devices (CarPC, arcade games, home automation, etc....?)
Also, what about other tools like minlogon to replace winlogon for faster boot ups and shutdowns?
Curt
React OS - nlite?
Moderator: Moderator Team
Re: React OS - nlite?
Well, Yes! I think this will be a thing that makes momentum to ReactOS some day. Imagine some company want to make a home-entertainment machine based on Windows, but they don't want to spend the money on WinXPEmbedded so they decide to sponsor ROS with some developers to apply ROS to their hardware thuss speeding up the development of ROS and they gain a fully configurable OS for their hardware.atarimuseum wrote:Just curious - since React OS is supposed to be a Win XP clone, is it structured modularly like XP, so that by using a product line Nlite, could React OS be stripped down and turned into an Embedded OS for use in various dedicated devices (CarPC, arcade games, home automation, etc....?)
Also, what about other tools like minlogon to replace winlogon for faster boot ups and shutdowns?
Curt
Both WinNT serie sound driver AND activex controls have worked fine in ReactOS for years (see ReactOS Wiki).kokodin wrote:[...] react os will be usles now in car pc because in this moment dont support sound drivers and active x controls
Fact is that we don't ship a open source sound driver, because no Windows compatible one exist ... remember that's also still a problem in Linux, which still come with closed source sound driver and the open ones are even up to now a niche player.
If you use "ibrowser" or the Explorer "web" function, it will download the mozilla gecko activex control, the same gecko engine also work in Firefox (but not as activex control).
ReactOS is in big contrast to WinNT the opposite of bloated, and if you need more tools and features you will be able in near future to install additional tools, drivers, apps, etc. (via package manager or what ever).atarimuseum wrote:Just curious - since React OS is supposed to be a Win XP clone, is it structured modularly like XP, so that by using a product line Nlite, could React OS be stripped down and turned into an Embedded OS for use in various dedicated devices (CarPC, arcade games, home automation, etc....?)
You can replace the logon-user-interface in WinNT serie with your own implementation and you will be able to do the same in near future in ReactOS too.atarimuseum wrote:Also, what about other tools like minlogon to replace winlogon for faster boot ups and shutdowns?
Sorry, but that is just plain incorrect. The vast majority of all sound drivers for Linux are open source and even in-tree (that is, they ship with the kernel itself)! The basic sound support of Linux is easily on par with any other operating system - even Windows. Actually, Linux supports far more sound hardware out of the box than Windows. Of course, when we consider what one gets from the vendor disks, Windows is in the lead by a smallish margin - Linux lags behind for bleeding-edge hardware for obvious reasons.frik85 wrote:remember that's also still a problem in Linux, which still come with closed source sound driver and the open ones are even up to now a niche player.
Wag the dog.
Most of the closed source sound drivers for linux have became Open Source these days.
It was just to embarsing for the makers of the drivers.
The opensource drivers were faster and more stable.
Only close source parts theres days is firmware. Not the drivers.
It what starts me wondering how defective windows drivers really are.
It was just to embarsing for the makers of the drivers.
The opensource drivers were faster and more stable.
Only close source parts theres days is firmware. Not the drivers.
It what starts me wondering how defective windows drivers really are.
What I said is true. Our project still needs a bunch of standard purpose open source drivers (especially sound and filesystem drivers), as closed source drivers are already available and shipped with all hardware. All, other operatings have generally driver problem, as only a small bunch for each hardware category exist for these platforms.Megari wrote:Sorry, but that is just plain incorrect. The vast majority of all sound drivers for Linux are open source and even in-tree (that is, they ship with the kernel itself)! The basic sound support of Linux is easily on par with any other operating system - even Windows. Actually, Linux supports far more sound hardware out of the box than Windows. Of course, when we consider what one gets from the vendor disks, Windows is in the lead by a smallish margin - Linux lags behind for bleeding-edge hardware for obvious reasons.
In case of Linux, all "driver" which come with the kernel or are available as a kernel patch. But patching a kernel is not for beginners and requieres, knowledge, tools, some extra time and in generally reboot(s).
"In the case of the Linux kernel, OSS was the only supported sound system used up to the 2.4.x series. Starting with version 2.5, ALSA, the Advanced Linux Sound Architecture was introduced, and the OSS interface became deprecated by Linux' authors. ALSA contains an optional OSS emulation mode that transparently appears to programs as if it was OSS."
-- http://en.wikipedia.org/wiki/Open_Sound_System
And even if ALSA (Advanced Linux Sound Architecture) is now the prefered sound system some proprietary closed source drivers are still shipped with almost all common Linux distributions.
linux <2.4 kernel ist still wide spread and in several cases the only way, as 2.6 may not be suitable for some tasks.
linux was just a sample which a lot of people know of; if i would have used *bsd or another operating system, only a some people in this forum would even know such platforms.
Who is online
Users browsing this forum: No registered users and 40 guests