| |
VK2ZRG > TECH 18.12.05 05:38l 46 Lines 1597 Bytes #999 (0) @ WW
BID : 1871_VK2ZRG
Read: DL1LCA GUEST OE7FMI
Subj: Re: A programming problem ZL1ANM
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0ACC<DB0GOS<DB0RES<DK0WUE<I0TVL<VK2TGB<
VK2IO<VK2WI
Sent: 051218/0242Z @:VK2WI.#SYD.NSW.AUS.OC #:1292 [SYDNEY] FBB7 $:1871_VK2ZRG
From: VK2ZRG@VK2WI.#SYD.NSW.AUS.OC
To : TECH@WW
VK2ZRG/TPK 1.83d Msg #:1871 Date:18-12-05 Time:2:19Z
Neil ZL1ANM wote re my bulletin
>
>
>Most likely, DOS allowed the renaming of an already-open file although
>as the Manual points out, it is good practice to close it first.
>So perhaps DOS didn't specifically forbid renaming an open file.
>
>When the later versions of Windows were introduced, Microsoft probably
>moved to plug the loophole, generating an error message if the process
>was attempted.
>
>My DOS 3.3 Manual gives no caveat against renaming a file, implying
>that you can do so even if it is already open.
>
>73 de Neil ZL1ANM
Hello Neil and readers,
What you say could be true but the strange thing
was that a PC booted to DOS with the DOS part of win-me, didn't give an
error when renaming an open file; but when booted to windoze it did.
Actually a little more investigation suggests that it is Pascal and not
DOS, that is the problem. I've tried some assembler code in Pascal and
get the same result. However a programme quick basick does give an
error if you try to rename an open file.
Re your DOS 3.3 manual; just because it's not stated doesn't mean
you should be able to rename an open file, it's more likely that M$
just forgot to tell you that you can't. My DOS 6.0 programmers manual
does state that a file must not be open when renaming with function
56 hex of the 21 hex interrupt.
73s from Ralph VK2ZRG@VK2WI.#SYD.NSW.AUS.OC
/ack
Taglines Version 1.00, by Colin Coker G4FCN
C Program run, C Program Crash...ReWrite in Pascal!
Read previous mail | Read next mail
| |
