TC 7.02 crash on Vista

[Just4In]

Today I installed v7.02, however it crashed twice when I RDP to my home PC (running Vista 32, the TC 7.02 is installed on the home PC), here is the event log:

Faulting application TOTALCMD.EXE, version 7.0.2.0, time stamp 0x2a425e19, faulting module ntdll.dll, version 6.0.6000.16386, time stamp 0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9, process id 0xdbc, application start time 0x01c7f16f1dd30fc1.

After I switched back to v 7.01, everything is fine so far.

[ghisler(Author)]

Unfortunately the given address isn't part of TC. What exactly do you mean with RDP? What did you try to do in Total Commander?

[Just4In]

Sorry for not making it clear

The TC 7.02 is installed on the my home PC ( OS vista 32 bit), and the TC is running. Right after I use Remote Desktop to connect to the desktop from my laptop (runing Windows XP), the Vista complained that the TC doesn't response and has to be closed, then Vista closed the TC and throw a APPCRASH error message.

I never encounter this problem with TC v7.01.

[ghisler(Author)]

It sounds like TC is trying to refresh some huge directory, or to connect to a network drive which doesn't respond (does the RDP connection add any network drives?).

[Just4In]

The RDP doesn't add any network drive. The largest directory contain 277 dirs.

[ghisler(Author)]

Currently I don't see any reason for this bug, I didn't add any new functions to TC 7.02 which react to system events.

What happens when you start TC AFTER establishing the RDP connection?

[Just4In]

Just try to click one of the files in TC.

It is in Application category of Event Viewer.

Error Info:

Fault bucket 507442776, type 1
Event Name: APPCRASH
Response: None
Cab Id: 0

Problem signature:
P1: TOTALCMD.EXE
P2: 7.0.2.0
P3: 2a425e19
P4: StackHash_b223
P5: 6.0.6000.16386
P6: 4549bdc9
P7: c0000374
P8: 000af1c9
P9:
P10:


Attached report:

Version=1
EventType=APPCRASH
EventTime=128336573476403745
ReportType=2
Consent=1
UploadTime=128336573756253745
Response.BucketId=507442776
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=TOTALCMD.EXE
Sig[1].Name=Application Version
Sig[1].Value=7.0.2.0
Sig[2].Name=Application Timestamp
Sig[2].Value=2a425e19
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_b223
Sig[4].Name=Fault Module Version
Sig[4].Value=6.0.6000.16386
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4549bdc9
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=000af1c9
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.0.6000.2.0.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=b223
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=39b46a738be909ff185f16ad44622962
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=03a0
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=5831197a0405f21d5a7ee8808b888d85
UI[2]=C:\Program Files\totalcmd\TOTALCMD.EXE
UI[3]=Total Commander 32 bit international version, file manager replacement for Windows has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Total Commander 32 bit international version, file manager replacement for Windows
AppPath=C:\Program Files\totalcmd\TOTALCMD.EXE

[Just4In]

It is possibly because TC trying to connect to a network drive which doesn't respond.

Right after install TC 7.02, I copy old wincmd.ini to install dir. in the old config file, there is a tab pointing to a network drive which is not available at the time.

But the same wincmd.ini is ok for TC 7.01.

[Kimon]

The RDP doesn't add any network drive. The largest directory contain 277 dirs.

Sometimes, RDP sessions redirect client drives as shared drives on the host.
Can this be the cause of it?
A "shared" drive, sure is a really slow network share, especially over a wan link.

[ghisler(Author)]

I have just tried to reproduce the error, by connecting from an XP Pro system by RDP to a Vista Pro system. TC 7.02 was running, and there was no crash at all. I can use TC without any problems via the RDP connection.

Have you tried what I suggested (start TC after establishing the RDP connection)?

[Just4In]

The two crashs happened when the TC already started on host Vista.

Host is Vista Ultimate 32bit, client is XP pro.

I will updated 7.01 to 7.02, try to reproduce the error.

[Just4In]

Yeah, it happened again right after I update TC to 7.02, with or without network drive mapping.

I got the window error screen captured, but seems the forum doesn't allow attachment.

If I RDP to Vista first, then start TC, there wouldn't be any error. The error only happen when you start TC (in Vista) first, then RDP to it.

Switched back again to 7.01, everything is fine.

The hardware of the Vista machine:
Inter Q6600, 4x1G RAM(only 3G recognied through), EVGA NVIDIA 8600GTS, 4x320G Raid 0+1

[Just4In]

Just found another wired problem:

I have a NAS (ReadyNAS NV+) in my home network , I use Super Flexible File Synchronizer to sync the files between the NAS and my home PC(Vista Ultimate 32), NAS appears as a network mapping drive in Vista.

After excuted Super Flexible File Synchronizer and closed it, I found that I am not able to use TC to delete not empty directory in the NAS, anyway I can delete file or empty directory(in the NAS too), I can also copy files or directory to it.
In the mean time, I can perform all the actions above in Windows Explorer.

After restart the Vista machine, TC back to normal again(I mean it can delete any file or directory in NAS again).

I guess Super Flexible File Synchronizer put some lock onto the NAS file, the lock prevent TC to delete any not empty directory, even at the time the Super Flexible File Synchronizer already been closed. Anyway the lock can't prevent Windows Explorer to function normal.

[ghisler(Author)]

2Just4In
Since it happens only when TC is already started, it may be due to the new function to update environment variables when the system changes them. Such a change happens also when you establish an RDP connection. Therefore please try to turn off the updating of environment variables: Choose Configuration - Change settings files directly, then add under [Configuration] the line
UpdateEnv=0

If this helps, then check your mail - I created a special test version for you where I changed the update env function a bit to avoid infinite loops. I also put it in a try...except block to catch any exceptions.

Please test as soon as possible if this helps! I'm currently preparing TC 7.02a, and it would be nice if you could fix your problem in it...

[Just4In]

Great, Adding line to config file works for v7.02! no more RDP problem.

The pre702a.exe have the same problem, but adding "UpdateEnv=0" also solve the problem.