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 straig
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 i
On 11/29/16 12:50, Travis Siegel wrote:
>
> 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.
>
But why the batch file in the first place? It
On Tue, 29 Nov 2016 13:02:59 -0800, H. Peter Anvin wrote:
> But why the batch file in the first place? It truly makes no sense: it
> pollutes the namespace equally, and can just cause problems (e.g. in the
> case of more than 9 arguments.) Not to mention slowing down a make.
Here's the thing: I,
Method 1 is the traditional DOS way of installing software.
Maybe some advanced usage of JOIN & SUBST is what you are looking for?
Another alternative (though slightly messy) would be to combine
Methods 1 & 4. By that, I mean, leave the *.bats in C:\DOS. The
*.bats will temporarily create a new
On 30/11/2016 8:54, Mateusz Viste wrote:
> Here's the thing: I, as a user, store lots of useful software on my PC.
> Many of these programs are so useful that I like to have them available
> immediately from anywhere: ZIP, UNZIP, UNRAR, UPX, NASM, TCC, OPTIPNG,
> QV, MPXPLAY, UHEX, GOPHERUS, LAM