DIR /Z Causes Application Error In At Least One Directory

Jan 9, 2009
40
0
#1
In a stand-alone 4NT window in:

TCC 10.00.59 Windows XP [Version 5.1.2600]
TCC Build 59 Windows XP Build 2600 Service Pack 3
Registered to Carl Johnson - 1 System License

I get the following Event Viewer Application Error when executing DIR /Z on at least one directory. Works ok on some other directories I tried. I viewed the DESCRIPT.ION file for the directory with LIST thinking there might be a bad record in the file but I don't see anything obvious, although I don't know specifically what to look for that might cause this problem.

Carl

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 03/22/2009
Time: 11:27:04
User: N/A
Computer: ASUS
Description:
Faulting application 4nt.exe, version 10.0.0.59, faulting module takecmd.dll, version 10.0.0.59, fault address 0x0000597c.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 34 6e 74 ure 4nt
0018: 2e 65 78 65 20 31 30 2e .exe 10.
0020: 30 2e 30 2e 35 39 20 69 0.0.59 i
0028: 6e 20 74 61 6b 65 63 6d n takecm
0030: 64 2e 64 6c 6c 20 31 30 d.dll 10
0038: 2e 30 2e 30 2e 35 39 20 .0.0.59
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 30 30 35 39 t 000059
0050: 37 63 0d 0a 7c..
 
Jan 9, 2009
40
0
#2
This as an addendum to my original post.

I initially forgot that I still have 4NT V6.01.241A (need for FILEWRITEB in some BTMs) and 4NT V8.01.70 installed, so I tried the DIR /Z command in the V10 "problem directory" and the command worked properly in both the above mentioned older 4NT versions.

Carl
 

rconn

Administrator
Staff member
May 14, 2008
10,582
97
#3
DIR /Z Causes Application Error In At Least One, But Not All, Directories

> I get the following Event Viewer Application Error when executing DIR /Z
> on at least one directory. Works ok on some other directories I tried. I
> viewed the DESCRIPT.ION file for the directory with LIST thinking there
> might be a bad record in the file but I don't see anything obvious,
> although I don't know specifically what to look for that might cause this
> problem.
Not reproducible here. Can you email me the DESCRIPT.ION file for that
directory?

Rex Conn
JP Software
 
Jan 9, 2009
40
0
#4
I figured it would be difficult to resolve this problem without the DESCRIPT.ION file, but I was hoping that maybe the exception address would provide a clue. Unfortunately that directory is on a TrueCrypt volume and the DESCRIPT.ION file includes many passwords that I don't want to send. Since I can view the DESCRIPT.ION file with LIST and my text editor I could edit out all the passwords but then the file would be different. I suppose I could change all the passwords in all the different places after sending the file but that would be a hassle.

I think what I'm going to do for now is to create a temporary TrueCrypt volume and move the files one-by-one to the temporary volume and run DIR /Z after each move to hopefully isolate the problem.

Thanks for the reply,
Carl
 

rconn

Administrator
Staff member
May 14, 2008
10,582
97
#5
BitPusher wrote:

> I figured it would be difficult to resolve this problem without the DESCRIPT.ION file, but I was hoping that maybe the exception address would provide a clue. Unfortunately that directory is on a TrueCrypt volume and the DESCRIPT.ION file includes many passwords that I don't want to send. Since I can view the DESCRIPT.ION file with LIST and my text editor I could edit out all the passwords but then the file would be different. I suppose I could change all the passwords in all the different places after sending the file but that would be a hassle.
>
> I think what I'm going to do for now is to create a temporary TrueCrypt volume and move the files one-by-one to the temporary volume and run DIR /Z after each move to hopefully isolate the problem.
I need a stack trace, not just a single address (which in this case just
points to a utility function that's called in several hundred places).

Normally if TCC crashes, it creates a TCC.GPF file that has the stack
trace & all of the register values.

Rex Conn
JP Software