Access Violation

English support forum

Moderators: Hacker, petermad, Stefan2, white

realtime
Junior Member
Junior Member
Posts: 9
Joined: 2003-10-29, 15:57 UTC
Location: Wrentham Massachusetts
Contact:

Post by *realtime »

Claude:

No RestrictInterface entry in <wincmd.ini>.
No "Dell QuickSet" installed.
User avatar
Clo
Moderator
Moderator
Posts: 5731
Joined: 2003-12-02, 19:01 UTC
Location: Bordeaux, France
Contact:

Post by *Clo »

>> realtime
No RestrictInterface entry in <wincmd.ini>.
No "Dell QuickSet" installed.
:)   Hello!
•  I might give up…
… but it's really an odd problem...
• I guess that something specific to "Dell™" PCs makes that the real display doesn't matches with the theoretical coordinates in the <wincmd.ini> So, the pointer couldn't be found, and the program hangs.

¤ A test : please, restart one computer as "Safety Mode" (or so, my Windows are in French…).
* You'll get a very ugly display. But minimal devices are loaded. Hoping that an eventual faulty one be in the not loaded ones…
* Then, lauch TC and see what occurs…

:mrgreen: Kind regards,
Claude { who caught a huge cold slowing down the brain… } :(
Clo
#31505 Traducteur Français de TC French translator Aide en Français Tutoriels Français English Tutorials
realtime
Junior Member
Junior Member
Posts: 9
Joined: 2003-10-29, 15:57 UTC
Location: Wrentham Massachusetts
Contact:

Post by *realtime »

Sorry for the delay (pressure of work)

Anyway, the problem has not happened during the last week! I said it was intermittent. Sometimes once/twice a day, and then nothing for a couple of weeks.

Thanks for the suggestion about starting in safe mode. I'll play around some more (Reboot, Safe Mode etc..) next time it happens and before I clear out <wincmd.ini>.

I'll let you know what happens
:)
realtime
Junior Member
Junior Member
Posts: 9
Joined: 2003-10-29, 15:57 UTC
Location: Wrentham Massachusetts
Contact:

Post by *realtime »

It's been a while since I've been getting these AV's but they're back and I think I've tracked it down this time.

Looks like I was right about WinVNC.

Instead of editing <wincmd.ini>, I stopped the WINVNC service (since I suspected this - see previous post). Sure enough, TC started right up. I restarted the WINVNC service again and TC still starts up OK.
Post Reply