Re: [Freedos-kernel] fresh freedos svn kernel updates
On 7/22/07, Eric Auer [EMAIL PROTECTED] wrote: again, I think that only IRQTEXT is what broke Bochs compatibility. So I applied a patch (revision 1341) which leaves the other 1325 changes intact. Jemm FASTBOOT should work with version 1341. With the 1325 IRQTEXT, all versions (1325 to 1340) failed in Bochs at some point around the PostConfig kernel relocate moment, even if no HMA was available. No idea why - 1341 is based on intuition and experiments, not on theoretical knowledge why IRQTEXT was bad. The problem was that the irqstacks.asm init (for config.sys STACKS=n where n0) was setting up the wrong segments for IRQ vectors. It should be correct now in SVN (tested with Bochs). IRQTEXT needs to be present to force the saved IVT vectors to be at 70:100, which is the RBIL documented location; otherwise they are stored somewhere else. Bart - 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-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] fresh freedos svn kernel updates
On 7/21/07, Eric Auer [EMAIL PROTECTED] wrote: Are there any volunteers to maintain the UNSTABLE branch of the kernel? I was looking into merging parts of UNSTABLE a few months ago but it's a lot of work since I don't like about half of the changes. And after that I ran out of time, and still am, just now spending a spare hour or two on FreeDOS. There are funny space savings in text strings just so that Lucho could get the compressed kernel under 40K. I found one bug in the inittext.c optimizations by Arkady. And so on. Although the ioctl.c restructuring is good, most of the chario.c savings also help. A lot more could be saved in initdisk.c by using the fact that the sector size equals 512 (the DOS code cannot assume that with ram disks etc, but the BIOS code needs to assume 512 because the BIOS int13 does not support any other size AFAIK -- though I've heard Aitor claiming some things about an old AT I do not understand how that can work -- what BIOS interface to use to figure out that sectors have 1024 bytes?). External country.sys and more windows 3.x support never hurt. Removing the internal country table makes things a little bit more dependent (Tom's point of having the internal table is that you don't need a country.sys file if all you want is the correct date-month-year display). Of course the internal table is not good for the 40K aim. Bart - 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-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] fresh freedos svn kernel updates
Hi Bart, I was looking into merging parts of UNSTABLE a few months ago but it's a lot of work since I don't like about half of the changes. Actually I think it might take man-months or more to review all the MANY changes between unstable and stable, plus merge all the fixes of stable into unstable first. or two on FreeDOS. There are funny space savings in text strings just so that Lucho could get the compressed kernel under 40K. I found one bug in the inittext.c optimizations by Arkady. And so on. Space should not be everything. But for people who do care a lot about space, it would be better to have several subsystems compile time selectable, for example any COUNTRY support at all, internal or external or FCB support and so on. Many patches of UNSTABLE are indeed peephole optimizations which can make the code very hard to read. Be glad you did not try to debug CuteMouse, for example ;-). So one has to be very careful / meticulous (?) / thorough / diligent when porting things from the UNSTABLE kernel to the stable / svn trunk branch. the BIOS int13 does not support any other size AFAIK I think there were Japanese diskette formats with 1k sector size? Probably not bootable, though. Same for optical WORM drives. External country.sys and more windows 3.x support never hurt. Yes. Especially the int2f stuff should be reasonably easy to port. Removing the internal country table makes things a little bit more dependent (Tom's point of having the internal table is that you don't need a country.sys file if all you want is the correct date-month-year display). Of course the internal table is not good for the 40K aim. I do like the internal table a lot and it UPXes well afaik but, as said, one could make the internal table and support for external country sys both a compile time option, including the option to compile a kernel with neither of the two enabled. In either case, there are still - few - unimplemented functions which should be added to stable before we start adding tuning stuff from unstable into stable if you ask me. Bugfixes from unstable are welcome in stable, of course, esp if smallish. Eric - 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-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
