> If the driver status > information gets displayed somehow, or there is some sort of "interaction" > between the drives in the software, though, it would always assume things > were consecutive.
Yes. I think I've seen drivers which display messages like "Installed <num> units, first drive <letter>:", which would then happen to display misleading information. However, I'm not aware of any drivers that interact with or access the DOS drives assigned to their units using DOS. There might be such drivers. But I think that the _majority_ of drivers would either work flawlessly if they were assigned non-consecutive drives, or only with minor display errors as described above. Because it therefore might be useful to behave in that way, I proposed to have at least a command line option to assign non-consecutive drives. > True, but there are several source code examples on how to do it, > including DEVLOAD itself, so you can't use the "I don't know how" excuse, > only the "I don't want to". In the case of DEVLOAD it's not necessarily as simple as copying the source code because of the licence's restrictions. (Even if one were to develop a program using assembly language or even NASM.) Other than that, DEVLOAD can of course always be studied as reference implementation. Regards, Christian ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
