Hi Greg, of course you are totally right - how embarrassing! ;-) > Von: "Greg King" <email@example.com> >> Just do an OPEN"FILE,L,"+chr$(n); and, then a CLOSE -- the directory >> keeps being empty. >> https://plus.google.com/u/0/108561624393340605896/posts/DyBxy6wsXMJ > > Your program reuses the "d" variable! First, it's the device number; then, > it's the sector number (in the error message). So, only the first open > actually talks to the drive -- the others open a REL file on the keyboard! > ;-) Of course it was not the fault of the DOS, but mine - as pointed out, I am reusing the "d" variable and after fixing this, the DOS behaves as it should! But what do I learn from this: 1) after long years of programming C, Java, and even structured assembler I am really used to scope and protection of local variables 2) do more reuse, even if such a small routine like reading the error channel - in another test program I had already found and corrected this error. 3) Peer review to the rescue :-) Thanks for finding this! André Message was sent through the cbm-hackers mailing listReceived on 2013-06-03 18:00:03
Archive generated by hypermail 2.2.0.