On 6/12/2016 7:23, Robert Riebisch wrote:
> I have used http://www.bttr-software.de/freesoft/menu.htm#linkln for
> many years.
Yeah, that sounds like the one I was thinking of (and the Free
Software list is probably where I came across it). I don't think
I ever used it (stopped using DOS around t
Hi Jason,
>> To achieve this, I know of four ways. Each comes with some limitations.
>
> Simtel had two programs that create links: exelink2.zip and linkln10.zip.
> I though I had the former, but apparently no longer; iirc it used a text
> file to store the links and a TSR to hook the EXEC call.
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
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 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,
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 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/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 Wed, 23 Nov 2016 19:25:52 +, Mateusz Viste wrote:
> I am trying to compile the FreeDOS kernel from svn's tag ke2042, but it
> appears that build.bat fails to assemble several files. For instance:
>
> nasm -DTC2 -DWITHFAT32 -i../hdr/ -DXCPU=86 -f obj floppy.asm
> nasm: error: more th
Hello group,
I am trying to compile the FreeDOS kernel from svn's tag ke2042, but it
appears that build.bat fails to assemble several files. For instance:
nasm -DTC2 -DWITHFAT32 -i../hdr/ -DXCPU=86 -f obj floppy.asm
nasm: error: more than one input file specified
nasm: error: more than
10 matches
Mail list logo
