And why do you keep deleting your messages?

You do realise you're expecting people to put significant effort into something that would be zero use for almost anyone at all (less than 0.0001%) and that would significantly detract from what is useful for the majority (more than 50%)

That's not sensible or sane

that's just foolish

take your old Pentium 1 box to the recycling center

Not just that, but there needs to be a cut-off point going backward.

That manufactured within the past 5 years

Also, you mean "what kind of hardware do most people use"

"What kind of hardware use most people?" lol sounds like a Russian reversal joke

In America, you watch television, in Soviet Union, television watches YOU!!

"Does ReactOS have support for symmetric multiprocessing?"

And the answer is "I don't know"

I'm finding forum posts from 8-10 years ago suggesting it does not

however, that's quite a long time ago

CD-ROM drives became ubuiquitus (present on over 97% of shipping systems) by 1997.

What about nettops and tablets?

What about nettops and tablets?

The only tablet I've seen that did not support USB booting was from 2002, and it had an integrated CD-ROM drive.

CD ROM is not common on them. USB is needed

CD ROM is not common on them. USB is needed

Yes, but again, almost all of the ones you encounter have native USB booting support. Just use Rufus and quit worrying about using hacks like PLoP

and since Rufus exists, there's absolutely zero reason for ReactOS to add it's own media creation tool.

No, never

What you're suggesting will lead to a very very bad thing

https://en.wikipedia.org/wiki/Feature_creep

unnecessary integrated functionality

If you're that desperate into integrating that kind of functionality into ReactOS, why not just include Rufus itself into the ISO and call it a day?

Or, more sensibily, just include Rufus alongside the ISO for people that need it

which is exactly the same route Microsoft takes with their Media Creation Tool

I have no idea, I don't go testing random software in ReactOS to see if it works or not. That's for someone who wants to spend the time doing that to go do.

account?

You do realise I'm not a member of the ReactOS project, yes?

I'm another user, just like you.

Jira is for bug/unit testing

not application testing

that would be something else, akin to the Wine AppDB

And ReactOS doesn't (to the best of my knowledge) maintain any such compatibility database

So as far as I know, there's absolutely nowhere for you to send in app testing results

I guess you could always make posts on the forum

but that's extremely ad hoc and disorganised

Well, you can always search the chat's backlog to see if someone's messaged this chat

what am i reading

we used to have a compatibility database

website upgrades some years ago removed it

we still haven't found someone to implement and manage a suitable replacement

it wouldn't be easy, either. it would have to have good security, and tools for preventing and managing spam

my personal thoughts on that are that whoever does it should probably be an experienced web developer, and it should probably be built on top of some existing (well-tested and actively maintained) collaboration framework

and I believe if someone were to decide to work on that, it would be best to develop it independently, and then present it to the team once it becomes something usable

but it would be best to talk to the proper people before starting such a thing, just in case the thoughts of the team differ from mine

Let's write it in go and MISC assembly

Seems perfect

my personal thoughts on that are that whoever does it should probably be an experienced web developer, and it should probably be built on top of some existing (well-tested and actively maintained) collaboration framework

I am a web dev with 2-3 years of experience

Well then, get crackin'

I will try To implement a database

On a repo of github

I will try To implement a database

If you get a live system, let me know, I might play with it.

jimtabor (https://jira.reactos.org/secure/ViewProfile.jspa?name=jimtabor) resolved CORE-11979 - Handling WM_ACTIVATE for dialog boxes is half-broken as 'Fixed' https://jira.reactos.org/browse/CORE-11979 This is now fixed!

Amine Khaldi (https://jira.reactos.org/secure/ViewProfile.jspa?name=aminekhaldi) resolved CORE-11993 - [PATCH] Fix all testIcmpSendEcho tests in iphlpapi as 'Fixed' https://jira.reactos.org/browse/CORE-11993 Committed in r72759. Cheers.

Mark Jansen (https://jira.reactos.org/secure/ViewProfile.jspa?name=learn_more) resolved CORE-12016 - Fix some tests in the com test as 'Fixed' https://jira.reactos.org/browse/CORE-12016

Why do you keep spamming links?

i guess when its ready...

Amine Khaldi (https://jira.reactos.org/secure/ViewProfile.jspa?name=aminekhaldi) resolved CORE-10573 - Rewrite of ping as 'Fixed' https://jira.reactos.org/browse/CORE-10573 Committed in r72765. Thanks!

😭

Estimating when reactos will be done is just simply not possible

10 years ago, when the project was on early 0.3, probably no one thought it would take 10 years to reach 0.4

so how long to 0.5? well it can be 2 years, or 5, or 25

The team must get more new contributors to realize the dreams of ReactOS

And or new members to help 'em

They could borrow some people from the Wine Dev Team

Sergey Stopkin (https://jira.reactos.org/secure/ViewProfile.jspa?name=serg_st) resolved ROSAPPS-334 - TRANSLATION: Russian translation update as 'Duplicate' https://jira.reactos.org/browse/ROSAPPS-334 wrong repo

so how long to 0.5? well it can be 2 years, or 5, or 25

1 year

And yes i have estimation marker

Lol no it's not going to be done in one year, not even close XD

Nope

i have collected all open bugs at the moment of 14 feb of 2015

I my guess was that all important bugs that prevents 1.0 to be happen are reported. All new bugs after thsi moment are for 2.0+

there were 1654 open bugs

now only 1004 are still open

one year and a half has passed, and 1/3 of bugs were resolved

so we need only 3 years more till release of 1.0

kek

❤

kek kek <-- this one kek kek kek