Re: [Freedos-user] Two non-bug reports.
Christian, don't get me wrong, I very much appreciate yours (and those of many people) when it gets technical. I just don't know if plain FreeDOS users end up getting a simple question when they are looking for it. Anyway, not many people answered, so perhaps my appreciation is wrong and everything is correct as it is. Aitor 2009/7/5 Christian Masloch : Users apparently don't want technical details on the Freedos-user list however. >> >>> I don't think so: some want, some do not. The question is that >>> currently there's no way to know about it. So I am almost decided to >>> create that freedos-basic list, so that technical details can run here >>> as usual. >> >> The solution is much easier - discuss technical details on >> freedos-devel and basic things on freedos-user as usual. >> >> Maybe recently more people discussed technical details on >> freedos-user because there is more activity there than on >> freedos-devel? Of course this should not be a reason to >> migrate threads or even start yet another list... ;-). > > Often threads started normal on Freedos-user but the discussion got > technical later on. I don't want to be accused of "geekifying" anyone's > list, so I'll simply stop writing any answers here that might be useful to > developers for fixing the problem. Good that I'll never have to provide a > "user" mailing list for my software. > > -- > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Two non-bug reports.
>>> Users apparently don't want >>> technical details on the Freedos-user list however. > >> I don't think so: some want, some do not. The question is that >> currently there's no way to know about it. So I am almost decided to >> create that freedos-basic list, so that technical details can run here >> as usual. > > The solution is much easier - discuss technical details on > freedos-devel and basic things on freedos-user as usual. > > Maybe recently more people discussed technical details on > freedos-user because there is more activity there than on > freedos-devel? Of course this should not be a reason to > migrate threads or even start yet another list... ;-). Often threads started normal on Freedos-user but the discussion got technical later on. I don't want to be accused of "geekifying" anyone's list, so I'll simply stop writing any answers here that might be useful to developers for fixing the problem. Good that I'll never have to provide a "user" mailing list for my software. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Two non-bug reports.
Hi Aitor, >> Users apparently don't want >> technical details on the Freedos-user list however. > I don't think so: some want, some do not. The question is that > currently there's no way to know about it. So I am almost decided to > create that freedos-basic list, so that technical details can run here > as usual. The solution is much easier - discuss technical details on freedos-devel and basic things on freedos-user as usual. Maybe recently more people discussed technical details on freedos-user because there is more activity there than on freedos-devel? Of course this should not be a reason to migrate threads or even start yet another list... ;-). Eric -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Two non-bug reports.
Hi, 2009/7/4 Christian Masloch : >> First non-bug: LFN-EN utilities don't work with my FAT32 partition >> under FreeDOS. >> >> After examining the source code, it turns out that the logic was coded >> in 1999 when >> the only DOS that could handle FAT32 was MS-DOS. When run under >> FreeDOS, the utilities >> assume no FAT32 support, so they misidentify the partition as FAT12. >> >> For test purposes, I made a version that accepted the vendor byte FD >> (FreeDOS) instead of >> FF (MS-DOS) and it worked, but anything used in production would have to >> use a different >> method to determine whether FAT32 is supported (FreeDOS comes both ways, >> and there are several DOSses today that support FAT32.) >> >> There is similar logic that determines which versions of DOS require >> volume locking >> (MS-DOS 7 or later.) >> >> Fortunately the LFN-EN utilities are open source, so someone could fix >> this. > > A reliable FAT32 test method is to check whether a common subfunction of > Interrupt 21h, Function 73h (FAT32 extensions) is supported. I disregard > any method that works per DOS version. Users apparently don't want > technical details on the Freedos-user list however. > I don't think so: some want, some do not. The question is that currently there's no way to know about it. So I am almost decided to create that freedos-basic list, so that technical details can run here as usual. Cheers, Aitor -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Two non-bug reports.
> First non-bug: LFN-EN utilities don't work with my FAT32 partition > under FreeDOS. > > After examining the source code, it turns out that the logic was coded > in 1999 when > the only DOS that could handle FAT32 was MS-DOS. When run under > FreeDOS, the utilities > assume no FAT32 support, so they misidentify the partition as FAT12. > > For test purposes, I made a version that accepted the vendor byte FD > (FreeDOS) instead of > FF (MS-DOS) and it worked, but anything used in production would have to > use a different > method to determine whether FAT32 is supported (FreeDOS comes both ways, > and there are several DOSses today that support FAT32.) > > There is similar logic that determines which versions of DOS require > volume locking > (MS-DOS 7 or later.) > > Fortunately the LFN-EN utilities are open source, so someone could fix > this. A reliable FAT32 test method is to check whether a common subfunction of Interrupt 21h, Function 73h (FAT32 extensions) is supported. I disregard any method that works per DOS version. Users apparently don't want technical details on the Freedos-user list however. Regards, Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
