1. Accessing Network Paths
- Posted by mattlewis (admin) Sep 17, 2011
- 1438 views
There have been some issues lately when accessing network paths on Windows (see ticket:696). Euphoria 4.0.3 can access these sorts of paths, referred to as Uniform Naming Convention (UNC).
The format of a UNC path:
server\share-name\etc
Also, note that you can use backtick quotes to avoid having to escape the backslashes:
`\\server\share-name\rest\of\path` "\\\\server\\share-name\\rest\\of\\path"
Matt
2. Re: Accessing Network Paths
- Posted by jimcbrown (admin) Sep 17, 2011
- 1429 views
There have been some issues lately when accessing network paths on Windows (see ticket:696). Euphoria 4.0.3 can access these sorts of paths, referred to as Uniform Naming Convention (UNC).
The format of a UNC path:
server\share-name\etc
Also, note that you can use backtick quotes to avoid having to escape the backslashes:
`\\server\share-name\rest\of\path` "\\\\server\\share-name\\rest\\of\\path"
Matt
Have there been any issues? Euphoric reported some but it turned out to be a problem of overquoting. Derek also reported OS-related issues, but he isn't clear on whether or not Euphoria was even used on those systems.
3. Re: Accessing Network Paths
- Posted by mattlewis (admin) Sep 17, 2011
- 1402 views
Have there been any issues? Euphoric reported some but it turned out to be a problem of overquoting. Derek also reported OS-related issues, but he isn't clear on whether or not Euphoria was even used on those systems.
Nothing euphoria related, AFAIK. There was a question recently on IRC about his while I was sleeping, and by the time I logged back on, the questioner was logged off. So, I thought I'd post this here as a way of continuing the conversation.
Matt
4. Re: Accessing Network Paths
- Posted by DerekParnell (admin) Sep 17, 2011
- 1375 views
Have there been any issues? ...
Nothing euphoria related, AFAIK. ...
I don't know of any issues of using UNC in the open() or dir() calls, but I think that there would still be issues with the routines that extract parts of a path and with the canonical_path() routine.
5. Re: Accessing Network Paths
- Posted by jimcbrown (admin) Sep 17, 2011
- 1384 views
Have there been any issues? ...
Nothing euphoria related, AFAIK. ...
I don't know of any issues of using UNC in the open() or dir() calls, but I think that there would still be issues with the routines that extract parts of a path and with the canonical_path() routine.
D'oh!
Should they support UNC or should we have a separate canonical_unc_path() et al to handle this case?
6. Re: Accessing Network Paths
- Posted by jimcbrown (admin) Sep 17, 2011
- 1393 views
Have there been any issues? Euphoric reported some but it turned out to be a problem of overquoting. Derek also reported OS-related issues, but he isn't clear on whether or not Euphoria was even used on those systems.
Nothing euphoria related, AFAIK. There was a question recently on IRC about his while I was sleeping, and by the time I logged back on, the questioner was logged off. So, I thought I'd post this here as a way of continuing the conversation.
Matt
Kat seems to have made a really simple, elementary error that is seemingly at odds with her mastery of DOS and W95. (Then again, administrative shares were new in W2K so this feature might have been too new for her.)
Either that or Kat is doing something really unusual, but then this contradicts her statements on not wanting to manually create and map shares.
7. Re: Accessing Network Paths
- Posted by m_sabal Sep 17, 2011
- 1357 views
I've been using UNC pathing under 3.1 with both open and dir for years now with no issues (except when I get overzealous with the backslashes, of course :p).
8. Re: Accessing Network Paths
- Posted by useless Sep 17, 2011
- 1420 views
Have there been any issues? Euphoric reported some but it turned out to be a problem of overquoting. Derek also reported OS-related issues, but he isn't clear on whether or not Euphoria was even used on those systems.
Nothing euphoria related, AFAIK. There was a question recently on IRC about his while I was sleeping, and by the time I logged back on, the questioner was logged off. So, I thought I'd post this here as a way of continuing the conversation.
Matt
Kat seems to have made a really simple, elementary error that is seemingly at odds with her mastery of DOS and W95. (Then again, administrative shares were new in W2K so this feature might have been too new for her.)
Either that or Kat is doing something really unusual, but then this contradicts her statements on not wanting to manually create and map shares.
And what would that error be?
I do not think i am doing something unusual in accessing files between computers using windoze's lan networking, instead of a custom socks-based system of sync'ing the computers. You guys keep changing Euphoria so code written a year ago can't be run on each new major version. I no longer recognise the socks code.
Thanks for the great example of how once i say something, i am forever pigeonholed that way, no matter what else i say. I have used winxp for over 10 years now, and i have already explained why. But you go ahead and keep on saying i use only dos and win95 on a 386 box. That said, on 6 of the 10 olde P4 puters in the cluster, there's as many as 7 dosboxes open on each, and code using system(), system_exec(), calling .bat files and non-windowed non-gui'd programs in all of them.
I made a work-around for the problem. It's an OS problem, i can replicate it outside Euphoria.
useless
9. Re: Accessing Network Paths
- Posted by mattlewis (admin) Sep 17, 2011
- 1350 views
I made a work-around for the problem. It's an OS problem, i can replicate it outside Euphoria.
I think Derek reported having trouble using UNC paths when Windows machines weren't part of the same workgroup. I believe that was with Windows 7, so it might not be relevant.
Matt
10. Re: Accessing Network Paths
- Posted by jimcbrown (admin) Sep 17, 2011
- 1337 views
Kat seems to have made a really simple, elementary error that is seemingly at odds with her mastery of DOS and W95. (Then again, administrative shares were new in W2K so this feature might have been too new for her.)
Either that or Kat is doing something really unusual, but then this contradicts her statements on not wanting to manually create and map shares.
And what would that error be?
Hmm. Am I really the only one who has noticed? It's really simple.
I do not think i am doing something unusual in accessing files between computers using windoze's lan networking, instead of a custom socks-based system of sync'ing the computers.
I don't think so either.
You guys keep changing Euphoria so code written a year ago can't be run on each new major version. I no longer recognise the socks code.
We've only released one major version (from 3.x to 4.x), so this is a pretty small sample size. That said, I think if breaking changes need to be made, it should be done in the major versions only.
The socket code is written in C, so I'd expect it to be unrecognizable (except for those who understand C).
Thanks for the great example of how once i say something, i am forever pigeonholed that way, no matter what else i say. I have used winxp for over 10 years now, and i have already explained why. But you go ahead and keep on saying i use only dos and win95 on a 386 box. That said, on 6 of the 10 olde P4 puters in the cluster, there's as many as 7 dosboxes open on each, and code using system(), system_exec(), calling .bat files and non-windowed non-gui'd programs in all of them.
In the past you seemed to have had an impressive knowledge of DOS and W95, hence my referencing your mastery of it. Since you were forced to use XP, whereas you used DOS and W95 by choice, I hesitated to state that you had mastered XP to the same level.
Perhaps I was mistaken. After all, the feature I believe that you are attempting to use was new to W2K, and AFAIK would not work on a W95-hosted server.
In any case, I deny making the statement that you "use only dos and W95 on a 386 box." For clarification, I'd like to say that while you are a master of DOS and W95 and W98, you clearly know your way around XP as well, even if you had not achieved the same level of mastery with it as you had with the earlier M$ systems.
11. Re: Accessing Network Paths
- Posted by useless Sep 17, 2011
- 1369 views
Kat seems to have made a really simple, elementary error that is seemingly at odds with her mastery of DOS and W95. (Then again, administrative shares were new in W2K so this feature might have been too new for her.)
Either that or Kat is doing something really unusual, but then this contradicts her statements on not wanting to manually create and map shares.
And what would that error be?
Hmm. Am I really the only one who has noticed? It's really simple.
Thanks for telling us what the error is, as i asked of you.
Not going to play with the nested bracketed quote forum syntax here, i have things to do, so apply the following to the rest of your post.
Re: versions, why must you be dense? I must have 5 versions of Eu between 3.1 and 4.whatever.it.is.now.
I have never used win98.
useless
I do not think i am doing something unusual in accessing files between computers using windoze's lan networking, instead of a custom socks-based system of sync'ing the computers.
I don't think so either.
You guys keep changing Euphoria so code written a year ago can't be run on each new major version. I no longer recognise the socks code.
We've only released one major version (from 3.x to 4.x), so this is a pretty small sample size. That said, I think if breaking changes need to be made, it should be done in the major versions only.
The socket code is written in C, so I'd expect it to be unrecognizable (except for those who understand C).
Thanks for the great example of how once i say something, i am forever pigeonholed that way, no matter what else i say. I have used winxp for over 10 years now, and i have already explained why. But you go ahead and keep on saying i use only dos and win95 on a 386 box. That said, on 6 of the 10 olde P4 puters in the cluster, there's as many as 7 dosboxes open on each, and code using system(), system_exec(), calling .bat files and non-windowed non-gui'd programs in all of them.
In the past you seemed to have had an impressive knowledge of DOS and W95, hence my referencing your mastery of it. Since you were forced to use XP, whereas you used DOS and W95 by choice, I hesitated to state that you had mastered XP to the same level.
Perhaps I was mistaken. After all, the feature I believe that you are attempting to use was new to W2K, and AFAIK would not work on a W95-hosted server.
In any case, I deny making the statement that you "use only dos and W95 on a 386 box." For clarification, I'd like to say that while you are a master of DOS and W95 and W98, you clearly know your way around XP as well, even if you had not achieved the same level of mastery with it as you had with the earlier M$ systems.
[/quote]
12. Re: Accessing Network Paths
- Posted by useless Sep 17, 2011
- 1388 views
I made a work-around for the problem. It's an OS problem, i can replicate it outside Euphoria.
I think Derek reported having trouble using UNC paths when Windows machines weren't part of the same workgroup. I believe that was with Windows 7, so it might not be relevant.
Matt
Yeas, they must be part of the same workgroup, etc., on winxp too, but that wasn't the problem here. In my usual manner of doing things in a hurry to make work happen, i didn't do a great job of debugging the problem. I had actually typed out the problem description here, which is outside Euphoria, but as jimcbrown didn't say what the mistake i made was, i deleted what i typed and i'm going to wait on him.
useless
13. Re: Accessing Network Paths
- Posted by jimcbrown (admin) Sep 17, 2011
- 1391 views
Not going to play with the nested bracketed quote forum syntax here, i have things to do, so apply the following to the rest of your post.
Re: versions, why must you be dense? I must have 5 versions of Eu between 3.1 and 4.whatever.it.is.now.
You said major releases. Generally, only pre-alpha and alpha releases are allowed to break things (otherwise the API should be considered set in stone, though there are a few cases where we had to break things in beta those are exceptions that hopefully won't ever reoccur). Otherwise, only major releases can change API in a breaking way.
Thus the move to 4.0 made major API changes and some breakage, but gong forward, 4.0.1, .2, .3 and so on won't break any code, and neither should 4.1.0, 4.1.1, etc. But 5.0, the next major release, might.
I have never used win98.
You had some experience with attempting to install it, IIRC. I vaguely recall a converstation along those lines, at least.
14. Re: Accessing Network Paths
- Posted by useless Sep 17, 2011
- 1350 views
So jimcbrown, what was the simple mistake you said i made?
useless
15. Re: Accessing Network Paths
- Posted by jimcbrown (admin) Sep 17, 2011
- 1344 views
So jimcbrown, what was the simple mistake you said i made?
useless
Forgetting the dollar sign $ after the drive letter (E in this case). Unless you purposely created a share with a one-letter name, which seems unusual to me since I've never seen it done before.
16. Re: Accessing Network Paths
- Posted by useless Sep 17, 2011
- 1335 views
So jimcbrown, what was the simple mistake you said i made?
useless
Forgetting the dollar sign $ after the drive letter (E in this case). Unless you purposely created a share with a one-letter name, which seems unusual to me since I've never seen it done before.
I did.
useless
17. Re: Accessing Network Paths
- Posted by jimcbrown (admin) Sep 18, 2011
- 1338 views
I had actually typed out the problem description here, which is outside Euphoria, but as jimcbrown didn't say what the mistake i made was, i deleted what i typed and i'm going to wait on him.
useless
Hmm. I missed this. Any ways, are you planning on typing it up now?
18. Re: Accessing Network Paths
- Posted by useless Sep 24, 2011
- 1261 views
I had actually typed out the problem description here, which is outside Euphoria, but as jimcbrown didn't say what the mistake i made was, i deleted what i typed and i'm going to wait on him.
useless
Hmm. I missed this. Any ways, are you planning on typing it up now?
The app cannot access files in the format of it's own lan name. This is a problem if you are sharing an Eu app across computers on a lan, where the shared program needs to access a file(s) on one of the computers for reading or writing status as they run, so, for instance, they don't pick the same data from some file to operate on. For instance, i have files "source.txt", "working.txt", and "done.txt" on one computer, and all ten computers access those three files.
Do a dos command ipconfig > to some text file, read in the text file and grab your lan ip, dns it to get that computer's lan name. In the program that's run on all the computers on the lan, where it accesses a file shared and common to all the running processes, you can write the distributed file to have the lan NAME address, like
sequence workingurls_filename = "\\\\PuterName\\ShareRoot\\path\\filename"
or somesuch. If the dns of your lan ip matches the PuterName, change the workingurls_filename to the local path. This is easiest if the share is an entire drive, because then
sequence workingurls_filename = "\\\\PuterName\\ShareRoot\\path\\filename" = sequence workingurls_filename = "ShareRoot:\\path\\filename"
So one file, unchanged, can access the shared file(s) by it's lan name even if it's run on the computer that file is on.
useless
