On Thu, 25 Oct 2007 17:46:40 +0200 (MEST), you wrote: Dear Developers:
>Our kernel is only ca 40 kilobytes on disk, which is quite small. I don't believe it's already optimized to zero excess code, there should be some way to improve, the previous slow accessing problem still not yet solved, I don't know if any specific memory problem or others, but keep the code clean always correct. >Agreed, the config sys syntax differs considerably. Compatibility >issues seem to be limited to Windows 32 bit mode mostly, or did >I miss other popular apps? :-) When come to DOS extender or some DOS extender program, FreeDOS usually not work (e.g. Han Chinese System) >We could name the FreeCOM and kernel versions according to their >SVN revisions. Note that stable is at 2038 release candidates, >not at 2036 test. Unstable/testing branch is at 2037 and has not >been stabilized / audited / moved towards 2039 for a while (the >numbering scheme now is Linux style: Even for stable, odd for >devel/testing/unstable editions :-)). This is for developers only, and how to judge what is "stable"? When a new kernel will release? To the users, "2037a" or "2037 beta" is confusing enough, please keep to 1.0, 1.1, minor fix should be 1.1a ... etc. >Well if you REALLY want the scene to wake up, then I think it is >VERY important to have a new release of the whole distro. In other New release of 1.0 is disaster, maybe I'm a bit exaggerated, but I found this word is the most similar to describe. Didn't you see how FreeDOS 1.0 react? Many people complain the ISO have problem, or the installed DOS not working properly. >throw the updated zips over the old ISO, fix a few small bugs >in the installer itself, and voila, we have FreeDOS 1.1 :-). >To get started, a BASE edition will be enough... Let me know >if you want to help :-). The FreeDOS 1.0 ISO is not small bug, people did have bad image about the whole project, saw a few people asking questions here several months ago, and no one can help them to solve, they're so helpless that finally I've sent them "medicine" and they're cured. I'm want but not able to help, coding not my talent. I've tried but seems you guys not very impressed about the "simplicity", also you have to solve duplicate software, make a clean "whatsnew.txt". >> Something like this will be even better: >> http://dosbox.sourceforge.net/status.php?show_status=1&begaming_website_session=afded9279c6b3e3b5b5b863917bc122d I saw Tom's comment about the percentage thing, my advise: Marketing is important, no matter how good your product is, without these buzzword people not going to buy from you, they like this stupid percentage thing. >This is a list of "percentage done per category" with categories >such as "graphics system". Remember that we already have similar: Good but not simple enough, don't underestimate the human stupidity >wiki.fdos.org/Main/Todo_1_0 Not simple enough, Tom was right about the stupid percentage, but people love these kind of presentation >wiki.fdos.org/Main/Post_1_0_Todo 1) DBLSPACE, FASTOPEN, MEMMAKER outdated, should be removed 2) Include the standard memory manager, and provide information for others available 3) MSAV is Anti-virus, too bad ClamAV have no DOS port, and F-PROT for DOS have no more update >freedos.svn.sourceforge.net/viewvc/freedos/kernel/trunk/docs/intfns.txt?view=markup Once a project got too big, it should have duplicate code or some quick and dirty code written, but not cleaning these up just can't keep development going on. I found that FreeDOS is "quite good" in some situation, that's why I don't want to see it slowdown and stopped completely. Rgds, Johnson. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
