ReactOS 'Support Database' for the new ReactOS Homepage
I wrote down a lot of ideas, questions, soulutions, goals, etc. for the
upcoming Support Database!
We need more ideas, suggestions, comments, etc! Please read the whole text
and then write an email to the mailing list! This text should start
discussion about that topic !!!
Thanks!
Note:
* some of the ideas are not completely new, i copy&paste the from winehq's
newsletter archive (i quoted the winehq's ideas and add the original post
date)!
* I have added some useful links at the of the text! Please try out the
links and explore the compatibility databases from other projects! You will
need it if you want to join the discussion. And I *hope* a lot of persons
join the discussion! So please visite the links and write down what could be
better or what's key features our database also should *clone*!
The 'Support Database' will contain the following 'databases':
* Compatibility Database (application, driver and hardware)
* Package Database (a list of download-able applications/driver; principal
for the ReactOS Package Manager)
(* Media Database (like the ReactOS Fansite Media Database; maybe we can
implement this later))
The 'Support Database' (project codename 'RosDB') will base on the package
manager alpha page that i have created april 2005.
Note: the package database will be combined with the compatibility datbase.
Both 'databases' will share the same 'application tree'! So it will be easy
e.g. you browse the compatibility db, you found a working app and think, "i
also want to download this app", then you will be able to click on a link
(on a central position) and you will be redirected to the package database.
In near future it should be possible (if you run ReactOS or Win32 with
installed and runing ReactOS Package Manager), that you can select your
favorite apps/driver you want to install (navigation like
amazone/ebay/compatibility db) and then click install (a normal link on the
package manager page) and your running (maybe as a service) ReactOS Package
Manager check/capture every clipboard item and if it is a valid 'package
style link' then it will connect to the online database and download all the
selected apps/driver and download it from mirror server (from their
developers/sourceforge/etc.) and then install all items (without or with
minimum of user interaction). In my (frik85) opinion, that would be one of
the 'hottest' feature someone can imagine (in connection with a homepage,
package manager, etc.).
This feature will became a main feature and everyone will use that *hope*
for ReactOs and also possible for Win32 (from MS). :) -- frik85
"ReactOS Compatibility Database
ReactOS has an Compatibility Database where Windows
application/driver/hardware compatibility is recorded. Registered users can
submit new items, and comment on existing ones. Screen shots are also
available for many apps. Users can also vote on their favorite apps." -- a
possible description
Design goals User wants to know following things:
* Does my application/driver/hardware work?
* How can I make it work?
* Does it work in the new ReactOS/application/driver/hardware version?
* Where can i download the application (maybe with the ReactOS Package
Manager)?
* list all working and non working application/driver/hardware
Management Issues/Goals:
We need a high 'input data quality', then the administration work will be a
minimum.
To reach this high data quality, i want to code a simple to use wizard for
the 'submit item' page.
You can view the sample wizard on the package manager alpha page (see link).
Have some form of a moderation system to let end users know the quality of a
given persons entry.
Maybe like the appDB from winehq? Where a registered user can ask for a kind
of moderator right for one specific item (e.g. application), so he can
manage the comments, add new info, etc.
-> taking ownership of an item (e.g. application): monitor comments on it,
track bugs (close bugs), and make sure quality level is high for application
description.
NO redundant entries for the same product! We need moderators who review all
new entries. The moderators should be able to read as many comments as
possible and help the normal users, report bugs to the bugzilla system, etc.
Reviews (aka user comments) should expire. (expire time 1 year?)
Track hit counts on each item (auto magic way of knowing which apps are most
desired) and maybe voting like in appDB (WineHQ) or in C4 (CodeWeaver).
Some ideas i found in old winehq's neewsletters: (maybe useful for our
project!)
"Idea: Tie the apps database to the api database. The idea is that we know
from the apps database which apps are the most popular. We know from the api
database which DLLs/entry points are used by those apps. We can then create
a report out of the api database of the list of the DLLs most needed by the
top ten apps, and then people writing test scripts (something Alexandre and
John Sturtz are working on), have a prioritized todo list. Again, this helps
us find useful things for the many volunteers to do." -- winehq newsletter
from 18 Oct 2000
Note: maybe a good idea to create such a api database; -> a simalar api
status output is currently generated from the svn server (with a small
console based application, see build tools).
You can view the api status on the svn server. A great chance to import the
data to the database and make the idea above possible! The only question, is
it usefull for someone? -- frik85
"Idea: Tie the apps database to bugzilla. If users have a problem with an
app, it's a bug, and should be in bugzilla. If we can get to a point where
we can easily get a report that says 'here are all the bugs that Quicken
depends on'. Or, here are the five bugs, the fixing of which will make 50
apps suddenly work. This would be wicked cool." -- winehq newsletter from 18
Oct 2000
Note: the bugzilla will be a subsystem of the RosCMS, so it will be (maybe)
possible to implement the idea above. Is something like this usefull for
someone? -- frik85
"if we add some 'relay statistics' in Wine code (of course, there will be
problems with COM objects where relaying does not work for now) and
incorporate these statistics in the database, we could have a list of the
most frequently used Windows calls.
(feel free to add new ideas for improvements :-) )" -- winehq newsletter
from 28 Dec 2000
"He [who take ownership of an item] definitely should have the application
installed and, very preferably, he should also be using it regularly (or
testing it regularly if it is not yet in the usable state). You are right in
pointing out that he cannot test all possible but I contend he does not have
to. His role would be to:
read the comments entered in the application's comment section.
engage into a discussion with the users who post interesting tricks,
information, report a sub-version as not working, report problems with a
specific Wine/Windows combination
extract and summarize the above in his application status report. This
section would come first in the application's page and only the application
maintainer would be allowed to modify it (whether it's strictly enforced or
not is another issue)
test the application regularly and update the information on the
application's page
help users having problems with that application " -- winehq newsletter from
28 Dec 2000
"Jeremy White proposed some scheme to help keeping the database usable: I
think the biggest problem with the app database is that we get garbage in,
it produces garbage out. I think we should not report or even use any user
scores until a trusted app db maintainer has validated that user experience
(and possibly users can become trusted reporters). Too many people say 'Hey!
The main screen came up! That's a 5! Witness the Slashdot post about MS
Office 2k. (anyone actually try to use Office 2K in Wine to author a sizable
document?)." -- winehq newsletter from 28 Dec 2000
The information we will gain from the support database
* the progress of ReactOS (for devs and normal user)
* the most wanted applications (when we implement a voting / hit counts
feature)
* a reference for application/driver/hardware that doesn't work without
tweaking, to get them working
* people may be able taking 'ownership' of an application and do regular bug
reports / regression testings).
Several questions, where we need a answer:
"How to 'classify' applications ?: the main point was how an application
should be identified (think of Word 5 vs. WinWord 5 cs. Word 7.0, and lots
of other quirks (limited versions, demo version, patched versions...)
What information should we have about an application ?: this would help in
knowing the correct context of execution of such an application (target
Windows version, used DLLs, used APIs...)" -- winehq newsletter from 28 Dec
2000
* And about a ReactOS releases ?
* How about scoring ?
* What additional information should one application/driver/hardware have?
We need as much ideas, (feedback after the relaunch/while the testing
phase), comments, (and flames) as possible the next weeks. After the website
relaunch We need volunteers to take responsibility for updating Apps in the
Compatibility Database.
We need to discuss this!
Then after the discussions ... only remains the hours of coding and
debugging to put it in place :)
Compatibility Databases from other projects:
http://appdb.winehq.org/http://www.codeweavers.com/compatibility/http://www.linuxcompatible.org/compatibility.htmlhttp://www.ntcompatible.com/compatibility.htmlhttp://www.microsoft.com/whdc/hcl/default.mspxttp://www.realtimesoft.com/multimon/search.asphttp://hardwaredb.suse.de/index.php?LANG=en_UKhttp://www.testingstandards.co.uk/compatibility_-_database.htmhttp://www.yellowtab.com/support/hardware/http://www.iyonix.com/software/http://www.ardi.com/compat_search.php?name=ALL&category=ALL&status=ALL
A kind of Package Database:
http://rpmseek.com/index.html?hl=en
If you know other websites that should be listed here, please write an email
to the mailing list!
Best regards,
Klemens Friedl <frik85>
PS: if you write a comment, do NOT quote whole passages or do NOT quote the
whole text! The reason, emails should be readable ...
--
GMX DSL = Maximale Leistung zum minimalen Preis!
2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
This makes it totally perfect for embedded applications like Set-top-boxes or Routers or why not game consoles right?
/Jaix
----Ursprungligt meddelande-----
From: Emanuele Aliberti ea(a)iol.it
Date: Thu, 1 Sep 2005 06:37:19 +0200
To: ReactOS Development List ros-dev(a)reactos.com
Subject: Re: [ros-dev] New Webserver System
> Richard Campbell wrote:
>
> > Well, i don't know about other devs around here, but i don't WANT
> > ReactOS to become another XP.
> >
> > Windows XP typically consumes over a GB of space.
> >
> > Remember NT4? It took between 30 and 100 mb of space depending on
> > features. Windows 95? About 15 MB. If users want additional apps,
> > they can either download them, or use a custom ROS distro that will
> > include such things. The source tree is cluttered enough as it is.
> > ReactOS should only include the basic software that earlier versions
> > shipped with...a notepad clone, possibly a wordpad clone, basic net
> > utils, etc.
>
> Also the Win32 subsystem is not technically necessary. All Win32 pieces
> could be moved off the main reactos tree and included as optional
> linking them from modules. I proposed it years ago. It is not an easy
> task, though, because setup should know that, if the user asks for no
> personalty at all, it should install none (now win32 is by default in).
> Personalities (win, posix, os2, vms, ...) should come on the cd-rom as
> separate cab files and post install procedures add registry entries,
> create directoryes etc. A no-personality ReactOS will be a really light
> OS, perfect for custom text/graphics boxes (you just need writing an
> entry in the registry for the session manager to start your native
> program, which will be the only user program in the box (excluding the
> sm itself).
>
> --
> :Emanuele Aliberti
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
Yours sincerely,
Jaix Bly
Hello,
Ros VGA driver does not work anymore in my real hardware configuration.
I'd like to know if the problem is confirmed by somebody else.
To reproduce it , disable the VBE drives in Hiveinst.inf file , make
registry and reboot.
The green Reactos logo displayed at boot is not displayed correctly (
color is red/yellow etc , the logo is not clearly displayed )
Here are the debug messages (DBG=1)
---------------------------
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\system32\drivers\mpu401.sys
(drivers\input\i8042prt\registry.c:218) Can't read registry: c0000034
(drivers\input\i8042prt\registry.c:224) Manually set defaults
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\system32\drivers\xboxvmp.sys
(ntoskrnl\ob\wait.c:246) Returning: 0
(subsys\win32k\ntuser\desktop.c:769) Trying to open desktop
(\Windows\WindowStations\WinSta0\Default)
(subsys\win32k\ntuser\desktop.c:580) IntShellHookNotify: No desktop!
(subsys\win32k\ntuser\desktop.c:769) Trying to open desktop
(\Windows\WindowStations\WinSta0\Winlogon)
(subsys\win32k\ntuser\desktop.c:580) IntShellHookNotify: No desktop!
(subsys\win32k\ntuser\desktop.c:769) Trying to open desktop
(\Windows\WindowStations\WinSta0\Screen-Saver)
(subsys\win32k\ntuser\desktop.c:580) IntShellHookNotify: No desktop!
(lib\ntdll\ldr\utils.c:2072) Relocating (77a90000 -> 431000)
C:\ReactOS\System32\version.dll
FIXME: CopyImage doesn't support IMAGE_ICON correctly!
(lib\ntdll\ldr\utils.c:1190) LdrGetExportByName(): failed to find mxdMessage
(lib\ntdll\ldr\utils.c:2015) Failed to create or open dll section of
'msacm.drv' (Status c0000135)
(lib\ntdll\ldr\utils.c:2015) Failed to create or open dll section of
'midimap.drv' (Status c0000135)
(SAMLIB:lib\samlib\samlib.c:399) User already exists!
(lib\setupapi\devinst.c:2513) not fully implemented
(lib\setupapi\devinst.c:2513) not fully implemented
(lib\setupapi\devinst.c:2513) not fully implemented
(lib\setupapi\devinst.c:2513) not fully implemented
(lib\setupapi\devinst.c:2513) not fully implemented
(lib\setupapi\devinst.c:2513) not fully implemented
Thanks
Gge
This is a suggestion:
Can ReactOS implement an OpenLDAP backend to the ReactOS website.
There are many benefits to implementing OpenLDAP into the reactos.com
website. First, reactos.com can use this software to authenticate
users in certain modules of the website such as future forums, wikis
(via publishing), and possible later implementation into a mass-
mailing system like squirrelmail or mailman, suggestions, hint hint,
or perhaps in the future an instant messenger engine. Also OpenLDAP
would be able to provide back-end website developers to verify status
of community members.
How is that for a baby step to implementing someone's ideas...
Rick Langschultz
rlangschultz(a)cox.net (Home)
rlangschultz(a)ellemaespa.com (Work)
rlangschultz(a)email.uophx.edu (School)
hi
i installed reactos on my hd but the installer doesnt give the
option to install de loader to the mbr only on the floppy so i didnt
installed because i dont have a floppy :p
then i create:
freeldr.ini ant copy the freeldr.ini but i didnt know what the
bootsect.ros is i didnt find info about it in the wiky
¿how can i create one?
--
[dalfa@MDK dalfa]$ cat .firma
[UsuarioGnu/Linux326018]
<Ymessenger> dalfa_id
<WebPage> http://dalfa.tk
<WebPage> http://dalfa.no-ip.org
<Jabber> dalfa(a)jabber.org
<skype> theenligthenedone
<aMSN> dalfa.theenlightenedone(en)gmail.com
<Blog> http://drakedalfa.blogspot.com/
<aim> drakedalfa
-> Y la verdad os hara libres...
- Hechos 4: 12
- Romanos 10: 9-13
I was looking through the installer, and noticed that it generated an
error for partitions created by linux fdisk. Shouldn't the user be
informed about this, so they know why. This type of information will
help a user solve the problem that caused the error.
Below is the code for the error I'm talking about.
if (WarnLinuxPartitions == TRUE &&
CheckForLinuxFdiskPartitions (PartitionList) == TRUE)
{
PopupError ("Setup found that at least one harddisk contains an
incompatible\n"
"partition table that can not be handled properly!\n"
"\n"
"Creating or deleting partitions can destroy the partiton
table.\n"
"\n"
" \x07 Press F3 to quit Setup."
" \x07 Press ENTER to continue.",
"F3= Quit ENTER = Continue");
while (TRUE)
{
ConInKey (Ir);
if ((Ir->Event.KeyEvent.uChar.AsciiChar == 0x00) &&
(Ir->Event.KeyEvent.wVirtualKeyCode == VK_F3)) /* F3 */
{
return QUIT_PAGE;
}
else if (Ir->Event.KeyEvent.wVirtualKeyCode == VK_RETURN) /* ENTER */
{
WarnLinuxPartitions = FALSE;
return SELECT_PARTITION_PAGE;
}
}
}
Since I heard of reactos, i have always considered it one day
replacing my Windows 2000 and XP boxes. Because ReactOS was going to
be an open-source alternative to the Windows NT API I felt that it
had and has serious potential to hinder or greatly replace Microsoft
Windows. I have suggested several ideas both through IRC (freenode)
and email messages how the computing world does things. I understand
that ReactOS is still in pre-production, and planning for the next
release is greatly important to the community development and testing
of the operating system, however I fail to grasp the concept behind
the hindrance of ideas being passed the the development community.
Some development plans I have talked about were:
1 - A 64 bit journaling file system with a SQL-like back-end.
Lookout WinFS; there that plan went down the drain.
2 - Implementing an instant messenger server for developers and
users to talk on, realtime, without IRC.
Maybe not quite MSN Messenger, but why not? iChat even
uses .mac.
3 - Implementing an OpenLDAP back-end to the website.
Active Directory has nothing on you... Plan knocked out again.
i would rather stick with something close minded like closed source
software than having no ideas be recognized at all.
I only suggest things like this because Microsoft will always be
releasing newer software that will leave reactos in the dust if they
not heed the advice of all, not just me, their developers, testers,
and users.
Why not; right? why envision something and it fail to be realized,
waste of time if i ever knew it...
Rick Langschultz
rlangschultz(a)cox.net (Home)
rlangschultz(a)ellemaespa.com (Work)
rlangschultz(a)email.uophx.edu (School)
|>hi,
|>
|>i have a problem with the installation from
|>setup to a real hd the setup dies with this
|>message:
|>
|>allowconsolo() failed (status = 0x0000001)
|>
|That one seems a well known bug:
|http://www.reactos.com/wiki/index.php/ChangeLog-0.2.7
|http://reactos.com/bugzilla/show_bug.cgi?id=688
thanks that show me the way ;) the problem is
my keyboard is usb one so i plug an ps2 one and
now all work :)
maybe a little more debug on the setup will help to
others to figure this :) more easy
thanks :)
|>the installation procedure is only the copy
|>of the reactos directory to the hd?
|>
|It also prepares the SYSTEM registry hive with values depending on the
|operator choices and (little) hardware probing and installs the boot sector.
thanks, now i can install the system and now i configure the
grub but i have another question the file bootsect.ros, wath has to say?
i made my freeldr.ini like this:
[ReactOS]
BootType=ReactOS
SystemPath=multi(0)disk(0)rdisk(0)partition(7)\reactos
Options=/DEBUGPORT=SCREEN
but the bootsect.ros i didnt find a example :)
thanks for the help
hi,
i have a problem with the installation from
setup to a real hd the setup dies with this
message:
allowconsolo() failed (status = 0x0000001)
well, my question is:
the installation procedure is only the copy
of the reactos directory to the hd?
Sorry to ask to the DevelList but in the
users list no one answer me :)
thanks
--
[dalfa@MDK dalfa]$ cat .firma
[UsuarioGnu/Linux326018]
<Ymessenger> dalfa_id
<WebPage> http://dalfa.tk
<WebPage> http://dalfa.no-ip.org
<Jabber> dalfa(a)jabber.org
<skype> theenligthenedone
<aMSN> dalfa.theenlightenedone(en)gmail.com
<Blog> http://drakedalfa.blogspot.com/
<aim> drakedalfa
-> Y la verdad os hara libres...
- Hechos 4: 12
- Romanos 10: 9-13
