On Tue, 25 Mar 2008, Eric Auer wrote: <snippage here and below>
> Indeed. You may have to set your screen to show more lines or > use RERROR or similar tools to redirect stderr to actually > see all error messages, but even if you reveal the last error > message which has not scrolled away, it still helps... > > You can also try to make a minimal diff between 2.01.01a11 > and 2.01.01a12 to find out how they broke DJGPP compatibility. > I guess the SMAKE based CDRECORD build process might try to > automatically select CPU optimizations based on the CPU you > have at that moment. Using older DJGPP will limit this a bit. > Or you could try to block the CPU type detect/optimize step. I wonder if these changes are also in Debian's fork? There's a fork of cdrecord that the Debian guys did when the guy changed the license and maybe it stands a better chance of being ported back to DOS than the original? -uso. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel