I know that there is always a chance that the os can do perminate damage.
(I beleave that even the stable linux kernel had a problem with distroing(killing) some cd-rom drives( Please dot quote me on that I not 100% sure)) but
My question is how likely is it to wreck my hardware in it current state. I download it and compiled it but the fact that reactos is pre-alpa worry's me. I would really like to run it just to see how far you come but don't want to wreck anything.
dose it use stable lib of someone elses work or is all of reactos in the alpa state. Buy just looking over the form it almost look like you using some of linux code for the drivers.
How likely is that reactos will do perminit damage
Moderator: Moderator Team
Now if you cannot risk your hardware their is a reason why reactos is provided with QEMU images. Use the qemu it will protect you machine from harm reactos will run slower but its safe.
One of the Stable Linux kernels had the problem that some dvd/cd rom drives did not follow spec. The result was a block of incorrect data written to the flash of the drive. Drive did not work due to stuffed flash. If you had a makers fix program or know where to plug into the drive or remove the flash all of those drives were recoverable. They were not damaged but disabled due to a bad flash same thing would happen with a power failing while flashing. Most of those makers provided linux people with replacement. It was their fault for not obeying spec.
Very quickly fixed. Using any old os ie Windows 3.11 with a old driver ran the same risk.
It Alpha not a nuke. Risks are quite a few. Video cards getting overclocked not likely due to standard Vesa Interface being used.
Most problems will be with hardware reactos indentify but contations a strange alteration from the interface spec reactos is using. Note even Windows suffers this from time to time it just get swept under the carpet.
Ok next bigest risk is filesystem damage due to reactos crashing at the wrong time. Really Windows XP is able to do that too but not as often as reactos. Most important is to have a backup.
Alpha is a risk always is. Most of the core driver parts have not been tested for 12 months and against a broad range of hardware to make sure its right.
One of the Stable Linux kernels had the problem that some dvd/cd rom drives did not follow spec. The result was a block of incorrect data written to the flash of the drive. Drive did not work due to stuffed flash. If you had a makers fix program or know where to plug into the drive or remove the flash all of those drives were recoverable. They were not damaged but disabled due to a bad flash same thing would happen with a power failing while flashing. Most of those makers provided linux people with replacement. It was their fault for not obeying spec.
Very quickly fixed. Using any old os ie Windows 3.11 with a old driver ran the same risk.
It Alpha not a nuke. Risks are quite a few. Video cards getting overclocked not likely due to standard Vesa Interface being used.
Most problems will be with hardware reactos indentify but contations a strange alteration from the interface spec reactos is using. Note even Windows suffers this from time to time it just get swept under the carpet.
Ok next bigest risk is filesystem damage due to reactos crashing at the wrong time. Really Windows XP is able to do that too but not as often as reactos. Most important is to have a backup.
Alpha is a risk always is. Most of the core driver parts have not been tested for 12 months and against a broad range of hardware to make sure its right.
Re: How likely is that reactos will do perminit damage
We changed the text from "pre-alpha" to "alpha" on the website frontpage. It's not easy to sum-up the current state, but we believe that "alpha" reflect the current status best.frog-o wrote:[...] but the fact that reactos is pre-alpa worry's me. I would really like to run it [...]
You can download a VMware player or QEMU image and test ReactOS.
If shit happens on a dual boot system
If something happens on a dual boot system (windows or dos) there are two things that can fix most problems:
1.) Restore MBR by running the "FDISK /mbr" from a boot disk
2.) Restore the boot files by using the "SYS C:" command from the system boot floppy.
After this you can delete all ROS files from the DOS-prompt.
If you can not re-install ROS you can probably just delete the files in C:\ReactOS\System32\Config directory and you should be able to get a working system up n' running.
1.) Restore MBR by running the "FDISK /mbr" from a boot disk
2.) Restore the boot files by using the "SYS C:" command from the system boot floppy.
After this you can delete all ROS files from the DOS-prompt.
If you can not re-install ROS you can probably just delete the files in C:\ReactOS\System32\Config directory and you should be able to get a working system up n' running.
How likely is that reactos will do perminit damage
i think you mean Permanent damageI know that there is always a chance that the os can do perminate damage.
time to run that spellchecker

permanent damage to what.. your nerves? or... (?)
it's not very likely that an OS will do physical damage to hardware
however a user may do damage if they unleash their fustrations by getting medieaval with peripherals

-
- Posts: 167
- Joined: Sat Oct 01, 2005 1:48 am
- Location: United States
Who is online
Users browsing this forum: No registered users and 1 guest