|
|
Post by bitpusher on Nov 26, 2013 18:37:57 GMT -5
I bought a Raspberry Pi to learn Linux and do various experimenting and tried to use //SERVER/SHARE notation in the SPFLite File Manager path field and it works but "beeps" and gives error message "Directory: //SERVER/SHARE does not exist". All the subdirectories show up and can be selected normally and the files edited. I tried accessing my Synology DS410 NAS by the same method and got the same result.
The goal is to do major C source code, script file, and configuration file editing for my RasPi using SPFLite from either my main Windows XP system or my Acer W7 noterbook instead of the Linux editors.
Is this a user error or a bug?
Carl
I forgot to add that I'm using SPFLite V7.0.3217.
|
|
|
|
Post by George on Nov 27, 2013 12:09:52 GMT -5
Bitpusher:
Looking at the code, there's a bit of 'hmm, wonder what THAT was supposed to be doing' stuff lying about. Looks like remnants from a real early version, so I just deleted the few lines, they weren't accomplishing anything.
This will be included in the next 7.1 release. Meanwhile, you'll have to bear with the Beeps I'm afraid. At least it's continuing to work.
Thanks for the report.
George
|
|
|
|
Post by bitpusher on Nov 27, 2013 20:37:21 GMT -5
Thanks for the replies. George - I thought you would like to know about the bogus error message. I can put up with that. I'm happy that it works because I would much rather do any major Linux text editing with SPFLite than with either nano, vim, or emacs plus it is much easier to specifiy the //SERVER/SHARE than fooling around with mounting it as a drive letter. Robert - I'm not a network guru either but I'm slowly learning it and Linux. SPFLite works with either forward or backwards slash characters. On my Windows 7 notebook I ran the following with CMD.EXE on my LAN network attached Western Digital WDTV Live Hub and as you can see the DIR command worked. However CMD.EXE will not work with forward slash characters and you cannot set the share as the current directory although I can do that in my JP Software TakeCommand command processor. C:\>dir \\WDTVHUB1\WDTVLIVEHUB Volume in drive \\WDTVHUB1\WDTVLIVEHUB is WDTVLiveHub Volume Serial Number is 0AFE-0FDD Directory of \\WDTVHUB1\WDTVLIVEHUB 12/21/2011 23:25 <DIR> . 11/27/2013 20:13 <DIR> .. 10/25/2011 11:38 250 DESCRIPT.ION 11/26/2013 15:49 <DIR> MUSIC 04/23/2011 15:15 <DIR> PHOTO 12/31/1999 19:01 <DIR> Sample Media 04/18/2011 20:06 0 TwonkyMediaServer-log.txt 11/14/2013 19:06 <DIR> VIDEO 2 File(s) 250 bytes 6 Dir(s) 248,793,927,680 bytes free C:\> Carl |
|
|
|
Post by George on Nov 28, 2013 12:55:14 GMT -5
Robert:
Bitpusher:
I tried this with my lan drive which I normally have connected as the Z: drive.
The old code I removed was testing if the name provided was accessible as a directory. Z: comes back as OK, as does something like Z:\CaLibre.
But the UNC name \\WD-Lan-Drive\Public gives the error message, but does seem to work.
The UNC name \\WD-Lan-Drive\Public\CaLibre does not produce the error, and works fine.
The old code tested to see if the name provided came back from a directory search marked with a Directory flag.
So I think Robert is correct in that the Share name is not officially considered a Directory name, but sort of still is, which is why it continues. This may be masked somewhat by the PowerBasic functions being used to do the tests. I'm not sure what pure Windows API calls would return.
Since all the old code did was issue a warning message, I just took it out. If it was really wrong, it would fail further down in the code with a message anyway.
George
|
|
