Live data from Hacker News

ReactOS 0.4.16

reactos.org

41–48 of 48 posts

Re: ReactOS 0.4.16

#43
post #19

Earlier quoted context omitted.

It's not only that it was text based, but that it failed in all sorts of ways. I had a particularly bad afternoon in early 2000s when I tried to install Linux on various machines (4 or 5, each one with different hardware) and failed with all of them. Of course, I wasn't as savvy as I am now, but it's been years since I've seen an issue with a Linux install; although I might have to download and compile a driver for o…

Mine was in the 90s and concerned X11 failing or crashing due to the video card typically. Redhat 5.2ish or Suse.

Same with me - late 90s. Celeron 366Mz, 64 MB RAM, 4.3 GB HDD. Don't remember the video card and the sound card. Used to stay up all night to try and fix X11. And once you got it running - victory !!!

Re: ReactOS 0.4.16

#44
After the news about the Start Menu, the name briefly had me convinced someone actually rebuilt all of Windows in React Native.

Re: ReactOS 0.4.16

#45
post #38

> a new DC21X4 network adapter driver Hasn't the point been for the OS to be compatible with the existing Windows drivers?

Yes, but native open-source drivers are needed for out-of-the-box support, legal compliance, and debugging missing kernel/NDIS APIs during development.

Re: ReactOS 0.4.16

#46
post #29

I do a lot of industrial automation and it is the one thing that keeps me boat-anchored to Windows. Every little programmable doodad like signal conditioners and temperature transmitters have their own USB programming cables and their own, mostly crappy windows config software. PLC software is another abomination, hopelessly Windows anchored, bloated GUI monsters, some built on top of Visual Studio (Beckhoff TwinCAT.…

You can forward USB devices into a VM. About 15 years ago I was using a Windows VM on Linux to program PIC18F??? devices with the custom (JTAG based?) programmer provided by Microchip. The upside is that you can preserve and share this windows environment for other coworkers, and have separate VMs for different projects (perhaps one you can update, and one you can't ...)

This is exactly what I do currently but it's flaky. Bekhoff installs a runtime on the development PC that works its way deep into the system that can and does crash the VM. Some USB devices work, some don't, some are buggy and may hang or fail in the middle of programming. I have to keep a dedicated Win PC just to make sure I have a working Winstall for my work. I keep VM's of 2k, XP, and 7 as I have to maintain a wide variety of hardware and software. I just want off the Windows upgrade treadmill.
Post reply on HN