Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
206 user(s) are online (190 user(s) are browsing Forums)

Members: 0
Guests: 206

more...

Support us!
Donate

Headlines
Recent files - OS4Depot - Your one stop for AmigaOS4 files

 
Jump to the bottom of the page Bottom    View previous topic Previous Topic    View next topic Next Topic

  Register To Post  

broadblues
What is the correct tecnique to determine if two files are on the same volume under AmigaOS 4.x?
Posted on: 2014/3/2 23:47    #1
Home away from home
Home away from home


See User information
I need to upgrade a function in a project I'm working on to AmigaOS 4.

This is the old code.

static BOOL OnSameVolume(STRPTR fname1, STRPTR fname2)
{
    struct InfoData __aligned idata;
    struct DeviceList *dlist1, *dlist2;
    BPTR lock;

    dlist1 = dlist2 = NULL;
    if (lock = Lock(fname1, ACCESS_READ)) {
        if (Info(lock, &idata))
            dlist1 = BADDR(idata.id_VolumeNode);
        UnLock(lock);
    }
    if (lock = Lock(fname2, ACCESS_READ)) {
        if (Info(lock, &idata))
            dlist2 = BADDR(idata.id_VolumeNode);
        UnLock(lock);
    }
    if (dlist1 && dlist2)
        return((BOOL)(dlist1->dl_Task == dlist2->dl_Task && dlist1->dl_Name == dlist2->dl_Name));
    else
        return(FALSE);
}


as struct DeviceList is now in dos/obsolete.h I'm wonder what the correct way to do the above is under AmigaOS 4?
Blender For OS4.x : Blues : Walker Broad
Go to top
joerg
Re: What is the correct tecnique to determine if two files are on the same volume under AmigaOS 4.x?
Posted on: 2014/3/3 1:35    #2
Just can't stay away
Just can't stay away


See User information
@broadblues

Quote:
I need to upgrade a function in a project I'm working on to AmigaOS 4.

This is the old code.
Not just old, ancient Kickstart 1.x code

Since AmigaOS 2.0 it's something like
static BOOL OnSameVolume(STRPTR fname1, STRPTR fname2) 
{ 
    BPTR lock1, lock2;
    BOOL result = FALSE;

    lock1 = IDOS->Lock(fname1, ACCESS_READ);
    lock2 = IDOS->Lock(fname2, ACCESS_READ);

    if (lock1 && lock2)
    {
       int32 same = IDOS->SameLock(lock1, lock2);
       if (LOCK_SAME == same || LOCK_SAME_VOLUME == same)
       {
          result = TRUE;
       }
    }
    
    if (lock1) IDOS->UnLock(lock1);
    if (lock2) IDOS->UnLock(lock2);

    return result;
}


Edited by joerg on 2014/3/3 1:55:31
Go to top
broadblues
Re: What is the correct tecnique to determine if two files are on the same volume under AmigaOS 4.x?
Posted on: 2014/3/3 11:05    #3
Home away from home
Home away from home


See User information
@joerg

Quote:

Not just old, ancient Kickstart 1.x code


This thing I'm working on has ancient roots!


Thanks for the solution.

Blender For OS4.x : Blues : Walker Broad
Go to top
salass00
Re: What is the correct tecnique to determine if two files are on the same volume under AmigaOS 4.x?
Posted on: 2014/3/3 11:20    #4
Just can't stay away
Just can't stay away


See User information
@broadblues

Quote:

as struct DeviceList is now in dos/obsolete.h I'm wonder what the correct way to do the above is under AmigaOS 4?


The DeviceList struct was moved to dos/obsolete.h because it's the same as struct VolumeNode only with a less logical name.

Quoting from the dos/obsolete.h include:
Quote:

Obsolete structure definition, although called a "devicelist" it was actually used only for volume nodes, how quaint !.
Go to top
broadblues
Re: What is the correct tecnique to determine if two files are on the same volume under AmigaOS 4.x?
Posted on: 2014/3/3 11:32    #5
Home away from home
Home away from home


See User information
@Salass00

Noted: but even if I had realised that before asking the question, the dl_Task entry referenced in the old code, doesn't exist in the 4.x includes. (presumably it was either FSPrivate or one of the reserved.

Best to update either way.
Blender For OS4.x : Blues : Walker Broad
Go to top
salass00
Re: What is the correct tecnique to determine if two files are on the same volume under AmigaOS 4.x?
Posted on: 2014/3/3 11:40    #6
Just can't stay away
Just can't stay away


See User information
@broadblues

Quote:

Noted: but even if I had realised that before asking the question, the dl_Task entry referenced in the old code, doesn't exist in the 4.x includes. (presumably it was either FSPrivate or one of the reserved.


The #?_Task fields in DosList, VolumeNode, DeviceNode, etc. structs are now called #?_Port. The old, obsolete names never made much sense since they point to the filesystem message port or FSVP in case of newer filesystems, not a Task structure.

Also, from dos/obsolete.h:
Quote:

#define dl_Task dl_Port


The equivalent in struct VolumeNode is of course "vn_Port".
Go to top

  Register To Post

 
Jump to the top of the page Top    View previous topic Previous Topic    View next topic Next Topic




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project