On 11/29/2016 3:32 PM, H. Peter Anvin wrote: > On 11/24/16 00:59, Mateusz Viste wrote: >> Hi, >> >> Your problem is related to the fact that your "nasm" command doesn't call >> nasm.exe directly. Instead, it calls a batch file named nasm.bat which >> has been placed in your %PATH% by the FDNPKG installer. This nasm.bat >> file is pretty straight-forward: >> >> @ECHO OFF >> C:\DEVEL\NASM\NASM.EXE %1 %2 %3 %4 %5 %6 %7 %8 %9 >> >> While in theory such trick should work (and it does work with most other >> utilities out there), somehow it doesn't play out right with nasm. Simply >> edit your CONFIG.BAT to set its XNASM variable to the full path to your >> copy of nasm.exe, and you're done. Enjoy! >> > And pray tell, why? > > -hpa > > > Because, apparently the nasm being called isn't in c:\devel\nasm, so change the path in the nasm.bat file to point to the proper place, and the problem should be solved. Either solution will work.
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ------------------------------------------------------------------------------ _______________________________________________ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
