Phil Bradley's weblog: Top 10 Useful Web Tools from Pandia:I use Picasa Web Albums instead of Flickr -- though lately Picasa WA has really been annoying me. Otherwise I'm aligned with Phil in all tool choices.
...Netvibes is their preference for a start page. I use Netvibes as my backup system on Internet Explorer, but I'm very firmly in the PageFlakes camp here. More flexible, better options, easier to use, larger user base ...
Thursday, November 08, 2007
Phil Bradley's Top 10 Useful Web Tools
A terrific list. I use many of Phil's choices, but Netvibes and PageFlakes are new to me:
Fixing a broken Windows XP Remote Desktop Connection install
This was so much harder than it should have been.
My home copy of XP Pro no longer had a Program shortcut to Remote Desktop Connection. It wasn't in Programs\Accessories\Communications or anywhere else I could find.
On the other hand RDC was installed. I tried reinstalling from the XP CD (see help for XP) but it said a newer version was already in place.
I tried looking for a way to uninstall RDC thinking I could then reinstall and retrieve my shortcut - I couldn't find any way to do that.
I tried searching my hard drive for the file and navigating windows folders, but I couldn't find it.
Eventually I found Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP (KB925876) and installed that. It went well, but it didn't create a favorite/shorcut!
Well, it turns out that c:\windows\system32\mstsc.exe is the remote desktop client (tsc probably stands for terminal server client).
Isn't that pretty bloody obscure.
So I created a shortcut to that and now everything is fine. Presumably I accidentally deleted the original when cleaning up my start folders (specifically, I moved a lot of stuff out of the "all users" folder to protect it from the children).
How did I figure this one out? I had to find another XP machine and identify where the shortcut went on that machine. There was no other way.
Incidentally, mstc.exe has some very obscure command line options:
My home copy of XP Pro no longer had a Program shortcut to Remote Desktop Connection. It wasn't in Programs\Accessories\Communications or anywhere else I could find.
On the other hand RDC was installed. I tried reinstalling from the XP CD (see help for XP) but it said a newer version was already in place.
I tried looking for a way to uninstall RDC thinking I could then reinstall and retrieve my shortcut - I couldn't find any way to do that.
I tried searching my hard drive for the file and navigating windows folders, but I couldn't find it.
Eventually I found Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP (KB925876) and installed that. It went well, but it didn't create a favorite/shorcut!
Well, it turns out that c:\windows\system32\mstsc.exe is the remote desktop client (tsc probably stands for terminal server client).
Isn't that pretty bloody obscure.
So I created a shortcut to that and now everything is fine. Presumably I accidentally deleted the original when cleaning up my start folders (specifically, I moved a lot of stuff out of the "all users" folder to protect it from the children).
How did I figure this one out? I had to find another XP machine and identify where the shortcut went on that machine. There was no other way.
Incidentally, mstc.exe has some very obscure command line options:
ParametersWhen I use RDC on a dual monitor setup, full screen mode is limited to the size of my primary monitor. I wonder if I could use the /w and /h options to set it to the size of my larger secondary monitor ...
ConnectionFile : Specifies the name of an .rdp file for the connection.
/v:server : Specifies the remote computer to which you want to connect.
/console : Connects to the console session of the specified Windows 2000 Server.
/f : Starts Remote Desktop connection in full-screen mode.
/w:width /h:height : Specifies the dimensions of the Remote Desktop screen.
/edit : Opens the specified .rdp file for editing.
Remarks ...
.rdp files are stored for each user as hidden files in My Documents.
Searching: Google and Yahoo are very different from Microsoft
Today a quite heavily used and very senior Mac site noticed that almost all their search referrals come via Google:
In any case I'm posting on this because I noticed something curious the other day that could be related.
I used the search string "Gordon's Tech" on Microsoft Live Web search. My blog didn't appear anywhere in the first few pages. Oh well, I thought, I can just type the URL. I have no delusions of fame after all.
On impulse though, I tried "Gordon's Tech" (phrase search, so with the quotes) on Google. The blog is the number one result. It's also, for that matter, the number one result on Yahoo (albeit with an older URL that still works).
I don't think this accounts for the TidBITS oddity, but it is a worthwhile reminder that Microsoft's search results can be very different from those of Google or Yahoo. So if you don't find what you expect on Google, try Microsoft.
Of course you can guess which search engines I approve of.
TidBITS Inside TidBITS: Google Used 70 Times More than Yahoo:Very strange. My first guess is that Google Analytics has a bug in it, but that would be one heck of a bug.
... What could possibly account for Google's utter dominance in our statistics? I know the crawlers come through all the time, and indeed, searching Yahoo and the others for the same keywords used in the popular Google searches brings up our articles. Do users of Yahoo and the others just not like us?
In any case I'm posting on this because I noticed something curious the other day that could be related.
I used the search string "Gordon's Tech" on Microsoft Live Web search. My blog didn't appear anywhere in the first few pages. Oh well, I thought, I can just type the URL. I have no delusions of fame after all.
On impulse though, I tried "Gordon's Tech" (phrase search, so with the quotes) on Google. The blog is the number one result. It's also, for that matter, the number one result on Yahoo (albeit with an older URL that still works).
I don't think this accounts for the TidBITS oddity, but it is a worthwhile reminder that Microsoft's search results can be very different from those of Google or Yahoo. So if you don't find what you expect on Google, try Microsoft.
Of course you can guess which search engines I approve of.
Word processing on OS X: my personal choices
A colleague asked me about what I use for word processing on the Mac. I started to respond, then realized it could be a quick post.
Briefly, I use Nisus Writer Express (NWE). It uses .RTF or .DOC as its native file format; that one absolute requirement of mine wiped out all the alternatives except Microsoft Word -- and I don't like Word. NWE is Cocoa native and works well with OS X services, it does the basics well. It has a great UI and has been fast and reliable in my experience. My wife uses it without any problems.
I haven't written any very long documents with it however.
Nisus has recently released Pro version of NWE. I'll eventually upgrade to, but it's a low priority for me. If the Pro version had a true outliner I'd probably have done it by now.
Nisus does a fair job importing simple Word documents, but even the Pro version can't import a Word Table of Contents. That's disappointing, since I use Word TOCs quite a bit. Nisus is, however, a much more agreeable word processing tool than Word. For one thing, the Styles actually make sense.
OS X 10.4 ships with TextEdit which uses a "package" version of RTF, but it's too feature sparse. The version in 10.5 is said to be closer to a true word processor and it has support for Microsoft's XML and the ODF file formats (inherited from 10.5). I've no experience with 10.5 though -- and I won't for months to come.
Pages, part of Apple's iWork suite, uses a proprietary Apple XML file format. That rules it out for me.
The only remaining alternatives are Word for Mac or Word 2003/2007 running in a Win2K or XP VM (VMWare or Parallels).
If all my machines were MacTel and I didn't use Nisus, I'd probably run Word 2003 in my Win2K VM. The tyranny of the .DOC file format should not be underestimated.
Update 2/28/2008: I've unfortunately become aware of Nisus Achilles heel. It can't compress embedded images. So a 3 MB JPEG embedded in a Nisus document produces a 20MB file -- Nisus stores the image as an uncompressed bitmap. Word compresses embedded images, and allows them to be clipped. I'm curious to see what Pages does.
Update 10/13/2008: When I moved my machines to 10.5 I also upgraded to Nisus Writer Pro. I haven't tested to see if it still has the bitmap problem, but it does have other issues. In a document where I used huge fonts (visually impaired user) Nisus was slow to redraw some pages. An image positioned using Nisus Writer Pro vanished when the document was opened in an older version of Nisus Writer Express. I have also become aware of how much I miss a drawing tool layer. AppleWorks drawing tools were particularly good, they really played to the strengths of AppleWork's compound document model. I might take another look at iWork, though that is a return to proprietary document formats. I do wish the rest of the world cared more about document longevity!
Briefly, I use Nisus Writer Express (NWE). It uses .RTF or .DOC as its native file format; that one absolute requirement of mine wiped out all the alternatives except Microsoft Word -- and I don't like Word. NWE is Cocoa native and works well with OS X services, it does the basics well. It has a great UI and has been fast and reliable in my experience. My wife uses it without any problems.
I haven't written any very long documents with it however.
Nisus has recently released Pro version of NWE. I'll eventually upgrade to, but it's a low priority for me. If the Pro version had a true outliner I'd probably have done it by now.
Nisus does a fair job importing simple Word documents, but even the Pro version can't import a Word Table of Contents. That's disappointing, since I use Word TOCs quite a bit. Nisus is, however, a much more agreeable word processing tool than Word. For one thing, the Styles actually make sense.
OS X 10.4 ships with TextEdit which uses a "package" version of RTF, but it's too feature sparse. The version in 10.5 is said to be closer to a true word processor and it has support for Microsoft's XML and the ODF file formats (inherited from 10.5). I've no experience with 10.5 though -- and I won't for months to come.
Pages, part of Apple's iWork suite, uses a proprietary Apple XML file format. That rules it out for me.
The only remaining alternatives are Word for Mac or Word 2003/2007 running in a Win2K or XP VM (VMWare or Parallels).
If all my machines were MacTel and I didn't use Nisus, I'd probably run Word 2003 in my Win2K VM. The tyranny of the .DOC file format should not be underestimated.
Update 2/28/2008: I've unfortunately become aware of Nisus Achilles heel. It can't compress embedded images. So a 3 MB JPEG embedded in a Nisus document produces a 20MB file -- Nisus stores the image as an uncompressed bitmap. Word compresses embedded images, and allows them to be clipped. I'm curious to see what Pages does.
Update 10/13/2008: When I moved my machines to 10.5 I also upgraded to Nisus Writer Pro. I haven't tested to see if it still has the bitmap problem, but it does have other issues. In a document where I used huge fonts (visually impaired user) Nisus was slow to redraw some pages. An image positioned using Nisus Writer Pro vanished when the document was opened in an older version of Nisus Writer Express. I have also become aware of how much I miss a drawing tool layer. AppleWorks drawing tools were particularly good, they really played to the strengths of AppleWork's compound document model. I might take another look at iWork, though that is a return to proprietary document formats. I do wish the rest of the world cared more about document longevity!
Apple's temperature problems: iMac again
This is very disappointing. The 1st generation flat panel iMacs had very serious heat problems, but Apple did come up with a passable redesign. The Intel switch was supposed to make this a thing of the past.
It appears that Apple forgot that lesson rather quickly:
It appears that Apple forgot that lesson rather quickly:
AppleInsider | Freezing iMacs may be victims of hardware, not softwareOnce again, proof that you never want to buy the first generation of any Apple hardware or software product - no matter how glowing the reviews. Apple does not have a "culture of quality" -- so customers need to wait for early adopters to do basic quality control.
...This and other reports provide increasing support for beliefs that the lockups and related symptoms are caused by excessive heat inside the all-in-one chassis. Users often report graphical corruption in the operating system as a precursor to the freezes -- a sign some PC users recognize of a video card pushed beyond its safe operating temperature. In some instances, the visual artifacts become increasingly likely as time goes on....
Wednesday, November 07, 2007
SpiderOak: online backup for Mac and Windows
SpiderOak provides online backup, unlimited public file share and differential backup (only changed parts of files). Cost $10/month but limited to 20 GB. Requires a proprietary client.
Interesting, but I don't trust their software enough to expose my machine to it. I'll keep an eye on them though, maybe when they've been around a while ...
It's a bit odd that they don't tell you how to sign up for their free 2GB service. I suspect it's done through the client but they might mention that. I suspect they'll clarify that omission pretty soon.
Interesting, but I don't trust their software enough to expose my machine to it. I'll keep an eye on them though, maybe when they've been around a while ...
It's a bit odd that they don't tell you how to sign up for their free 2GB service. I suspect it's done through the client but they might mention that. I suspect they'll clarify that omission pretty soon.
Microsoft LifeCam software progress: now the blue screen can't be read
I bought a Microsoft LifeCam VX-6000 over a year ago. That was before I realized the quality consumer desktop videoconferencing market was dead on Windows. (Ok, there may be an rare exception.)
At the time it installed without a problem on my home XP machine, but on my Dell Latitude D620 it was another story:
Gordon's Tech: Microsoft LifeCam VX-6000 - personal impressions
... On my pure, clean, office laptop however, it produced the XP Blue Screen of Death (STOP error) on launch. I don't remember ever seeing the XP BSOD. I think it's produced by an 'inner ring' memory error, something that only device drivers can do...This is what one sees in white on blue text:
A problem has been detected and windows has been shut down to prevent damage to your computer ...
STOP: VX6000xp.sys
kmixer.sysHappens every time on launch of LifeCam (is it doing some kind of dynamic device driver hack?). When you get these errors, btw, you get to file a special bug report with Microsoft on system restart.
I restored the system to health per Microsoft troubleshooting recommendations:
System restore: restored to the point set by the LifeCam install.I'll try again in September when Microsoft says they'll put the installer files online.
sfc /scanonce: ran sfc.exe to verify core XP files were intact. See xp resource kit, system file tools
Well, I didn't get back to it in September 2007, but I tried again today, 13 months later. I downloaded the latest XP SP 2 LC 1.4 installer.
I'm pleased to report that Microsoft has made a lot of progress in the past year. Now the blue screen vanishes so quickly it can't be read, and the system doesn't let me generate a bug report on restart.
I think there's something buggy with the video in my Dell laptop. Once again I miss my Macs.
I wonder if Microsoft is going to decide they need to buy Dell and emulate Apple ...
Subscribe to:
Posts (Atom)