kairozamorro's hangout

Happy new year everyone! Ok its not quite 2010 where I am but for some of you it may be! I guess this goes under the 2010 blog posts category

KVM switches? Sure, techies are quite familar with them. Keyboard, Video, and Monitor switches traditionaly allow you to control two computers using the same mouse, keyboard, and monitor as well as speakers on models that support audio. Today I present my review of a different type of KVM switch from IOGear.

I was surprised to say the least when I randomally came across IOGear's USB Laptop KVM switch for a few patiular reasons:

• Its portable and no software needs to be installed other than the proper mass storage device drivers just like any USB device you plugin which is plug 'n play. The switch connects two computers strictly using USB
• Includes an additional USB port for accessing files on removeable devices
• Utilizes a virtual CD-rom drive similar to SanDisk's U3 platform where the software can be found and ran.
• Uses Virtual Network Computing (VNC) solutions to connect the two computers and allow file transfer, but does not require internet connection whatsoever cause the bridge is established trough USB.

Its been out for awhile now, so another benefit I can think of is price. It started out over a $100 but I got mine at Best Buy for a mere $40.

Benefits? Here's the practical benefits the product's intended for (you can find the product page here):

• Quickly transfer files between two PCs
• Maximize space (Just use your laptop to control a desktop so no additional keyboard, mouse, monitor etc are needed)

Techie benefits:

• Alternitive to Windows Easy Transfer. While manual it does allow you to actually control the desktop in addition to transfering files between the two PCs.
• I bought it solely to save time on jobs I do. Its a lot better than going back and forth between each computer transferring drivers and other important files.
• Use it with your laptop to locally control and fix problems on your home servers without having a spare K, V, or M around. Perhaps you can finally put that old junk PC you use to serve up network goodness in a closet out of sight now? Thought so

Now onto the cons of this product. Some of them I'm not too pleased with but I'll leave it up to you to decide if its nevertheless worth a purchase:

1. Ovbiously doesn't work with Windows Easy Transfer, so can't use that to transfer other things in addition to files like user account settings or applications depedant on installation.
2. Only works in Windows (as it relies on Windows software and AutoPlay)
3. Needs to open a port in firewall though the connection is established via USB. This may be a problem because some firewalls may block the connection until its approved.
4. Again, relies on AutoPlay to start local and remote software needed to support connection. You can start it manually, but thats a pain and even with AutoPlay enabled you still need to select to run the software from the virtual CD drive in the AutoPlay prompt, which would need to be done with the K, V, and M attached to that paticular computer which rules out saving space or not needing an addtional K, V, and M.
5. Most of the time pretty stable, but I should mention I did get a blue-screen one time. If somethings not working disconnect and reconnect. You also need to get the latest firmware update to fix some problems with the orginal software that ships.
6. They claim the projected screen from the controlled computer is automatically adjusted to screen size of controlling computer. I beg to differ
7. No logon support, but I suppose than the software would need to be installed to do that. Still its a pain for us that apply it in technical settings. Best have no password protection on startup with autologin enabled.

The most important con deserves its own paragraph and google hasn't revealed any valid workarounds/fixes that I have found. Because the product relies on VNC technologies, you automatically get disconnected any time you want to do something that requires admin rights that would trigger a User Account Control (UAC) prompt. For causual use its not an issue but for technicans its a nightmare. On XP its not a problem but with the implementation of this technology nearly 4 years ago now into the Windows operating system its a shame they don't develop an update to address it. I mean comeon, this product was released after the launch of Vista if I'm not mistaken. They claim compatibility for Windows Vista, but truly its not until you have disabled User Account Control on the system. In Windows 7 the problem is reduced slightly thanks to autoinvoke of builtin Windows utilities, but still nevertheless a problem.

Now I'll list some workarounds for the UAC problem:

• Disabling the switch to secure desktop setting for UAC might allow you to use it but it'll be less secure. Can't tell you how to disable it off the top of my head but some googling well show you how.
• In the coming release of Compatibility Sword 2.5, CSword well allow run as another user to be used even on a UAC system, so you may easily use the builtin administrator account for logon credidentials for such applications while leaving UAC enabled for system security. The builtin Windows Administrator account by default never has to deal with such UAC hassles.
• Disable UAC all together. If you do, I suggest you always run under a limited account to protect your computer, only using an admin account or the Administrator account when needed. You could also use the above workaround in this secnario, and with the current version of Compatibility Sword you can use run as even on Windows Vista as long as UAC is disabled.

So there you have it. I admire the amount of effort that's gone into this innovative product, but it could use a little more to keep up with the times. Do share your opinions if you've tried this product before, or especially if you've found alternitive solutions to the listed cons I have provided relating to it.

The re-write of TRT is going well. I just thought I'd let everyone know though not to expect a release until 2010. I have some teasers though as to how the new interface well look for you today. For one its definetly not as plain as the orginal one was:

Well I'm no designer or anything, but hows it look? Like it? Good, I've spent quite a bit of time (more than I would have liked) on the way TRT looks. I figured hey if people are going to be using TRT productively on a day to day basis it could look a little nicer.

Post your comments here if you have any or provide feedback in the TRT feedback forum. Thanks everyone and I hope to put out TRT 3.0 when its ready but only when its ready

Compatibility Sword 2.4 is completed.

Changes from 2.3 to 2.4:

• Re-compiled so it can be used on machines that have only .net framework 2 installed (ie 98, 2000, xp if its not updated, etc.)
• Compatibility Sword supports translation now to other languages through the use of a file you can have it generate for you using the new /translate switch. This file must be present in Compatibility Sword's directory in order for translation to occur.

With translation support anyone willing to translate to a second language and provide me with the file well have a link to their translation posted or hosted here for others to use.

I found an interesting post and thought I'd share on adding ext2fs/ext3fs support by manually creating the files to make ext2fs ifs a plugin. Going to give it a go. Reply if you've tried this and had any sucess

Ok, before I just had a Guestbook up for feedback other than in blog posts and I still do for those who don't want to register as a member on the site, but now I've decided to take it a step further. The forums on the site well be a good place to find/or give support and feedback.

Re-installing drivers in a fresh install of Windows is never a pleasant task. Its enough to haft to go find updates and re-install the software. What if you don't have the CD's for your devices anymore or you don't want to install the extra software they often include if its not needed? Last of all, you may have updated some of these drivers throughout the life of the current install, and may want to be able to restore updated drivers.

Fortunately, there is a solution. Most of the driver backup solutions are shareware now, but Double Driver is not. Freeware Double Driver is a driver utility capable of listing drivers on the system and backing them up so they can be restored later. In addition to structured folder backup, you can choose to have DD compress the drivers into a single compressed file or optionally create a self extract/restore exe.

Double Driver also comes standard in UBCD4Win, so you can backup your drivers from a non-booting copy of Windows. Never again worry about missing a driver and spend less time tracking software down for re-installs.

Today I've spent quite a bit of time working on DAD wiki. Documentation of Compatability Sword's command line options can be glanced over on Compatibility Sword's page now. I have re-uploaded all downloads except for FileDir2Prompt as zip packages so now you don't need 7-zip to extract downloaded files as promised. I have removed the long descriptions from CSword help message. It is my hope I'll have translation support for CSword in the future.

Anyway, speaking of CSword I have 2.3 finished.

Changes from 2.2 to 2.3

• Don't know whats up with the random messages in W7/XP, so I think I've at least suppressed them. The errors are logged if logging is enabled but not displayed.
• Run as user option only lists Administrators.
• Support for recursive logging (uses random filenames)
• Logging can be enabled anywhere in the arguments to Compatibility Sword and all arguments well be logged (before it didn't log anything before the /log switch in the arguments).
• /savelog switch added. Same as /log except the log file is perserved rather than automatically deleted.
• /hide switch added. Use to hide background utilities and other console applications from view.

I realize not everyone may have 7-zip handy to extract downloads here, so in a few days time I'm expecting to have self extracting files or standard zip files up instead. With these you won't need 7-zip to extract, just simply tell it where you want the extracted files to be and you're done.

Another major release for Compatibility Sword.

Changes from 2.1 to 2.2:

• Initial directory for application selected defaults to current application's directory. If no app has been specified it remains at system directory
• Leading space is automatically removed now in application arguments when filling it with directory/application paths
• You can select multiple files at the same time when filling application arguments
• Use the more option to display large amounts of console output only a few lines at a time using the more utility. Automatically enables /keepopen for you.
• New run as user options. This is so you can perform admin actions from a limited account on a system that doesn't have UAC or UAC is disabled. Before you had no choice on these systems but to run under an admin account. Now you do
• New /user switch added to specify user at command line rather than using the user interface
• New /password switch added to specify user password at command line rather than using the user interface (though for security reasons its better to use the user interface). If you are worried about security don't specify it (only the /user switch) and CSword well assume the /gui switch which well open up user interface and allow you to enter in secure manner before starting the process.
• /gui switch added. This switch is useful because if you supply it you can have the user interface display instead of running the process immediately with any other specified options pre-filled.
• /uacme switch added back. Well run Compatibility Sword in an administrative session.
• /more switch added. Causes console output to display a few lines at a time using the more utility. Assumes /keepopen whether or not you specified it.

Also, I'm pleased to announce that CSword is also now available as a U3 installable package meaning you can install it on your U3 drive and have easy access to it from U3's launchpad menu easily regardless of when and where you need it. I expect to have a U3 package for TRT as well with the release of 3.0 when it is released, perfect for the traveling student.

Ok everyone, off to other things I go

Just to let everyone know TRT development is not dead, not by any means. I've been so busy with CSword and life in general which is probably one reason why its taking as long as it has to even post an update yet have a release for 3.0.

I have some good news and some bad news. I guess I'll start with the bad news...

The bad news is I started over :p Why? Well, things were starting to get into unorganized matter again and a build was already greater in size than I would have liked. I came up with some new ideas for the program and have since started with a new GUI as well. I well have screenshots later when its somewhat functional.

The good news? Well... remember when I said quick test edit/test from explorer would go away? Nope! It's going to be there. I also said there wouldn't be selected import but there well be if all goes well.

Anyway, there's your update. I well be hitting the ground running with more active development on TRT shortly as CSword is pretty stable at this point.

Have you ever needed to do remote support for someone? A friend? Maybe your grandparents that live 3,000 miles away? Well... I think I've found the best tool for the job so here's my review of it.

Recently for this purpose I had used a tool known as CrossLoop. This tool's very useful indeed, so much so that its even been included in ubcd4win as a plugin. However, TeamViewer has some extra perks that I was delighted to find out about. They are:

• Completely portable for the support person thanks to the portable version available from portableapps.com. CrossLoop has to be installed.
• A single no install download for the user (The "Quick Start" version of the application) you're supporting. Just have them run it and in a few seconds you're looking at their desktop. With CrossLoop you haft to guide them over the phone with the install proccess. That's something relatively simple for us techies, but not so much for those we are helping.
• Secure connection is made automatically without manual configuration using SSH/SSL technologies
• Drag and drop files straight to remote system's desktop
• It is UAC W7/Vista friendly
• You are not bothered immediately upon startup to register a user accont and don't need one
• They have a test service so you can try it out to see if you like it
• The connection was a lot more reliable

For these reasons I decided to make the switch. Crossloop's not too bad until you start dealing with UAC on newer Windows systems and whenever a prompt comes up you get disconnected. With TeamViewer it even allows you to press the continue button in those prompts from your computer with of course no disconnecting.

Support (Full) version screenshot in Windows:

Quick Start version screenshot for those you help in Windows:

Not only is it free like Crossloop is, but they also offer a server version of the product, where system admins can setup unattended servers for 24/7 remote access. The remote support application supports both Windows and Mac users and for using from a Linux box they've got web access via flashplayer in your favorite web browser. You can even customize a version of the quick start application with personal tuch such as custom text/instructions and perhaps a company logo. Their business licenses are actually somewhat decent too, but I image most of you reading this would like to try it at the personal level first which is fine being completly free for non-commerical use.

Find out more about TreamViewer at teamviewer.com and obtain a portable full version from portableapps.com utility category  if the one they've got on their site doesn't work.

Major release today... Compatibility Sword 2.1 is ready

Changes from 2.0.0.2 to 2.1:

• Minor UI modifications and some extra tweaking to use fewer resources
• Fixed a bug where working directory was ignored for applications
• Added make system command in the UI
• Inital directory for application selection starts in system directory
• CSword now checks system directory for applications if you omit the path to them (before it just checked current directory and root of the current directory only)
• CSword automatically tacs on file extensions if omitted. Right now it only recognizes standard executible extensions and in this order: *.exe, *.com, *.bat
• Added /sys switch which opens a new command window elevated in system directory
• Added /sysdir switch. Works the same as /dir except it opens system directory
• Added /lappdatadir switch. Works the same as /dir except it opens user's local application directory (so you don't haft to go hunting it down and disabling hide hidden files/folders in explorer if you don't want to)
• Added /log switch. Comaptibility Sword's now got logging ability ! Now you and I myself can see what CSword's up to in the background and providing me with a log when you have problems may help me fix something if there's a bug I've overlooked.

I'd highly recommend updating if you've got an older release. Now time to start putting some effort into TRT

2.0.0.2 corrects an issue with applications automatically assumed to be console applications when elevated that appeared in CSword after drag and drop functionality for console applications was added in 2.0.0.1. Some additonal fixes/enhancements:

• Relative path "\" is correctly recognized now. Before it would just open the current directory instead
• Title on the GUI indicates when CSword is in an administrative session

Enjoy!

Just wanted to let everyone know that I've updated all the tutorials relating to Compatibility Sword and FileDir2Prompt. You can rest assured that the examples given are now accurate to CSword 2.x usage. I well probably be posting yet again another build. I've noticed that because of the changes made to enable drag drop console application usability like was present in FileDir2Prompt that when you use the GUI CSword automatically assumes you want to run a console application when you choose to elevate it regardless of whether keep open is selected or not. This automatically creates what may be an unwanted command window for graphical applications. I'll be working on that and few other minor tweaks.

Probably not the most useful thing but I'd thought I'd point it out. You can use relative paths in command prompt like ., .., or \ as a directory with Compatibility Sword. Watch the directory open up for you in a new command window. You might even be able to use variables which is great, say in batch programs. Pretty useful when you need to do tasks that require mutliple windows. I was going to add this functionality through some additional switches  but apparently Windows does it for us.

Quick breakdown for us that don't mess around with command prompts too often:

. = current directory

.. = parent of current directory

\ = root directory of the drive of the current directory

So here's what I'm thinking... wouldn't it be cool to have a way to open a new command prompt window that would be elevated from the current directory in the command window you forgot to elevate? Thanks to Compatibility Sword  and Windows playing nice this is quite easy.

You'll need Compatibility Sword 2.0 or later for the following to work correctly. Drop Compatibility Sword in your c:\windows\system32 directory or in 2.1 or later click the "Make System Command" link in the user interface. All done! Now to use...

csword . /uac

Simple enough right? You can toss out the /uac switch if you just want another window. CSword's now a system command, which means you can just refer to it as csword ... in command prompts or csword at a run dialog/creating new shortcuts regardless of directory that you may be in. It'll make it much easier to write batch files that use CSword to carry out application compatibility tasks as well. Any user (including non-admin users) well be able to use it (since everyone should have at least read access to the system32 directory).

News for XP users - 2.0.0.1 released. Compatibility Sword 2.0.0.1 corrects an inability to use the GUI to select a custom date when used in XP. This was not an error in the software itself as custom dates from the command line were tested and worked. This was due to XP not handling some condition checking that disables some admininistrative actions in the GUI correctly that's in place so CSword runs smoothly.

Some additonal changes have been made as well, thanks to everyone who provided feedback:

• "Cancel" option changed to "Exit" to be less confusing
• Some keyboard shortcuts have been added
• Applications passed to CSword as command line arguments with no additional parameters are now automatically assumed to be console applications you would like to see the output from so a new console window is created. This is to bring back drag drop functionality for applications from the past FileDir2Prompt project. If you need to pass other paremters such as compatibility mode, elevation, working directory, etc you still need to specify /keepopen to treat the app as a console application.
• Fixed running without any directory/app specified from command line

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

At this point I'm considering the merge offical. FileDir2Prompt is in the proccess of being integrated with the full re-write of Compatibility Sword. At this time 1.3 of FileDir2Prompt well remain available for download. Other than some confirmed bugs it should still work correctly for the time being until Compatibility Sword 2.0 can be completed and uploaded. Thanks to all who gave feedback and contributed to this decision. If you would like to see some screenshots of the completed GUI you may do so here.

Ok, if you read my last software development post you might have noticed some of the problems I've been having, paticulary with C# string formatting syntax causing a majority of the bugs I'm finding.

That said, I was working on the next release of FileDir2Prompt but I have been debating whether or not I should merge FileDir2Prompt with the re-write of CSword with no profiles. Since I don't use C# for CSword this would eliminate the workarounds and constant debugging of errors due to C#'s limitations. It'll make for one neat system utility. So what do you think? Drop a comment. Without it I may assume the ideas good and I don't want to totatlly rule out others opinions. I am planning on beginning development on CSword with the merge this weekend if everyones ok with it.