This is what the source has to say: #if 0 /* YES, this is too early, caused a sharing violation - 0.91q */ // Force_Drive_Recheck(); /* or is this too early??? - 0.91k */ #endif
So commented out as of 0.91q, to prevent a "sharing violation". I do not know what sharing violation means in this context. > Am 26.08.2024 um 08:19 schrieb Kirn Gill via Freedos-devel > <freedos-devel@lists.sourceforge.net>: > > Dumb question: Is there a source history that we can peruse and triage where > that call was commented out? > > -- > Kirn Gill II > Mobile: +1 813-300-2330 > VoIP: +1 813-704-0420 > Email: segin2...@gmail.com > LinkedIn: http://www.linkedin.com/pub/kirn-gill/32/49a/9a6 > > > On Mon, Aug 26, 2024 at 1:15 AM Bernd Böckmann via Freedos-devel > <freedos-devel@lists.sourceforge.net> wrote: > Re-enabling the Force_Drive_Recheck() after bootsector write fixes the format > problem for the uninitialized 720K floppy in a 1.44M drive. However, as this > was commented out most probably for a good reason, unconditionally > re-enabling this does not look like the best idea. Any proposals? > > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
