Coice's macro editor?

onorok

onorok

O N O
Is this still out there and working? The last build I have of it, I got an error last time I tried to load it up, says:
Thinstall: Executable 'C:\Program Files\CMEditor\FFXIMacro.exe' had the following unrecoverable error:
Couldn't find library MSVCR80.dll
Please ensure that is is installed
​
I'm not sure where to find the MSVCR80.dll file :confused:
 
Yep, you have a newer version of the framework installed, will get this error regardless of what you do. I was working on an updated version of the editor with some 'windower' support. Though I got severely sidetracked by another (paying? lol) project.

That bug is fixed in the current version of the editor (which I have not released due to some unstable code which I haven't had time to resolve)

Best answer I can give you, lol.
 
the issue is cause by microsoft's .net framework 2.0
uninstall 2.0 and revert back to 1.0/1.1 and the editor will work perfectly
 
furax said:
the issue is cause by microsoft's .net framework 2.0
uninstall 2.0 and revert back to 1.0/1.1 and the editor will work perfectly
Click to expand...

I have atleast 2 Apps at work that cannot use .NET 2.0 -- I have only allowed .NET 1.1 (with SP) due to various problems with the changes between .NET 1.1 and .NET 2.0.
 
umm... you guys know you can install 1.x and 2.0 side by side right? lol
 
Uhh.. yes you can. You just specify an xml configuration file that tells it to use 1.1/1.0.
 
If an app is written using .NET framework 1.0/1.1/2.0, it works like that. Maybe I'm missing something.
 
The protection I applied is what is causing the screw up pertaining to my program. You guy can argue all you want, lol, my app works on 2.0 of the framework without my protection applied, with it, it gets screwy.

If you guys know of a good FREE way to protect my app from being decomplied tell me and I'll re-release the current version with that instead. Currently using an old version of thinstall.
 
we're talking about CME though, not other apps. You heard it from him, it won't work on 2.0 with the protection he has implemented. So here it is, one more time:

Resolution: Uninstall 2.0.
 
Update: The bug is in Thinstall, not .NET. What version of Thinstall are you using?

P.S. If anyone tells me to uninstall .NET 2.0 again I'm going to scream, since some people actually have apps installed on their system that require it.

Just out of curiosity, is there any reason that just obfuscating it is insufficient to protect against reverse engineering? Sure, techncially they can still decompile it, but does it really matter? That's the whole point of obfuscation. I can decompile an EXE produced from unmanaged C++ into assembly language. But why bother, lol. Decompiling obfuscated managed code is only slightly less annoying than decompiling machine code into x86 assembly.
 
Last edited:
Kalia said:
Update: The bug is in Thinstall, not .NET. What version of Thinstall are you using?

P.S. If anyone tells me to uninstall .NET 2.0 again I'm going to scream, since some people actually have apps installed on their system that require it.

Just out of curiosity, is there any reason that just obfuscating it is insufficient to protect against reverse engineering? Sure, techncially they can still decompile it, but does it really matter? That's the whole point of obfuscation. I can decompile an EXE produced from unmanaged C++ into assembly language. But why bother, lol. Decompiling obfuscated managed code is only slightly less annoying than decompiling machine code into x86 assembly.
Click to expand...
And that's where I went cross-eyed! :badshape:
 
An old habit.

I've developed a few programs where I did not trust the clients at all and the source was worth substantially more then the executable. That's why I was using thinstall. But yeah, honestly its overkill for the macro editor, lol.

The version of thinstall is an old version, I am not about to pay $5000 for the current version (lol), I dont need it like I used to anyhow.

As to the framework, do not uninstall 2.0 of the framework, you will just prevent whatever application that needed it from running. If it is installed on your computer, there is probably a good reason.
 
You must log in or register to reply here.
Back
Top