Hacker News Reader

Comment by torstenvl | Hacker News Reader

I'd love to try this out, but any attempts at booting in a VM fail with an error that it's unable to open txtsetup.sif. I've tried pre-formatting the drive as FAT32, FAT16, with and without FreeDOS installed, nothing. I tried the 0.4.14 release as well as recent 0.4.15-dev ISOs, to no avail.

This has apparently been an issue for a while, and is a regression.

https://jira.reactos.org/browse/CORE-9057 https://jira.reactos.org/browse/CORE-16043 https://jira.reactos.org/browse/CORE-18227 https://jira.reactos.org/browse/CORE-17818

The latest version I can get to boot is reactos-bootcd-0.4.13-dev-1080-g4843c1a-x86-gcc-lin-dbg.7z available at https://iso.reactos.org/bootcd/reactos-bootcd-0.4.13-dev-108...

The fact that this regression has been dismissed with "Works on my machine!" is deeply troubling. I can't foresee trusting anything to ReactOS.

View on HN

I just tried compiling newest Qemu from Qemu git repo, and newest ReactOS 32bit nightly, it works great with networking support, with these instructions that work for any Debian or Ubuntu based Linux on any CPU:

https://github.com/AsahiLinux/docs/wiki/SW%3AUbuntu-Asahi-Qe...

As well, you do not describe the exact sequence of actions that leads you to the error. Without it, you cannot be helped.

You also provide a list of bug reports that are just similar, but probably not related to your particular issue.

> not related to your particular issue

That's extremely unlikely and it's concerning that you think the exact same error at the exact same point starting after the exact same last-known good build is "not related." If that's a possible failure mode of your code base then your code base is pure shit.

This problem is very rare. It is very hard to encounter it, unless you have some very specific conditions.

You said nothing about the version and name of VM you are using.

As well, you do not describe the exact sequence of actions that leads you to the error. Without it, you cannot be helped.

> you cannot be helped

I'm not the one who needs help. Your software is.

I linked to several detailed bug reports and told you very clearly that I had the "exact same" problem. It is not encouraging that you won't even read the bug reports, and certainly doesn't encourage anyone to further help you.

I really don't understand your childish behavior. You flaunt your unwillingness to cooperate, as revenge for the offense allegedly inflicted on you by someone. This is stupid and naive. There is nothing difficult about naming your version of the Virtual Machine.

The error "Failed to open txtsetup.sif" can theoretically pop up for a million reasons\scenarios, and even fixing all of them may not help in your particular case, without providing information from you.

However, this error is extremely rare. Developers can't fix a bug that they can't reproduce. Therefore, extra efforts are needed to catch, eliminate or bypass it.

Hysterical insults on volunteer developers of a free open source project are not the best example of interaction.

You said nothing about the version and name of VM you are using.

Reply on news.ycombinator.com