🚀 go-pugleaf

tchnd-au@garnet.berkeley.edu (Yuval Oren) writes:

>I would like to implement soft links for DOS. I planned to trap the
>file open, close, etc. interrupts, and re-direct them to the address
>stored in a "link file," which would have one line, the full path of
>the real file. But then I thought, how can I open this file to find
>out where to go? Any ideas for me?

Presumably your INT21 handler would remember the address that it used to
have stored, so that it could pass non-linked file calls on to DOS.
Just use the old INT21 handler to handle your link calls.

I would love to see a good symlink handler for DOS.  I saw one once that
seemed to work, but it did not support the DOS EXEC call, so I could not
use it to symlink program files to each other.  This would have been
perfect for the PBMPLUS tools.

One question:  How do you propose to be able to tell the difference
between a symlink file and a real file that happens to contain a
pathname?

-- 
#ifdef TRUE        | Fuzzy Fox (a.k.a. David DeSimone)       fuzzy@netcom.com
#define  TRUE   0  |
#define  FALSE  1  |  "911 Emergency Rescue Service - Can you hold, please?"
#endif             |

In article <1993Jan11.170104.6198@rei.com> fox@rei.com (Fuzzy Fox) writes:
>tchnd-au@garnet.berkeley.edu (Yuval Oren) writes:
>
>
>One question:  How do you propose to be able to tell the difference
>between a symlink file and a real file that happens to contain a
>pathname?
>

The link files will have a special header -- one that no other file
would have, such as: @@@UVLINK FILE@@@

My symlink will support EXEC and also directory linking. One question,
though -- how do I allocate a 81 byte area in a .com assembly file
(I'm new at it). Can I just do:

DB	?	,81 

? or something like that?

Yuval

-- 
________________________________________________________________________
|Yuval Oren						               |
|yuval@ocf.berkeley.edu     				               |
| "One spoiled green bird is worth two cooks in the other grass broth."|