Page 1 of 1

ReactOS self corrupts after going through setup boot

Posted: Fri May 17, 2019 1:05 pm
by Reactions
Hi all,
I have tried installing ReactOS multiple times with the newer nightly builds and am having issues getting it to not self corrupt on Real Hardware. I have noticed the issue getting progressively more severe no matter what storage device I use over the past releases. Should I go to Jira?

Re: ReactOS self corrupts after going through setup boot

Posted: Fri May 17, 2019 2:07 pm
by mrmajik45
Are you using Fat32 or BTRFS for the partition?

Re: ReactOS self corrupts after going through setup boot

Posted: Fri May 17, 2019 2:10 pm
by Reactions
mrmajik45 wrote: Fri May 17, 2019 2:07 pm Are you using Fat32 or BTRFS for the partition?
Fat32 and I have tried BTRFS

Re: ReactOS self corrupts after going through setup boot

Posted: Fri May 17, 2019 3:19 pm
by mrmajik45
Well if you can get a debug log of what it is complaining about then sure, go to jira.

Re: ReactOS self corrupts after going through setup boot

Posted: Fri May 17, 2019 4:05 pm
by Reactions
Ok sounds good. Thanks!

Re: ReactOS self corrupts after going through setup boot

Posted: Sun May 19, 2019 3:20 am
by middings
Reactions wrote: Fri May 17, 2019 1:05 pmI have tried installing ReactOS multiple times... and am having issues getting it to not self corrupt on Real Hardware. ... Should I go to Jira?
Before you create a formal issue in JIRA, try discussing your problem here in the Support forum. If you start an issue in JIRA, you'll be expected to do all the following steps (but much more rigorously) anyway.
  • Begin by searching for an existing report on the problem. If reporting a suspected bug in the Support forum, search the Support forum. If using JIRA, search JIRA.
  • Give your new JIRA issue or new Support forum topic a short, specific title. Avoid cluttering the title with "ReactOS" or such phrases as "ReactOS won't". They are redundant because if you're not using ReactOS then why are you here? Just mention the application or feature that misbehaves and the misbehavior seen. Think about the search terms someone else who later encounters the same problem might use and use at least one of them in your title.
  • Describe what you are doing in enough detail that someone else could reproduce what you are doing.
  • Name the exact build of ReactOS that you have tried.
  • Name the manufacturer, model name, and model number of your PC's hardware. Supply a link to the manufacturer's web page that describes your PC's specifications, if available. (If your PC is a white box, supply equivalent information about the manufacturer and model of its motherboard.) Identify the amount of RAM and type of mass storage installed. (Users of a virtual machine [VM] should supply equivalent information about their VM, its version, and its configuration.)
  • Describe how you chose to format your mass storage (hard disk) on the PC you installed ReactOS on, FAT32, BTRFS, or NTFS. (NTFS is no good at this time but some people plunge ahead anyway). If you are using multiple partitions, describe all the partitions.
  • Describe how you Atried installing ReactOS. (Burning an .iso file to a CD-ROM then booting from a CD-ROM drive on an IDE or SATA connection remains the surest route to success at this time. Sorry about that, USB drive users.) If you are using a multi-boot scheme, describe how you configured it and the software tool (name, version, and web link to where it can be obtained) you used.
  • If you are using any application with ReactOS, please give its name, version ID, and the web link where it can be obtained.
  • If you reporting a fault in an application running under ReactOS, verify that the same fault does not occur in ReactOS's implementation compatibility target, (at this time) Microsoft Windows Server 2003. If you do not have Server 2003 available, check the application with Microsoft Windows XP SP3. Please give the application's name, version ID, and the web link where it can be obtained. (If the application is not freely available on the web, then the reporter may be asked to supply legal copies of the application to ReactOS's development team at the reporter's own expense.)
  • Try to reduce your actions that lead to the corruption you encountered to the fewest and simplest steps possible. This is called 'reducing the problem' or 'reduction'.*
  • Describe what you expected to occur then describe what actually occurred.
See also these ReactOS-specific bug hunting and reporting tip sheet here. Only pay attention to the first post in the topic. The information (vicmarcal?) provided has become a bit outdated but it is still useful. Maybe I'll Wiki-fy and update it someday but everybody else here in these ReactOS forums is welcome to jump the queue, do it first, and receive the credit.

Additional general bug reporting tips are available here (short and gentle), here (still gentle but long), here (firm and about a single kind of poor bug report), here (firm and about another kind of poor bug report), here (very harsh and very comprehensive in its catalog of common bug report shortcomings). For those who prefer learning from negative examples of the sort seen in the book How To Lie With Statistics,** look here.

* Microsoft's Raymond Chen reported in his blog The Old New Thing, "Reduction is so important that our defect tracking database has a special field: Reduced by."

** recommended

Re: ReactOS self corrupts after going through setup boot

Posted: Sun May 19, 2019 6:21 am
by Reactions
Ok, thanks!