I've been trying to setup an external drive (connected to an AEBS) to share my iTunes library between two computers.
Computer A - MacBook Pro (bootcamped)
Computer B - Desktop
Both machines are connected to the AEBS by ethernet.
I've consolidated my library using iTunes on OSX. I've been following a tutorial that lets me share a library between OSX & Windows... apparently you need to create the library in OSX first, then add the .itl extension to the library file. Shift-clicking iTunes in OSX lets you select this 'new' library with the result that a new database (iTunes Library.itl.xml) is created.
Anyway, long story short, if the external drive is connected to the AEBS, OSX will find & open the library... no problems there. If I try connecting to the same library through Windows (on either machine), I get an error saying 'the iTunes application could not be opened. An unknown error occured (13005)'. However, if I connect the external drive directly to either machine running Windows (bypassing the AEBS), I'm able to open the library ok.
FWIW, the external drive is formatted as HFS (journaled), & each Windows machine has MacDrive installed... but there doesn't seem to be an issue in accessing the files through Windows. Opening the drive through Explorer lets me view & edit files, even when its connected to the AEBS.
I've even tried connecting other drives to the AEBS, one formatted as HFS & another as FAT32... the same result. iTunes won't even let me create a NEW library on either volume.
So it would seem the focus of the problem is the way in which Windows accesses the Airport disk. OSX can handle it ok, but Windows won't let me access or create an iTunes library on a shared volume... anyone else encountered this issue?
Computer A - MacBook Pro (bootcamped)
Computer B - Desktop
Both machines are connected to the AEBS by ethernet.
I've consolidated my library using iTunes on OSX. I've been following a tutorial that lets me share a library between OSX & Windows... apparently you need to create the library in OSX first, then add the .itl extension to the library file. Shift-clicking iTunes in OSX lets you select this 'new' library with the result that a new database (iTunes Library.itl.xml) is created.
Anyway, long story short, if the external drive is connected to the AEBS, OSX will find & open the library... no problems there. If I try connecting to the same library through Windows (on either machine), I get an error saying 'the iTunes application could not be opened. An unknown error occured (13005)'. However, if I connect the external drive directly to either machine running Windows (bypassing the AEBS), I'm able to open the library ok.
FWIW, the external drive is formatted as HFS (journaled), & each Windows machine has MacDrive installed... but there doesn't seem to be an issue in accessing the files through Windows. Opening the drive through Explorer lets me view & edit files, even when its connected to the AEBS.
I've even tried connecting other drives to the AEBS, one formatted as HFS & another as FAT32... the same result. iTunes won't even let me create a NEW library on either volume.
So it would seem the focus of the problem is the way in which Windows accesses the Airport disk. OSX can handle it ok, but Windows won't let me access or create an iTunes library on a shared volume... anyone else encountered this issue?