Hi Jerome, > not everything required by the installer quite fits on a 360k. > (Although, I must admit, with a little more pruning and juggling > by the installer and dropping the 386 kernel, It may just squeeze > onto a 360)
Sounds like a great solution :-) Found something interesting in my archives: 2007 map files from old open watcom kernel compiles :-) 386 FAT16, UPXed kernel file size 41190 bytes,TGROUP 51694, I_GROUP 8712 (and PGROUP 256, LGROUP 1588, DGROUP 5814, but those are constant) ==> HMA_TEXT 37718, INIT_TEXT 13966, Total memory size (?) 72184 386 FAT32, UPXed kernel file size 45894, TGROUP 55925, I_GROUP 8808 ==> HMA_TEXT 41610, INIT_TEXT 14309, Total memory size (?) 76520 (FAT32 plus 3.9k resident, 0.3k transient) 8086 FAT16, UPXed kernel file size 43389, TGROUP 53852, I_GROUP 8690 ==> HMA_TEXT 39001, INIT_TEXT 14844, Total memory size (?) 74306 8086 FAT32, UPXed kernel file size 45922, TGROUP 57994, I_GROUP 8714 ==> HMA_TEXT 42827, INIT_TEXT 15192, Total memory size (?) 78522 (FAT32 plus 3.8k resident, 0.3k transient) The 8086 FAT16 kernel is 2.2k larger on disk and uses 1.3k more RAM than the 386 FAT16 kernel. The 8086 FAT32 kernel is not larger on disk, but still uses 1.2k more RAM than the 386 FAT32 kernel, which is the default recommended kernel. The summary is that 8086 compatibility costs 1.2k to 1.3k RAM and 0 to 2.2k of disk space, while FAT32 costs almost 4k RAM. Which might be just the 4k you need more to make something work on your 8086, while having less HMA free on a newer PC with HIMEM or XMGR is less critical. So it would be a very good idea to provide a KSSF / VSPAWN FreeCOM for 8086 where the command.com XMS swapping is not applicable. Regards, Eric _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
