Mobius
-
Posts
943 -
Joined
-
Last visited
-
Days Won
3
Mobius's Achievements
-
Mobius reacted to a post in a topic:
ClipBoard.au3 udf extras
-
Am I missing something, the "here" link points to a thread about "how to make html help". Spiderbasic is from the creators of purebasic isn't it? Should be good I'll be sure to check it out, syntax is very similar I see.
-
Mobius reacted to a post in a topic:
Autoit/Python DuckHunt IRC Bot - Beta
-
yutijang reacted to a post in a topic:
AutoCamo - 98.18b
-
Mobius reacted to a post in a topic:
Real Time Assembler
-
Mobius reacted to a post in a topic:
DLL callback register ?
-
Mobius reacted to a post in a topic:
GUI Dark Mode Windows 10 possible ?
-
argumentum reacted to a post in a topic:
GUI Dark Mode Windows 10 possible ?
-
GUI Dark Mode Windows 10 possible ?
Mobius replied to Aether's topic in AutoIt General Help and Support
I doubt the op is still looking for a solution 3 years later guys. But you never know. -
First post download links fixed
-
Heya sylremo, Busted again are they, I'll see about fixing them when I get back to the office in a little while.
-
So to follow up on the last user query for other users since they have not responded. I could find no reference in the documentation to Autoit being able to include .a3x files unless it is beta branch functionality (possible). Regardless, the following is true: An Autoit script built with AutoCamo will NOT recognise a3x files/data that were generated in the traditional way, ONLY a3x files that are built using the same modified builder (with the same generation seed) as the current executable being generated will be recognised. This is fairly simple to do at runtime with AutoCamo and there are examples of it working within the distribution.
-
I don't see why this would be the case but then it has been a long time. What does this do in Autoit code? #Include .a3x Ed: Wait I think I see now, you are saying that when you include pre built a3x files in your exe it is unable to run them is that correct?
-
Unzip a large number of compressed folder fast
Mobius replied to antmar904's topic in AutoIt General Help and Support
You could still automate the process with a script or batch file running the command line utility 7z.exe if you wanted to. -
Yep as mentioned in update post, 64 bit is not really supported. I should really have been clearer on this. The options for 64 bit remain (rather confusingly) because they could be introduced modularly in the future should I or someone else be inclined without updating the main program.
-
Don't know the cause your end but the same code my end generated the following working binaries: test.exe just the source built testapcc.exe as above but with apc option c checked. Is your chosen autoit build in the program files directory or somewhere else that requires admin rights? ONTOSY_test.7z
-
98.18b pretty old and no longer relevant these days. Compiled and tested on windows 10 pro 64 bit under a virtual machine. Baseline functionality tested with Autoit v3.3.15.4-beta only with distributed examples. This does not mean it will work with your advanced scripts since the resources example that uses a significant but older Autoit source header does not work correctly. It is simpler to say this program is not compatible with 64 bit Autoit interpreters so avoid if that is a requirement. The interface was sluggish as all hell to initialize for me under build/test os conditions so a reminder if you want to run it as a console program: To patch it to console run DRXL. exe A3C.exe @PB 3{220 To patch it to windows run DRXL. exe A3C.exe @PB 2{220 Or you can use the interface menu option. Or these batch files - a hex editor or script etc. A3C_WINCON_BAT.zip
-
Hao reacted to a post in a topic:
AutoCamo - 98.18b
-
Ontosy, Your primary problem is that you are running mpress before the build, this option should be reserved for older overlay dependent builds of Autoit. In your config file change the B at the end of the mpress execution line to A to tell it to run after the build. You probably are already but if not you must use the most recent build of mpress 2.1.9 as older builds are known for corrupting 64 bit exes that are even the slightest bit abstract. You don't really need to define aut2exe_x64.exe just aut2exe.exe when using the 64 bit interpreter (gui) A3C_X64 (cfg) option since this option runs the builder with the /x64 command line switch when enabled. Hope this helps you. Vlad
-
To patch ac to console by default from the gui: Click on the star toolbar button > execute - DRXL - Swap Autocamo interface A console window should appear, close the autocamo window which closes the process allowing it to be patched, then press "Y" and enter as instructed in the console window. Success or failure should be reported in the console, if everything went ok AC should now be a console program by default. Ed: alternatively you can pop A3C.exe into a hex editor and at offset 220 flip the byte from 02 to 03 in the Pe header and save, if it does not work or you don't have DRXL.exe for some reason. I am looking into your primary issue
-
Ontosy, I've just checked it and the a3x mods and package containers produce a working binary from the beta 3,3,15,3 Could you please explain what you mean by no longer works, I'd prefer we use this thread for discussion but if an explanation requires details that are frowned upon then you can pm me if you wish. Vlad
-
Mobius reacted to a post in a topic:
AutoCamo - 98.18b
-
Excellent thanks. Ed: Additionally the current build of AC can actually be used as a pure console program (log output goes to stdout) if you prefer, you do this by patching its pe subsystem.
-
Hi, When that build is released i'll be sure to check it out