Darryl> Perhaps I'm being dense, but I don't see how this is going to work. Darryl> While gnuclient does have problems with DOS absolute paths and path Darryl> separators (this part of your patch is good), I don't see how changing Darryl> (for example), "c:/foo" into "/c/foo" is going to work; with this, Darryl> gnuclient is going to look for file "foo" in directory "/c" of the Darryl> current drive, and not in "c:/". Darryl> [ The cygwin gnuclient may need a similar change ("c:/" --> "//c/"), but Darryl> note that cygwin needs TWO (2) leading slashes; one slash won't work. ] My fault. I had mount'ed all of my drives so this would work. I think I have a better solution: Just realize that "c:\foo" is an absolute pathname and let xemacs deal with it. This can be handled by using a adding a pattern to file-name-handler-alist. Is this a better solution? Or should cygwin builds convert the drive to have two leading slashes, as you say above, and non-cygwin builds just leave everything alone? Ray