Graal Forums  

Go Back   Graal Forums > Development Forums > Tech Support
FAQ Members List Calendar Today's Posts

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
  #7  
Old 03-12-2016, 04:05 PM
fowlplay4 fowlplay4 is offline
team canada
fowlplay4's Avatar
Join Date: Jul 2004
Location: Canada
Posts: 5,200
fowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond repute
I found a workaround that allows the editor to work in Windows 10 64-bit.

If GraalEditor.exe loads d2d1.dll and/or d3d11.dll in C:\SysWow64 it causes the crash on open and iertutil.dll which causes the file dialogs to crash.

Blocking access to the dlls allows it to run properly.

To safely block access to those dlls:

1. create a second user (e.g. test) with a password and configured a runas batch script:
2. changed ownership of the dlls to administrators
3. set deny full control to test user

Editor.bat:

PHP Code:
runas /env /user:test /savecred "GraalEditor.exe %1" 
Then configured my .nw files to open with the batch file:

__________________
Quote:

Last edited by fowlplay4; 03-12-2016 at 04:24 PM..
Reply With Quote
 


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 09:18 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.
Copyright (C) 1998-2019 Toonslab All Rights Reserved.