The file is ASCII but has a string of 208 NULs near the beginning. HEAD can deal with it TYPE (output snipped below) can't.
Garbage from TYPE
- Thread starter vefatica
- Start date
If you send the file to support@jpsoft.com (or attach it here) I'll take a look at it.
But to be honest I don't particularly care if TYPE's output is different from HEAD for binary files (which TYPE doesn't support anyway unless you use /X).
But to be honest I don't particularly care if TYPE's output is different from HEAD for binary files (which TYPE doesn't support anyway unless you use /X).
Not a very interesting file. AS I said, plain ASCII except for a 208-byte string of NULs. But those nulls make TCC go nuts ... dumping stuff from god knows where.
P.S. Was TYPE always that fast or did the latest update from MS make the console a lot faster? It takes 0.7 sec to dump that 39000-line, 3.4MB file to my 9000-line console ... even faster in TCMD!
P.S. Was TYPE always that fast or did the latest update from MS make the console a lot faster? It takes 0.7 sec to dump that 39000-line, 3.4MB file to my 9000-line console ... even faster in TCMD!
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
| L | FTYPE in TCC, less quirky than in cmd.exe | Support | 3 | |
|
Using TYPE with non-English text | Support | 22 | |
| V | TYPE behaving randomly | Support | 10 | |
|
|
@DRIVETYPE shows IMDISK as 3 Fixed Disk, not 6 RAM Disk | Support | 6 | |
| V | TYPE resets console tab settings | Support | 14 |