kairozamorro's hangout

I've been working mad over the last 3 days and for success it has been. I'm very pleased to introduce to everyone Compatibility Sword 2.0. Though such a short-time to its existence it has been carefully re-designed and tested to not only past functionality, but additional new features as well as features that have been ported from former project FileDir2Prompt. You can expect much easier operation, none of the path bugs that FileDir2Prompt was a faiilure for, and less of an intimidating interface all around.

Changes from 1.5 to 2.0:

• Complete re-write/GUI re-design.
• Smaller size for greater portability compared to previous versions of Compatibility Sword and FileDir2Prompt... and they're both one tool now!
• Non-UAC equipped or disabled Windows system friendly
• Automatically disables actions that would require you to be an admin if you don't have admin rights to perform them on a Non-UAC equipped or disabled Windows system.
• If the folder/app you want to run is in the current directory or in the root of the drive of the current directory, just type its name (No worries about typing full paths anymore!)
• Switch syntax changed. Switches and their arugments are separated by a space rather than an = sign.
• Added /dir parameter that functions like FileDir2Prompt's /dir parameter did. /adminapp parameter wasn't ported over due to current /uac parameter in CSword which does the same thing.
• Added /keepopen parameter for use with console applications to keep command windows open like FileDir2Prompt did.
• Multiple application parameters with spaces can finally be passed through the command line correctly to the application you wanted from CSword. When you wanted to accomplish this before you had no choice but to use the GUI.
• Removed /app parameter. Now you just enter the filepath without it.
• Removed /uacme parameter. Compatibility Sword can now do everything with at most a single UAC prompt. No more 3-4 UAC prompts everytime something needs to be changed that requires admin access. If you still want to run an admin session of CSword though you can do so by specifying "csword.exe csword.exe /uac".
• Removed profiles. Doing that allowed to me concentrate on the most important parts to whats now a well working release and reduced clutter on the GUI. If you want to save settings you can still do so though in the form of commands to CSword using scripts/batch files.

Get CSword 2.0 today and start noticing the difference for yourself