Has anyone else noticed a memory clash between Wordperfect X4 and Google Earth 5.1running under Windows 7?
When Goggle Earth is loaded and WP X4 has a file open, when one attempts to pan in Goggle Earth it will cause WP X4 to report an Improper File Type Error if a subsequent attempt is made to save a file. On some occasions, I have also been able togenerate a DLL load error in WP X4 (evidently file save related), when more than onefile is open. Problem seems to disappear when Google is terminated.I am editing some very large files (WP X4 works but very slow), but the clash does not seem to be associated with file size. Rather it seems that some internal Windows dynamic memory access layers are being inconsistently (simultaneously) being used by the two programs.Needless to say, this is horribly annoying and a fix would be extremely desirable as much of my work often involves evaluation of locality data derived from use of Google Earth.Currently running:WP X4 14.0.0.7563andGoogle Earth 5.1.3533.1731 Build Date Nov 12, 2009 Build Time 11:59:29 amRenderer DirectX 9 Operating System Microsoft Windows Vista (Service Pack 0)Video Driver 000010DE (00008.00015.00011.08603) Max Texture Size 8192x8192Server kh.google.comUnder Windows 7 (32 bit) on a Dell XPS M1330 with 4.00 GB Ram (3.50GB usable), with IntelCore2Duo CPU t7500 @ 2.20 GHz and 2.20 GHz using a NVIDIA GeForce 8400M GSvideo display adapter. Typically I run the two programs on multiple monitors,XPS M1330 and a HPw233h on an extended desktop, but I do not believe the problemis related to the vide card or its performance. .
I am experiencing the same problem.
We've tried the following:
WordPerfect Office X4 Service pack 2 on Windows 7 (Fully updated)
Google earth 5.2.1.1329 beta launched and running all day while working in WordPerfect.
There must be another ingredient required....
Heather BlaineUser Experience Designer, Corel Corporation
Hi,
Comment from WordPerfect Office developer -- it's beyond my knowledge level of computers but hopefully it makes sense to you:
...might be related to his specific machine being a 32-bit version of Windows 7 and having more than 3GB of RAM - He might need to go into his bios to activate a feature sometimes called 'memory hole' - the video card will conflict with addresses used in Windows... So, scrolling with DirectX would corrupt memory...