Any ReactOS users here?
-
@Tsaukpaetra said in Any ReactOS users here?:
it's getting late
I.... think I broke it.
Oh well!
@Onyx said in Any ReactOS users here?:
.NET stuff does work in Wine, after a fashion
Yeah, that's what I was trying to get working. Apparently the mono wine installer thingy never shows up, but does things silently (can't tell, can't find logs before it crashes the disk). Now I'm stuck with a missing shell (I think) or something that doesn't even let me bring up Task Manager.
-
@error said in Any ReactOS users here?:
retty sure he was going for a Usenet reference.
Still better than Discourse.
-
@antiquarian said in Any ReactOS users here?:
@error said in Any ReactOS users here?:
retty sure he was going for a Usenet reference.
Still better than Discourse.
Then again, those turn of the century community hosts are better than Discourse.
-
@dkf said in Any ReactOS users here?:
Why? Servers tend to not be the ones running physics engines or UIs. Without those tasks, the main jobs become communications, state management and persistence, and those aren't the sorts of loads typically associated with GPUs.
GPUs are really good at massive parallelization, and using them for processing lots of events happening sounds like a good idea to me.
-
@Adynathos said in Any ReactOS users here?:
Maybe it could be used for physics... Nvidia's PhysX for example, but I don't think it is used in servers.
Even if you can simulate a big number of physical bodies - you can't send all that data through network.You literally have to do all your physics calculations on the server and synchronize positions. Clients do physics, but only predictively so that games feel responsive.
-
@Magus said in Any ReactOS users here?:
You literally have to do all your physics calculations on the server and synchronize positions. Clients do physics, but only predictively so that games feel responsive.
The number of physical objects that matter in a game (players, projectiles) is rather small and you can synchronize their state through network + their physics are cheap, so I don't think they would use GPU for that. Also there is a delay on getting data back from GPU.
But clients can do their own physics for decorative objects that are not replicated - like sparks in a particle effect, or if an explosion spawns shards flying around - you can do that on GPU and probably even tell the GPU to move the particles on its own.
-
@PleegWat said in Any ReactOS users here?:
Hm, no branching at all? Does it have conditional execution of instructions?
It does, sort of - when branching occurs, the cores that don't enter the branch stop execution and resume when other cores are done with branch. Alternatively, all the code executes on all the cores regardless of conditions, but results of instructions that "shouldn't" be executed are discarded. Don't know which is closer to actual implementation.
-
@Tsaukpaetra said in Any ReactOS users here?:
@Tsaukpaetra said in Any ReactOS users here?:
it's getting late
I.... think I broke it.
Oh well!
Wow, what a wonderful... recovery... shell?
-
@dkf said in Any ReactOS users here?:
I'm not 100% sure, nor even as much as 75% sure, but I think what you do is compute the values that you need and conditionally merge them without a branch
At least until some time ago this was the sole option. Later on there was some limited branching (though the core that took the longest determined throughput IIRC). I have heard nowadays the scheduling has become more flexible, but branches incur penalties still.
Btw. in some cases conditional merging without branches can be more efficient on the CPU as well. (Not only with SSE/AVX.) The time it takes for the pipeline to flush can easily accommodate quite a few instructions. Depends on how well the CPU can predict the branch, though.
-
@Tsaukpaetra said in Any ReactOS users here?:
@Onyx said in Any ReactOS users here?:
.NET stuff does work in Wine, after a fashion
Yeah, that's what I was trying to get working. Apparently the mono wine installer thingy never shows up, but does things silently (can't tell, can't find logs before it crashes the disk). Now I'm stuck with a missing shell (I think) or something that doesn't even let me bring up Task Manager.
Okay, I managed to install Xibo, and navigate through the config dialog well enough to set the proper settings. But starting it, I got a wonderful BSOD:
Resetting the machine got me:
Screenclip:
Not yet!
-
@Tsaukpaetra said in Any ReactOS users here?:
Now I'm stuck with a
It is so easy to fuck the system up... :(
-
@Tsaukpaetra said in Any ReactOS users here?:
@Tsaukpaetra said in Any ReactOS users here?:
Now I'm stuck with a
It is so easy to fuck the system up... :(
FFS!!!!
I give up.
-
@Magus said in Any ReactOS users here?:
GPUs are really good at massive parallelization, and using them for processing lots of events happening sounds like a good idea to me.
Only if you can do essentially the same thing at the same time on those lots of parallel threads. A large fraction of what the server will be doing is messier than that (hey, that's I/O for you!) and just better suited to being done with lots of normal CPU cores. It's a SIMD vs MIMD distinction.
-
@Tsaukpaetra said in Any ReactOS users here?:
[insert outdated joke about how it perfectly emulates windows]
-
@lucas1 said in Any ReactOS users here?:
React os win32 compatibility is about 15 years out of date. You are better using wine or a vm.
And I suspect 15 years in the future it will become very popular. There's a huge amount of Windows software that's not going to disappear, and Microsoft seems less and less interested in maintaining compatibility with it, so we will need alternative implementations sooner or later. Same thing that's going to happen with Flash.
-
@XanderTheGamer said in Any ReactOS users here?:
@antiquarian said in Any ReactOS users here?:
@error said in Any ReactOS users here?:
retty sure he was going for a Usenet reference.
Still better than Discourse.
Then again, those turn of the century community hosts are better than Discourse.
So were Fido echoes over 1200 baud modems.
-
@ScholRLEA said in Any ReactOS users here?:
So were Fido echoes over 1200 baud modems.
And X11 sessions over 14400 baud modems.
Provided you avoided Framemaker, which ran incredibly slowly.
-
This post is deleted!
-
@dkf said in Any ReactOS users here?:
@ScholRLEA said in Any ReactOS users here?:
So were Fido echoes over 1200 baud modems.
And X11 sessions over 14400 baud modems.
Provided you avoided Framemaker, which ran incredibly slowly.
So was dialing BBSes over a C64 VIC modem.
-
@XanderTheGamer Anyone want to bid 'ASR-33 connected to a remote mainframe'? How about 'smoke signals'? Going once, going twice...
-
Alrighty, got a bit of an update. Turns out if I tell VMware I'm going to use Windows XP 32-bit, instead of "Unknown OS", ReactOS will install. I got it installed however it doesn't have a built-in E1000 NIC driver . This is really weird because the VMware guest tools for XP install just fine in ReactOS and do a reasonable job of mouse/keyboard capture, but without installing the NIC driver.
Other issue is the OS appears to be 32-bit only, which is a concern because I was hoping to host a Space Engineers dedicated server from it and Space Engineers loves RAM.
I'm trying to figure out the NIC thing, if all goes well I'll have more to report later.
-
@mott555 said in Any ReactOS users here?:
Other issue is the OS appears to be 32-bit only, which is a concern because I was hoping to host a Space Engineers dedicated server from it and Space Engineers loves RAM.
No, that can't be right - what's your source of info? The amd64 port was merged into trunk a long time ago.
-
@LoneRifle I don't know that for sure, it was trial-and-error with the VMware settings. If I chose a 64-bit OS in the VM settings, ReactOS wouldn't install. If I told it 32-bit, then it installed. I know this option doesn't really change the emulated architecture, so it's probably just some emulation quirk.
That gives me an idea, I was installing the 32-bit VMware tools. I should try 64-bit and see if that fixes my NIC issue.
EDIT: Nope.
ERROR_BAD_EXE_FORMAT - D:\setup64.exe is not a valid Win32 application.
-
@ScholRLEA said in Any ReactOS users here?:
@XanderTheGamer Anyone want to bid 'ASR-33 connected to a remote mainframe'? How about 'smoke signals'? Going once, going twice...
Walking to the other person's house to say "loved that post" is better than Discourse. Even if you're barefoot and you have to cross an ocean to get there.