Hi, >> So here is a list of tickets for which I believe that they can >> get updated, closed or whatever. Please comment and update :-) >> >> https://sourceforge.net/p/freedos/bugs/153/ crash at dir change >> (may 2016) probably general emm386 versus disk fail, file there
> Again, I don't see the point of loading (J)EMM386 (by default) at all > since many machines seem to have problems with it. > N.B. This (2016!) bug report is regarding FD 1.0 (2006), so it's > probably pointless. As much as I hate to say it, the resolution should > be "don't use EMM386" and/or "upgrade to 1.2-pre". EMM386 is useful because it provides upper memory. having more memory below 1 MB is very useful for real mode operating systems. >> https://sourceforge.net/p/freedos/bugs/151/ sys seems to fail to >> update the boot sector or mbr (?) (may 2016) > Same dude as previously, using old (unsupported) FD 1.0. Probably > should give same resolution (and close!). FreeDOS system installer AUG 10 2011. certainly not FD 1.0 >> https://sourceforge.net/p/freedos/bugs/147/ interlnk failure >> (feb 2016) tom lists a patch, where in the pipeline is the patch? > Jeremy said, "Tom's workaround will be in svn kernel soon, but I need > to do some more testing as I'm still getting crashes ...". > Ulrich claimed at that time that the following (esp. "/LOW") worked > around the issue entirely: > DEVICE=C:\UTIL\INTERLNK.EXE /AUTO /NOPRINTER /LOW this is about an operating system bug. having a workaround doesn't solve the bug. btw: best workaround is 'use a serious operating system' > N.B. An old FD technote suggests using File Maven instead: > http://www.freedos.org/technotes/technote/archive/108.html this sucks. File Maven is in no way a replacement for interlnk; just like FTP is not a replacement to a network drive. >> https://sourceforge.net/p/freedos/bugs/92/ welcome screen of distro >> mis-spells pasquale villani as pasqualle... > Trivial, should be closed. should be CORRECTED, then closed. >> https://sourceforge.net/p/freedos/bugs/88/ set /p fails to close pipe, >> leading to creative sources of problems :-p > "set /p" is non-standard, and FreeCOM is not exactly actively > maintained, so probably close as "wontfix". (As much as I hate to say > it, there's probably better tools to do similar functionality. Ask > Jerome or take a look at J. Hoffman's DOSUTILS.) nothing of FreeCOM is exactly actively maintained. Are you suggesting to no longer fix bugs? or are you suggesting that *you* are not able/interested/... to fix bugs. >> https://sourceforge.net/p/freedos/bugs/63/ some interesting but totally >> forgotten xms related lbacache failure on via c7 cpu, unlikely to be >> ever looked at unless somebody has a via c7 to test... > Just close it, we can't confirm it or test it anyways, it's just way > too obscure. AMD allegedly has 20% of the x86 market, but VIA has > almost none (esp. for end users). should be closed. not because of market share, but because the bug report ends with 'I got mail again, problem solved, and I still can't answer. Please CLOSE this BUG.' >> https://sourceforge.net/p/freedos/bugs/29/ discussion whether xcopy >> should copy timestamps while copying and under which conditions... > Probably should just use DJGPP Coreutils "cp -p" instead. (See > /current/v2gnu/fil41br2.zip .) BS. XCOPY should work like expected. read the manifest. >> https://sourceforge.net/p/freedos/feature-requests/61/ WISH live CD >> we probably made one since 2012, or not? > With RUFUS (as mentioned), you can do live USB, which is similar > functionality (and less cramped than floppy). Close this bug! there should be a live CD or a way to make a useful USB stick with FreeDOS, without the need to install it. there is *no* excuse for the having a live boot medium. >> https://sourceforge.net/p/freedos/feature-requests/56/ WISH boot USB >> the current distro edition is offered as USB image as far as i know! > There are several (third-party) ways to do this already, and they are > (semi-)well known. Close! exactly. several, semi known. this project is in real bad shape. Tom ------------------------------------------------------------------------------ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
