what is the maximum length of masm 16 file Name

[Magnum]

As far as XP is concerned, long file name progs do NOT work, both Masm and Tasm produced.

And using Senor Dave's code.

Code: [Select]

C:\16_BIT>longmasm7.com
Bad Command or file name

C:\16_BIT>


[FORTRANS]

Hi,

   Works here with Windows 98, Windows 2000, and Windows XP.

Code: [Select]

G:\WORK>COPY TEST44.COM BLABLABLABLA.COM
        1 file(s) copied.

G:\WORK>                BLABLABLABLA
G:\WORK\BLABLA~1.COM

G:\WORK>
Steve

[japheth]

IIRC, the NTVDM supports LFNs, but XP's built-in DOS-Extender DOSX does not automatically translate those functions - which is a regression compared to Win9x.  So it might be that some old DOS-extended programs ( i.e. Tasm ), which were written in the Win9X era, may indeed have problems with LFNs on XP.

[dedndave]

it's a .COM (tiny) program
shouldn't matter which assembler is used, as it does not have a header

adding ".com" to the end of the commandline probably isn't helping, though

it may be a matter of xp version
i have xp mce2005 sp3, which is a "professional" edition of xp
it may not be the same on xp home editions

[FORTRANS]

Hi,

   I seem to recall from another thread that he has short filename
support turned off.  That could hurt things like Dave's program.

Regards,

Steve N.

[jj2007]

.model tiny
.code
   org 100h
start:
   mov ah, 09h   ; write string to STDOUT
   mov dx, 82h   ; get command line
   int 21h      ; show it... ;-)
   ret
end start

Commandline:
HelloWorldDOS.com And I told you that long filenames are fine on Win7-32....

Result:
And I told you that long filenames are fine on Win7-32.... ;)

[Magnum]

Thanks Steve,

I temporarily re-enabled 8.3 name creation and the progs run.

http://support.microsoft.com/kb/121007

Why I turned it off.

Code: [Select]

The creation of 8.3 filenames and directories for all long filenames and directories on NTFS partitions may decrease directory enumeration performance.

It would be nice if I could actually test if performance did actually improve.

Andy


[dedndave]

it would seem that the console is a 32-bit console window, until you run a 16-bit program under it
after that, it's a 16-bit console

so - i doubt you really want to optimize your system for 16-bit programs to run

[Magnum]

Read this. Nothing to do with 16 bit programs.

http://support.microsoft.com/kb/121007

[dedndave]

i read that
not sure how much difference it makes though

let me put it this way...
i haven't disabled 8.3 indexing on my machine, and i'm happy with the performance
not to say it couldn't be faster, of course

as for the per-instance console window

Code: [Select]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Masm32\Asm16\16-Bit Templates => blahblahblah
Hello World !

C:\Masm32\Asm16\16-BIT~1 =>something changed from before to after
it would seem that the console became "8.3 aware", only after a 16-bit program was executed

[dedndave]

in the past, i have tried disabling indexing, altogether
performance improved, in some respects, but suffered in others
i no longer do that

[FORTRANS]

Hi,

it would seem that the console is a 32-bit console window, until you run a 16-bit program under it
after that, it's a 16-bit console

   Yes.  As far as I can deduce, CMD.EXE runs COMMAND.COM to
support 16-bit programs.  Run a program that lets you shell out
to a command line and run "MEM /D | MORE".

Regards,

Steve N.

[dedndave]

shell - interesting notion, Steve

Code: [Select]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Masm32\Asm16\16-Bit Templates => cmd /c blahblahblah
C:\MASM32\ASM16\16-BIT~1\BLAHBL~1.COM

C:\Masm32\Asm16\16-Bit Templates =>so, if you want to run a 16-bit program without making it a 16-bit window   :P
if you run command.com, it converts to 16-bit, but....

Code: [Select]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Masm32\Asm16\16-Bit Templates => cmd /c command
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\MASM32\ASM16\16-BIT~1 => ver

Microsoft Windows XP [Version 5.1.2600]

C:\MASM32\ASM16\16-BIT~1 => exit

C:\Masm32\Asm16\16-Bit Templates =>

[Magnum]

cmd.exe gives a larger exe program size than command.com.

[dedndave]

much larger, i suspect
but - command.com also requires NTVDM.dll