Access Violation

[TonyWhitley]

I've recently started getting access violations with 5.5:

EAccessViolation in module TOTALCMD.EXE at 00018048
Access Violation at address 00419260 Read of address 0344FFFE

I updated to 5.51 and now it happens on start up (((

Exception EReadError in module TOTALCMD.EXE at 0001076B
Error reading SplitPanel.Cursor: Access violation at address 0041EF64. Read of address 0344FFFE

Help! I can't work without it.

[Geoffrey]

Did you install anything before it started ?

I got something similar with my browser (couldn't go back !), and it was due to a plugin. Maybe you tried to install an unofficial TC plugin ?

Regards,
Geoffrey

[TonyWhitley]

No, I'm using a vanilla TC install. The good news is that it's come back to life - I just hope it lasts.

[ghisler(Author)]

Exception EReadError in module TOTALCMD.EXE at 0001076B
Error reading SplitPanel.Cursor

This error means that TC couldn't read its EXE file during runtime, or that an older version of the EXE is somewhere in your PATH. Some virus scanners may also cause such behaviour (by blocking read access to the EXE).

[realtime]

I am also using TotalCmd v5.51 (with a few addons etc) and cannot live with out it.

This problem has now happened to me 3 times. Each time I used old explorer to find my WinCmd.ini, searched for the section which coresponds to my Video Resolution: [1280x1024 (10x20)]
I then deleted the entire section.

TotalCmd.exe then started up without any problems.

[ghisler(Author)]

Another case when this can occur is if you have an older version of TC somewhere in your PATH, or in the current directory. Windows may then try to extract the icon from the wrong EXE, and fail with the above error because the cursor is in the wrong location...

[realtime]

This can be a real pain.

I never have more than the most recent version (v6.02) of Commander available in my path. No multiple executables.

I have had this error with each of the last 3 or 4 versions though. Currently the AV happens at address 0x041A960. As usual, clearing out all my display resolution info from my WinCmd.ini file clears the problem.

Maybe one day, the problem will get fixed.

[ghisler(Author)]

Do you have a copy of the bad resolution section? If yes, can you post it here please? Maybe I can reproduce the error then. Thanks for your help!

[realtime]

I'll do that next time it happens

[realtime]

Happened sooner than I expected

Here are the details from WinCmd.INI

[1024x768 (8x16)]
CompareX=0
CompareY=0
CompareDX=940
CompareDY=740
CompareMax=0
CompareDivider=339
SearchX=236
SearchY=171
SearchDX=551
SearchDY=508
SearchMax=1

FYI: =========================================
The OS is Win2000 (with all latest MS fixes). I have only 1 version of TC installed and it is v6.02. There are no other display sections in the WinCmd.ini (because I delete them all when this error happens). The AV message reports:
Exception EReadError in module TOTALCMD.EXE at 000117BF.
Error reading SplitPanel.Cursor: Access violation at address 0041A960. Read of address 02E4FFFE.

(Also, - hopefully irrelevant - I have the TightVNC Server version 1.2.9 service running. I mention this because I have had some occasional customer problems with software I have developed. The problems occurred when moving the cursor and the VNC service was active. Difference is that my customer problems have a remote session active. THERE WERE NO active VNC sessions when the SplitPanel.Cursor AV happened. )

Any other info gladly supplied on request.

[SanskritFritz]

I suspect there is an error in your file system (a resource seems to be corrupt in TC exe). Check the disk for errors, maybe there lies the problem.

[realtime]

That might be a reasonable guess if I only ever used one system, (rather than one system at a time). I have had this error on at least three different systems (all similarly configured as mentioned above).

[Clo]

2realtime
  Hello !
• Maybe not helpful, but I thought to compare your display section in
<wincmd.ini> with mine below :

Code: Select all

[1024x768 (8x16)]
Tabstops=132,142,201,-1,459,93
FontSize=11
FontName=Times New Roman
FontSizeWindow=9
FontNameWindow=Arial
FontWeight=700
FontWeightWindow=700
Iconsize32=21
FontCharset=1
SearchX=217
SearchY=209
SearchDX=551
SearchDY=179
SearchMax=0
maximized=0
x=11
y=76
dx=1010
dy=600
Divider=500
DividerQuickView=500
DividerComments=500
MenuChangeX=0
MenuChangeY=0
MenuChangeDX=768
MenuChangeDY=558
MenuChangeMax=0
CompareX=-7
CompareY=116
CompareDX=1026
CompareDY=543
CompareMax=0
CompareDivider=500
SyncX=201
SyncY=108
SyncDX=615
SyncDY=470
SyncMax=0
SyncTabs=92,132,227,250,342,382
RenameX=166
RenameY=254
RenameDX=638
RenameDY=286
RenameMax=0
RenameTabs=115,145,345,405,525
FontCharsetWindow=1
FontNameDialog=Arial
PrintX=200
PrintY=108
PrintDX=640
PrintDY=497
PrintMax=0
TreeDlgX=144
TreeDlgY=257
TreeDlgDX=429
TreeDlgDY=460
TreeDlgMax=0

• Else, have you "RestrictInterface" instructions ? Could cause problems too sometimes...
• Further, whether your three systems are set in the same PC, I don't see another reason than a common hardware problem (Mother-board, Graph.-card and / or its driver...)
  Kind regards,
Claude
Clo

[realtime]

Claude:

Thanks for your info from your <wincmd.ini>. I used to have all that stuff in there too, and if I don't get the AV for a while, it can (almost) get the same again.
Don't know what you mean by "RestrictInterface" instructions!

As for hardware - the 3 systems are not in the same PC (one is my laptop, one is my desktop and the other is a development machine - they are all Dell - but I don't think that is relevant.)

I am beginning to suspect that the connection could well be with VNC as all 3 machines have a VNC server running. On the other hand, I have a couple of colleagues who use TC (on Dell PC's) with VNC server running. I haven't heard any problems from them.

[Clo]

2realtime
  Hi again !
RestrictInterface is an instruction-entry in <wincmd.ini>... But it doesn't exist by default (please, see the Help / Tutorial about this)
• In the other hand, have you the utility: "Dell QuickSet" installed ?
- If you have it, you could try to disable it, then see what happens...
* To be continued…
  KR
Claude
Clo