Hi, as far as I understand, this bug report tells us "works now but needs LOCK", and as far as I remember, SYS now contains LOCK. I think http://www.freedos.org/bugs/bugzilla/show_bug.cgi?id=1715 can be closed.
the curious thing is that the poster explicitly mentioned b9rc3 in combination with lock and locking was already addressed by Lucho for kernel 2032; b9rc3 contains 2032a ... So I don't understand and I'm not sure if this bug can really be closed.
Indeed, not only the kernel understands LOCK and UNLOCK now but also SYS does do a "lock logical volume" (CX = 84Ah) before writing the boot sector and "unlock logical volume" (CX = 86Ah) after that. The only reason I can why he had to issue the "lock" command before SYS I can think of is that he ran it on FAT32 and now the corresponding calls for FAT32 are needed (CX = 484Ah / 486Ah) instead. But MS-DOS 7.10 SYS.COM contains only the lock commands I already implemented in our SYS, it does NOT contain the corresponding FAT32 commands! And I just tried to SYS a FAT32 partition when running MS-DOS 7.10 - worked without problems and without a previouls LOCK command! What operating system and file system he ran SYS on?
Lucho
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
