Back to Website

How did you know about ReactOS?

If it doesn't fit anywhere else, drop it in here. (not to be used as a chat/nonsense section)

Moderator: Moderator Team

Re: How did you know about ReactOS?

Postby milon » Mon Oct 30, 2017 6:52 pm

Fraizeraust wrote:@Michael Long: An OS is a digital software, it is entirely impossible to damage your hardware physically...


It's actually NOT impossible for software to damage hardware. It has happened before - never related to ReactOS as far as I know - but it's incorrect to say it's impossible. (For example, https://www.computerworld.com/article/2 ... -bugs.html)

Having said that, it's unlikely in the extreme that any use of ReactOS would result in physical harm to the hardware involved. When it comes to real hardware testing with ReactOS, I would pretty much expect to see data corruption, but nothing worse than that. When I test on real hardware, I physically disconnect my 2 main HDD's first to prevent exactly that.
milon
 
Posts: 923
Joined: Sat Sep 05, 2009 9:26 pm

Re: How did you know about ReactOS?

Postby Michael Long » Mon Oct 30, 2017 9:02 pm

Thank you.

Yes, I already had a case where a hard disc of mine was meant to run at 7.200 rpm. It did so for hours but suddenly it was spinning up like there was no limit. Luckily I was sitting right next to it and pulled the power plug fast enough otherwise the motor would have overheated. After switching the computer on again everything was back to normal. But I was using Windows back in then. Very very strange bug. I can't say if it was a software bug but in general the software controls the hardware. I think it's also possible for the software to lower or raise some voltage levels (like CPU core voltage and memory voltage). Just a wrong value in certain areas of the memory and the computer can go up in flames (if I remember correctly some functions of the x86 architecture are memory mapped).

Anyway, sorry for the off topic discussion.
Michael Long
 
Posts: 36
Joined: Wed Oct 25, 2017 7:51 pm

Re: How did you know about ReactOS?

Postby val » Mon Oct 30, 2017 9:53 pm

Of course software could damage hardware. How did you forget about overclocking? As Michael mentioned - raising voltages too high could damage related modules. OC requires overvoltage. There is "dangerous" hardware parts like CRT monitors, impropoer configuring the underlying VGA controllers could make those collapse.
Or making constant program erase cycles on the same erase block for NAND (NOR) flash devices. I am sure there are yet examples.
val
 
Posts: 52
Joined: Fri Feb 10, 2017 5:22 am

Re: How did you know about ReactOS?

Postby PurpleGurl » Tue Oct 31, 2017 2:08 am

Using ROS on real hardware caused the cat in the backyard to have a litter of puppies that are not sure whether to bark or meow. ;-)

I learned about ROS maybe 8 years ago or so. I had the notion that maybe there were 3rd party DLL solutions that did the job faster or better. But I couldn't find faster alternatives to Windows components, but I did find ROS. That was like a dream, a free version of Windows that you could use without it expiring, and you could legally modify it if you wanted. Sadly, while loads of work have been done since then, not many more machines can run it than then without emulation. Notable things since then have been mouse/keyboard fixes, ATA/SATA driver fixes, sound improvements, a new explorer, limited NTFS support, and many graphical fixes.

Several attempts have been made to fix USB support, and it still isn't stable for everyone. There were changes made in last year's GSOC, but not sure if all were merged, and there is more work needed for the legacy USB drivers. Yes, someone is working on 3.x support. While that is needed for 3.x ports, and while it supports all common modes, it will, AFAIK only help 3.x sockets. The legacy mode support is limited to that which can be done on 3.x devices. That means that other sockets still need the other 2-3 drivers. The 2.x support for 2.x ports does not help 3.x at all, and vice-versa, with the 2.x mode of a 3.x driver not being of use to a native 2.x port. I know that because on machines I've used with 3.x support, the sockets are often "dead" if there is no 3.x driver, while the 1.x/2.x sockets work with the Windows driver. So the 3.x driver was started as a courtesy for those with 3.x on their machines, not to replace 2.x or even 1.x. The rationale is that if modern machines with 3.x ports don't have XP or 2003 drivers, then we should provide them.

On the hardware thing, I will add some things. Hard drives do have some programmable registers and memory locations, like the acoustic dampening level. And old IDE drives did not block low level formatting attempts, even though IDEs cannot be successfully low-leveled by end users. So you'd erase the "servo" markers, and the drive would be unable to find it's platter addresses, thus bricking the drive. Or, with a few that might succeed at this, they might reformat to a lower capacity. Later IDEs (and SATA) intercept low-level formatting attempts and treat them as simple data clearing requests. So issuing low-level formatting commands will not attempt to rewrite their sector boundaries.
PurpleGurl
 
Posts: 1502
Joined: Fri Aug 07, 2009 5:11 am
Location: USA

Previous

Return to Off Topic

Who is online

Users browsing this forum: No registered users and 1 guest