Metadata Sharing Strategy

Hi,
In the standard SOA install you have a SOA infra metadata repository.
When AIA is installed AIAMetadata is then added to this repository.
AIAMetadata contains the abstract WSDL’s, xsd’s etc. for all the enterprise level artefacts.
We have Development, Test and Production SOA Servers which each have their own metadata. We have a patching system which deploys metadata to each sever.
It has crossed my mind that we could have a single metadata store and connect all three SOA Servers to that one. There are already strict rules for adding files to metadata so this should not be a problem. There is also the need for other systems (ADF servers, OSB, etc) to access the abstract WSDL’s. This would avoid all the management issues involved in creating metadata in Dev and needing it to be moved from system to system.
What are the best methods to share enterprise metadata across the environments?
Thanks
Robert

Robert,
while your thoughts make sense conceptually, there are technical constraints that would not allow one central MDS for all your environments. If you take a closer look at your MDS, you will not only find the AIA meta data you described, but also environment specific data such as the deployed composites for a SOA infrastructure that is connected to that MDS.
So the best parctise at this point is to maintain the source of truth of your shared AIA meta data on the file system, typically managed through a source control system. You use a file system level tool to keep the meta data in your AIA Homes in synch as required and then use the usual AIA deployment tools to get this moved to each MDS. I assume this is what you already do anyway.
Gerhard

Similar Messages

  • ITunes Sharing Strategy

    Does anyone have any suggestions for a family needing to share and play iTunes on or via multiple devices?
    Here's the scenario.
    i) 3 users in a house.
    ii) Installed in the house, 2 x Apple TV and a MacMini.
    iii) 2 Users have MacBooks, one of these users has an iPhone, the other an iTouch
    iiii) 3rd user has iTouch.
    Each of the users has an iTunes library and whatever the strategy, they would like to keep the libraries separate.
    The ideal solution would be that the MacMini is a music server but, only if there's no need to switch users as the only access to the MacMini is via the network.
    Is there a way to keep each users's music separate on a single user account? (other than dragging music into libraries!)
    The current problem is extended because there are 7 AirPort Express units driving speakers in different rooms. When another Mac or iTouch/Phone tries to use a remote library, if the remote Mac is set to use multiple speakers, music plays in rooms not required but there's no way for the remote user to control the multiple speaker settings. Is there, maybe, a script that triggers when a remote user logs on and automatically re-sets multiple speakers to computer only?
    Is there a way, if the iTunes account users agree to share, that an iTunes user can enter more than one account name to overcome the sharing problem of 5 registered devices?
    Has anyone written a multiple Mac, iTouch, iPhone and AppleTV iTunes strategy?
    Appreciate any suggestions.
    Regards, Norm

    I'm still searching for an iTunes / Apple TV Home Sharing solution but wonder if anyone thinks this idea might work ...
    Here's the hardware situation (ASA = Apple Store Account):
    House
    Apple TV Lounge ASA User 2
    Apple TV Master Bedroom ASA User 2
    Apple TV Pool Room
    MacMini ASA (User4 ?)
    User 2
    MacBook Pro ASA User 2
    Apple iPhone ASA User 2
    User 1
    MacBook Air ASA User 1
    iTouch (Music from iMac in Office) ASA User 1
    (Office iMac) ASA User 1
    User 3
    iTouch ASA User 2
    * ASA = Apple Store Account
    Create a new ASA in the name of thehouse. Set up the MacMini with 4 users, User1, User2, User3 and User4 (thehouse) each using their own ASA. Enable fast user switching and have automatic start-up on all 4 accounts (if possible?). Set-up Home Sharing on the MacMini using User4 ASA (thehouse) Have each user's iTunes music synced from their personal device/s to the MacMini. This should mean that User1, User2, and User3 will each have an iTunes replica of their master much library. User 4, the new thehouse account, will also be used on the Apple TVs in the living room, Master Bedroom and (soon to be installed) Pool Room. Hopefully, the MacMini will, via Home Sharing, make all three iTunes libraries available to all the Apple TVs.
    Anyone think this might work?

  • Metadata & shared volumes

    Hi all,
    with the command mdls we can obain information on the medadata of a file.
    In particular I need to use the information provided by the field: kMDItemLastUsedDate, that
    is updated with the last moment a file was read.
    I noticed that the field is normally updated if I read a file locally.
    Some problems arise when I read the files on a shared volume even if I access the volume with the local user account.
    In this situation the field isn't updated and it's like none has read the file.
    Is there any option in order to make the field always updated.
    Thanks.

    Whenever you paste an icon onto a disk or folder, the Finder creates a .VolumeIcon.icns or Icon? file, which contains your custom icon. The inability to see the custom icon may simply be a permissions issue. Check to see that the icons files have at least read-only permissions for the users who are connecting.
    --Gerrit

  • Creating less expensive small xSAN for 2 editors - suggestions?

    I've been setting up a second editing bay for our company which is supposed to have identical capabilities to my own. It's a Quad with Kona LHe, just like I'm using. We mostly edit TV comercials in DV50, uncompressed 10bit SD and DVCProHD 720P so our bandwidth requirements usually out spec editing over ethernet.
    Since both editors need to have equal capability, I have chosen to create a small xSAN to allow both editors to access the same media drives simultaneously. With a SAN, large server volumes (located on a fibre channel network) show up on the editor computers just as a simple local hard drive would at very fast speed. You can point FCP scratches to the same places on each machine, then use any machine to edit any project instantly. My budget is large by my standards, but not very large on the scale of typical xSAN implementations so I've been collecting "deals" on the gear I need before I put it all together.
    Since I'm on a budget, it has been fun finding much of the gear on ebay, etc. FYI, here is a quick list of the stuff I've acquired:
    xServe RAID 5.6TB refurbished from Techrestore.com: $5900
    xServe 2Ghz Metadata controller w/ Tiger Server 1.5GB ECC RAM, PCIX fibre card new, but last year's model from Smalldog: $2600
    Brocade Silkworm 3200 8 channel 2Gb entry fibre switch new on ebay: $950
    2 PCI Express fibre cards new for 2 editor G5 quads: $1100
    3 xSAN licenses new on eBay: $1300
    Mini GB ethernet network stuff and switch (for metadata only - separate from our LAN network): $150
    Misc. fibre cables and tranceivers: $700
    One of my editing G5's will act as the fallback Metadata controller in case the xServe goes down at any time.
    I also am planning on at least 8 hours of time from a local xSAN authorized tech to help me set everything up and teach me what I need to maintain the system. This should be about $700 or so.
    I have found several articles posted at xsanity.com very helpful in planning this.
    If any of you have any experience with xSAN, you might agree this is a very low cost of entry into this very exciting new workflow. $13.5K for a fully functioning xSAN of this size is not bad at all. Many would spend that on the xServe RAID alone, sans SAN;-) And I can expand very easily since my switch will still have 3 unused ports. Note: the 5.6TB xServe RAID will only be about 4TB after accounting for the RAID 5 and dedicated (and mirrored) metadata volumes. Only 4TB. Pity!
    Now that I have the main hardware components ready, it's time to install and setup the system. I'll be posting my progess in the next few weeks as this happens, but first would like to hear any impressions on this. Suggestions or warnings are appreciated by those with experience with xSAN. The xSAN forum here at Apple is used mostly by IT professionals and I'm mostly interested in hearing comments from editors and those that use the system in small settings like my own.
    One question for the Gurus: I don't believe FCP projects can be opened and used by two people at the same time, but if there is a way to do this without corrupting the project file, I would love to know.
    I'm also seeking to hire an assistant to occupy the new editing bay. Broad multimedia skills are needed, but I can train to a degree. We're an advertising agency just north of Salt Lake City, Utah. Please let me know if any of you are interested.

    Thanks for the suggestions. Brian, I'll be sure to get you some points once I close the topic.
    I didn't realize the Project files are best copied to the hard drive. Is this for a permissions related reason or just to avoid short spikes in bandwidth during saves?
    I agree that Metadata is best on a dedicated controller with full scale xSANs, however with just 2 systems editing mostly DVCPro50 resolution projects I can't imagine burning up more than 100MB/sec at any given time. OK, maybe, but this is unlikely for next year or so. I've read that a single controller can achieve 80MB/sec easily, so 2 should be around 150MB/sec under heavy load. I'll have the metadata mirrored to 2 drives on one side of the XSR and the remaining 5 drives on that controller in a RAID 5. The other side of the XSR will be a full 7 drive RAID 5. These 2 data LUNs will be striped together in xSAN to achieve a full bandwidth of about 150MB/sec. I was told that the XSR controller can handle multiple RAID's at the same time so I can send metadata to one mirror array and designate the other as a RAID 5 LUN. Considering the small size of the data going to the metadata volumes and the relative simplicity of RAID 1 mirroring, I believe the controller shouldn't be adversly affected by this. Is this incorrect in your experience?
    I do plan on turning off the cache of the XSR since the system will be used for editing, yet it would be nice to have cache for the metadata so that's a point to consider.
    THe metadata should be segregated on its own XSR controller.
    Are you saying that the metadata sharing the same controller as the video data is going to slow the whole system down even though the metadata is located on separate, dedicated drives in that controller? I thought metadata was tiny and required very little bandwidth on the bus of a controller. If this is the case, the only bottleneck would be the RAID chip in the XSR. Again, these metadata files are very small and RAID 1 is very simple, so I don't see how it could slow things down enough to justify another $4K for a new XSR. If you still disagree, please let me know.
    As per your suggestion, and considering your stellar reputation in this forum, I'm shopping right now for a mostly empty xServe RAID to use this for just the Metadata volumes mirrored. It just seems like a huge waste to get an XSR just to use 2 drive bays mirrored. The plus side of this is I could begin filling the other controller in the future as my storage needs expand.
    It would be really cool to use the 2 drive bays in the Xserve Metadata controller for the metadata volumes, but I can see how that would cause problems if the xServe goes down, making the metadata invisible to the fallback MDC. 100% uptime isn't that big of a deal for me, however. As long as the XSAN comes back online safely after the xServe reboots without trouble, I'm OK with such a setup. Have you ever seen this done? It seems a bit of a hack to use anything but fibre channel data. I'd hate to introduce too much complexity just to save some bucks, but it is an intriguing idea and would cost a fraction of a new XSR. It would be fast since the writing the metadata would be local with very little latency.
    For this reason, I'm also very interested to find any other simple and less expensive Fibre based storage solutions that could host my metadata as an alternative to full blown XSR for this. There are all kinds of fibre drives out there, but I don't want to waste a valuable fibre switch port just for one drive. All I need is 2 hardware mirrored bays accessible over fibre, preferably sharing the same channel on my switch. Does anyone know where I might find something like this?

  • Best practice file management

    Hello everyone
    I'm hoping to receive some advice on the best way to store a large collection of music, pictures and video, whilst keeping my computer as empty as possible to maximise it's processing power for professional video editing in the future. The computer is for both personal and business use, and I share it with my partner who is a music fiend, but not computer savvy.
    I have recently purchased a new 27" iMac with the standard specs (3.1GHz Quad-Core Intel Core i5, 4GB memory, 1TB hard drive).  It is currently running Snow Leopard (v. 10.6.6), and I plan to update to Lion when I purchase a new broadband account.
    I also have:
    One external 1TB Western Digital drive, currently at 85% capacity, with music, videos and pictures
    One external 1TB Western Digital drive, currently empty
    A new 2TB time capsule which is not yet set up
    Apple TV, not yet set up
    A mobile USB modem and basic account, soon to be replaced by a fairly high speed broadband modem with a fairly large download cap
    So far, I have:
    created three user profiles - one administrator, and two users
    Set up iTunes so each user shares a single library and itunes media folder
    We would like to also digitise a large collection of CDs and records.
    I was thinking about using the time capsule not only for storage/back up, but also to create a wireless network, allowing it to be stored with my printer and the hard drives can be stored in different room to the computer, away from sight.  The computer is so very gorgeous on it's own after all.... I've been advised also to use it as a wireless router when we purchase our broadband account, so I'm assuming the modem should also be connected to the time capsule in the other room.
    Rather than droning on about what I think I should do, I wondered if one of you experts could advise me on the best way to set everything up? I'm not sure that it's the best idea to set it up so the computer is always having to find files wirelessly from the time capsule and connected drives...  Wouldn't that be slow?
    The advice I've read in the various forums has been rather confusing, so your advice would be really appreciated!!
    Cheers
    Fiona

    Hi Fiona,
    Like your question, I'm in same boat and new to iMAC all together and want to setup backup and sharing strategy via best practice right up front.  Did you get any response or any good best practice you ran across in your research you an share with me?  Thanks.

  • Smartview Refresh Changes Dimensions To Old Version

    I am having an issue refreshing a smartview file that our department shares on a public network drive. When our users save the file to their own computer, open in smartview and refresh, the member options/dimensions change to an older saved version. We have all become used to this situation when only one or two dimensions would change but now as we are changing from forecast to plan and 2013 to 2014, etc. it is creating a bigger issue.
    Are there some settings or bugs that anyone knows about so that no matter what members are selected in the POV, when the file opens they stay and dont revert back?

    Log into HSS (Hyperion Shared Services) console (http://server:port/interop/index.jsp)
    Expand the Application group->Foundation->Deployment Metadata->Shared Services Registry->Essbase-> APS LWA
    Check the host/server name and port in the properties files present beneath them if they are pointing to the right server and port.
    HTH -
    Jasmine

  • Hyperion Provider Services Connectivity to the Essbase Server

    Hi All,
    I have seen a new issue in Epm 11.1.2 Issue is
    I have installed my provider services services are now up and running in port 13080
    Now when Iam trying to connect thru smartview Iam using following URL
    http://Servername:13080/aps/SmartView
    When Iam going thru the new connection creation process
    Step 1 when I give the URL and click on the next its shows up next page.
    In this page basically I have to select the server and the application.
    But here in my case server and application doesnt show up its BLANK.
    I have checked from my browser provider services shows up perfectly
    Have anyone faced this issue let me know your ideas
    Thanks,
    KRK
    Edited by: KRK on Nov 4, 2010 11:03 AM

    KRK wrote:
    Sorry for the delay in the response I have installed this on a single server but it was the issue with datasources.xml file
    Below are the steps to resolve the issue.
    1. stop APS
    2. Go to http://<machine>:19000/interop
    3. Expand Application group->Foundation->Deployment Metadata->Shared Services Registry->Essbase-> And locate APS LWA
    4. Right click on datasources.xml file and “Export for Edit”
    5. Save the datasources.xml file and not open it.
    6. Open with notepad and make changes so that essbase server name is listed like below:
    etc...I think your reference above to Go to http://<machine>:*19000*/interop should be changed to Go to http://<machine>:*28080*/interop for shared services.
    In looking at this I could not find the datasources.xml file reference following your outline.

  • Jmx hanging process

    For the background processes we make use of JMX Beans.
    We develop them with JDeveloper 10g (10.1.3) and deploy to OC4J.
    We have a background proces for the processing of messages (xml-files from a queue) into the database (using ADF BC).
    Most of the time this works fine, but sometimes it seems that the process is hanging (?), there are no error messages (not in logfile of the application and not in the directories of the Oracle Application Server). We had to restart the process and then the same message has to be processed well.
    In the Java code we put a lot of debug-messages.
    When it goes wrong, the last debug message is just before the database commit (getTransaction().commit()).
    In the database there are no locks, waiting processes, or something like that, at the moment.
    Any tips how I can figure out what the problem can be?

    Since the problem is periodic, I guess this is happening because of some weekly loads. There might be some weekly loads running on every Saturday, which is consuming most of the resources and hence creating problems for your PC.
    To process the Idocs manually, you should go in SM58, select the Idocs, and press F6.
    To get rid of this, you should have a proper load sharing strategy.
    To get a mai/notification, this is possible. You need to include an ABAP program in your PC and configure your mail box. As soon as some loads fails, it kicks out a mail. I used to get a mail in such cases.
    Thanks...
    Shambhu

  • SuperDrive Media Disc(s) .. Assist ...

    07.11.2005
    Dear Apple Mac Mini User forum participants
    b Macmini SuperDrive : Matsushita DVD-R UJ-845C
    How do we confirm the correct read/writable disc(s) media for our Mac mini ?
    We have searched widely .. specifically .. and generally .. online.
    And we come away with no new definitive knowledge. Others
    have trialled and erred .. and learned .. and reported. But still
    we are ill-informed about which particular media we should
    be restricting ourselves to use in our Mac mini.
    Are you able to assist by sharing your garnered information(s)
    about the correct media(s) for the Mac Mini Superdrive.
    We seek your illumination by kind response, if you will.
    Point us to the worthy online repositories or share your personally
    accrued gems of optical SuperDrive media disc management.
    And finally, for now, we would like to hear your formula for establishing
    the minimum specification to share your media disc(s) among your Mac
    computers in use and even with an XP machine, from time to time.
    Establishing the upper performances and the lower compatibilities would
    provide a practicable strategy to managing machine restricted and machine
    to machine informations sharing by optical drive media disc(s).
    Positively thanked will you be.
    very much obliged,
    Stuart .

    09.12.2005
    Dear Apple Mac mini user discussions participants
    Thank you to everyone who has constructively added to
    the body of useful knowledge now available in this
    humble thread. Your contributions are genuinely prized.
    Gems.
    We have read and re-read your entries, acting where
    able, to discover more about the true capabilities of
    the Mac mini SuperDrive mentioned. Along the way, we
    have discovered a few many other related and relevant
    aspects to the personal industry of media disc burning.
    Here is the Apple Mac mini ..
    About This Mac ..
    More Info ..
    Disc Burning ..
    MATSHITA DVD-R UJ-845C:
    Firmware Revision: DPP9
    Interconnect: ATAPI
    Burn Support: Yes (Apple Shipped/Supported)
    Cache: 2048 KB
    Reads DVD: Yes
    CD-Write: -R, -RW
    DVD-Write: -R, -RW, +R, +RW
    Burn Underrun Protection CD: Yes
    Burn Underrun Protection DVD: Yes
    Write Strategies: CD-TAO, CD-SAO, DVD-DAO
    Media: No
    One of the informations we seek is the speeds capacities
    of the SuperDrive mentioned. More frequently now .. in
    the stores .. you find speed rated disc media for
    burning. What are the rated speeds of the Mac mini
    SuperDrive and media ?
    What does CD-TAO mean ? TAO : TrackAtOnce
    What does CD-SAO mean ? SAO : SessionAtOnce
    What does DVD-DAO mean ? DAO : DiscAtOnce
    What does .. Media: No .. mean ?
    From here we begin to discover compatible media ..
    the original mission.
    Online .. here and elsewhere .. we are educated by the
    many who have trialed and erred before us. Most demanded
    manufacturer of disc burning media is 'Taiyo Yuden(s)'.
    Made in Japan. Taiyo Yuden Company Limited is mentioned
    by www.cdfeaks.com WIKI as the most preferred media too.
    Most recommended brand name of disc burning media is
    Verbatim.
    We searched for Taiyo Yuden(s) media in our geographical
    locale. Rare as hens teeth. Sold out before arrival.
    Premium price no deterrent to those in the business of
    quality disc burning. We settled for a couple of
    Verbatim DVD+RW media discs. Made in Taiwan. Every disc
    we could locate in retail was either made in Taiwan or
    made in Singapore.
    We began our media disc burning adventure by applying
    the native OS X Tiger 10.4.2 disc burning applications.
    Finder and Disk Utility. We bothered not with itunes,
    iphoto, since our mission is data. Problems emerged
    early. From the log file automatically kept by Disk
    Utility (top right hand corner of the DU window) you are
    able to read for yourselves the two error messages
    reported as operations failed. Error messages ...
    Finishing burn
    Verifying burn...
    Verifying
    Burn failed
    Verification of the burn failed.
    Unable to burn “backup xxxxxxxxxxxxxx xx.xx.xxx.dmg” -
    Verification of the burn failed..
    Burning Image “backup xxxxxxxxxxxxxx xx.xx.xxx.dmg”
    Preparing data for burn
    Opening session
    Finishing burn
    Burn failed
    The device failed to calibrate the laser power level
    for this media. Unable to burn “backup xxxxxxxxxxxxxx
    xx.xx.xxx.dmg” - The device failed to calibrate the
    laser power level for this media..
    Finder media disc burn error message ...
    This disc did not verify correctly and is unreliable.
    Because the disc is unreliable, discard it and try again
    using a new, blank disc. (Error code: 0x80020063)
    Success message - without verification ...
    Burn completed successfully
    Image “backup xxxxxxxxxxxxxx xx.xx.xxx.dmg” burned
    successfully.
    Operations failure .. we quickly discovered .. does not
    mean media disc burn total failure.
    All media disc burn operations were 'successful'. And,
    as soon as we unticked Verify data at end of disc burn
    (DU), we were regularly greeted with successful media
    disc burn dialogue affirmation. Encouraging .. and
    further confirmed as we examined the data burned and
    satisfied ourselves of the totality of the writing
    event. Otherwise .. DU had zero challenges media disc
    burning and reading burned media and copying data files
    back onto the originating apple mac mini hard disk
    drive. Remember that DU is limited to media disc burning
    in apple format only and multi-sessioning where on
    screen you will be greeted with individual icons
    representing each session burned on the same media disc
    burned.
    However, things went south far to soon and without very
    apparent reason. The DVD+RW was suddenly and perpetually
    rejected by the SuperDrive. No doubt .. the more
    informed among you are smiling and nodding knowingly ..
    at our novice and amateur opening efforts. Useless disc.
    You may be able to pinpoint the moment of coaster
    creation from the supplied error messages logged.
    We imagine that the lack of verification availability ..
    always displayed with an unsuccessful burn message,
    every time .. points directly to media disc quality.
    Unusable disc an eventual certainty. Perhaps.
    Every disc burned delivered an unsuccessful burn message
    whenever Verify data burned was ticked. Finder media
    disc burning does not provide apparent opportunity to
    switch off verification. Read-on .. if you are
    interested to discover our further media disc burning
    experiences and experimentations.
    We re-examined the apple computer help system from DU
    and learned that DVD+RW is the favoured alternate re-
    writeable format disc for DVD re-writing intended to
    replace the capabilities of DVD-RW and DVD-RAM and
    provide higher compatibility with set-top players ..
    though some DVD drives or applications may not support
    recording to this disc format. At the store .. we re-
    read the retail store chart by Verbatim on DVD options
    and learned of media designation purpose distinctions.
    Still .. we appear to have chosen within the SuperDrive
    capabilities. Another disc we should like to sample is
    the DVD-RAM disc .. which is not specifically mentioned
    as compatible media .. are you able to clarify whether
    Mac mini users with the mentioned SuperDrive
    MATSHITA DVD-R UJ-845C are able to use this designation
    ? And the reason for the question is that we have
    discovered a DVD-RAM disc available from a Japanese
    manufacturer. Premium price at the retailer .. assuming
    premium quality too. Appears, however that we are unable
    to use DVD-RAM media burn disc(s).
    After media disc burning the DVD+RW disc we then fed the
    written disc (and at that time, readable - by the
    originating Mac mini machine) to the iMac DV SE
    (graphite) running OS X 10.4.3 Tiger to confirm
    compatibility. Nightmare on Apple street. Barely able to
    read the media disc burned .. we eventually had to force
    the iMac cough the DVD+RW disc back out by manually
    restarting the iMac machine (side button) and holding
    the mouse button down on start-up. Disc retrieved ..
    safely. First time ever in five years of ownership ..
    since new. Bummer. To eliminate speculation of poor iMac
    DV SE drive performance we set about throwing other CD
    and DVD discs at the machine. Perfect. From the iMac ATA
    Device Tree - ATA Bus ... (no media disc burning capability)
    MATSHITADVD-ROM SR-8184:
    Model: MATSHITADVD-ROM SR-8184
    Revision: AA32
    Serial Number:
    Detachable Drive: No
    Protocol: ATAPI
    Unit Number: 1
    Socket Type: Internal
    Disk Utility and Finder are limited media disc burning
    applications. DU creates multi-session disc by burning
    separate instances that manifest as separate disc icons
    on the desktop. Operationally limiting and eventually
    problematical. iMac DV SE showed only the first media
    disc burn of a multi-session disc burned. DU is limited
    to media disc burning in Mac OS format only too.
    We returned the DVD+RW discs to the retailer .. one
    opened and used and fully rejected and the other
    unopened. Instead we chose to step down to Verbatim
    CD-RW discs .. made in Taiwan. We continue with our
    experimentations. Finder help reveals more about disc
    burning and under; "I got an 'unknown error' message
    while burning a CD or DVD disc" we find two links ..
    Apple Service & Support article: Problems burning discs
    [http://www.info.apple.com/kbnum/n25480] reads ...
    Mac OS X: "Unknown Error -2147352480" when burning CD-R,
    CD-RW, or DVD-R media Learn how to troubleshoot burn
    underrun protection issues ("Unknown Error -2147352480"
    alert) when burning a disc. This document applies to Mac
    OS X 10.2 or later.
    Try these tips:
    * Specify a burn speed that is less than the maximum
    speed rating for the optical drive.
    * Quit open applications you are not using. Open
    applications are marked with a triangle in the Dock.
    * Once a burn session has started, do not move, bump,
    or vibrate the computer.
    * Do not put labels on blank discs before burning them.
    * Use blank discs that are rated for the burn speeds of
    your drive, or consider using a different brand of media.
    * See "Macintosh: Factors That Affect Writing to or
    Reading From Optical Media".
    Your computer may also benefit from installing additional
    memory (RAM) or a higher-bandwidth system interface for a
    burning device (such as SCSI).
    You might also consider having the optical media device
    tested by an Apple Authorized Service Provider.
    Additional information
    The Console utility or log may report:
    "-2147352480 = 0x80020060 = kDRBurnUnderrunErr = Device
    drained buffer without burn underrun protection"
    Low disk space or RAM availability issues can lead to this.
    These are some clues that this might be the case:<
    * The issue more often occurs during the burn process.
    * The failed burn more often leaves data partially
    written to the disc, and he disc can't be reused.
    Physical source of these issues can lead to burn failures
    and can sometimes be identified when:
    * The issue more often occurs at the start of the burn
    process.
    * The failed burn session more often leaves the media
    untouched and ready to be burned. (It is still blank.)
    * The burn starts, but an external incident interrupts
    the session.
    ... and the one link on that page ...
    "Macintosh: Factors That Affect Writing to or Reading From Optical Media" ...
    Factors that affect writing to or reading from optical media
    This document discusses things can affect your computer's
    ability to write CD and DVD discs, and what can potentially
    affect their being read by other computers and consumer
    electronics equipment.
    Several things can affect the mastering of recordable media
    and the ability to read them by other devices. These factors
    equally apply to CD-R, CD-RW, DVD-R, and DVD-RW media.
    To consistently achieve successful burns, be aware of these
    factors
    The source for the media
    Third-party discs that conform to the specifications of the
    drive should operate as expected. However, since Apple has
    not physically tested these discs, you should contact the
    manufacturer if full compatibility cannot be achieved.
    Apple-brand discs are tested and qualified for use with
    Apple-installed optical drives and are fully compatible.
    The optical drive used to master the media
    Earlier drives may not work with some later, high speed
    media. Use discs recommended by your drive's manufacturer.
    Make sure you have installed any firmware updates available
    for the drive. Some updates may address media compatibility
    issues, or update the function of the drive in other ways.
    The software used to master the media
    Make sure the application software you use to master the
    discs is up to date. Make sure the options you choose in
    the application, such as the burn speed, work with the
    drive and the media you are using. Varying the burn speed
    may affect the compatibility of the media in the playback
    device. This may make a difference in the accuracy of the
    mastering of an audio CD or DVD. Burning applications often
    perform a verification after the burning process is complete.
    This ensures that the final disc is ready for playback.
    If the verification fails, try choosing a slower burn speed.
    The connection method for your optical drive
    If your burner is connected via USB, you may not be able to
    burn at the highest speed the drive is capable of using.
    Trying to burn at too high of a speed may lead to a failed
    burn because there is not enough bandwidth on the bus.
    If you have a SCSI burner, make sure the SCSI cabling is
    configured correctly, and that the SCSI chain is properly
    terminated. Issues may result from improper termination.
    Also, make sure you use properly-shielded cables to connect
    the burner to the computer.
    To successfully use your burned media, be aware of these factors
    The source of the media
    In general, if you are able to successfully burn discs in a
    drive, that drive should be able to read the same discs without
    an issue.
    Note: Apple optical drives work with standard 650 MB-capacity
    discs, but not all drives work with 700 MB-capacity (80 or 90
    minute) discs.
    The optical drive used to read the media
    Earlier optical drives may have issues reading modern media.
    Early DVD-ROM drives, for example, may not read burned DVD-R
    or DVD-RW discs. Some may read DVD-R, but not DVD-RW. This is
    true for consumer audio CD players, car audio players, and
    DVD-Video players, too. Depending on when the drive was
    manufactured, it may or may not be compatible with certain
    burned media. Check the documentation that came with the player,
    or check with the manufacturer for more information. A firmware
    update may be available that improves compatibility. Even if it
    is considered "compatible" with certain media, you may encounter
    issues with some brands of media, or issues with media burned at
    certain speeds.
    The software used to read the media
    You may find that software designed to copy data to discs cannot
    successfully copy video or audio to discs. Make sure you are
    using a current version of the application, and that the software
    can copy the kind of data you are working with.
    For best success in reading media, use the latest version of
    the Mac OS. Also, make sure that you burn the disc in a format
    that can be used by the operating system that will read the disc.
    For example, a CD burned in Mac OS Extended (HFS Plus) format
    may not work with a Microsoft Windows-based computer.
    If a disc's format is not normally recognized by the computer's
    operating system, you may need to install software that allows
    the computer to recognize it.
    Additional information
    60849: "Mac OS: How to Determine a CD or DVD Drive's Mechanism
    and Firmware Version"
    120029: "Power Macintosh G4 CD-RW Firmware Update: Information
    and Download"
    86130: "SuperDrive: Important Information About Using With
    High-Speed Media"
    ... 60849: "Mac OS: How to Determine a CD or DVD Drive's Mechanism
    and Firmware Version" ...
    ... blah about Apple system profiler .. where we started .. just
    one possibly useful link ...
    For the latest information about compatible CD-RW drives, visit
    the iTunes website.
    So .. we did .. and found nothing of specific use ..
    86130: "SuperDrive: Important Information About Using With
    High-Speed Media" ...
    ... blah about older mac computers and SuperDrive .. inapplicable.
    Apple Service & Support article: Hardware specifications
    [ http://www.info.apple.com/support/applespec.html ]
    ... interesting .. and could have been useful .. maybe
    .. if the mac mini were itemised at all .. not to be ..
    yet the hypertext link is in the mac mini help .. anyone
    see the mac mini here ? ...
    ... Moving along ..
    Finder help also explains about burning blank CD or DVD
    disc(s) and states that it will create burned disc(s)in
    'hybrid' format that can be read by most computers,
    including Windows computers. The (burned) disc contains
    these filesystem: HFS+, ISO-9660 with Rock Ridge, and
    Joliet with Rock Ridge. However .. "The names of files,
    folders, and the disc can't be changed after the CD is
    burned." So, a CD-R or DVD-R would seem the appropriate
    media disc(s) to use as they cannot be (erased and) re-
    written .. on any machine. [ but they can be written
    until full with other softwares and on other operating
    systems .. e.g. XP ]
    We used CD-RW to experiment with this capability .. by
    media disc burning data files to find out what we could
    do after the first Finder burn. Initially recognized as
    a CDR media disc. As you, dear reader, are by now, well
    aware, media burn automatic verification failed.
    Automatic ejection occurred after the burn and at the
    (usual) verification failure message from Finder.
    Re-insertion (after a delayed period) showed the CD-RW
    disc to be CD-RW Untitled CD .. even though we had
    titled the disc at dialogue box burn time. One folder
    and zero nested folder or data files content were shown
    as recorded in the Finder window. We know something is
    on the disc because the usage amount is shown as 353.6MB
    on the desktop icon. Second attempt to burn gave
    message: Insert a blank disc to begin. So CD-R is better
    value (read: cheaper) media than CD-RW for Finder burns.
    You can use use DU to erase the CD-RW. DU agrees with
    the media burned disc volume usage.
    Finder is doubly confusing because of two apparently
    colliding help entry explanations.
    Under: Disc burning options are dimmed or unavailable ..
    is the explanation: If the entry contains "-R", your
    computer can write to a CD-R or DVD-R disc only once. If
    the entry contains "-RW", your computer can erase a CD-R
    or DV-R disc and write to it again.
    However ..
    Under : I can't burn files on my recordable CD or DVD
    disc .. is the explanation: If the entry contains "-R",
    your computer can write to a CD-R or DVD-R disc only
    once. If the entry contains "-RW", your computer can
    erase a CD-RW or DVD-RW disc and write to it again.
    Personal experience proves the latter explanation to be
    the more correct one. We are unable to erase a CD-R or
    DVD-R disc on either Mac or XP machines. Whew.
    Are we missing something here ?
    Or is that the correct facts of the designations ?
    Finder also provides a run-down of Types of recordable
    CD and DVD media.
    Types of recordable CD and DVD media
    If your computer has an internal or external recordable
    optical drive supported by Apple, you can "burn" or
    record your favorite music, applications, documents,
    digital photos and video, and other digital files to
    recordable CD and DVD discs. You can create your own
    music CDs and play them on a standard audio player, or
    create DVDs with movies and slideshows and play them on
    a DVD player.
    There are several types of recordable CD and DVD media:
    • DVD-R discs hold about 4.7 GB of information.
    You can burn files on a DVD-R disc using the Apple
    SuperDrive. DVD-R discs are not reusable; you can burn
    files on them only once.
    • DVD+R is an alternate DVD Recordable write-once
    format. Some DVD drives or applications may not support
    recording to this disc format.
    • DVD-RW discs hold about 4.7 GB of information on
    each side. If you have an Apple SuperDrive, you can read
    information on these discs, but you can't burn files on
    them using Mac OS X. DVD-RW discs are reusable: you can
    burn files on them, erase them, and then burn again (if
    you have an application that is compatible).
    • DVD+RW is an alternate DVD ReWritable format
    intended to replace the capabilities of DVD-RW and DVD-
    RAM and provide higher compatibility with set-top
    players. Some DVD drives or applications may not support
    recording to this disc format.
    • CD-RW discs come in normal and high-speed
    formats. You can burn files on CD-RW discs using the
    Combo drive (or another supported CD burner). CD-RW
    discs are reusable: you can burn files on them, erase
    them, and then burn again.
    • CD-R discs come in two types. One holds 74
    minutes of audio, or about 650 MB of information. The
    other holds 80 minutes of audio, or about 700 MB of
    information. You can burn CD-R discs using the Combo
    drive (or another supported CD burner).
    For recording audio CDs, it is best to use CD-R discs
    because most standard audio CD players cannot read CD-RW
    discs. For longer-term storage and reliability, use CD-R
    discs.
    You can't burn anything on a CD-ROM or DVD-ROM disc.
    Enter Microsoft Windows XP Professional
    We are .. for once .. fortunate enough to have Microsoft
    Windows XP machine available to us with media disc
    burning hardware installed. Just like the Mac mini .. we
    do not have any other software installed for media disc
    operations, only from the native XP OS supplied tools.
    However .. we quickly discover that the XP machine has
    an edge .. licensed Roxio software integrated into the
    XP OS. And it works well. We discover that the Apple OS
    X media disc burning software Disk Utility .. chooses
    only to format in Apple OS. Meaning .. DU media disc
    burned with Mac mini are only able to be read by Apple
    OS machines. Confirmed by attempting to have the XP
    machine(s) read the disc burned. Unable. But .. media
    discs burned by XP machines are able to be read by the
    Apple machines. Because XP machines native OS media
    disc burning format appears to be an industry standard
    OS independent. Couldn't tell from the available
    information from the XP OS but suspect it is an ISO 9660
    format variation. To be exactly confirmed .. and it will
    be .. because the entire outcome of this mission is to
    arrive at a total media disc burning and sharing
    strategy among Apple and as a matter of operating
    contingency .. XP machines too. Open source
    applications in use by us are deliberately cross
    platform between XP and Apple machines. Data generated
    is able to be swapped or even shared among the machines
    with little or mostly no user operating challenges.
    Focus on productivity. The media disc(s) burned in the
    XP machine reads well in the Apple machines.
    The Finder media burned disc .. mentioned above earlier
    .. CD-RW .. read immediately on the XP machine .. folder
    and data files burned .. all there .. all on display.
    99% able to be copied to the XP machine hard disk .. and
    confirmed as a CD-R formatted disc since only option is
    to erase the disc and not add to the existing content ..
    thanks to the Apple Finder format for the re-use sharing
    limitations. So Apple SuperDrive cannot read it's own
    disc but XP machine can and is able to verify burn by
    way of 99% trouble free copy to XP machine hard disk.
    Here .. we begin to struggle with what is happening in
    our limited media disc burning experience(s).
    Enter Media Disc Burning Software
    Additional software has become necessary to accomplish
    our media compatibility and resource management
    requirement(s) .. and we are surely open to your welcome
    suggestions for software applications that enhance the
    available Tiger OS X applications for dependable
    outcomes.
    Remembering for a moment that we have arrived at almost
    total incompatibility between the two Apple disc media
    drives mentioned after burning disc(s) in the Mac mini
    using DU and Finder and attempting reading in the iMac
    DV SE. We are searching for ways to achieve worthwhile
    compatibility.
    And one way is to use the XP machine to create data
    burned media disc(s) that are instantly able to be
    easily read by both Apples in our humble possession.
    This fact is an earlier discovery .. when migrating
    (again) from the XP realm to Apple heaven. Moving open
    source application data files form the XP realm to
    the Apple iMac DV SE machine was unencumbered. Easy.
    How unprepared we are for the encounter with OS X media
    disc burning tools limitations.
    We go on-line to seek any worthwhile open source media
    burning software for OS X. www.pure-mac.com lists
    several possibilities. We need to burn media disc(s)
    that are able to be read by a wider population of
    computer systems including Apple (OS X) and PC (XP) and
    be fully (re-)used to their manufactured storage
    capacities. A combination of Finder and Disk Utility,
    if you will.
    We quickly learn that Roxio is evidently the developer
    of the supreme media burning software available to Apple
    users. And garner from on-line sources that Roxio is
    favoured by the serious and casual user who demands
    quality.
    For the moment we choose to learn more by trialing less
    expensive media disc burning software(s) to find out
    whether our simple needs (and open source patronages)
    can be met by available applications without unnecessary
    bells and whistles. We may be wasting our time here ..
    if Roxio or similar is favoured by so many and not
    because of the bells and whistles but rather
    because of media disc burning performance quality and
    standards then we are likely to arrive at that same
    destination too. As satisfied Roxio user.
    www.pure-mac.com displayed the media disc burning software list below .. in alphabetical order ...
    CD Session Burner
    BurnAgain
    BurnX Free
    Burnz
    DiscBlaze
    Disc-o
    Dragon Burn
    FireStarter FX
    ImageBurner
    Jam
    PatchBurn
    Popcorn
    Toast
    YuBurner
    BurnAgain is one of the programs we chose to experiment
    with to create more standards compatible media disc(s)
    burned. BurnAgain is developed only for the OS X.
    BurnAgain automatically and only formats in ISO 9660
    (Rock Ridge) .. guaranteeing Windows machine
    compatibility. And it does .. so far .. we have used up
    about 5 of the available 10 burns before registration
    should be made with the author. We learn from the
    BurnAgain help system that iTunes burns the same as
    Finder.
    However, BurnAgain focuses only on CD-R and CD-RW media
    .. SuperDrive is capable of more. And you are
    discouraged from mixing media disc burning applications
    to burn the same media disc. BurnAgain prefers you to
    stay the course. DU is the OS X solution to alternate
    media burning (DVD) .. but apple OS format only.
    However, still our iMac is troubled and challenged to
    fully and properly read the BurnAgain media disc(s)
    burned (CD-RW) by the Mac mini .. it couldn't .. but
    eject was a formality and not a crises recovery
    management procedure as before with the DVD+RW disc
    burned by DU on the Mac mini.
    XP machine could read the BurnAgain CD-RW Verbatim
    disc(s) easily and fully .. but copying was about 99%
    accurate (same as Finder). We are writing about 350
    Mbytes of data files recorded on the CD-RW media disc
    with nested folders up to several deep. However,
    subsequent burns to disc(s) wouldn't repeat the same
    data file errors .. meaning if you noted the delinquent
    files then you could just BurnAgain those files and
    expect eventual full disc to hard drive copy success on
    the target machine (XP in our situation) of those
    deliquent datafiles.
    Originating Apple Mac mini machine could read the
    BurnAgain CD-RW verbatim disc(s) easily and fully .. and
    copying was 100% accurate back onto the originating
    Apple Mac mini machine hard disk .. all 350 Mbytes of
    data files .. no error messages reported. Meaning the
    originating machine is performing as expected .. with
    BurnAgain .. but sharing remains a challenge with other
    machines. Particularly iMac DV SE. Remember that Finder
    media disk burned couldn't read again on the Mac mini.
    BurnAgain is clearly an improvement of standards based
    media disc burning .. since originating Mac mini could
    read it's own burn and XP machine 99% accurate too. DU
    is OK if you are confining yourself to Apple machines
    and they can actually read the media disk burned .. only
    originating Mac Mini was able to read it's own burn 100%
    MATSHITA DVD-R UJ-845C is the most modern and capable
    (Super)drive among the five disc media equipped machines
    available here. For now we are confused whether that is
    any advantage or disadvantage.
    We are going to run through the remaining media disc
    burning softwares available from the www.pure-mac.com
    website to determine if our simple needs can be met
    or whether we are required to plumb for the creme deluxe
    (Roxio) and have greatest confidence that our media disc
    burning needs are fully met. We may report back our
    findings to anyone so interested at this forum. Are you?
    We also chose to sample a Verbatim CD-R media disc for
    burning and copying of data files among machines.
    However .. the BurnAgain burn went well .. but the
    copying was problematical to the XP machine hard disk ..
    file copy errors .. and back on to the originating Apple
    Mac mini machine hard disk too .. Error code - 36 (same
    file errors as XP machine). We tried again and met error
    messages from the BurnAgain application .. to the effect
    that BurnAgain would not permit a further media disc
    burn .. even though few hundred megabytes available on
    target media CD-R disc. This outcome .. according to
    Disk Utility help is because: "Mac OS Extended allows
    burning the disc more than once. Formats such as ISO
    allow burning the disc only once." Off to the XP machine
    and burn an additional small file to the disc. Perfect.
    Back to the Apple originating machine .. copy file to
    the Mac mini HD. Perfect. Kept the disc for any future
    file transfers between the XP to the Mac(s) until fully
    used. How confusing .. and .. yes .. frustrating too.
    Burnz is the only other program we choose to sample
    after studying the homepages and value propositions
    and our needs assessment. Thank you to www.pure-mac.com
    for the compilation(s) and accessibilities. Appreciated.
    Burnz developer www.thinkertons.com have other software
    available too. While downloading Burnz media disc burn-
    ing software for trial evaluation .. we browsed Burnerz
    .. another application from thinkertons that is 100%
    free. Burnerz is an informational tool .. and retrieves
    whatever informations available on your system about
    optical media drives fitted and attached and your
    computer systems' optical media drive compatibilities.
    Burnerz is a welcome assist for the knowledge starved
    and delivered up useful confirmations of the MatShita
    DVD-R UJ-845C optical superdrive fitted by Apple. Nice
    one thinkertons.
    Here is the information display from Burnerz ..
    106 Supported Drives in this Version of OS-X
    ( that would be Tiger 10.4.3 fully updated mac mini )
    AppleShipping MATSHITA DVD-R UJ-845C, Internal via ATAPI
    Device Information
    2005-12-06 15:39:56 +1300
    ProfilePath: built-in
    IORegistryEntryPath: IOService:/MacRISC2PE/pci@f4000000/
    AppleMacRiscPCI/ata-6@D/AppleKauaiATA/ATADeviceNub@1/
    IOATAPIProtocolTransport/IOSCSIPeripheralDeviceNub/
    IOSCSIPeripheralDeviceType05/IODVDServices
    CanWriteCDText: YES
    CanWriteDVDPlusRDoubleLayer: NO
    CanUnderrunProtectDVD: YES
    CanWriteDVDR: YES
    CanWriteDVDRAM: NO
    CanWriteDVDDAO: YES
    CanWriteIndexPoints: YES
    CanWriteDVDRW: YES
    CanWriteCDTAO: YES
    CanTestWriteCD: YES
    CanUnderrunProtectCD: YES
    CanWriteCDSAO: YES
    CanWriteCDRaw: NO
    CanWriteCDRW: YES
    CanWrite: YES
    CanWriteCDR: YES
    CanWriteCD: YES
    CanWriteDVD: YES
    CanWriteDVDRDualLayer: NO
    CanTestWriteDVD: YES
    CanWriteDVDPlusRW: YES
    CanWriteDVDPlusR: YES
    CanWriteISRC: YES
    PhysicalInterconnect: ATAPI
    FirmwareRevision: PP9
    LoadingMechanismCanEject: YES
    ProductName: VD-R UJ-845C
    SerialNumber: MATSHITADVD-R UJ-845C 5D0A25C7
    VendorName: MATSHITA
    LoadingMechanismCanInject: NO
    WriteBufferSize: 2048
    PhysicalInterconnectLocation: Internal
    SupportLevel: AppleShipping
    LoadingMechanismCanOpen: NO
    Device Status
    2005-12-06 15:39:56 +1300
    MaximumWriteSpeed: 2822.4
    MediaState: MediaPresent
    CurrentWriteSpeed: 2822.4
    MediaIsBlank: NO
    MediaBlocksUsed: 173914
    BurnSpeeds: Object of Class: NSCFArray, description: ()
    MediaBlocksFree: 0
    MediaIsReserved: NO
    MediaIsAppendable: NO
    MediaIsErasable: NO
    MediaFreeSpace: 0
    MediaClass: CD
    MediaIsOverwritable: NO
    MediaSessionCount: 1
    TrackNumber: 1
    FreeBlocks: 0
    SessionNumber: 1
    TrackLength: 173914
    BlockSize: 2048
    TrackIsEmpty: NO
    SessionFormat: 0
    TrackType: Closed
    TrackStartAddress: 0
    BlockType: 8
    MediaType: CDROM
    MediaBlocksOverwritable: 0
    MediaUsedSpace: 173914
    TrackRefs: Object of Class: NSCFArray, description: (<DRTrack: 0x003B4950>)
    MediaBSDName: disk1
    MediaOverwritableSpace: 0
    MediaTrackCount: 1
    IsBusy: NO
    IsTrayOpen: NO
    And here is the Media information from Mactracker ..
    www.mactracker.ca .. a free informational tool on
    everything Apple hardware ...
    Media: 4x8x16x8x24x SuperDrive
    .. Dunno exactly what those numbers mean ..
    And here is the Media information from Mactracker on the
    iMac MATSHITADVD-ROM SR-8184 ...
    Media: 24x CD-ROM or 4x DVD-ROM
    Imagine that means read at 24x CD-ROMs and 4x DVD-ROMs
    Back to BURNZ
    Burnz has a particular feature that meets our
    requirements and added weight to the application's value
    proposition. You are able to choose the specific optical
    media disc burn format. Five graduations exist.
    Each graduation includes (all) of the lower ranked media
    burn format qualities. Top to bottom sliding scale.
    HFS+
    ISO 9660 Joliet extensions
    ISO 9660 RockRidge extensions
    ISO 9660 level 2
    ISO 9660 level 1
    Visually affirmative .. this feature gives user
    confidence about media disc burned format
    compatibilities. And the website and written materials
    from thinkertons make clear that compatibility is well
    covered for all optical media drives. Exactly what we
    seek. Default is HFS+ which thinkertons encourages you
    to maintain unless you do reason to otherwise change.
    Finally, for now, Burnz writes DVD media disc(s) too.
    Wethinks .. could we go wrong now .. as we progressed to
    practical evaluation. 10 free burns before registration
    is required by thinkertons. Here we go ..
    We chose 407.29mb data files .. application downloads
    and Tiger updates (.dmg, .zip, .bin) .. in one folder
    to brand new Verbatim CD-R (702.82mb available according
    to Burnz) .. and settings to maximum possible speed
    (automatically selected at 16x) .. other selectable
    speed setting is 8x .. and leave disc appendable ..
    verify burned data ON ...
    Burn failed...
    StatusError: -2147352477
    ErrorString: Verification of the burn failed
    RE-inserting the media burned disc gave desktop CDR
    icon with the burn folder named and 406.9 MB usage ..
    Finder (double click on the desktop disc icon) shows
    all 18 items burned .. copy from CDR back to new desktop
    folder showed the appropriate copy dialogue box and
    progress bar without color .. left awhile to see what
    happens ...
    The Finder cannot complete the operation because some
    data in "Gimp-2.2.8.dmg" could not be read or written.
    (Error code -36).
    Error code -36 is becoming an old friend ..
    Repeating the operation minus "Gimp-2.2.8.dmg" ..
    same drill .. offending file "MacOSXUpdate10.4.3.dmg" ..
    repeating minus "MacOSXUpdate10.4.3.dmg" .. same
    drill .. repeating minus "PDFLab.dmg" .. that's three
    out of total 18 so far .. and not one copied from disc
    to desktop .. last chance before coaster designation
    is applied as we get the pattern and the picture ..
    down to 245.9 MB to copy and still no satisfaction ..
    and now number 4 "Firefox 1.0.7.dmg" ..
    Houston .. we have a coaster .. trajectory .. garbage.
    Won't bother trying this disc insert into the iMac.
    However, we troubled ourselves to find out what would
    happen in the XP machine .. same outcome .. yes,
    readable by XP but copy failure to hard disk on the
    larger .dmg files. Not unexpected. Media format
    compatibility confirmed .. just as Burnz promised.
    Repeating the entire exercise with brand new Verbatim
    CD-RW (just to reduce CDR coaster count) .. this time
    at 4x write (automatically determined with no other
    speeds selectable - maximum possible) .. all other
    settings unchanged ... samo .. samo ..
    Burn failed...
    StatusError: -2147352477
    ErrorString: Verification of the burn failed
    RE-inserting the media burned disc gave desktop CDRW
    icon with the burn folder named and 406.9 MB usage ..
    Finder (double click on the desktop disc icon) shows
    all 18 items burned .. copy from CDRW back to a new
    desktop folder showed the appropriate copy dialogue box
    and progress bar color .. copy began immediately and
    reached the end .. Bingo .. we have a winner ! .. or
    do we ? .. Opening 50% of the now copied to desktop .dmg
    files produced an error message: The following disk
    images failed to mount. And for each delinquent .dmg ..
    the same Reason: codec overrun .. quite whatever that is
    meaning .. we appreciate the .dmg is damaged and now
    useless. Always the larger .dmg files .. up to 125 MB.
    On the Apple .. we are down two for two .. let's go
    again with burn verification off .. but first erase the
    disk with DU quick erase .. done .. now regarded again
    as an empty CDR by Finder .. (note that 'Erase disc
    before burning' is an available option in Burnz and on
    the Burn Disc dialogue box .. but it wasn't available
    as soon as the previously burned media disc was
    re-inserted for deleting and re-burning) ..
    No burn failure message .. as expected .. 406.9 MB
    usage on CDRW .. as expected .. Finder shows all
    18 items burned .. copy to desktop .. seemingly
    good .. as before and usual .. opening .. again
    a 50% failure rate .. same message .. same result.
    And in the XP machine .. same for read and copy to HD.
    OK .. let's give it one last go with the .dmg's, .bin's,
    and the .zip files .. by erasing again (with DU again)
    and media disc burning the CD-RW with just one file at
    a time and then copying back to confirm burned file
    integrity .. that's totally 18 burns .. but we shall
    only go as far as 9 file burns and copy back to the
    desktop from the burned media disc .. if all 9 are
    good then we shall assume it would all be good. We
    trial the big .dmg's to begin .. interestingly, erase
    disk before burning is available now and so we use
    that feature rather then DU (perhaps because the
    burn is less than the remaining disc storage available)
    .. is that a bug ? we wonder .. we turn Verify burned
    data ON .. just curious .. we are asked about our erase
    certainty before proceeding .. we click yes ..
    burning .. 97 MB .dmg .. burned (no negative
    verification error message) .. now copying back to
    desktop .. opening .. and .. codec overrun message.
    Finally, for now, we return to our original evaluation
    folders and files trialled with BurnAgain .. and perform
    the same media disc burn and onto the same (new) media
    disc (i.e. CD-RW) from the same batch too .. using Burnz
    .. Verify ON ...
    Burn Failed ... blah
    Copying back to desktop .. copy back is good .. just
    like BurnAgain .. encouraging.
    What that says about the larger .dmg files or perhaps
    any larger (50mb+) files to burn is unclear .. do you
    need even better hardware (media and burner) and
    software ? .. or are you out there in expert land able
    to advise readers how you do exact maximum confidence
    on the larger files media disc burn(s)?
    No DVD media burn disc(s) lying around here, for now,
    so we shall reserve any outcomes for another day of
    evaluations and experimentations.
    BurnAgain and Burnz go head to head .. From the tests
    performed to date we are able to comment from personal
    experimentation and practical experience .. they are
    very much similar quality .. Burnz does DVD's too.
    However, neither managed to accomplish entirely reliable
    media disc burn(s), of use, beyond the originating Mac
    mini SuperDrive .. nor accomplish verification .. is
    that normal ? Or do we have a particular problem ?
    We are back to square one for verifiable media disc
    burning.
    Interestingly .. those 10 free media disc burns
    available .. have only reduced by the number of burns
    without verification .. since negative verification
    appears to not count .. 8 free burns still available ..
    Recap On Applications, Capabilities and Limitations as
    encountered To Date ..
    SuperDrive MATSHITA DVD-R UJ-845C : Mac mini (Apple)
    Apple OS X Disk Utility : apple OS format only
    : multi-session burn(s)
    Apple OS X Finder : apple OS format,
    : ISO 9660 Rock Ridge..
    :..Joliet with Rock Ridge
    : one burn only each media disc
    OS X BurnAgain : ISO 9660 Rock Ridge
    : do not mix burn applications
    : CD-R & CD-RW media disc(s)only
    : no DVD media disc burn feature
    OS X Burnz : ISO 9660 level 1
    : ISO 9660 level 2
    : ISO 9660 RockRidge extensions
    : ISO 9660 Joliet extensions
    : HFS+
    : CD-R & CD-RW media disc burn
    : DVD-R & DVD-RW media disc burn
    [1]Sony cd-rw crx230e (CD 207x rd, 52x Wr):XPmachine(PC)
    XP integrated tools .. : ISO 9660 ?*
    .. Windows Explorer :read SuperDrive Finder CD media
    :..disc(s) burned and copy to HD
    :..and write to CD media disc(s)
    :..burned with Finder
    :read SuperDrive BurnAgain
    :..CD media disc(s) burned and
    :..copy to HD and write to CD
    :..media disc(s) burned with
    :..BurnAgain application but
    :..preferred that you do not
    : limited to and tested only CD
    ?* .. opening resource: http://aumha.org/win5/a/xpcd.php
    Explains more about XP native CD media disc burning and
    further links to more well informed research webpages
    that show XP appears to apply ISO 9660 Joliet .. to
    manage long file names, primarily. The entire area is
    wide-scope with technicalities .. access
    www.cdrfaq.org and see for yourself how deep the rabbit
    hole goes. Software is performing an important aspect
    of your optical drive media disc burning capability ..
    as hardware specs improve and softwares fully use the
    available service offered by the developing hw/sw
    standards .. as evidenced by browsing the cdrfaq.org
    .. you can see how things have moved along for the
    user's benefit and advantage.
    MATSHITA DVD-R UJ-845C : iMac DV SE (Apple)
    : read only media disc(s) burned
    from Mac mini.. : cannot read SuperDrive media
    from mac mini.. :..disc(s) burned on DVD or CD
    from XP machine.. :can read media disc(s) burned..
    from XP machine.. :..on XP machine (test only CD)
    : if SuperDrive media disc burn first and then further
    written and so added to by XP machine..unable to read.
    (applied to Os X Finder, BurnAgain and Burnz
    applications)
    We are safely at the point where we can assert that we
    have a potential operating solution for the Mac mini
    media disc burning. However, we remain reliant on our
    XP machine to create media disc burned that can be read
    fully by the iMac DV SE. And we have no confidence to
    date in the ability to share information burned by the
    Mac mini with any other party .. except where we can
    repeat ourselves over several iterations to accomplish
    100% data transfer .. and that means we are confined to
    our home operating computer systems. For now, XP machine
    is required to write a media disc that can then be read
    by the iMac DV SE. (Yes, we do have a Mac to Mac network
    .. but if data is unavailable on either of the Mac
    machine drives then we are required to resort to hard
    media backup) Media disc(s) sampled to date .. Verbatim
    CD-R, CD-RW, DVD+RW .
    Apple quality media pack (8x DVD-R only)*• is available
    at www.apple.com and in our locale. We shall sample the,
    not inexpensive, apple media disc(s) in the near future
    .. and report back. Still the DVD-R is write once. And
    no mention of any CD-RW apple quality media
    availability. Remember ...
    *• DVD-R discs hold about 4.7 GB of information.
    You can burn files on a DVD-R disc using the Apple
    SuperDrive. DVD-R discs are not reusable; you can burn
    files on them only once.
    [1] Action item one is to acquire genuine quality media
    disc(s). [ to, ideally, accomplish burn verification ]
    If 100% media disc burn and verification were able to be
    accomplished by the OS X supplied applications Finder
    and Disk Utility then only limitations to overcome are:
    Finder's (improved standards adhering) write once only
    to media disc feature and Disk Utility's apple OS only
    media disc burned format limitation and maybe multi-
    session disc burning feature.
    [2] Action item two is to acquire genuine quality media
    disc burning software(s). [to accomplish burn media
    capacities and maximum standards adherences ]
    If fuller standards compatibility and media disc burn
    usage features are available then items one and two
    requirements seem to be met. And actions items three
    and four are no longer options of any material
    significance. That would be welcome.
    [3] Action item three is to optionally acquire an
    alternative media disc burning solution. [ to accomplish
    100% or nearest possible media burn quality and
    consistency ]
    [4] Action item four is to forego media disc burning
    (item three) in favour of external hard disk solution
    (which could be partitioned) to share datafiles among
    differing machines and operating systems. [ to resolve
    the media sharing challenge in the absence of
    satisfactory value media burning solution that meets
    quality, consistency and compatibility needs ]
    Hopefully .. this tale of media burning discovery does
    ignite some passion and interest among certain others of
    you who may be willing to share a little of your own
    enlightening discoveries in the industry of media disc
    burning and any Apple SuperDrive MATSHITA guidelines or
    guidance(s) that you have established .. in particular.
    For now .. and until any further future update .. thank
    you again everyone .. we look forward to any remedial
    solutions that you may have developed to your media disc
    burning operating satisfaction. Much have we to learn ..
    search for answers continues ...
    Well .. it's been fun .. in an adventurous and discovery
    kinda way .. but back to our chosen path must we return.
    Stuart.
    Additional Informations ...
    We only ever used the software system default media disc
    burning speed settings where no choice permitted, or
    where choice permitted .. we used half (the
    automatically selected ) speed setting or lowest
    possible speed setting.
    Xp machine OS: Windows XP (5.1.2600 Service Pack 2)
    XP machine media disc burner: Sony cd-rw crx230e
    [+]Sony cd-rw crx230e (CD 207x rd, 52x Wr)
    This is what we want(ed) to know about the Apple
    MatShita SuperDrive too ! (opensourceuser note: crx230ae
    is the closest we could find to XP revealed Sony optical
    drive)
    [+]SPECIFICATIONS
    PART NUMBER CRX230A/U
    DRIVE TYPE Internal
    MEDIA & MODES SUPPORTED CD-R, CD-RW, CD-ROM (Mode 1 & Mode 2),
    CD-ROM XA (form 1 & form 2), CD Audio, Video CD,
    CD Extra, Multi-Session, Packet Writing
    READ/WRITE SPEED CD-R Write: 4X, 8X, 12X, 16X CLV, 24 ~ 40X P-CAV,
    52X CAV (turbo mode) max.
    CD-RW Write: 4X, 8X, 10X, 12X CLV, 16 ~ 32X CAV max.
    CD Read: 52X max.**
    SUSTAINED DATA TRANSFER RATE 600 kB/s (4X CD-R/RW read/write)
    (CD-R/RW DISCS): 1,200 kB/s (8X CD-R/RW read/write)
    1,800 kB/s (12X CD-R/RW read/write)
    4,800 kB/s (32X CD-R/RW read/write max.)
    7,800 kB/s (52X CD-R read/write max.)
    RANDOM ACCESS TIME 100 ms
    INTERFACE ATAPI/EIDE
    LOADING MECHANISM Motorized tray
    MOUNTING Vertical or Horizontal
    BURST TRANSFER RATE PIO Mode 4: 16.7 MB/s, Ultra DMA Mode 2: 33.3 MB/s
    BUFFER MEMORY 2 MB
    POWER REQUIREMENTS +5V / +12V V DC
    POWER CONSUMPTION +5V: 1.5A / +12V 1.5A
    DIMENSION (W x H x D) 5.75 x 1.63 x 7.49 inches
    WEIGHT Approx. 2.2 lbs.
    PACKAGE CONTENTS CRX230A/U Drive
    ATAPI Cable
    Software installation CD-ROM: B’s Clip and B’s Recorder Gold
    Mounting Screws
    Quick Start Guide
    Limited Warranty Card
    SYSTEM REQUIREMENTS Intel®Pentium®II processor 400 Mhz or faster (or equivalent)
    CPU, 64 MB RAM, 1 GB available hard disk space
    recommended. Microsoft®Windows®98SE, Windows®
    Millennium Edition, Windows®2000 Professional, or
    Windows®XP Home/Professional operating systems
    WARRANTY One Year Limited
    *Buffer underrun protection technology is conformed to Sony’s Power-BurnTM drive specifications.
    **Requires Ultra High Speed Plus CD-RW Media
    (opensourceuser note: datasheet(s) supplied with images
    of the recommended Sony media disc(s) - however on
    closer inspection at the local store - Made in Taiwan)
    Still we did find TDK media disk - Made in Japan - at
    the same store and apart from the DVD-RAM media discs,
    the only one type CD-R, everything else from China to
    Singapore.

  • Unable to Load Metadata (Error in shared.context.ContextLoader in startup)

    Hi,
    I am currently installing fixes on an environment, and every time a patch was installed the application server starts up. The application starts up successfully until I installed 8424662. I still don't know if this is the patch that causes the error, but here's the part of the log that states the error:
    - 2010-03-29 07:31:12,030 [Thread-1] ERROR (shared.context.ContextLoader) Unable to load metadata for package com.splwg.base.domain.common.masterConfiguration
    java.lang.NullPointerException
         at java.io.Reader.<init>(Reader.java:61)
         at java.io.InputStreamReader.<init>(InputStreamReader.java:55)
         at com.splwg.shared.context.PackageMetaInfoLoader.getManagedObjectDataAndExtractHashInfo(PackageMetaInfoLoader.java:53)
         at com.splwg.shared.context.PackageMetaInfoLoader.getContextEntities(PackageMetaInfoLoader.java:48)
         at com.splwg.shared.context.PackageMetaInfoLoader.read(PackageMetaInfoLoader.java:44)
         at com.splwg.shared.context.ContextLoader.loadFromStream(ContextLoader.java:90)
         at com.splwg.shared.environ.ContextManagedObjectSet.loadFromStream(ContextManagedObjectSet.java:120)
         at com.splwg.shared.environ.ContextManagedObjectSet.loadFromStream(ContextManagedObjectSet.java:107)
         at com.splwg.shared.environ.ContextManagedObjectSet.loadAllContextManagedObjects(ContextManagedObjectSet.java:72)
         at com.splwg.base.support.context.ContextFactory.loadManagedObjectForApplication(ContextFactory.java:194)
         at com.splwg.base.support.context.ContextFactory.buildContext(ContextFactory.java:106)
         at com.splwg.base.support.context.ContextFactory.buildContext(ContextFactory.java:90)
         at com.splwg.base.support.context.ContextFactory.createDefaultContext(ContextFactory.java:498)
         at com.splwg.base.web.startup.DeferredXAIStartup.run(DeferredXAIStartup.java:73)
         at java.lang.Thread.run(Thread.java:595)
    - 2010-03-29 07:31:14,873 [main] INFO (web.startup.SPLWebStartup) Application Context shutdown successfully
    Any help on this problem is greatly appreciated. Thank you so much!

    Patch 8424662 incorporates an entry in contextManagedObjects.xml that points to a class com.splwg.base.domain.common.masterConfiguration but this class is not yet present in spl-base.jar file. Patch 8711158 should be installed, since it contains this class.

  • Read-only access when saving metadata to file from Adobe Lightroom on a MAC OS to Windows shared drive

    We have a group of 5 people editing and indexing photos to a shared drive on a windows server, everyone has its own catalog and working on different folders to avoid any locking conflicts.
    The windows computers don't have any problems but the Mac's don't write the updated metadata to all files because they get the message "Photos have read-only access".
    The environment is the following:
    2x Macs workstations running:
    - Adobe Photoshop Lightroom 5.7.1
    - iMAC with MAC OS X Yosemite 10.10.2
    3x Windows Workstations:
    - Windows 7
    - Adobe Photoshop Lightroom 5.7.1
    Server:
    - Shared drive on a Windows Server 2012 Standard
    I have searched the internet, no one has this problem with this exact setup but I have tried all the solutions I found, namely:
    1. Connect to the network drive with cifs:// protocol
    2. Change the settings of the nsmb.conf for 'smb1_only' protocol
    3. Mount the drive manually by command line
    Nothing worked, any ideas?

    Did you ever find a solution to this problem?  I have the same issue and wonder if Lightroom 6 will resolve it.  I  tried AFP, SMB2, SMB3 and they all failed to save metadata randomly. When I use NFS from OS X then it works fine but it's a little slower than SMB and it's not as native as the mount via AFP or SMB, so it's harder to maintain.     My server is a FreeNAS 9.2 (FreeBSD) which is running Samba, Netatalk and native NFS.

  • Editing and sharing custom metadata/keywords through Adobe Drive in Adobe Bridge

    I am part of a four-person video production unit operating within a local governmental entity. We are currently using four licenses of Adobe Master Collection CS5, and are about to get access to dedicated SAN storage.
    We would like each user to have the ability to assign specific keywords to any given video clip (or remove keywords from clips) within Adobe Bridge, and have the three other users see the same results. I've noticed that Bridge alone will allow for keywords to be added or removed, but this list is specific to each user. Importing one list into other users' profiles is a start, but would no longer work, once keywords are added or taken away.
    The overview page for Adobe Drive 3 says that it, "allows users to edit and view custom metadata/properties through Adobe Drive in Adobe Bridge," but I haven't found any explanation in either the website, forums, or user's guides that delves any farther into this area. If we incorporate Adobe Drive/Bridge into our workflow, will we be able to share/sync keywords between users? Is there some other (affordable) solution that would let us do this?
    Thanks for any insight you might be able to offer.
    Chuck

    Hi,
    Thanks for sharing your case.
    The keywords you mentioned is XMP metadata, if all your digital assets are managed by ADEP CQ DAM service, you can use AD3 with built-in ADEP connector to communicate with the DAM server, then, I think it can meet your requirement, it means, the keywords can be set by one user through metadata panel in Bridge, and can be viewed by other users.
    for custom properites, it's different from XMP metadata, it refers to the properties of one asset which is managed by a Content Management service. users have to use another UI to edit/view them in Br after AD3 is installed.
    here are some requirements to use it.
    1) CMIS 1.0 compiliant server should be used to manage all your digital assets
    2) use the built-in CMIS with AD3 to connect to the server.
    if other kind of servers are used, you should develope a custom connector through AD SDK to enable custom properties feature as well as some other handler required by AD SDK
    thanks 

  • Can IPTC metadata be included in Shared Photo Streams?

    I was surprised that my version name and all IPTC data such as my ratings, key words, etc. are not appearing in my Shared Photo Streams. Is there any way to include this metadata?

    Since you are seeing the Shared Photo Stream Albums in Aperture, but empty, you have all preferences set up correctly.
    Aperture or iPhoto should be filling the albums from the folder I mentioned, but they cannot, because this folder is empty.
    There may be two reasons for this folder being empty. Either the Photostreamagent is not running or you may be  having a permissions problem with your home folder.
    Have you tried to toggle the Photo Sharing off and on again in  the System Preferences, as described here in this link?   iCloud: Troubleshooting iCloud Photo Sharing and Shared Photo Stream
    You could also try if removing the empty folder ~/Library/Application Support/iLifeAssetManagement/assets/sub-shared   and restarting the Mac will help.
    As a test you could try, if the Shared Photo Stream will work in Safe Mode: Mac OS X: Starting up in Safe Mode
    If all fails, launch the Console from the Applications folder and check, if there are any error messages relating to "photostreamagent".

  • Sharing to flickr doesn't push the metadata of modified photos

    In iPhoto 09, we can share photo on flickr.
    There is a very annoying problem though. If a photo has been modified in iPhoto, the metadata is lost (well, it's not lost really, since it's kept in a database outside of the file) but the file corresponding to the working copy of the photo doesn't contain the metadata of the original file. Although this is very annoying for many reasons, I understand that one photo in iPhoto is not necessarily 1 file. Fine.
    The problem is that contrary to when a photo is exported, the metadata is not added to a photo that is shared on flickr (using the new 09 "share to flickr feature").
    It works correctly when sharing on facebook though.
    Here is a very basic scenario:
    Take a photo in "landscape" mode and another in "portrait" mode.
    Import them in iPhoto. Normally, the one in "portrait" mode will be rotated automatically by iPhoto so that it is displayed as it was meant to be display (great).
    Select those 2 photos and share them on flickr.
    The one in portrait mode will not have a "date/time taken" so the value will be the same as for "date/time uploaded". The one in "landscape" mode should be fine.
    I think this is because the file that is shared for the picture in landscape mode is still the original file while the one for the portrait photo is a working copy that doesn't contain the metadata.
    Is this a bug? Any chances to get a fix?

    I believe so.
    I have done some more tests and it looks like only the photos that have been rotated automatically because they were taken in portrait mode are affected.
    For example, the pictures that I have modified in iphoto are exported AND shared on flickr with all the metadata. So it is not a matter of having a working copy of the original photo or having the original photo file.
    It is really only for pictures that were taken in portrait mode.
    I have done this simple test:
    I import a photo that was taken in portrait mode, and export it with all the possible information check box checked (including location)
    => the exported photo doesn't contain the "generated date" and contains very little metadata (it does contain the location though).
    I then go back to iPhoto, and "revert" the photo "to original". It doesn't appear to change, and it still is displayed in portrait mode. But now if I export it, the export contains the full metadata.
    If I export a photo that got heavy modifications but that was taken in landscape mode, all the metadata is there.
    So it really looks like a bug related to the "portrait" automatic orientation. The metadata is lost somehow...

  • Displaying Album Usage/Sharing Metadata

    I know this has been asked before, but I was wondering if anyone knows how to display in the Metadata Inspector tab, which albums might contain a selected image. The reason I ask has to do with posting images to Facebook for example.  Working with a project containing many images, I selected a number of them to be published to Facebook.  Essentially this creates an "album" containing these images. At a later date, I might want to add additional images from this project to the Facebook album. Looking at all the images in the project, there is no way of knowing if a certain image has already been published or not.  I know you can use the Sharing Metadata View in the inspector which tells you if a selected image has been shared or not.  This works only for the Facebook "Album" or other published albums.  There is no corresponding way to know if a selected image is in any other type of album by using the metadata inspector. I know you can filter the images by using the Aperture metadata field "album name" with any of a number of conditions, which does provide the information.  However, as far as I can know, you can't display the Aperture metadata field "album name" in the metadata inspector. Am I understanding this correctly?
    Thanks!!
    Ed

    I know this has been asked before, but I was wondering if anyone knows how to display in the Metadata Inspector tab, which albums might contain a selected image. The reason I ask has to do with posting images to Facebook for example.  Working with a project containing many images, I selected a number of them to be published to Facebook.  Essentially this creates an "album" containing these images. At a later date, I might want to add additional images from this project to the Facebook album. Looking at all the images in the project, there is no way of knowing if a certain image has already been published or not.  I know you can use the Sharing Metadata View in the inspector which tells you if a selected image has been shared or not.  This works only for the Facebook "Album" or other published albums.  There is no corresponding way to know if a selected image is in any other type of album by using the metadata inspector. I know you can filter the images by using the Aperture metadata field "album name" with any of a number of conditions, which does provide the information.  However, as far as I can know, you can't display the Aperture metadata field "album name" in the metadata inspector. Am I understanding this correctly?
    Thanks!!
    Ed

Maybe you are looking for