Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
Hello Bart, I added the hook... very sorry about this delay... Aitor 2009/6/5 Bart Oldeman bartolde...@users.sourceforge.net: Hi Eric, 2009/6/5 Eric Auer e.a...@jpberlin.de: Bart seems to work on this a lot, but unfortunately there is nothing about the progress on the mailing list. well, at the time of setting up SVN I asked Jim if he could set up sourceforge so the patches to go to the existing freedos-cvs mailing list (where CVS commits were sent), put he seemed to not understand what I meant. Anyone with admin rights, Aitor? Jim? Pat? you can do this on SF: click Project Admin click Feature Settings click manage next to Subversion add an svnnotify hook, and type freedos-...@lists.sourceforge.net as the email address. the main ideas of the changes: * there are only two near fnodes, and almost all operations use the first fnode, fnode[0] except for dos_rename(), which also uses fnode[1]. * file state is only kept in SFTs: an open/creat uses fnode[0], then copies the state to an SFT a read/write copies state from the SFT to fnode[0], does its work on fnode[0], then copies back to the SFT. a close copies from the SFT to fnode[0], and closes the file. * For FAT16 kernels, the SFT layout is documented in RBIL * For FAT32 kernels, the SFT layout follows that of MSDOS 7.10 (not documented in RBIL). * the share support also needed some changes, because it needs to walk the SFTs instead of the far fnodes to merge changes. Otherwise I would ask why r1416 rmdir drops the 00/eof check (does it?) and why r1397 drops the dos_commit-only way of close(?) and how get_f_nodes_cnt works, among other things... well, you ask these questions anyway, one wise or otherwise... r1416: Look at what dir_read(fnp)==1 means in fatdir.c... r1397: dos_commit was no longer necessary: a commit (int21/ah=68,6a), in DosCloseSft() just calls dos_close() without closing the SFT. get_f_nodes_cnt() was an intermediate function that no longer exists (to keep individual changes small) It just walked the SFT chain and computed the FILES= value. Bart -- OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
Hi Bart, well, at the time of setting up SVN I asked Jim if he could set up sourceforge so the patches to go to the existing freedos-cvs mailing list (where CVS commits were sent) I do not know how many people read that list, but my suggestion was more to talk about the code rather than reading it :-). After all, I can read the SVN commit list and diffs easily via the web interface or my SVN client, but this does not tell me what the code changes mean and what the background of their design is ;-). Anyone with admin rights, Aitor? Jim? Pat? you can do this on SF: click Project Admin click Feature Settings click manage next to Subversion add an svnnotify hook, and type freedos-...@lists.sourceforge.net as the email address. Sourceforge.net seems to have problems at the moment but it seems that Aitor and Pat are indeed the people to ask :-). * there are only two near fnodes, and almost all operations use the first fnode, fnode[0] except for dos_rename(), which also uses fnode[1] I remember part of that, and I think it is a good idea that you now hardcode the 0 / 1 index now instead of the old alloc scheme. Actually by making dos_rename the first f-node-free implementation you could already get down to a single global f-node :-). * file state is only kept in SFTs: an open/creat uses fnode[0], then copies the state to an SFT a read/write copies state from the SFT to fnode[0], does its work on fnode[0], then copies back to the SFT. a close copies from the SFT to fnode[0], and closes the file. F-nodes largely overlap SFT afair, but also have the dir entry (relevant for performance?). Looking at your changes, it seems you move towards dynamic transformations between SFT and F-Node shape of the data, to make F-Nodes more virtual and get them closer to being abandoned. Certainly not trivial :-). * For FAT16 kernels, the SFT layout is documented in RBIL * For FAT32 kernels, the SFT layout follows that of MSDOS 7.10 (not documented in RBIL). Documented in MSDN then? Could this cause significant classic DOS app / driver incompatibilities when using FAT32 kernels? * the share support also needed some changes, because it needs to walk the SFTs instead of the far fnodes to merge changes. That sounds really interesting. Does it mean we need FreeDOS specific SHARE now and will be able to use any DOS SHARE in the future? Note that our SHARE could use tuning to reduce the memory footprint (or rewrite in ASM?) and that people have made patched versions (Japheth?) for compatibility reasons... Otherwise I would ask why r1416 rmdir drops the 00/eof check (does it?) and why r1397 drops the dos_commit-only way of close(?) and how get_f_nodes_cnt works, among other things... r1416: Look at what dir_read(fnp)==1 means in fatdir.c... You mean it already implies end of directory? r1397: dos_commit was no longer necessary: a commit (int21/ah=68,6a), in DosCloseSft() just calls dos_close() without closing the SFT. Still do not get it, but I assume you know what you are doing :-) get_f_nodes_cnt() was an intermediate function that no longer exists (to keep individual changes small) It just walked the SFT chain and computed the FILES= value. Strange, seems to be meant the other way round: The user sets FILES and then the SFT uses the available number of handles, with the JFT of each task saying which SFT items are in use? Eric :-) -- OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
Hi dos386! Can you forward details about that dmidecode / bttr forum thing? PS: I would like to quote IBID_AG 4. I would rather see more of the features from 2037 in stable Ask IBID... country sys support is very useful for SOME languages, but which other features of 2037 are really hot? :-) WfW support in stable, these might be handy. WtF is WfW ??? Windows for Workgroups 3.11 - quite different from Windows 3.0 and 3.1, because WfW always runs in 386enh mode (unless you call a sort of minimal safe mode running). FreeDOS runs Windows 3 in standard mode easily, but support for 386enh mode is even an experimental compile-time extension of the experimental 2037 kernel. Pretty unstable, in other words :-). As for SYS, I think I'll keep both versions (stable and unstable) due to different feature sets. Actually I had forgotten to point this one: there used to be SYS 3.5 or 3.6 back in 2005 ... that's what EDR-DOS SYS was forked from ;-) This is simply the unstable branch of SYS - Udo of course likes the ability of that SYS to make other operating systems bootable, in particular EDR DOS :-). But yeah - we should take care with the version numbers, otherwise we get 2 totally different SYSes which have the same version number! Eric -- OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
dos386 schreef: PS: I would like to quote IBID_AG 2. Congratulations on a great kernel/OS 4. I would rather see more of the features from 2037 in stable List ??? * external Country.sys support (including MODE, DISPLAY, NLSFUNC etc) * That FNODES stuff (Bart seems to be working occasionally on this, but now based on 2038) * Windows 3.1x support WfW support in stable, these might be handy. WtF is WfW ??? Windows for Workgroups , which is a flavor of Microsoft Windows 3.11 And SHSUCDX with UDF support does seem higher priority. UDF-CDEX would be separate from kernel development As it always was. What does UDF support do? Enable copying video DVD? or enable packetwriting? Actually I had forgotten to point this one: there used to be SYS 3.5 or 3.6 back in 2005 ... that's what EDR-DOS SYS was forked from ;-) Jeremy Davis created SYS 3.5 yes with support for several other DOS-based operating systems by generating their bootsectors. Found some old info at my ancient Blog on Jeremy's server [ http://wiki.fdos.org/Blog/Bernd ] Indeed DR-DOS got its SYS from here. I seem to recall that SYS did not support FAT32 bootsectors for Windows 95OSR2.x and Windows98/98SE/ME. As we're on the kernel list anyway, would anyone be able to tell me if it's possible to modify the kernel enough with additional code so that it could read a Isolinux/Memdisk commandline including arguments? Followed by searching for a config=x option where x=[0..9] and then executing that menu option in (fd)config.sys. The benefit of this is taking away 1 keypress Currently it's : 1) select to boot FreeDOS from CD , 2) select which menu option you want. I'd rather create multiple Isolinux options which would then tell the same FreeDOS diskette image what to do, in config.sys already. Eric Auer had a commandline utility for this, which is already quite usefull, but means there's no support for loading device drivers (and specially DOS=HIGH, DOS=UMB, the kernel and FreeCOM , XMS saves a lot of memory) Bernd -- OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
Eric Auer schreef: Hi dos386! Can you forward details about that dmidecode / bttr forum thing? http://www.bttr-software.de/ http://www.bttr-software.de/forum/forum.php software: http://www.bttr-software.de/misc/dmide29b.zip (I guess) Nowadays a hardware diagnostics tool at boottime seems to be HDT, for Syslinux [ http://syslinux.zytor.com/wiki/index.php/Hdt_(Hardware_Detection_Tool) ], with a so-called COM32 module at http://konilope.linuxeries.org/hdt/hdt_0_3_3.c32 Bernd -- OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
* Windows 3.1x support seriously: is ANYBODY using Windows 3.x ? IMHO Windows 3.x is 100% obsolete, so why would anybody want windows 3.x support ? WfW support in stable, these might be handy. Windows for Workgroups , which is a flavor of Microsoft Windows 3.11 WfW support will probably never come; WfW was tighly coupled to the kernel (at least according to Schulman et. al., WfW is MUCH more then just a flavour of Windows 3.11) And SHSUCDX with UDF support does seem higher priority. UDF-CDEX would be separate from kernel development What does UDF support do? Enable copying video DVD? or enable packetwriting? being able to read UDF formatted DVD's, in particular all packet writing DVD software Tom -- OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
Hi Bernd, Tom, Bart, others, * external Country.sys support (including MODE, DISPLAY, NLSFUNC etc) Definitely useful. I hope it can be combined with compiled-in 2038 style basic support: Things like date/time/number format. While only external country.sys adds sort/uppercase/lowercase override possibilities, people with mostly ASCII languages can still enjoy the (smaller on disk, easy to use) built-ins. Can you find other useful and reasonably easy to port features on http://apps.sourceforge.net/mediawiki/freedos/index.php?title=Unstable_Kernel_Branch http://freedos.svn.sf.net/viewvc/freedos/kernel/branches/UNSTABLE/?sortby=dateview=log Would be interesting to know :-) * That FNODES stuff (Bart seems to be working occasionally on this, but now based on 2038) Bart seems to work on this a lot, but unfortunately there is nothing about the progress on the mailing list. Otherwise I would ask why r1416 rmdir drops the 00/eof check (does it?) and why r1397 drops the dos_commit-only way of close(?) and how get_f_nodes_cnt works, among other things... Windows for Workgroups , which is a flavor of Microsoft Windows 3.11 Actually people who say Windows 3.11 almost ALWAYS actually mean Windows for Workgroups 3.11 ... There is also a year 2000 patch for Windows 3.1 which is called Windows 3.11 but that is by far the less frequently used type of Win 3.11. Windows 3.0 and 3.1 are quite different. I disagree that they would be useless without 386enh mode. I remember WIN /S still was quite useful for me but then I do not use Win32s based (Win9x-ish) software that would require 386enh mode... :-). Tom, can you give details on this: WfW support will probably never come; WfW was tighly coupled to the kernel (at least according to Schulman et. al., WfW is MUCH more then just a flavour of Windows 3.11) What is Schulman et al? I wonder whether the experimental patch for the experimental 2037 branch was for making 3.1 enh mode or 3.0 enho mode or rather WfW work in FreeDOS, or maybe several of them, does anybody know? Note that it is hard to run old Windows on modern hardware with any DOS. It can help to tell your HIMEM to show only max 256 MB of RAM, avoid EMM386, avoid Windows direct disk access drivers and maybe do other config tricks. Windows 3 is probably not extremely obsolete - I remember even that 3.0 worked, 3.1 did not of the deliberate DR DOS incompatibility long ago really hurt DR DOS market... What does UDF support do? Enable copying video DVD? UDF is popular for rewritable disks, writing on the fly and large disks with large files, in the CD and DVD world. Many DVDs and CDs still have normal ISO9660 instead, sure. Jeremy Davis created SYS 3.5 yes with support for several other DOS-based operating systems by generating their bootsectors. Found some old info at my ancient Blog on Jeremy's server http://wiki.fdos.org/Blog/Bernd ] I seem to recall that SYS did not support FAT32 bootsectors for Windows 95OSR2.x and Windows98/98SE/ME. it's possible to modify the kernel enough with additional code so that it could read a Isolinux/Memdisk commandline including arguments? Possible of course, desirable no ;-). There is that GETARGS tool and you can use it in autoexec. You can also use DEVLOAD if you want to use the fetched text for device driver options. Followed by searching for a config=x option where x=[0..9] and then executing that menu option in (fd)config.sys. The benefit of this is taking away 1 keypress Bad ratio between benefit and exotic feature ;-) Currently it's : 1) select to boot FreeDOS from CD 2) select which menu option you want. You can also use SYS CONFIG to enable Tom's function to skip STARTING DOS and boot the next drive instead with a hotkey. Then the ISOLINUX / GRUB4DOS / ..: menu could be configured to always LOAD DOS without choice. but means there's no support for loading device drivers (and specially DOS=HIGH, DOS=UMB, the kernel and FreeCOM I would suggest to make XMS, no EMS, no UMB the default and keep the menu (yes, sorry :-p) to select options like with JEMM386 or run only DOS, do not start the installer or maybe even no driver minimal mode. Yet the latter is already covered when you use F5... ;-). Eric PS: For those who want to use the can boot other OSes unstable variant of SYS, please consider porting six updates of stable to make a more stable version first: - 1315 update OEM name - 1342 fix FAT32 and LBA handling - 1342 make copy much faster, in particular for SYS A: B: with 1 drive - 1352 preserve file timestamps, improve copy and alloc code - 1356 update backup boot sector as well in FAT32 - 1367 fix compilation for odd OW 1.8+ headers -- OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
On Fri, Jun 5, 2009 at 2:05 PM, Eric Auere.a...@jpberlin.de wrote: Hi Bernd, Tom, Bart, others, ... WfW support will probably never come; WfW was tighly coupled to the kernel (at least according to Schulman et. al., WfW is MUCH more then just a flavour of Windows 3.11) What is Schulman et al? I wonder whether the experimental patch for the experimental 2037 branch was for making 3.1 enh mode or 3.0 enho mode or rather WfW work in FreeDOS, or maybe several of them, does anybody know? Note that it is hard to run old Windows on modern hardware with any DOS. The Windows specific patches are minor but add a small amount of code hence the extra work to enable (Windows is the only application for them). The kernel worked with windows 3.11 in enhanced mode except for an issue with keyboard input in DOS boxes not going to the proper VM instance, but I think this is related to VM instancing which took the shotgun approach and not the proper these are the parts of the kernel that need to be instanced. There are a couple settings in win.ini or system.ini that improve reliability, but really the hard part is getting a memory manager working reliably. For the kernel, load FreeDOS share so windows does not try to load the vshare.vxd. Windows actually goes a bit out of its way, if in a somewhat strange manner at times, to work with multiple DOS versions. The important parts for Win3x support I think was really the support added for country (the internal hooks to allow somewhat reentrant use of DOS). See http://wiki.fdos.org/Main/Windows for full details about using win3. ... Jeremy Davis created SYS 3.5 yes with support for several other ... PS: For those who want to use the can boot other OSes unstable variant of SYS, please consider porting six updates of stable to make a more stable version first: sys 3.6a is the current version, changes to older versions should be considered for maintenance purposes only. It is not unstable and it (or newer) will be in the 2039 kernel release. The support for other DOSes is compile time selectable so those dual booting need only 1 sys program and those who don't want it can compile sys without it. The FreeDOS sys was modified to work with DR-DOS and those changes were later folded back into the official version; now also as a compile time option to select FD sys or DR sys. Jeremy -- OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
Hi, as there was no reaction to the mail of dos386 ten days ago, I would like to repeat it as new thread: Tested and didn't find anything eclatantly evil so far :-) - It works mostly, see shot: http://img211.imageshack.us/img211/4611/ker2038.png This screenshot shows a 46208 byte kernel, 15550 byte SYS 3.3, the latter still lacking a Force LBA / Force CHS command line option for FAT32 use, alas. It also shows the output of a tool which tests int 21.7303 and displays the values: ver 0 size 2c sec/cluster 8 bytes/sector 200 free clusters c333 total clusters c334 free sectors 61998 total sectors 619a0 free clusters' c333 total clusters' c334 free space c333000 / 204681216. Version text says build 2038 May 16 2009 compiled May 16 2009. - my GetDiskFreeSpaceEx bug seems fixed Nice :-) - history.txt neglects any development, oops Eric already pointed it, also, Yes, still waiting for any reaction on my 18 May mail here... Can we update the history txt file for www.fdos.org/kernel/latest/ and on SVN soon? It is a pity that we already have post 2038 updates even though 2038 itself is not complete yet. In spite of all the warnings during the last year that documentation or lack thereof was the main thing which blocked official release. the filename should be HISTORY.TXT and not history.txt of course DOS filenames are not case sensitive. Actually lower case names are better if you want to keep case sensitive OSes happy. SourceForge page still shows 2006-May-21 (3 years old !!!), so, those having the power please fix this now or give the power to someone else. Pat, Jeremy: Please FIRST update history txt BEFORE we make a sourceforge file release of kernel 2038. Thank you :-). Eric Here is a suggested history.txt section for 2038 based on http://freedos.svn.sf.net/viewvc/freedos/kernel/trunk/?sortby=dateview=log http://freedos.svn.sf.net/viewvc/freedos/kernel/trunk/docs/history.txt?revision=1364 In short, SVN revisions 1365 to 1385 are undocumented...! Also, Bart already made 2039 related revisions - 1411 ;-) His changes are f_node / SFT and tuning things... It would be nice to have a web page where the unified diffs can be looked at for proofreading. Revisions 1386-1388 are about Linux cross compilation, 1385 bumps version.h to 2039-svn. A bit unrelated is 1396 sft.h: 0b start cluster is not set (RBIL 01642) or high part (Bart?) of if FAT32 kernel, file size and position (incl rel cluster) are unsigned and some fields at offset 1b-1e (current cluster/sector) change a lot. Is the sft_status sft_cuclust sft_ifsptr really correct?? - *please change*: Build 2038 is May 2009, not Apr 2008, and my email is the one I use now, not eric at coli. - *please add*: + Changes Jeremy 2009 * r1381-r1384 update bugs.txt, version.h, LSM, tag SVN for 2038 release * r1374, r1380 fcbfns FCB open old GEM compat (bigsize/recsiz/recno...) * r1379 dosfns.c fatfs.c proto.h from Eric: only check for SHARE on open/close, avoid extra 2f.1000 calls. * r1378 dsk.c from Lucho: Press any key, not Press the any key ;-) * r1377 initdisk.c from RayeR: Use total cyl count, not max cylinder (fixes off by one bug on non-LBA PC) fix overflow by ULONG cast. Improve DebugPrintf calls, fix format string (only in debug kernels) * r1376 inthndlr.c from Tom: 21.1c return AL=0xff for invalid drives (fixes bug for apps which use int 21.1c to find FAT drive letters) * r1372, r1375 process.h/entry.asm make CP/M call PSP[5] work (1 line jbe versus ja fix plus detailed comments, by Bart) This fixes SF tracked bug 2421577. * r1373 kernel.asm add : after _HMATextAvailable avoid nasm warning * r1371 watcom.mak make sure even Windows Watcom C builds a DOS SYS (would otherwise make a SYS meant for use in Windows by default) * r1370 default bat make compiling without UPX possible again * r1369 let DosGetExtFree 21.7303 accept drive with and w/o slash This fixes SF tracked bug 2380828 (GetDiskFreeSpaceEx if no slash) * r1368 tag for ke2038test - *please change*: Please add to the Changes Bart + Eric part: * r1367 sys.c from Bart: 32bit date/time if WATCOMC 1279+ (OW 1.8) * r1366 config.c, config.txt allow BUFFERSHIGH as alias to BUFFERS, buffers are in UMB, we use HMA anyway. Drop unused int 16.1 call. * r1365 inthndlr.c allow/ignore type hints in int 21.7305 disk read - *please add to r1334 comments*: Fixes SF tracked kernel bug 2362450: http://sf.net/tracker/?func=detailaid=2362450group_id=5109atid=105109 PS: I would like to quote IBID_AG: 1. I have checked out the latest build (kernel 2038-32). It works fine with GEM/XM. (So did the 2nd RC.) Nice :-) 2. Congratulations on a great kernel/OS 3. PLEASE stop the flame wars--the last few digests have looked rather (?!) 4. I would rather see more of the features from 2037 in stable than get more oddball features in unstable (ExFAT, FAT+). Once we get COUNTRY.SYS WfW support in stable, these might be handy. And SHSUCDX with
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
Folks, I am not as up to date on the changes as you may be. I'm looking for a volunteer (or volunteers) to update history.txt for 2038 and 2039. When I get the updated files, I'll follow through and get them on the web sites. Pat On Sun, May 31, 2009 at 9:05 AM, Eric Auer e.a...@jpberlin.de wrote: *** SNIP *** Pat, Jeremy: Please FIRST update history txt BEFORE we make a sourceforge file release of kernel 2038. Thank you :-). Eric -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, Big Spaceship. http://p.sf.net/sfu/creativitycat-com ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
Hi Bernd, Pat, Jeremy, Pat, Jeremy: Please FIRST update history txt BEFORE we make a sourceforge file release of kernel 2038. Thank you :-). I just uploaded updated history.txt / readme.txt / contrib.txt as subversion revision SVN r1412 for Pat :-). NOTE: Please ONLY updated those 3 when making a zip, otherwise you would make a zip of kernel almost 2039. This history.txt update describes ONLY the changes until 2038, not the newer changes, to make it easier to use my updated history.txt for a kernel 2038 zip :-) http://freedos.svn.sourceforge.net/viewvc/freedos/kernel/trunk/docs/?sortby=date#dirlist http://freedos.svn.sourceforge.net/viewvc/freedos?view=revsortby=daterevision=1412 In case you want to have a quick look without using a SVN tool: http://freedos.svn.sourceforge.net/viewvc/freedos/kernel/trunk/docs/history.txt http://freedos.svn.sourceforge.net/viewvc/freedos/kernel/trunk/docs/readme.txt http://freedos.svn.sourceforge.net/viewvc/freedos/kernel/trunk/docs/contrib.txt As ideal as this seems, I'm glad there's a 2038 now. There was a 2038 snapshot before, on http://rugxulo.googlepages.com/ What I mean is: When we put a fresh 2038 kernel zip file on http://sourceforge.net/project/showfiles.php?group_id=5109 it must include documentation / changelog about 2038 :-). Feel free to make a history.txt for 2039, as you seem to mention This documentation was only about 2038 and you must have a proper changelog if you want users to understand what they download and what they can expect in a new version. there's some patches already again anyway (which would mean a 2039 isn't too far away). There are dozens of patches between each two versions and I am sure that Bart will update history.txt after each block of patches to document changes, for example explaining the details on how he removed fnodes and in which C/H/ASM files. As for SYS, I think I'll keep both versions (stable and unstable) due to different feature sets. The unstable-branch SYS is more like a boot manager ;-) As for FreeCOM, guess we're stuck with the old one. Should we offer 4DOS as an option during installation time of any distribution? I would put 0.82pl3 as default but the install scripts as triggered by FDPKG / installer in FreeCOM 0.84 / 4DOS zip packages can be interactive and ask the user whether he wants to make 4DOS / 0.84 the SHELL line if he prefers that way :-). Eric PS: Other pending things are add force LBA or CHS option to SYS for FAT32 configuration, get explanation of SVN r1396 on sft.txt (offsets 0b, 1b-1e, sft_status _cuclust _ifsptr...), check UDF-CDEX possibilities, check which features beyond the COUNTRY SYS support from unstable are interesting for porting, http://apps.sourceforge.net/mediawiki/freedos/index.php?title=Unstable_Kernel_Branch -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, Big Spaceship. http://p.sf.net/sfu/creativitycat-com ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038
Tested and didn't find anything eclatantly evil so far :-) - It works mostly, see shot: http://img211.imageshack.us/img211/4611/ker2038.png - my GetDiskFreeSpaceEx bug seems fixed - history.txt neglects any development, oops Eric already pointed it, also, the filename should be HISTORY.TXT and not history.txt of course SourceForge page still shows 2006-May-21 (3 years old !!!), so, those having the power please fix this now or give the power to someone else. -- ~~~ wow ~~~ -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, Big Spaceship. http://www.creativitycat.com ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038
Hi Jeremy, Kernel 2038 tagged and available at http://www.fdos.org/kernel/latest/ Someone with access, please upload to ibiblio and release on SF. Please update history.txt - it represents the state of 13 months ago... While you are at it, could you update my email to mceric at users.sourceforge net in contrib.txt and other places? Thanks! Please test and report any new issues to the mailing list. Depending on any reported issues, 2039 scheduled to be released in about a month. Comments about new or existing bugs to focus on for next release welcome. Interesting :-) Eric -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] Kernel 2038 and plans
Hello all, 1. I have checked out the latest build (kernel 2038-32). It works fine with GEM/XM. (So did the 2nd RC.) 2. Congratulations on a great kernel/OS 3. PLEASE stop the flame wars--the last few digests have looked rather (?!) 4. I would rather see more of the features from 2037 in stable than get more oddball features in unstable (ExFAT, FAT+). Once we get COUNTRY.SYS WfW support in stable, these might be handy. And SHSUCDX with UDF support does seem higher priority. Thanks for developing FreeDOS! -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038
I'll take care of it tomorrow. Pat On Sun, May 17, 2009 at 11:11 PM, Kenneth J. Davis jere...@fdos.org wrote: Kernel 2038 tagged and available at http://www.fdos.org/kernel/latest/ Someone with access, please upload to ibiblio and release on SF. Please test and report any new issues to the mailing list. Depending on any reported issues, 2039 scheduled to be released in about a month. Comments about new or existing bugs to focus on for next release welcome. Thank you, Jeremy -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- Amateur Radio Station: WB2GBF U.S. Army MARS station: AAR2BY/T -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] kernel 2038
Kernel 2038 tagged and available at http://www.fdos.org/kernel/latest/ Someone with access, please upload to ibiblio and release on SF. Please test and report any new issues to the mailing list. Depending on any reported issues, 2039 scheduled to be released in about a month. Comments about new or existing bugs to focus on for next release welcome. Thank you, Jeremy -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] kernel 2038
Kernel 2038 tagged and available at http://www.fdos.org/kernel/latest/ Thanks :-) Even my GetDiskFreeSpaceEx-BUG is fixed ? I'll test :-) Someone with access, please upload to ibiblio and release on SF. Indeed ... now it says latest kernel is from 2006 !!! Depending on any reported issues, 2039 scheduled to be released in about a month. COOL. But why not 2040 ? The 2036/2037/2038 mess has been around for 5 years ;-) -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038
answer didn't work -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
