Home
Products
Overview
Compare Products
Actual Window Manager
Actual Multiple Monitors
Actual Title Buttons
Actual Virtual Desktops
Actual File Folders
Actual Transparent Window
Actual Window Minimizer
Actual Window Guard
Actual Window Menu
Actual Window Rollup
Download
Actual Window Manager
Actual Multiple Monitors
Actual Title Buttons
Actual Virtual Desktops
Actual File Folders
Actual Transparent Window
Actual Window Minimizer
Actual Window Guard
Actual Window Menu
Actual Window Rollup
Order
Single User License
Corporate Sales
Upgrade Center
News
Latest news
Newsletter
Support
FAQ
How to Upgrade
Restore License Key
Online Demos
Online User Manual
Forums
Announcements
General
Feature Requests
Technical Support
Tips and Tricks
Beta Testing
Feedback Form
Beta Testing Section
Resources
Articles
Reviews
Success Stories
Multi-Monitor Wallpapers
Company
About Us
Contact Us
Privacy
Our Clients
Press Center
Press Releases
In The News
Reviewer's Guide
Logos and Screenshots
Publishing-friendly Graphics
Forums list
New topics
Topics list
Search
Help
Login
Register
Topic: «
AWM 5.5b2 Explorer crash
, Access Violation opening Explorer window » on forum:
Beta Testing
Views: 8143
David Lomas
Advanced user
Posts:
377
Joined:
03/16/2006
Posted:
11/09/2009 04:14:42
Every time I use Hamachi to open an explorer window on a remote machine I connect to, I get the following error and the explorer window is closed.
---------------------------
Application Error
---------------------------
Exception EAccessViolation in module aimemb.dll at 0002A2FF.
Access violation at address 01D2A2FF in module 'aimemb.dll'. Read of address 00ED0FB5.
---------------------------
OK
---------------------------
This only seems to happen if I use the Hamachi interface to open the window - if I manually open an explorer window from My Computer and type the remote machine address in, it works OK.
Cheers,
Dave.
Top
Jolly Wykoff
Registered user
Posts:
45
Joined:
10/08/2009
Posted:
11/09/2009 10:32:32
Try turning on Data-Execution for ALL programs. That seems to have fixed the Explorer errors for me.
Top
David Lomas
Advanced user
Posts:
377
Joined:
03/16/2006
Posted:
11/10/2009 02:54:53
I don't seem to have that option under XP SP3 - you have to manually specify every executable you want to disable DEP for. However, I disabled DEP for explorer.exe, rebooted, and the error does seem to have gone away.
However
, I wouldn't consider this a fix, as with MS track record on buffer overruns, DEP is probably a useful bit of protection. At least it might help narrow down the problem, but from the error, it looks like its in the aimemb.dll library anyway, not explorer.exe.
I'll be turning DEP back on, and see if the error returns (I can work around it for now, until the fix is included in AWM).
Cheers,
Dave.
Top
Alexander Belyakov
Administrator
-retired-
Posts:
196
Joined:
06/07/2007
Posted:
11/13/2009 09:09:49
David, you are right, the problem was in aimemb.dll.
We've fixed this bug today. The fix will be available in the next version.
In fact, we are kinda confused about how disabling DEP could prevent Explorer crash in this situation
Top
User(s) reading this topic
Number of guests:
1
, registered members:
0
, in total hidden:
0
Forums list
New topics
Topics list
Search
Help
Login
Register