When history file reaches 500 kb, TCC starts to have problems

May 30, 2008
80
0
Gerakas, Greece
After some troubleshooting in a couple of PCs, I found out that if your history file (setting HistFile) reaches about 500 kb (mine was 536.462 bytes), TCC starts to behave a bit erratically.

Symptoms at my pc were:
  • Very slow startup
  • dir and pdir commands would give out corrupted data (usually missing part of the name, or just displaying blanks
  • Folders could not be deleted (they were deleted very easily with cmd.exe though)

The obvious workaround was to delete the history file and start over. This is just a heads up, that there *is* a workaround, and there is also a problem that probably needs to be addressed.

Of course it is entirely possible that there was some problem with my environment, since the results (apart from the very slow startup at least) are not very reproducible in other PCs.
 

rconn

Administrator
Staff member
May 14, 2008
12,316
148
When history file reaches about 500 kb, TCC starts to have problems

> After some troubleshooting in a couple of PCs, I found out that if your
> history file (setting HistFile) reaches about 500 kb (mine was 536.462
> bytes), TCC starts to behave a bit erratically.
>
> Symptoms at my pc were:
> * Very slow startup
> * dir and pdir commands would give out corrupted data (usually missing
> part of the name, or just displaying blanks
> * Folders could not be deleted (they were deleted very easily with
> cmd.exe though)

I can't reproduce any problems with corruption, but you'll definitely (as
expected!) have very slow loads if you try to load a big history file into a
small history buffer. What is the size of your TCC history buffer (OPTION /
Command Line)?

Rex Conn
JP Software
 
May 20, 2008
11,292
95
Syracuse, NY, USA
When history file reaches about 500 kb, TCC starts to have problems

On Tue, 02 Feb 2010 20:08:19 -0500, gschizas <> wrote:

|After some troubleshooting in a couple of PCs, I found out that if your history file (setting HistFile) reaches about 500 kb (mine was 536.462 bytes), TCC starts to behave a bit erratically.
|
|Symptoms at my pc were:
|* Very slow startup
|* dir and pdir commands would give out corrupted data (usually missing part of the name, or just displaying blanks
|* Folders could not be deleted (they were deleted very easily with cmd.exe though)

I don't know about the other symptoms, but it seems any HistFile would slow down
start/exit because it's read at startup and written as exit. I don't usually
use a HistFile, but I just configured one with option. After the first exit,
the file was 143KB. And subsequent startups took about 4 seconds (compared to
the .06 second to which I am accustomed!).

SHRALIAS does a good job of always making the history available.
--
- Vince
 
May 29, 2008
565
4
Groton, CT
After some troubleshooting in a couple of PCs, I found out that if your history file (setting HistFile) reaches about 500 kb (mine was 536.462 bytes), TCC starts to behave a bit erratically.

Symptoms at my pc were:

...

  • dir and pdir commands would give out corrupted data (usually missing part of the name, or just displaying blanks
...

I've seen that symptom before, but didn't relate it to anything at the time.
Thanks for the clue.
 
May 30, 2008
80
0
Gerakas, Greece
I can't reproduce any problems with corruption, but you'll definitely (as
expected!) have very slow loads if you try to load a big history file into a
small history buffer. What is the size of your TCC history buffer (OPTION /
Command Line)?

Rex Conn
JP Software

Unsurprisingly, it's 500000 bytes for commands and 50000 for directory.
 
Similar threads
Thread starter Title Forum Replies Date
D What does the file "..\Everything\Run history.csv" store? Support 5
S Debugger Bat file call history Support 9
D Dir History file check Support 18
D Directory history file and global directory history Support 23
R History window wrong size, can't remember size change Support 12
T How to? retain command history across reboot? Support 6
nikbackm Speeding up the history dialog Support 6
D ParentDirectory does not update directory history Support 6
vefatica Command history search is off Support 7
D Directory History Window with wildcard search Support 3
R Long commands retrieved from command history have blank line when wrapped Support 20
Joe Caverly @HISTORY issues Support 4
vefatica Deleting entries in the command history popup? Support 3
H History and TPipe Oddness Support 3
D History and control-C Support 1
G Console exe up / down history Support 8
rps Cmd history recall Support 4
David McClelland Command history loosing entries Support 18
R history features. Support 6
rps How to? Shralias and producing history.sav, alias.sav .. Support 6
M Ctrl-C when using command line history does nothing Support 2
Charles Dye Ctrl-Shift-Up doesn't update directory history Support 1
vefatica ESC after recalling a command from history Support 3
T TCHelp executable history? Support 2
thorntonpg @blahblah added to history. Support 0
M Call History popup-window? Support 0
M HISTORY lessons ... Support 0
vefatica The help and IE's history Support 16
D Towards shared (dir-)history lists Support 3
vefatica Ctrl-Enter in command history window? Support 8
vefatica History recall turns off Quick-Edit Support 4
C history is getting deleted under unknown circumstances Support 9
R V19 - At startup, TCC save directory in the directory history list Support 2
T [TCC 18] Can't read nor write history Support 1
I Possible Bug: History /n Returns Nothing Support 3
jbanaszczyk Lost history Support 4
T history.sav Support 4
T How to? sort history in tcexit.btm Support 22
vefatica OT: Windows console history? Support 7
S directory history locks up TCC Support 3
R In addition to ALIAS /Z and FUNCTION /Z, HISTORY /Z? Support 1
E TCC History popups too small Support 0
C How to? Keeping all history lists Support 4
E Command History not showing on up arrow button Support 8
nikbackm HISTORY /R1 performance Support 3
T Selecting line from popup history without executing Support 8
A How to? Filter history list with unicode chars Support 0
vefatica WAD HISTORY /R, No closing quote? Support 10
vefatica WAD DO /S ... all dirs wind up in the history! Support 12
ehab aboudaya How to? Command Input history for each tab? Support 0

Similar threads