Hi, On Thu, Oct 11, 2018 at 7:02 AM Tom Ehlert <t...@drivesnapshot.de> wrote: > > on 12. September 2018 um 03:14 schrieben Sie: > > > On Tue, Sep 11, 2018 at 8:12 AM Tom Ehlert <t...@drivesnapshot.de> wrote: > >> > >> > The GNUC version seems to mostly work, > > > I didn't quite have the time or energy to test TC or Watcom builds > > yet. > often this is not needed; bugs in one version of FreeCOM will most > likely also occur in the other versions (compilers should take care of > this). fixing this one bug in GNU freecom most likely also fixes the > watcom bug. > > so once you locate an error in one FreeCOMxyz, please write down > the failing batch, and circumstances how to reproduce. > > once bugs are reproducible the fix is usually easy.
newwget.bat is a dependency of some "tests" (e.g. "tests c89") because the older Wget won't work on Github anymore. Trying it again, it does seem to work with TurboC and Watcom builds ... but not the GNUC / GCC one! > > Did you want a list of "successful" tests?? Or just the failures, > > right? > just the failures. If you type "tests", it should show you a list of various tests you can run. But it's brittle, and some things have regressed, so some things don't work (or aren't obvious). It wasn't meant to be super obvious or useful (necessarily), just some random stuff I tried. The tests were moreso for making sure the pieces all worked together correctly, not necessarily for installing and using the programs "as is". (Also, it was to try to pretend to be halfway reproducible for some things and test some compilers.) > > You have the same files that I do (now), if you think it makes > > much of a difference (since 0.6). > > but you refuse to tell te failing tests. any reason for this? newwget.bat was (part of) the failing test. Actually, that's a stub, but you know what I mean. The other errors I was getting were irrelevant (spurious, aka fake), so it still worked but outputted some weird text to the screen. > >> > However, trying to run NEWWGET.BAT seems to hang > >> > forever. > >> what f**king NEWWGET.BAT? not part of my copy of this world famous > >> METADOS. > >> mind sharing this with us so we might try to reproduce this? BTW, part of the problem is trying to use both FTP and Wget. So don't be surprised when it's mixing both. Somewhat confusing but can't be easily helped. I wish everything was available from FTP, but it's not. Anyways, at startup, you can "set QUIET=" (to unset) for some more verbose output. Technically, you can do that at any time for FTP, but Wget uses its own wgetrc file, so that's why you have to do it at startup (or else edit the text file manually). So "maybe" that will be more verbose and helpful for you?? > > Aug. 21 email (in last thread about previous prerelease) had a link to > > my DropBox, which I explicitly mentioned here. Inside > > "network/stubs.zip" is indeed found "newwget.bat" (which is unpacked > > to "%RAMDRIVE%:\utils" at bootup). Are you still using only (old) 0.6? > > It was because of your alleged confusion (0.6 or newer?) that I > > uploaded this for you. > in the age of internet it helps to post links to the uploaded stuff. > > remember: this is a mailing list. it's content should still make sense > when someone else reads this 2 years later. Here's the DropBox link (again), in case it wasn't obvious: * https://www.dropbox.com/s/6whjgmb9xhdgw29/metados-0.7.zip?dl=0 BTW, "2 years later" is somewhat unfairly optimistic. Back in November (almost a year ago), MetaDOS 0.6 relied exclusively on the old (2008) DJGPP build of Wget 1.11 already mirrored on iBiblio for years. And it worked fine, but then Github and SF.net changed protocols or whatever, so now it won't work. So even things that do work will regress or break due to unforeseen external circumstances. It could be anything (QEMU bug or SeaBIOS bug or abandoned Windows port). I guess nothing lasts forever. (Heck, I don't use Windows 10 32-bit, but Andris from DJGPP said even there NTVDM has been broken for months. I don't know the details or if they fixed it, but last I heard it was still broken. See what I mean? Everything breaks without warning.) _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
