I have a request for a new set of tools: CS Command Line Tools. This tools could be integrated in Command Prompt Portable or as a separate group of tools. This project consists on several DOS external command that add functionality to the DOS Prompt.
The project has a prepared batch file that makes possible to run CS Command Line Tools from anywhere without having to set the required environment variables. The batch file sets them temporarily, leaving no trace.
I think that the project could be of some interest to be added to PortableApps. Essencially, it would be required only to have the command executables and the batch file, leaving the "Setup Manual" outside, since it has no relevance for PortableApps case.
The project is located at:
http://sourceforge.net/projects/cs-cmdtools/
The project is under GNU GPL v3.0. It would be better if the correspondence between the original installers and the PortableApps installers was mantained, but that is just for reference and not required. I am the project manager and up to date the responsible for all developments in the project. Feel free to ask me anything about CS Command Line Tools. I will gladly answer it.
P.S.: This project will have more text conversion tools. Their release is predicted for December (I hope). It would be really good it the command executables could be compressed a bit more.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
What do these tools do? I read the discription to find little information on what the program does.
OliverK> you don't live on a cow
IRC: It brings out the best in all of us...Especially when tired.
They are mere additional commands to DOS. For example, DOS2Unix converts a text from DOS to Unix format, by converting CR/LF pairs to LF characters. Unix2DOS does the opposite, by converting LF characters to CR/LF pairs. It doesn't convert LF characters if they belong to a CR/LF pair. TypeHex is like Type, but uses hexadecimal notation to output a file contents. Other last important tool is Compare, which compares two files byte per byte, casting out the differences. I'm planing to integrate more tools in December. The total I've planned it is in the order of 10 tools.
I think that they would be an useful add-on, but if it is possible to compress those *.exe files, it would be better.
I'm planning to make a file splitter, and a file merger to "glue the pieces together".
How are these tools different from the comprehensive package of tools in GnuWin32?
I'd expect the GnuWin32 package would be the core for PA, since they are so common throughout the computer world (so tools learned in Windows can be used on the Mac or Linux, for example).
Some of the functions you mention can be handled by GnuWin32 tools already.
MC
I've used a lot of computers over the years and NONE of them have the GNUWin32 stuff on them...NONE. That package is not "common" at all on Windows machines.
You have to remember a HUGE portion of the Windows user base have no clue what Linux is and could care less about command line tools.
Cancer Survivors -- Remember the fight, celebrate the victory!
Help control the rugrat population -- have yourself spayed or neutered!
"How do I command the line tools?" or *blank stare*
But if we geeks can get some additional useful tools I'm all for it!
~Lurk~
As you would use any other command. For example:
typehex license.txt
compare one.exe two.exe
You missed the joke. The one where I poke fun @ the "end user". (In reference to the last part of the comment I was responding to.)
*sigh* The moment is gone...
~Lurk~
Not "common" indeed. "Inexistent" would be a more apropriate term, unless you add them.
That package is not "common" at all on Windows machines.
Well, of course it isn't. But it is common on just about everything else.
Besides, we're talking about what to take with us on our portable drive, or (gasp) what system to learn if we have no CL experience at all and are feeling geeky.
I'm just asserting my opinion that it might be better to use the GnuWin32 tools (where they are available and do the job) rather than special windows-only command line tools that are quite unlikely to ever show up on a different OS.
MC
Indeed. Then GNUWin32 would be a better alternative. I didn't knew they existed. Better abandon this idea and consider them instead.
I was not aware of GnuWin32 existence, but I can assure you that GnuWin32 commands are not a given for none of the Windows system. This applies to CS Command Line Tools commands as well (except compare that existed in early versions of Windows). Besides, my packages are aimed for portability.
Anyway, or GnuWin32 or CS Command Line Tools would be an interesting addition for who wants them. We have to take unexperienced users that don't know how to set Portable Command Prompt to call these tools. So an installer would be more neat.
CS Command Line Tools doesn't have the specific purpose to cover Linux commands. Its purpose is to expand DOS functionality by adding new general purpose commands (for now). Specific purpose commands are being considered though, but only useful ones.
Since the command executables will work from any directory, why not just put them in your default DOS directory on your drive? If you are already running CommandPromptPortable, the path should already be defined.
The batch file does nothing except append a directory, based on the current environment variable %CD% (which isn't even defined on my WinXP Pro box) to your path, switch to the current drive's root directory, and execute CMD. As it happens, it does NOT clean up after itself, leaving the revised path in effect. So, all someone has to do is to look at the environment variables (to see the path) to know you have not only executed something 'outside' the box, but it was even CLI! Maybe Portable, but certainly not Stealthy!
"...As it happens, it does NOT clean up after itself, leaving the revised path in effect. So, all someone has to do is to look at the environment variables (to see the path) to know you have not only executed something 'outside' the box, but it was even CLI! Maybe Portable, but certainly not Stealthy!"
The revised path affects only the window concerning CmdLine.bat of the project. "set path" will affect the path temporarily on Windows NT based machines (Windows NT, 2000, XP) and will not work like in Windows 95 or 98 (wont set it definitely). So it is as stealthy as it could be.
Anyways, it is better to consider GNUWin32. I didn't opened a new request since I searched and saw requests made for GNUWin32.
Although it's how most forums work, the title does not need to be "RE: Whatever" and we recommend not to set it to that. You can put a title yourself or you can let Drupal take the first few words automatically.
"If you're not part of the solution, you're part of the precipitate."
I know Drupal chooses the title by the first few words on the comment, but I like to choose the apropriate title. Since I'm answering to you, I put "RE:" before the title of the post I'm answering.
Because the discussions are threaded (indented in order with who you replied to), there's no need. It should be a summary of what you've said.
"If you're not part of the solution, you're part of the precipitate."
I like the completeness of GnuWin32, but its a rather large package taken as a whole. A streamlined version of the essential Unix command line tools is available from here: http://openetwork.com/berk.html. It's portable using the general instructions for "Command Prompt Portable" extensions. It's freeware but not open source.
_______________________________________
I never know what to pub in signatures.