On Wed, 2003-04-09 at 20:49, Mike Chambers wrote: > On Tue, 2003-04-08 at 09:34, Christopher A. Williams wrote: > > I'm looking for additional documentation on the smb:/// URL type for > > browsing Windows shares. Basically, I need to know if there is a way to > > configure Nautilus to see folders for shares with names that have > > spaces, special characters or just have long names. > > And why can't it see them? Mine does. If he knew that, I guess he wouldn't be asking here, would he? ;o) > > Moreover, if, in the Nautilus window, you use the URL: > > > > smb://<server>/Chris'%20Stuff > > > > You can browse the contents of the "Chris' Stuff" share, even though you > > can not see the folder for the share itself. > > You can't? Hrm, guess I should take a screen shot of what mine looks > like with two names and able to see them and view them? > http://www.netlyncs.com/~reddawg/filebrowsing.png > I think in his case, the issue isn't the space, but the apostrophe. Here's the behavior I see accessing shares from a Win2K install running in VMware (named Osgiliath): Shared folders that have apostrophes in the names do not appear at the share level, but will appear as subfolders of shared directories. So if I share My Documents and My Documents\Bob's Tattoos from Osgiliath, only My Documents appears under smb://osgiliath. Opening the My Documents share reveals Bob's Tattoos amongst all the other subdirectories. Rename Bob's Tattoos to Bobs Tattoos, and both My Documents and Bobs Tattoos appear under smb://osgiliath. Win2K seems to have no problem with the apostrophe'd share. > -- > Mike Chambers > Madisonville, KY > > "Hand over the code, and no one gets hurt!" -- Michael Knepher <limbo@xxxxxxxxxxxxxx>