Page 1 of 1
Compatibility database?
Posted: Sat Mar 21, 2009 9:39 am
by RaptorEmperor
Is the compatibility database being maintained? I see new compatibility reports being filed but I had trouble finding it without searching the website. The reason I'm asking is that I have ReactOS installed on my testbed computer and I don't want to spend time submitting compatibility reports if it's a deprecated part of the website. If compatibility testing is still an active part of development then it should be a bit easier to find on the website.
By the way, I submitted a compatibility report for The Sims, though I'm not sure if I did it right.
Re: Compatibility database?
Posted: Sat Mar 21, 2009 10:21 am
by Lone_Rifle
it's deprecated, but i suppose some people still use it for reference.
Re: Compatibility database?
Posted: Sat Mar 21, 2009 10:41 am
by vicmarcal
I thought that CompData was deprecated too, and i said that in IRC,Fireball answered that Database isnt deprecated... maybe he misunderstood me...or i misundertood his answer...but... i sometimes send reports to the CompData.
About The Sims:
-Seems nice report, but if you find a bug..(the demo installer doesnt work//wrong colours)..you should create a bugzilla report...
As you have tried to install Sims at 0.3.8, and since the release date we have improved a lot the graphics, i recommend you to retest against head revision in order to check the wrong colours bug before sending the bugzilla report..
-Are you trying to run the Sims from an original CD or a "back-up" cd?Maybe the autorun doesnt work because the Driver protection. Please test a backup cd...(if you have the original of course).Test against 0.3.8 and head please. if still doesnt work then make a bugzilla report
witn an attached log.thanks
Re: Compatibility database?
Posted: Sat Mar 21, 2009 1:48 pm
by Black_Fox
It seems Dangerground may eventually find some time to rework it... it would be nice in something more AppDB-like, with HOWTO guides to make programs work, cross-linking with Bugzilla entries etc.
Re: Compatibility database?
Posted: Sat Mar 21, 2009 2:49 pm
by Haos
I agree, it needs some polish and optimization, for data input not to take so darn long.
Re: Compatibility database?
Posted: Sat Mar 21, 2009 5:36 pm
by vicmarcal
Agree.. adding an App is a Pain ...i think that is preventing people add(or update) the DataBase.
A really good option would be doing possible that "Bugzilla connection";
So a Bug in Bugzilla could point to an App in our Database App..it will help to have the DataBase more updated and also more useful.
Maybe each App in the Database App could have a section of Bugs..fulfilling it would fulfill a Bugzilla Bugreport, and when closing a Bug as Fixed in Bugzilla will delete that Bug in the App..so in that way the AppDatabase could evaluate (with the Stars) itself.
Re: Compatibility database?
Posted: Sun Mar 22, 2009 7:45 pm
by DangerGround
I already working on it. But it will take some time.
Re: Compatibility database?
Posted: Sun Mar 22, 2009 8:01 pm
by vicmarcal
nice Dangerground
thanks for your work
Re: Compatibility database?
Posted: Fri Mar 27, 2009 7:02 pm
by RaptorEmperor
It's nice to hear the compatibility database isn't deprecated. I can't code for crap, so it's one of the few ways I can contribute. Thanks for the info!
Re: Compatibility database?
Posted: Thu Jul 09, 2009 11:43 pm
by MadWolf
hi
can you add the ability to report incorrect Vendor info for example Steam and
http://www.reactos.org/support/index.ph ... group/145/ the vendor info is incorrect the Vendor is not Sierra but is Valve
http://www.reactos.org/support/index.ph ... group/289/ and the ability to clean
Re: Compatibility database?
Posted: Fri Jul 10, 2009 10:06 am
by hefner
maybe a edit - function would help
Re: Compatibility database?
Posted: Fri Jul 10, 2009 10:17 am
by DangerGround
fixed manually
Re: Compatibility database?
Posted: Thu Aug 06, 2009 8:50 am
by forart
As
already asked before, a "more objective" compatibility database would be mutch more useful (and not only for ROS).
I believe that a user's log reported by a System information tool loaded into a "matrix" could help mutch more to hunt bugs (for exampe different users with similar machines but different bios or drivers versions, same chipset with different graphic boards, etc) than a personal (and often inaccurate) submission.
A freedos-based disk/usb image with a reporting tool that writes the log would be good just for hardware, but it would be interesting to have an integrated tool that (after user permission) automatically uploads the detailed machine specs into the official database.
EDIT: seems that someone else had a similar idea, called
Pootypedia
Pootypedia is a software that helps you track hardware among your users. Typically you install the server part, configure the client part, and distribute it to all people who are willing to report their hardware and software configuration to you. The program is made available, free of charge, under the GNU Public License (GPL).
The typical user of Pootypedia would be a software project which wants to know about the hardware that its users install the software on. Names that come to mind are Fedora, Debian, SuSE, and other Unix like systems. The hardware probing is done through kudzu, a fine hardware detection program already known to run on a variety of hardware. In order to port pootypedia's client to another architecture, you need to ensure that kudzu runs on it, and that you have some way of finding out the other essentials on the machine, the CPU, the memory, and a list of software (with version numbers) installed on that machine. The server end doesn't much care where the client is running, as far as the client is capable of doing an HTTP POST, to send the report file over. The report file is in XML, and can be generated and stored on the client end. The client can choose to edit the hardware description, and can also choose to save the XML file. The server part of pootypedia is written with a view towards readability and extensibility.
Hope that inspires !