Hello Peter, On 18 June 2004, 02:01 +0200 (01:01 local time) Peter Ouwehand [PO] in mid:[EMAIL PROTECTED] wrote:
...<snip> MW>> Windows XP warns you if you include a space in the share name; for MW>> example you wouldn't be able to access these shares from DOS. PO> Such shares not being accessible by DOS is correct. But, really, who PO> cares, I don't. My W2k does not warn about it (PC's on my network all PO> run on W2k). I know NT4 warns you, but again, who cares about DOS these PO> days?? It was the first MS-OS to support long (*NIX alike) PO> directory/filenames. I think you would have the same problem with a Samba share. What you have works for you; that's okay. I was passing on best practice. Also, I'd be surprised if you can use hyper links to access network shares. MW>> I think you'll find it's the same for URI; you shouldn't include MW>> spaces in network resources. PO> True for internet domain names. From the top of my head, not true for PO> directory names, can't find the related RFC right now though. That's not what I was saying. \\SME\mp3 isn't a directory name it's a networking resource. That's why the UNC applies. PO> Reviewing your original remark, we're getting off track here. Yep. I'll copy this to TBOT should you wish to continue the thread. PO> Your comment was related to TB and windows shares like PO> \\server\share. This is not internet related, which (very simply PO> stated) uses protocol://server/dir/file. Look carefully; they're the same... using backslashes is a Windows thing. PO> Just another remark: TB can't work with something like (windows) PO> \\server\share to store mail bases. You'll need to use a mapped PO> network drive for that. That's correct. -- As ever, :Martin_Webster: Jabber mjw | ICQ 15893823 | PGP Key ID 0xD644460D The Bat! 2.12 Beta/1 | BayesIt! 0.5.5 (Windows XP Professional Service Pack 1) ________________________________________________ Current version is 2.11.02 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
