FreeDos is likely assigning the drive letters A: B: C: etc. in a different order or with letters that are different that the other DOSs. Search through all possible drive letters from A: to X: from your editing utility. Or just try it from the command prompt to find out what letter has been assigned to the network drive. If and when you find the right drive letter a simple DIR should reveal if the files on the network drive are accessible. I thinks with most device drivers you could specify the drive letter but if a real hard drive trumps a virtual or substituted or assigned drive every time and you get a default letter assigned sometimes without a message telling you so. It all depends on the choices and defaults the wanker who wrote the device driver or OS guts decided on.
On 5/12/14, Eric Auer <e.a...@jpberlin.de> wrote: > > Hi Sebastien, (and hi Ulrich ;-)) > >> I posted my problem in FreeBasic forum but the problem is not of FreeBasic >> but FreeDos >> can you please read the thread >> :http://www.freebasic.net/forum/viewtopic.php?f=4&t=22469 > > The core FreeBASIC experiment seems to be: > > var filename = curdir() + "\texte.txt" > print "opening '" + filename + "'..." > > var f = freefile( ) > var errnum = open(filename, for binary, access read, as #f) > print "open() = " & errnum > if errnum then > print "failed to open file '" + filename + "'" > end 1 > end if > close #f > > > (that Basic code looks a bit like C ;-)) > > The interesting outcome is that when trying with > X:\dossier\texte.txt it returns error 2, file not > found, if the file exists but 0, OK if it does not! > > Which DOS function does Basic call when you say > open(filename, for binary, access read, as #f) > int 21.3d? 21.6c00? Which other calls down the > call chain are made? Could the SHARE "driver" > be part of the problem or the solution here? > > Maybe somebody could recommend a tool to log the > call chain to screen or to a file to check more? > > Of course you could try in dosemu, which has a > built-in debug and log function, but given that > your problem is with msclient remote files, it > seems more realistic to try on more plain DOS. > > Regards, Eric > > PS: I assume your LASTDRIVE is doing fine and it > does not matter whether you use curdir() or some > manually specified location... > > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform > available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
