Hi again, > BTW: Did you add the recent Rayer's fixes into kernel > to be it able to boot on cheap notebooks?
You probably refer to this: "mieh tuh!" by RayeR 12 Jan 2009 in a thread about 7-Zip 4.62 near the bottom ;-). www.bttr-software.de/forum/board_entry.php?id=5533#p5789 Rugxulo told me about this and together we figured out what exactly Rayer had modified. He had already mailed me about parts of it, but he has not yet explained the rest. So I sent him the mail pasted below, but it seems that he did not react to it yet, maybe on vacation? Eric Forwarded (part of) mail to Rayer about his patches on http://rayer.ic.cz/hardware/evo-t20/fdk2038s.zip ...: ... please do not make that *disable LBA* the default. A simple SYS CONFIG in your BAT files can tune your own copy later. This affects kernel and exeflat sources. Of course I am interested *why* you had to disable LBA for that special computer :-) Next are some patches where I do *not* think it would be useful to add them to the SVN: clean - deletes compile result? (instead of only intermediate files) initdisk - show partn count on error (always shows same if BSS okay) initdisk - start / size printed more wide, why? does it really help? initdisk - reduced parentheses and whitespace a lot, why that?? initdisk - always display if LBA is supported (only for testing?) initdisk - LBA-Transfer error message extended, was that useful? initdisk - added debug dump of all partn w/o using debugprintf?? The last two things might be useful, but I would say the debug dump is so verbose that it should use a separate define, "ifdef DEBUG_INITDISK"...? I assume the other patches were only left-overs from during your BIOS/LBA/CHS bugfix experiments? Actually was there any real bug? Or just in BIOS? Now the patches which looked *nice* :-)) However, I would like to know *which* of them I already had as "bundled" diff files and which of them, if any, are already even in SVN...? dosfns, fatfs, proto - IsShareInstalled new "lazy check" (8/2008?) init-mod - add watcom C to BSS_INIT must-init-explicitly category initdisk - floppy type 6 handling added...? initdisk - DDT should have cyl+1, why? initdisk - too large to handle - message replaced, probably good initdisk - some comments added, drive param debug printf extended initdisk - total_sectors must use ULONG and cyl+1, not cyl...? initdisk - Error reading partition clarified by saying 02Xh hex initdisk - ca 1240/1270 init_readdasd *and DF_DISKCHANGE, DF_NOACCESS? dsk - re-enabled DF_NOACCESS, assuming unknown format bug was old? main - InitializeAllBPBs comment updated main - InitializeAllBPBs if FAT32 then init DBP as FAT32 I would say the InitializeAllBPBs and DF_NOACCESS would need some *testing* Did the patched kernel work at least as good as the unpatched kernel for you, in particular regarding first drive access after boot and regarding the use of FORMAT and similar tools? How about the two cylinder count +1 modifications? I remember we did talk it, but what did you find out? :-) Did you experience any *side effects* from the BSS_INIT change for *Watcom* ? I believe there was also a format *string bug* in some initdisk debug message or similar, is that already fixed in SVN or did I just overlook that your patched kernel has that fix as well? :-). So far my comments on your collected patches and your kernel :-). If you can make a version which has LBA enabled by default again, we should probably ask the people on BTTR and freedos-user to try it and see if it improves or worsens anything for them :-). Then I could start "chunking" the changes into per-topic ones and start uploading them into SVN as well. Thanks :-) I hope I didn't flood you with too many comments ;-). ... ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
