[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=date&view=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=detail&aid=2362450&group_id=5109&atid=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
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
Eric Auer schreef: > Pat, Jeremy: Please FIRST update history txt BEFORE we make > a sourceforge file release of kernel 2038. Thank you :-). > As ideal as this seems, I'm glad there's a 2038 now. Feel free to make a history.txt for 2039, as you seem to mention there's some patches already again anyway (which would mean a 2039 isn't too far away). As for SYS, I think I'll keep both versions (stable and unstable) due to different feature sets. As for FreeCOM, guess we're stuck with the old one. Should we offer 4DOS as an option during installation time of any distribution? > Eric > Bernd -- 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
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 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=rev&sortby=date&revision=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
