b.cognosco

There are three modes of remote K-Logging. They are:

1. Remote access to a K-Log through a browser on a random PC.
2. Mobile laptop with a local K-Log tool.
3. Remote K-Logging via e-mail.

In my own post on the issues I noted that while using a mobile laptop is an enticing idea I don't want to give up my desktop workstation, so until there is a way to synch Radio across multiple computers I can't do this.

Well, Jon Udell has a story addressing a simple way to solve my dilemma. In Radio Supports XCOPY Deployment Jon explains:

FWIW, my recipe for backing up Radio, and also transplanting it to/from my notebook PC for travel, is simply:

xcopy /s /d C:radio. T:radio.

In this era of fast networks and capacious hard drives, it's really no problem.

BTW this feature, long missing from Windows due to registry entanglements, is touted as a new thing -- "xcopy deployment" -- in the .NET marketing literature. Works in Radio too :-)

I'm guessing there are some path issues to resolve here, but maybe not. In any case, I know I've seen a script somewhere for fixing paths. So if it is an issue I'm sure there is a fix. Being able to move Radio to a laptop for travel but not having to use a laptop all the time is great thing for me. Thanks to Jon Udell and the power of the web for getting this info to me.

Update: a link to the discussion thread on Andy Fragen's myFixFilePathsAndAddresses script.