Hacker News new | past | comments | ask | show | jobs | submit login

Good question. I understand the motivation behind it and am impressed with the work done but can't imagine it being used as someone's primary os.



We use it on a Bitcoin ATM that converts spare pocket change to BTC (think Coinstar) in order to avoid licensing issues with Microsoft and Windows CE.


Are you using existing ATM software that was written for Windows, or was this custom development (i.e., did you choose ReactOS over Windows, or over e.g. Linux)?


The hardware drivers for the coin counting ATM machine were provided as precompiled WinNT/CE drivers by the vendor without sources and using ReactOS was easier than reverse engineering them all.


A wrote up about this would almost certainly make the front page of HN.

Not that that should be the primary motivation for writing it, but surely the validation won't hurt! Projects like these are the most interesting ones for me to read!


That's really cool and IMO a great use case for ReactOS. Sounds like a neat project. Did everything just work out of the box? If so that's pretty impressive on the part of ReactOS.


Seems like a pretty reasonable use case. Thanks for sharing!


That is pretty interesting


At home, I would not consider it because it is a Windows clone, and I have certain, strongly-held views on Windows. ;-)

At work, the problem is different - even if ReactOS achieved 100% bug-for-bug compatibility with Windows 10, using it on client PCs would be too painful, because every time some application misbehaved, there would be that lingering doubt if the problem is with the application itself or with the OS. And if you called some software vendor's support hotline, the moment you let it slip that you are running something that is not Windows, they would start laughing and hang up on you.

There are scenarios where I would consider a Windows 10-compatible ReactOS at work - e.g. for reviving a PC where the "native" Windows version has gone out of support, and it only needs to run MS Office or Windows' RDP client, or a browser. But in the five years I have worked as Windows admin, this has happened so rarely I doubt it would matter a lot.

If the project got to the point where ISV's support hotlines did not care whether you are running MS Windows or ReactOS, ... that would change things in a big way.


I feel like I should launch it in a VM and start using it for some of my Windows tasks just to see if I can. I wonder if it can run WebEx..


I would assume you can run WebEx because ReactOS says they have 100% binary compatibility with Windows.

What you’d need to run any Windows program is a way to parse the PE executable format, load it into memory, and emulate or simulate W32 api calls. I’m sure there are other steps but I can’t think of many more off the top of my head.


Well, for that you just use WINE. ReactOS goes a lot further.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: