LB Booster
« UNC paths »

Welcome Guest. Please Login or Register.
Apr 1st, 2018, 03:50am



ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018.
We apologize Conforums does not have any export functions to migrate data.
Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.

Thank you Conforums members.
Speed up Liberty BASIC programs by up to ten times!
Compile Liberty BASIC programs to compact, standalone executables!
Overcome many of Liberty BASIC's bugs and limitations!
LB Booster Resources
LB Booster documentation
LB Booster Home Page
LB Booster technical Wiki
Just BASIC forum
BBC BASIC Home Page
Liberty BASIC forum (the original)

« Previous Topic | Next Topic »
Pages: 1  Notify Send Topic Print
 thread  Author  Topic: UNC paths  (Read 234 times)
Richard Russell
Administrator
ImageImageImageImageImage


member is offline

Avatar




Homepage PM


Posts: 1348
xx UNC paths
« Thread started on: Sep 13th, 2016, 07:05am »

I have been reminded that LB 4 doesn't support UNC file paths ("\\server\path\file.ext") which can be a limitation if you are trying to open a file on a network server and you can't be sure that it is mapped to a consistent drive letter (or at all). Needless to say LBB doesn't have this limitation and UNC paths can be used whenever a filename is expected.

Richard.
User IP Logged

Richard Russell
Administrator
ImageImageImageImageImage


member is offline

Avatar




Homepage PM


Posts: 1348
xx Re: UNC paths
« Reply #1 on: Sep 18th, 2016, 5:56pm »

Here's an LBB version of a demo program posted recently by Chris Iverson, demonstrating that UNC paths work without any need to use direct API calls:

Code:
    print "Attempting to open test document on SysInternals share."
    print "This may take a while, depending on your internet connection..."
    print
    open "\\live.sysinternals.com\Tools\About_This_Site.txt" for input as #hFile
    print hwnd(#hFile)

    while not(eof(#hFile))
        input #hFile, a$
        print a$
    wend

    close #hFile  

You may find that the program takes a long time to open the file, or even times out and fails to open it at all, depending on the availability of the SysInternals server at the time.

Richard.
User IP Logged

Pages: 1  Notify Send Topic Print
« Previous Topic | Next Topic »

| |

This forum powered for FREE by Conforums ©
Terms of Service | Privacy Policy | Conforums Support | Parental Controls