Hi Sébastien, > Hm... i'm lost ! > I don't understand how do ... it's a bug of freedos ? > why i not have this problem with msdos or drdos ?
That is a good question! You should investigate it by having a very close look at the exact differences. For example you could try if using more MS or DR drivers "fixes" FreeDOS or if using more FreeDOS drivers can "break" MS or DR DOS. If yes, you could be on your way to find a certain driver or combination of drivers to "blame" for the problem. If not, there could be some issue with our kernel. I think the SHARE driver could also be a factor, because network drives may need it. Also, if you check my mail from the 12th, you can try some file name variations: With and without directory specification, with or without explicit drive letter. > 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 > 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? ... If you yourself can not answer those questions, you could ask on the FreeBASIC forum, or upload a test program to any homepage or bitbucket and then mention the URL here so people can try exactly your program: In that case, also show your config and autoexec for the two DOS operating systems where it works and the one where it does not. Also mention which version of the DOS kernel and drivers you use, so people can be specific in their attempts to reproduce your problem or can give specific suggestions for config changes. I know that this sounds like a lot of work for making something work in FreeDOS which works anyway in other DOS versions without extra efforts. However, if such work leads to interesting answers, they will help ALL users of FreeBASIC in FreeDOS with network drives and maybe even users in completely different situations which happen to trigger the same problem. The answer can be as simple as a recommendation for configuring FreeDOS (maybe you just overlooked a special property of drivers that you expected to configure differently or maybe you loaded an old driver or forgot one) but it could also be that we have to repair a FreeDOS part which has a bug in general network drive processing. Thanks for checking! Regards, Eric ------------------------------------------------------------------------------ "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
