ien
perditi...@gmail.com wrote:
> Thank you. I will try to get a fix implemented this week. Your patch
> corrects supporting the 32nd drive if provided as value 1 thru 32 (0 is
> default) but still doesn't handle if passed as ascii value ` (0x60).
>
> Jeremy
>
> On
Hello,
I found a small problem in ioctl code that leads to drive number 32 to not be
usable with device related functions (int 0x21, ah=0x44..) and leading to
returning information about another drive without signaling any error. As I
suppose this is not widely used (drive 27 to 32 are most oft
Hello,
I took a look at this problem, and I think it comes from check done at
inthndlr.c:1657: if (dpbp != NULL && ISFAT32(dpbp)))
As the dpbp content has still its default initialisation value (filled with 0
during kernel initialisation), dbp_fatsize is 0, leading to error 0x0207.
In that case
Hello,
I did some search about the
http://sourceforge.net/tracker/index.php?func=detail&aid=2901916&group_id=5109&atid=105109
problem and find one potential reason for that: in function to convert from sft
to fnode, a value is used before being initialised. This lead to a drive to not
be cons
