Some web browsers do not like an HTML file to end with a EOF byte. Technically, the browsers are broken, but it doesn't do any good to point fingers and jump up and down. The offending browsers (NS Navigator 4.x for Win, and IE for Win) will display a "box" at the end of the page when they encounter the EOF byte. Note that NS 4.61 for OS/2 does not have this problem!
Back when I used to try to use E.exe to edit HTML files, I'd have to go back and edit the file with some other utility and resave it to get rid of that box. It used to drive me nuts, but I never really tried to pin down what was causing it. Then I switched to the MED editor and I hadn't thought about this for a while, until the topic came up recently in conversation with someone else who figured out the cause.
Here's a test file:
created with E.exe, and containing the EOF marker (1Ah).
It looks just fine if viewed via NS 4.61 for OS/2.
But, if viewed with NS 4.76 for Windoze, it shows the box char at the end.
To further confuse the issue, if this file is served by an ftp server, it is rendered OK again by NS 4.76/Win.
So it's only a problem if an HTML file is served via http and rendered by the Win version of NS.
Felix Miata compiled this table:
Appends 1Ah Yes No ---------------------------------------- PC DOS 6.1 EDLIN.COM X PC DOS 2000 E.EXE X OS/2 E.EXE X OS/2 EPM.EXE X OS/2 TEDIT.EXE X Norton Commander Internal X M$ DOS 6.22 EDIT.COM X Freeware TED.COM X WordPerfect 6.2 for DOS X Composer 4.61 for OS/2 X Totals 3 7The 'Fix'
There is also a modified version of the e.exe that ships with MCP FP1 (XR_C001) at Paul's server.
|Return to home.|
|Send mail to Al about this page.||
Last updated 30Apr2013