Hi again, On Tue, Oct 2, 2018 at 12:24 PM stecdose <stecd...@gmail.com> wrote: > > I have tested untardos.exe, it is great. > But running it the first time on real hardware untardos locked the > system with a "invalid opcode" error.
Are you using JEMMEX, perhaps? (X=TEST I=TEST) Otherwise, I'd like to know what shell, kernel (ver /r), memory managers, etc. are loaded (and what cpu, how much RAM, etc). Obviously if that problem is reproducible, it should be isolated and then avoided or fixed. I'll admit to not having used UNTAR lately, but it always worked fine for me. (Maybe you grabbed it from FTP incorrectly, ASCII instead of Binary mode??) Here's what I get from a quick re-download from iBiblio: c:\rugxulo>md5sum untardos.exe 0858daf85c4b3401724bdf56ae227122 untardos.exe c:\rugxulo>crc32 untardos.exe 0x6503EA89 (22,439) _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
