
mariano
Members-
Posts
12 -
Joined
-
Last visited
Profile Information
-
WWW
http://www.galinux.org
mariano's Achievements

Seeker (1/7)
0
Reputation
-
Yeah... you know what I mean, maybe amateur programmers but programmers after all. My tool is intended for low level operations, some of them are simply too risky. I just wanted to make clear that I'm not going to provide support for each single use of it. For ex. if someone wants to mess with his partitions or MBR, I don't want them to complain "hey, you didn't warn me about bla bla..." Draygoes: Thank you very much! I wish in anytime soon we will see in this forum some new kinds of apps like DVD rippers, HD managers, recovery tools, etc.
-
dd.exe (think of it as "double data") is a tiny tool for performing fast high/low level copies. It can deal not only with normal files but with many sorts of devices. Some of its features are also present in AutoIt, but never as fast as a really compiled tool. Other feautres, AFAIK, are simply imposible to do with AutoIt. And that's why I decided to make this pack. DD.exe is a ported version of the dd *nix shell command. It needs the Cygwin DLLs bundled with this package. Cygwin is free software released under the GPL. Please, read carefully the license terms in http://cygwin.com/licensing.html With dd.exe you can provide your AutoIt scripts with advanced features like extracting ISO files, raw-writting a floppy, directly send some text to a printer, use your serial ports, get some music played, recover a Master Boot Record, backup your HD partitions, instantly create null-filled files, manage your clipboard, direct read/write to memory, etc. etc. It's up to you and your imagination to create wonderful apps with it. This zip contents: -The exe and the required libraries. -An AutoIt demo script. -dd_help.txt, a dump of the brief help that you get typing dd --help. You'll see and "ADDED" section: that was not in the original help of the file. I appended that text cause it can be a great primer to the dd/gycwin sintax. -dd_manual.txt is the complete manual of the command. Please note that I didn't care about matching the manual and command versions; more, the CygWin version is quite limited when compared with the original one. Some options/parameters could not work or do it in a different way. Depending on the feedback about this package I might make more with other usefull tools for being used in AutoIt scripts. Please don't ask me for more demo scripts, several apps using dd, a complete reference manual and things like that. More, don't mail me saying "hey, that readme.txt of yours is rather a mess". Please note that: -Everyone around this forum is supposed to be a programmer, right?. -I'll be back at work in september the 1st and I won't have lots of spare time. -Now I'm involved in a couple of important personal projects. Releasing packages like this one is just my 2 cents to the community, not a priority at all as you can imagine. I'm not interested in a big chatting about them. If you like it, take my work "as is" and if you miss something, get it done by yourself and share it! Download: http://www.atma.es/dd.zip 28-Aug-2008
-
In short: Find.exe is a tiny tool for performing complex and fast searching in your file system. I've docummented and packed it avaliable for download from http://www.empresas.mundo-r.com/aidega/find.zip Hope you'll enjoy it! (KOSHY MAY BE RIGHT, IT WAS A TOO BRIEF DESCRIPTION) The find utility recursively descends the directory tree for each pathname listed, evaluating an expression (composed of ``primaries'' and ``operands'') in terms of each file in the tree. You can filter files/dirs, depending on their accesed time/hour, size, name, etc. The complete list of parameters comes in a couple of attached texts. Find.exe was not built from AutoIt. It's a Linux tool ported to Windows. I call it from AutoIt with Run() for performing searchs and dump the results on a txt log, but you can redirect the output to any other program, including AutoIt scripts of course. I provide a BAT file with two examples.
-
It was clear. The question that arises here is how can you argue a single word about what you ignore. No comment. You've self-described here. Is this an advice, a cosmical law, or just means that you are too limited for imagining new horizonts? Posting about issues that you ignore and never will to learn is not blind posting. I see.... This must be one more "cosmical law". The fact is that it works like a charm. The bash one? It isn't, indeed, smart boy. It's a linux script as I said, thank you muttley I can run bash from autoit and viceversa through Wine. What a "true" interaction should be under "cosmical laws"?
-
I DO understand and I've got no problem. Absolutely not. From Autoit you CAN access the linux shell. Didn't you checked it before blind posting?. No you didn't; it's clear from your words that you have not tried my example, nor ever worked with Wine. Too lazy for trying? "Mini-kernels" and "program layers"? Who's the one that does not understand some points? More, have you got any particular interest in people not trying by theirselves what I proposed? My example is here to stay, so that everybody can test it and decide weather it's me or you who is right, hehehe. A special gift for unbelievers:
-
James: I agree: Autoit is for making life easier, that's why I love it and prefer it. You're right also about those kinds of scripts: self-writing scripts and things like that are not unusual in Linux world. I don't need to replace each single command in Autoit, only a few when needed. For example, if you provided the right paths, "FileWrite" and related work like a charm, so does GUIs and others. I was talking about a few things perhaps too dependant of the hardware, like @IPAdress1. Easy to find workarounds now. "Autoit will never support Linux systems as mother tongue". I know and I knew from the beginnig as I stated in my first post. Why can't some of you believe that I am already aware of that?. I'm afraid that the power of my proposal is not being fully understood, cause you keep on warning me about "system internals", "Windows world", "recompiling"... Well, I did what I had to do: tell the others about this. It's a pity but never mind if no one cares. The fact is that I've already started making my first portable app with a very little effort, it's working nicely and that will be a persistant plus for my creations. IMHO it's worth to write some more lines if you get such an advantage but I don't want to make me and others waste time explaining the same thing more than once, so thank you for your comments; just let's do it in each one's way and joy for everyone muttley
-
Sure it needs a "next", put it at the end of the script. One more thing... I have not a running autoit at hand right know but I think that you can not use "If" without the closing "EndIf". Cheers.
-
(Richard, I'm sorry if you were not talking to me; I wonder what an "OP" is) Actually the "function that calls things from the command interpreter" is as familiar as "Run" or "RunWait"! What I meant before is that there is no need for the "RunShell" thing, cause it is already possible to call a linux script with Autoit as is, hence no need for complicated hacking into its code, etc. That's what I found out and what my example is intended for. If you use Autoir in Linux+WINE and some commands don't work for you, just replace their functionalities by your own bash scripts. It's great that with a little extra-effort, I (anyone) can make portable applications! Surprisingly there are things that already go fine, as mouse management. Others need some home-made work under linux. For ex., @IPAddress1 doesn't return the correct value. But now we know how to solve it: "RunWait" your bash script as said, instead, perhaps such a simple one as: #!/bin/sh ifconfig|grep "inet addr" Now one step beyond... If anyone else is willing to make some bash scripts we could join our efforts to build something like a wine-alternate-functions collection. Anybody interested? By the way, I hope that those not using KDE have already noted that kdialog should not be avaliable using other window managers. Please replace it for the proper command under your WM... of forget it: that was just a toy.... you've already got a shell from Autoit!!!
-
Already done! All you need for recoverying faulty commands is replacing them for your own linux shell scripts/commands. Want to test it? create a new empty bash script and fill it with: #!/bin/sh echo "Bash: Start" kdialog --msgbox "This pop-up was called from Bash." & xterm echo "Bash: Ended" Let's name it "bashscript.exe" and set it executable, start Autoit and type this single script: RunWait("D:\projects\bashscript.exe", @ScriptDir) Notice that you'll need to replace the path by the yours. Both scripts are in the same folder in my example. When you run the Autoit script you'll get a testing pop-up run from Linux and a Xterm. You've got the power! Tested running Wine 0.9.58 and TMLinux2007 (PClinuxOS in spanish). Many thanks to "Cladan" who had posted all the info I needed at http://forum.winehq.org/viewtopic.php?t=14...f0551643d95fd6b Post here your complains or let me know by email muttley
-
Wow! this happened to be a very active forum. Nice! But that's not what I asked. No need for real system calls, just some way of invoquing bash. If provided it would be possible to take total control of the alien system from that single command. I ignore how difficult could be to include it but I do believe that there is nothing imposible in the end. And this is the funny thing: if denied as I supose, perhaps I'll try to do it by myself in some months from now and post it here as an UDF, plug-in or whatever could be. You'b better have started telling me so, my friend!. I didn't know that. Mine was not such a a great new after all muttley
-
Perhaps you've missunderstood due to my limited english skills. Didn't I say "I've already seen that Autoit was never intended for other platforms than Windows" and "you can use Autoit under Linux" ?. Autoit=Windows, that is out of the question and I'm aware of it, man. What I mean is exactly what I wrote: you can USE it under GNU/linux. Nobody has requested a port but a simple command, a interface that could be an open door to the internals of such systems. I guess that it should be clear that a port is a different thing by far. Anyway my intention is not arguing. If I were a Linux fanatic I wouldn't be using Autoit. I'm just an open mind and It just happened that I gave it a try and worked much better than suposed. This info could be important for some people, obviously not you but who knows.... Cheers.
-
Ok, I've already seen that Autoit was mever intended for other platforms than Windows. But.... I've been testing it with PClinuxOS (an user friendly distro) and Wine (not a windows emulator but very likely). Scite works like a charm, so does all of the GUI commands that I tried. As expected, those too close/dependant on the hardware fault, but not a big amount of them. Both compiled and interpreted scritps seem to be working fine. So these are my news: As far as I tried, you can use Autoit under Linux!!!!! Last, my own feature request (I know, there is already a different place for this and surely it will be not approbed): What about a new feature called "RunShell" or alike?. As it is for now you can not use bash-scripting from Autoit (or am I wrong?). These could tune it into a powerfull developer tool under Linux as well.