Hallo Bart,

If the ZIP drive has its own device driver (with DEVICE=) than whatever is
in floppy.asm has no influence. Or is it really handled via the BIOS as drive A: or drive C:?

When BIOS boots through it, yes. But even if not, its driver probably hooks Int 13h, so fl_diskchange() has to ask it.


In any case a change to init_readdasd in initdisk.c (+ your change in
dsk.c) may be more appropriate than floppy.asm since the changeline status
of a drive won't change after booting -- and I don't think DOS is advanced
enough to handle hotplugging between non-changeline and changeline floppy drives...

:) Of course, but the point is that the device driver hooks Int 13h, so then asking it whether it supports changeline in fl_diskchange() looks reasonable to me.


I fixed the two debug input redirection bugs with the patch below. Now the redirected output contains two consequtive carriage returns though. Maybe there is a way to remove one of them?

Why is echo_char(LF, sft_idx) called in read_line_handle()? Isn't there a danger than it writes the LF to the input file?

Lucho

(from http://linux.tu-varna.acad.bg/~lig/freedos/CVSPATCH.TXT):

--- cvs/kernel/kernel/chario.c2004-01-27 22:07:26.000000000 +0200
+++ src/kernel/kernel/chario.c2004-03-18 09:30:50.000000000 +0200
@@ -320,7 +320,7 @@

  int echo_char_stdin(int c)
  {
-  return echo_char(c, get_sft_idx(STDIN));
+  return echo_char(c, get_sft_idx(STDERR));
  }

  STATIC void destr_bs(int sft_idx)
@@ -410,6 +410,7 @@
      switch (c)
      {
        case CTL_F:
+      case LF:
          continue;

case RIGHT:


------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Reply via email to