ReactOS Forum

I have a Qubes OS (Xen virtualization system derivative) system and was previously disappointed that I could not get React OS to install years ago, but just now actually got it to install and run!! I was excited because I really did want to play with it to see how far you have come over the years. So far so good... so I thought.

Then I tried to run Applications Manager hoping to install something like a browser so that I could start migrating tools and applications to see how it does, only clicking on Application Manager from the desktop link or the menu (Control Manager -> Add or remove Programs) completely freezes the system. I have to forcibly kill the VM and this of course destroys all the logs because there is no persistence saved from that run. Event manager and all other apps seem to run but there is nothing in the Application or Security events and I'm not sure where else I could look to figure this out without some kind of persistence for any logs.

Anyone have a clue what might be going on here? Is there any way to watch the system logs in real-time to see what might have happened just before the VM freezes?
thanks,
Steve C

Edit: I tried running it with the "Screen" option and while it didn't ever show the desktop it continually showed a line which looks like it's trying to load something for the ARM architecture, and obviously failing. I'm not sure what this could have to do with Application Manager unless that specific app is getting confused as to what architecture to load applications for.

I found the problem! There is an IP address assigned to the VM running React OS but the configuration does not pick this information up. Once I found the place to put the IP address, network mask, and gateway then the Application Manager could run rather than crashing the entire VM. Why would trying to access the network crash the OS?

Note to developers: There is obviously a IP validity check needed to be sure that a valid IP exists before calling some networking method. I don't know what method in the Application Manager causes this specific error, but one of the developers might have a clue.

In the mean time I am up and running and testing things. It appears that most current versions of windows software is unsupported simply because of the version reported by the OS. I know with Wine you can trick the software by having the runtime report a different OS version. Is this possible on React OS? Just getting past the install would be the first step to making this platform more useful.

Thanks for all your hard work!