2005 or 2006 Threads???

Hi
While searching for the old threads I could not find the threads that have been created in the years 2006 or 2005. SDN is only allowing to search from 2007 year.... Where are all the
threads of years 2005 and 2006 have gone?? Are they archived? if yes, can any one please let me know where I can find 2005 or 2006 Threads?
Thank you in advance

All the threads are available there while searching. Just depends wether the search string exists that time or not. Also, Select ALL in Date Range while doing a search.
Regards,
Amit
Reward all helpful replies.

Similar Messages

  • My iPhoto 6 isn't reading my 2005 and 2006 folders

    Boy, I give up. My Library has 2005 listed under iPhoto Library>2005 and 2006 is under iPhoto Library>Originals>2006, and both contain the photos. The problem is they aren't showing up in my library. The other years are, tho. Yes, the boxes are checked next to them. I've updated my system, iPhoto and repaired pemissions. I can't import the folders because iPhoto won't import items already in the library. when I've brought new photos in, they disappear next time I launch iPhoto. Any ideas on how to fix this? Thanks!
    Chris
    powerbook   Mac OS X (10.4.6)  

    HI chris,
    close iPhoto
    Drag your iPhoto Library folder to the desktop
    Duplicate the iPhoto Library folder as a backup
    Open the original library folder
    For the 2005 folder that is loose at the root of the library folder ...navigate through it and see if it has any photos in the roll folders. If not, then delete that Year folder. If it has photos in it, note if they are already imported into the iPhoto Library folder and showing up when you view the library within iPhoto.
    If they are in the library and showing up, you can delete them. If they are not showing up in the library, drag them to a new folder on the desktop so you can import them later if needed.
    Now in the Originals folder you should have the Year folders. In the Year folders there should be roll folders.
    Are you saying there is a Year folder (2005) inside a Year folder (2006)?
    If so, they somehow are misplaced.
    Take the 2005 folder and put it in the Originals folder so it would look like the screenshot.
    iPhoto 6 Library folder in the Finder
    Now what you are going to do next is create a new library and import the Originals folder back into it.
    close iPhoto
    -drag the iPhoto Library folder to the desktop (you already did this)
    -launch iPhoto and create a new library
    -double click the iPhoto Library folder on the desktop to open it
    -the two main folders you will need to import are the Original folder and the Modified folder (only if you want to import the edited images).
    -the Originals folder has all your originals photos unedited. the Modified folder has all images that you have edited, rotated, cropped, etc.
    -Drag these two folders to the desktop
    -If you want to save the edited image, find it in the roll in the Modified folder and drag it into the roll of the same name in the Originals folder. It will replace the originals and now will be the original.
    -If you don't care to save any edited images, then don't import the Modified folder into iPhoto or don't bother replacing the edited image with the original image like I just described.
    -If you import the Originals folder into iPhoto you will have all your originals in their named rolls.
    -If you import the Originals and Modified folders into iPhoto, you will have all of the being in the originals folder in the finder. The roll with the same name as the other will have a _1 appended to it's name (in the finder)
    -the roll from the originals will be next to the same roll from the Modified folder within iPhoto. You can then delete any of the images from there if you want.
    I know this might sound confusing but it really isn't.
    Get back if any of this sounds like something you might want to do.

  • Thread 1 cannot allocate new log, sequence 1196,Checkpoint not complete

    We were receiving the following messages in alert log. We have Oracle 10g R2 database having four redo log groups with two members each (50 MB). To overcome this error yesterday we added two more groups with same config. Again we received the same message in the alert log.
    Alert Log contents:
    Fri Dec 22 11:21:39 2006
    Thread 1 cannot allocate new log, sequence 1193
    Checkpoint not complete
    Current log# 1 seq# 1192 mem# 0: /u02A/oradata/admin/origlogA/redo01.log
    Thread 1 advanced to log sequence 1193
    Current log# 5 seq# 1193 mem# 0: /u02A/oradata/admin/origlogA/redo05.log
    Thread 1 cannot allocate new log, sequence 1194
    Checkpoint not complete
    Current log# 5 seq# 1193 mem# 0: /u02A/oradata/admin/origlogA/redo05.log
    Current log# 5 seq# 1193 mem# 1: /u02B/oradaFri Dec 22 11:21:50 2006
    Thread 1 advanced to log sequence 1194
    Current log# 6 seq# 1194 mem# 0: /u02A/oradata/admin/origlogA/redo06.log
    Current log# 6 seq# 1194 mem# 1: /u02B/oradata/admin/origlogB/redo06_2.log
    Thread 1 advanced to log sequence 1195
    Current log# 2 seq# 1195 mem# 0: /u02A/oradata/admin/origlogA/redo02.log
    Current log# 2 seq# 1195 mem# 1: /u02B/oradata/admin/origlogB/redo02_2.log
    Fri Dec 22 11:22:05 2006
    Thread 1 cannot allocate new log, sequence 1196
    Checkpoint not complete
    Current log# 2 seq# 1195 mem# 0: /u02A/oradata/admin/origlogA/redo02.log
    Current log# 2 seq# 1195 mem# 1: /u02B/oradata/admin/origlogB/redo02_2.log
    Thread 1 advanced to log sequence 1196
    Current log# 3 seq# 1196 mem# 0: /u02A/oradata/admin/origlogA/redo03.log
    Current log# 3 seq# 1196 mem# 1: /u02B/oradata/admin/origlogB/redo03_2.log
    Thread 1 cannot allocate new log, sequence 1197
    Checkpoint not complete

    You might not want to revivify threads from 2006. Create a new thread, including all the information to make it a [url  http://catb.org/esr/faqs/smart-questions.html]smart question. Which version and patch level of Oracle are you on, which platform, how often are your logs switching, a relevant clip from your alert log surrounded by {noformat}{noformat} tags, etc.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Compatability - Contribute 3, Quickbooks Pro2005/2006, Dantz Retrospect etc

    Am about to buy a new iMAC Core Duo for my wife (she has a G4 iMAC) and have managed to nail down all her software ito compatability with the Core Duo... with the exception of:
    1. Macromedia Contribute 3
    2. Quickbooks Pro 2005 (or 2006 i..e I will upgrade her to that it 2006 works and 2005 doesn't) - I know the new iMAC's ship with 2006 NUE, but I read NUE is a slimmed down version
    3. EMC Dantz Retrospect 6
    4. HP Scanning & Image Zone Software for Scanjet 4670
    I have spent hours of the various companies websites... sent them e-mails... called them... all to no avail...
    If I can nail down these 4, she's getting a new Core Duo... if not... maybe I'll wait...
    Help?
    Power Mac G5 Dual 2GHz   Mac OS X (10.4.4)  

    I have heard back from Dant'z and they say... Not compatible... but are working on a release that will. Also just heard back from Macromedia and they say they are not sure if Contribute will or worn't work... they say they are in testing mode. Still haven't heard about Quickbooks pro 2005 or 2006. Anyone know if those will run under rosetta?

  • Ipod no longer authorized (unknown error -42408)

    posted this at itunes site as well.
    out of blue, having problem i've never had syncing my 60G ipod.
    for years have been syncing this ipod with my itunes on my macbook (only). for the past few times (?month or so), i'm getting an error message when i try to sync that first says, the ipod/macbook is not authorized for this ipod (which it always has been).
    then it asks me if i want to authorize it. when i hit "authorize", it brings up an old itunes account i had and asks me for the old password, which i enter. then i get an error message that says:
    "unknown error -42408. error in itunes store. please try again later."
    how do i fix this so that i don't get this error message and can continue syncing with my most recent account, which has NEVER been a problem in the past?
    thanks.

    I have exactly the same problem. My iPod is a 30GB one from 2005 or 2006 (I don't know how to identify its category). When it was new, I had a PC; then a year and a half ago I switched to a Mac and got everything transferred ok, and have been synching the iPod to the Mac with no trouble since then. (Well, slight trouble, because the iPod is now very full, and I haven't figured out the best way to synch "almost everything", but so far I'm managing somehow.) But just before leaving Moscow March 10, I wanted to synch and recharge the iPod, and got the same problem, with the same sequence of messages described at the start of this thread. So I only recharged it. Now I'm in Amherst, tried again, exact same problem. So now only recharging again.
    Same computer, same iPod, why does it suddenly not recognize that this computer is authorized to synch this iPod, and why does it make this error when I tell it to authorize it? And how can I fix it?
    Grateful for any help.
    Barbara

  • How to split a report in many PDF

    Post Author: metoo
    CA Forum: Other
    I have a BO report that has two groups: year and location. This report has to be exported to different PDF files which correspond to the data of one of the groupsyear. For example, one pdf file has only data for 2004, another one for 2005, and so on. The VB code that I am using is below, labeled "Working Code" and works fine. Now, I want to create pdf files by location. So, I made a copy of the code and change some names and values and now it generates the different PDF files but it dumps the whole report in each file (all the locations) instead of just showing the data that correspond to the specific locationsee code below labeled "Not Working Code".  Any suggestions on how to fix this? Does it have to do with what is in ""? "Location" is the name of the dimmension, should I be delcaring something else somewhere else?
    "Working Code"
    Sub creates_yearsPDF()     ExportToPDF "2004"    ExportToPDF "2005"    ExportToPDF "2006"    ExportToPDF "2007"              MsgBox "Exporting Year Report to PDF files has been completed."
    End Sub
    Private Sub ExportToPDF(strFName As String)
        Application.Variables.Item("Year").Value = strFName
        ThisDocument.ActiveReport.ForceCompute    ThisDocument.ActiveReport.ExportAsPDF "c:\PDF file for " & strFName
    End Sub
    "Not Working Code"
    Sub creates_locationsPDF()     ExportToPDFL "North"    ExportToPDFL "South"    ExportToPDFL "East"    ExportToPDFL "West"              MsgBox "Exporting Locations Report to PDF files has been completed."
    End Sub
    Private Sub ExportToPDFL(strFName As String)
        Application.Variables.Item("Location").Value = strFName
        ThisDocument.ActiveReport.ForceCompute    ThisDocument.ActiveReport.ExportAsPDF "c:\PDF file for " & strFName
    End Sub

    This thread might be helpful (but not my contributions I fear ;-)
    Re: SQL query report columns

  • Lost inbox and sent mail only

    There are lots of posts on this but not exactly as it's happened in this case. I have read thru all the posts and was able to recover some files but not all. Apparently MAIL was quiting and when data was imported, acct settings were changed. There were over 8,000 emails in INBOX and as much in SENT. Here's what's in the mail folder:
    default counts
    envelope index
    LSMMap@
    Mailboxes (folder)
    messagesrules.plist
    messagerules.plist.backup
    messagesrules.plist
    messagerules.plist.backup
    POP-(email address) (folder) >
    ...deleted messages.mbox
    ...drafs.mbox
    ...junk.mbox
    ...MessagesUidsAlreadyDownloaded
    ...MessagesUidsAlreadyDownloaded2
    ...Sent Messages.mbox
    POP-(same email address) (folder) Same except inside only has > INBOX.mbox, Junk.mbox, MessagesUidsAlreadyDownloaded2
    signatures (folder)
    smartMailboxes.plist
    I assessed that most of the emails that are not coming thru to MAIL were in the first POP listed. I can see the emails if I open each one for the years missing 2005 and 2006.
    I cleaned out dups of imports and rebuilt mailboxes. it was 6.6Gigs now down to 3GB.
    I used "other' to import what did get imported via copying mbox file onto desktop and retrieved 2004 and some 2005 files.
    How can I get them to show up in MAIL?
    thank you
    G4 powerbook   Mac OS X (10.4.8)  

    You’re welcome.
    The reason I post your entire quote is so that you have
    complete info again
    I see the entire thread every time I read any of the posts, so the only thing quoting everything accomplishes is actually reducing the amount of relevant information I can see on the screen.
    Did you get a chance to read all of my replies?
    Yes, and none of them explained what prevents you from solving the problem doing what I suggested in my first post...
    I don't feel that you understood that I have done the easy import
    as per your email several times which did not resolve my problem.
    The only place where you mentioned having already tried importing anything is your first post, and the first thing I said in my reply to that post is precisely that I didn’t understand what you said there. So yes, you’re right that I didn’t understand it. Moreover, I still don’t understand it...
    I am here because NOT all emails were recovered
    And I’m trying to help you recover them, but I cannot do so if you don’t explain what’s the problem exactly.
    Email stored in the individual MAILBOXES did import.
    This, for example, doesn’t make sense. All the messages are stored in one mailbox or another. It doesn’t make sense that you can import the mailboxes but not the messages. Mail’s mailboxes in the filesystem are folders with an .mbox suffix, e.g. INBOX.mbox. Maybe you’re calling ‘mailbox’ something else?
    ps. when I import using OSX I get the following error:
    "No valid mail for OSX files were found"
    Ahhh! Now, this makes sense. This is the first thing you’ve said in this thread that allows me to understand what’s the problem exactly. Wouldn’t it have been easier if you had reported from the very beginning any error messages you were getting?
    Pay attention to the instructions that Mail displays when choosing Mail for Mac OS X as the data format. Mail wants you to select the folder that contains the mailboxes to be imported (i.e. the POP account folder in your case), not the *.mbox folders themselves. If you select the *.mbox folder itself, Mail says “No valid Mail for Mac OS X files were found” because it cannot find any *.mbox folders within the folder you’re selecting.
    I was able to recover some emails using the "other" radial in import.
    If you could recover any messages importing as Other, that means those mailboxes have files used by Mail 1.x (Mac OS X 10.3) that Mail 2.x (Mac OS X 10.4) leaves there after the conversion to the new *.emlx format. The only messages you would find there would be from before upgrading that computer to Mac OS X 10.4 (Tiger).
    Maybe it’s one of those files (mbox) what you’re calling ‘mailbox’? If that’s the case, wouldn’t it have been clearer referring to those files by their name instead of (or in addition to) interpreting what they are?
    The only items within a mailbox (i.e. within an *.mbox or an *.imapmbox folder) used by Mail 2.x are Info.plist and the Messages folder. Any other files you may see there are almost certainly Mail 1.x files that Mail 2.x leaves there after the conversion. This is poorly explained in Mac OS X 10.4 Mail: Some mailbox files used by Mac OS X 10.3 are not deleted after importing. The article only talks about mailboxes in ~/Library/Mail/Mailboxes/, but the same can also be said about mailboxes in “POP-”, “IMAP-”, or “Mac-” account folders.

  • Problem with admin console

    Hai Folks,
    I have installed Weblogic8.1 SP5.I have created mydomain with user name,password,and all other portdetails host.
    When I start server it is running properly with out any errors..the out put window shows the below message..
    Starting weblogicserver with Java HotSpot(TM) Client VM Version 1.4.2_0
    Inc.>
    2006 11:14:55 AM CDT> <Info> <Configuration Manageme
    r is being started as the administration server.>
    2006 11:14:55 AM CDT> <Info> <Management> <BEA-14110
    8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
    XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 6
    2006 11:14:56 AM CDT> <Notice> <Management> <BEA-140
    ration from configuration repository at C:\bea\user_
    config.xml.>
    2006 11:14:59 AM CDT> <Notice> <Log Management> <BEA
    e C:\bea\user_projects\domains\mydomain\myserver\mys
    ver side log events will be written to this file.>
    2006 11:15:02 AM CDT> <Notice> <Security> <BEA-09008
    ing security realm myrealm.>
    2006 11:15:03 AM CDT> <Notice> <WebLogicServer> <BEA
    Admin Server "myserver" for domain "mydomain">
    2006 11:15:11 AM CDT> <Notice> <WebLogicServer> <BEA
    dmin Server "myserver" for domain "mydomain" running
    2006 11:15:11 AM CDT> <Notice> <WebLogicServer> <BEA
    RUNNING mode>
    2006 11:15:11 AM CDT> <Notice> <WebLogicServer> <BEA
    ad.Default" listening on port 7001, ip address *.*>
    But when i try to open admin console through browser giving the url as
    http://localhost:7001/console the page is not displaying its giving page not found error.I tried it again by restarting the system,but again the same problem..Please help me regarding this problem.
    Thanks,
    Sai

    mmm, it could be CPU, it could be a network-related issue... are you using multicast or unicast?
    can you reproduce the issue?
    if yes, can you run "top" to verify the CPU usage,
    and do a thread dump on the admin server?
    or at that point the box is entirely unresponsive?
    in that case, running a scripts which periodically does a thread dump, and running top to sample every 10 seconds, could help...
    jm2c

  • Regarding conversion of String to Date

    Hi
    Ravi here and I am getting the following exception when i am working with String to date conversion.As i am working in LAN this code is working for all others .This problem is with my system only.This is not supporting with yyyy-MM-dd format.One more thing in my system only we installed VisualStudio.Is that a problem for this exception.I am using Myeclipse
    Plzzzzzzzzzzz help me I got strucked .
    Thanks in advance
    Code:
    public void testSaveDates() throws HibernateException, ParseException{
    try{
    Date date=new Date();
    String str1 ="2006-05-06";
    Date dateFormatter = new SimpleDateFormat("yyyy'-'MM'-'dd").parse(str1);;
    System.out.println(dateFormatter);
    catch(Exception e){
    e.printStackTrace();
    Exception:
    java.text.ParseException: Unparseable date: "2006-05-06"
         at java.text.DateFormat.parse(DateFormat.java:335)
         at chaitanya.MyTest.testSaveDates(MyTest.java:282)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at junit.framework.TestCase.runTest(TestCase.java:154)
         at junit.framework.TestCase.runBare(TestCase.java:127)
         at junit.framework.TestResult$1.protect(TestResult.java:106)
         at junit.framework.TestResult.runProtected(TestResult.java:124)
         at junit.framework.TestResult.run(TestResult.java:109)
         at junit.framework.TestCase.run(TestCase.java:118)
         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:421)
         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:305)
         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:186)

    Date date=new Date();You don't need this line.
    Date dateFormatter = new
    er = new
    SimpleDateFormat("yyyy'-'MM'-'dd").parse(str1);;As already told, you don't need the single quotes. And you don't need two semi-colons - that's unnecessary.
    I just wrote a sample code to test that out. Check it and see for yourself.
    import java.text.SimpleDateFormat;
    public class Test {
         public static void main(String[] args) throws Exception {
              System.out.println(new SimpleDateFormat("yyyy-MM-dd").parse("2005-04-18"));
              System.out.println(new SimpleDateFormat("'yyyy'-'MM'-'dd'").parse("2005-04-18"));
    }Output:
    Mon Apr 18 00:00:00 EDT 2005
    Exception in thread "main" java.text.ParseException: Unparseable date: "2005-04-18"
            at java.text.DateFormat.parse(DateFormat.java:335)
            at Test.main(Test.java:6)I wonder why it is not feasible to write a quick sample code.

  • SuperDrive media disc(s) .. assist .. update concluded . . .

    Concluding post in relation to the earlier postings on this particular subject and thread (now officially closed by apple support) .. and to be found at SuperDrive Media Disc(s) .. Assist ... [http://discussions.apple.com/message.jspa?messageID=759874#759874]
    APPLE DVD R DISC MEDIA TRIAL
    DVD-R
    8x speed
    Certified for use with Apple DVD-R drives :: 4.7GB Media
    Made in Japan
    MAC MINI MATSHITA DVD-R UJ-845C
    Mac mini 1.42GHz PowerPC G4 | 512 MB DDR SDRAM
    Tiger OS X 10.4.3
    Finder Burn - single folder containing many sub-folders totaling about 800Mbytes and approx. 4000 files.
    Burn Speed Options : 4x(faster) : 2x : 1x(more reliable) - actual Finder media disc burn dialogue descriptions
    [default selection is 4x(faster) ]
    We choose 1x(more reliable) ..
    Observations include .. no 8x speed media disc burn available from our little Mac mini Matshita DVD-R UJ-845C burner .. and .. as this is a DVD R .. we have time .. but no going back once burned .. and we want maximum systems compatibility .. you, dear reader, already know the drama we have previously experienced with Finder burns and older Apple iMac DV SE machine DVD drive (media disc burned) read compatibilities.
    The total burn was a lengthy delay before the entire routine was completed including automatic verification.
    OUTCOME
    This disc did not verify correctly and is unreliable. Because this disc is unreliable, discard it and try again using a new, blank disc. (Error code ) 0x80020063
    Total disc burned is almost 800Mbytes and about 4000 files.
    Verification was not an available option for the burn .. a Finder burn .. meaning verification was apparently automatically included as an unseen 'yes' option at media disc burn execution time.
    Examining the resulting Apple DVD R media disc burned .. we discover that things are good .. biggest single files (.dmg's at about 100Mbytes expanding to 350Mbytes - e.g. OS X 10.4.3 update) are able to be copied from the burned Apple DVD R media disc back to the Mac mini hard disk again and verify 100% when opened for installation. Encouraging. Better than anything previously experienced.
    iMac DV SE [ DVD MATSHITADVD-ROM SR-8184 ]
    Into the Apple iMac ancient (500 MHz PowerPC G3 operating OS X 10.4.3 Tiger | 640MB SDRAM) and we are greeted with goodness .. same accessibility as the originating Mac mini machine .. satisfying.
    And yes the 'problem' of multi-session burns is yet to come on the ancient iMac and if the response is any good as now .. it may not be a problem worthy of mention. At 800 Mbytes burn and 4.7 Gbytes capacity .. one could loosely forecast up to another 5 media disc burn sessions before the DVD R is full and complete.
    XP MACHINE
    And now into the PC machine for an XP looksee and again .. more goodness. Cross compatible files are fully accessible (an entire - own - website burned). Large files copy 100%. Better than before.
    Two thumbs up for this disk and burn.
    Verification failure remains a current mystery. Anyone ?
    It is easy to figure how one may doubt one's media burning hardware is any good by now .. but the gathering volume of supporting entries at the relevant media burning and error message forums reveals that hardware is unlikely to be (entirely) at fault .. rather something else .. say firmware ?
    Apple Media DVD R discs are manufactured in Japan (stated on the disc) and the quality difference and price premium are consistent with what others have written of the place of manufacture and the Apple media disc as well. Mostly positive.
    Still .. we should like to have access to dependable RW discs from Apple too .. for reliable re-useability.
    As for the subject of burn speed ...
    Many forum readers are well aware of an ongoing and gradually escalating matter between Apple and this gentleman http://www.crc.id.au/page/2/ .. we have curiously followed the unfolding events to observe the outcome of the burn speed specification variation. As you know .. our Mac mini is rated at maximum DVD media disc burn 4x and fitted with a MATSHITA DVD-R UJ-845C which is a later edition than Mr H's UJ-835 .. however .. we are more curious to observe whether the final outcome will satisfy Mr H or not. Burn speed, primarily, and quality of burn, secondarily, on selected media by Mr H. Once the outcome is known and to Mr H's satisfaction .. then we may enquire about his satisfaction with burn quality at the chosen burn speed(s) by Mr H.
    Here is an offline forum communication that we shared with another Mac mini user about disc media burn speed. As you may read .. he is entirely dissatisfied with the Mac mini media burn speed and isn't too keen on using the Apple disc burn media either ...
    So...Have you found any dvd-r or +r media that burns reliably on the mini? (non apple media please).
    I am completely disgusted with my new mini's pathetic superdrive that I paid way too much for.
    I have purchased new & built from new parts several PC's that burn DVD after DVD on a wide variety of media reliably.
    No one has even replied to my post
    http://www.123macmini.com/forums/viewtopic.php?t=2773&start=0&postdays=0&postord er=asc&highlight=
    Thanks
    .. and at latest check .. no-one has responded to the post .. maybe no-one knows .. outside of Apple HQ .. mind you .. no-one has truly usefully responded to our post either .. we responded thusly ...
    Mac Mini SuperDrive .. burn speed .. and burn .. reliability
    Sometime I just can't get my head around the subject and have to step back and breathe in real deep .. which makes me kinda dizzy .. and wait until the focus is on the forest before
    choosing the tree(s) to climb. This particular tree is getting taller ...
    And congratulations on your Apple ownership. Small is beautiful.
    Regret your coaster experiences. Frustrating and unfortunate.
    What SuperDrive description is fitted in your new mac mini ?
    We seem to be staring into a gaping black hole of acknowledgement .. from anyone.
    PC users, windows operating system software computers, appear to have an extreme edge .. when it comes to media disc burning. i.e. successful burns.
    Re-reading that lengthy post .. which doesn't fully format as intended .. has me fully believing that less is more and small is beautiful (still). Future specific posts will probably follow as a matter of personal self-committment .. to persist until the solutions are fully to hand. For now .. may we refer to your mentioned post in our next planned post please ? Solidarity of negatory outcome experience is credibility.
    Three forums have we frequented and participated to learn more about the black hole .. we know as SuperDrive media disc burning .. only you have provided any feedback whatsoever .. post reader numbers grow but answers are missing in action .. absent from class.
    http://www.crc.id.au/page/2/
    We have thought the SuperDrive matter you have referred to in your post was of no concern to us .. but now you have us thinking again .. although model numbers differ .. (ours is a later numerical reference) the concerns appear to be similar .. or largely about performance .. we shall also refer to this domain in our planned next post. Yes, we are aware of the matter .. from another forum .. but shall now supply the link for others to weigh and hopefully dish out their two cents worth .. where a consensus could mean we are also a part of this particular action. An ideal consensus would be firmware is unsuitable .. requires immediate update .. and in particular the quality of burn is consensually unacceptable .. action could follow.
    We have progressed no further with burning experimentations .. and will be using Apple media before progressing with our findings reporting. For now, we are unable to add to your ease of mind .. frankly .. unless the burning media is made in Japan .. we doubt any burn verification success is to be had. And we cannot find any burning media made in Japan in our locale. Where is the Apple media made?
    We have come to appreciate the SuperDrive is all about the firmware .. but have no new firmware to apply .. in fact .. our research to date shows that we have been unable to find the Matshita SuperDrive at all online and cannot confirm specifications .. neither could we locate the specifications at www.apple.com.au .. which is just plain odd.
    A third look has provided ... from www.apple.com/macmini/specs.html ..
    Storage
    * One of the following optical drives:
    o Slot-loading Combo drive (DVD-ROM/CD-RW): reads DVDs at up to 8x speed, writes CD-R discs at up to 24x speed, writes CD-RW discs at up to 16x speed, reads CDs at up to 24x speed
    o Optional SuperDrive (DVD±RW/CD-RW): writes DVD-R discs at up to 4x speed, writes DVD-RW discs at up to 2x speed, writes DVD+R discs at up to 4x speed, writes DVD+RW discs at up to 2.4x speed, reads DVDs at up to 8x speed, writes CD-R discs at up to 16x speed, writes CD-RW discs at up to 8x speed, reads CDs at up to 24x speed
    Where were you able to establish your SuperDrive (burning) specifications ?
    Writer's note : .. some things change .. and so have the Apple Mac mini SuperDrive burner specs changed .. since recording those detailed above. In fact .. they read like they maybe should have all along .. 8x DVD R media burn speed. DL is a bonus. Can anyone tell us what the drive designation is please ?
    CRC says: ".. This limits burn speed to 4x for Mac Minis and 8x for Powerbooks.".
    While speed matters .. and it does .. you appear to have exactly the same media disc burning problems that we are experiencing .. failed verification(s) .. and for us .. in short .. complete DVD-R media disc burned rejection from the Apple OS X.
    Do we .. in actual fact .. have two separate operating challenges here .. speed of burn and quality of burn .. any burn ? Speed was not our first priority .. quality is .. now we figure that at any speed the burn quality is anywhere from dubious to coaster.
    CRC says: ".. The UJ-835 that Apple use is firmware limited to suit various bits of hardware that they want to put together. The burner in the Mac Mini is the exact same model as the one in the PowerBooks. Apple load a 4x firmware on the Mac Mini, and an 8x firmware on the PowerBook drives.
    My bet is that this is for marketting reasons only. ".
    One of the contributors to http://www.crc.id.au/?p=21 . . says . .
    # Moneky Boy Says:
    August 14th, 2005 at 1:03 am
    My parents have a mini and my has one of the PowerBooks. Confirmed the drives are Matsushita UJ-835. They have never had an issue burning DVDs. Confirmed it by burning DVDs last night on the wife’s 12″ PowerBook.
    As far as updating the Firmware in your optical drives, no, you do not have to remove them from the machines to update their firmware. I’ve updated the firmware on my optical drives (for Region Free and/or speed gains) via the GUI in Mac OS X. One application that will do this is called DVRFlashX I believe. The key is then finding the firmware, which is platform agnostic.
    BTW, removing the drive wouldn’t void the warranty on your Mac but messing with the firmware certainly will void the warranty on the drive.
    Our primary concern remains SuperDrive media disc burn quality .. while you do appear to share the same concern as well as speed performance. Mr Haigh's only concern appears to be speed .. and here we may have missed any opportunity .. since the MATSHITA DVD-R UJ-845C
    SuperDrive is a later designation and the speed performance specifications showing on the apple web-site are likely consistent with current performance capabilities of that SuperDrive and later .. including yours ?
    Mr H may have indeed received marketing materials that promised 8x while actually receiving a 4x SuperDrive .. which only performs at 2x unless exceptional media disc(s) .. so he does have a legitimate claim concerning performance. Do we ?
    What has us fully curious is whether he can burn quality media disc(s) with his new SuperDrive ..
    (Update 24/12/2005 07:10pm (+11 GMT)
    Well, it seems that Apple have decided to replace my hardware. I've started the proceedings yesterday and will hopefully get some news in the new year as to what they are going to replace. At the moment, I'm looking to send in the 12" Powerbook for a replacement, then see what changes in the mac mini side of things. I'm not going to accept the same DVD drive - as we all know the problems with the UJ-835. Stay tuned for more details as they come to hand.) .. http://superdrive.crc.id.au/
    .. which would likely be the same as yours .. now that should prove an interesting outcome .. which he seems likely to voluntarily report and will be the essence of any enquiries from us in the near foreseeable future assuming Mr Haigh is forthcoming in his SuperDrive computing developments.
    Mr Haigh may have begun to scratch the surface (so to speak) .. and find the more serious problem is that no matter how fast or slow the SuperDrive .. reliable media disc burns are a fantasy !
    As yet no update .. almost three months .. could the delay by Apple could have something to do with the model identification of any replacement DVD burner .. if they use an UJ-845 .. then all **** could break loose as Apple users realise (such as we) they do have the same DVD burner and (in a Mac mini) are limited to 4x maximum speed DVD media disc burning performance .. so another designation may be required .. one that already delivers 8x DVD burns .. bit of a mess really .. and the latest Mac mini SuperDrive sports 8x DVD R media burn speed.
    We are curious about you too, dear reader .. are you satisfied with your non Apple disc media burn quality ? We are able to openly admit that we are dissatisfied with our non Apple disc media burn output quality.
    We are currently satisfied with the Apple DV R disc media burn quality. However at a price of premium dollars and an unexplained media burn verification failure message.
    Burn speed, we nonchalantly confess, is not our greatest concern, and, for now, falls to a lower priority of importance with us.
    For now the matter is at rest with us.
    How about you ?
    Yours Sincerely
    Stuart
    PS. .. helping to explain the confusions surrounding the Mac mini SuperDrive is this extracted from ..
    http://en.wikipedia.org/wiki/Mac_mini
    October 2005–February 2006
    Multiple reports exist that the Mac mini was quietly upgraded in October 2005 to 64 MiB VRAM, and either a 1.33 GHz (up from 1.25 GHz) or 1.5 GHz G4 (up from 1.42 GHz) processor, with 512 MiB of PC3200 RAM while underclocking it to PC2700. The 80 GB drive is currently a Seagate Momentus 5400.2 ST9808211A, which runs at 5400 RPM with an 8 MiB cache. The SuperDrive is a MATSHITA DVD-R UJ-845, which supports +R DL burning, and may also have unofficial support for DVD-RAM. Apple did not revise the official specifications on their web site. This may be to avoid issues with discounting or discontinuing of old stock.
    Well .. whatever .. we use a MATSHITA DVD-R UJ-845C SuperDrive .. wouldn't that mean we have +R DL feature too ? .. probably not judging by the following explanations .. sort of .. and yes you could grab the mac_min.pdf service manual and do your own upgrading and overclocking as it pleases you .. try google for more info.
    PPS. .. http://www.macintouch.com/macmini11.html
    Mac Mini Part 11
    January 9, 2006
    Stealth Upgrade
    Xxxxxx Xxxxxxxx
    I recently received the SuperDrive Mac Mini that I ordered from Amazon the day after Christmas. To my delight, my Mini contains a 1.5 GHz PPC and 64MB of video RAM.
    The SuperDrive is listed as a Panasonic UJ-845. According to Panasonic's web site this drive is supposed to allow DVD-RAM writing (and I assume reading). Has anyone attempted to use DVD-RAM discs with this drive under 10.4.3?
    Xxxxxx Xxxx
    I also have a new SuperDrive mini with the same specs, and note that the UJ-845 drive doesn't include DVD-RAM capability, though as Gordon notes the OEM Panasonic drive does. However, Panasonic's spec page is for the UJ-845-B drive, and I expect that the one in the mini is instead a special version of the UJ-845 that Panasonic made for Apple with DVD-RAM disabled. For some reason Apple doesn't seem to want to support DVD-RAM, which is a pity. I believe the drive will work with DVD-RAM discs, but treat them like DVD-RW, requiring complete erasure every time they're used, rather than allowing addition and subtraction of individual files, which is what makes DVD-RAM a great backup/exchange medium, especially for travelers.
    My new PowerBook came with an Apple-labeled Panasonic UJ-825-C drive, which System Profiler saw as simply "UJ-825" and which didn't include DVD-RAM although Panasonic's specs showed it; I replaced it with an 825-B I got on eBay, which System Profiler sees as "845-S" and which now does DVD-RAM even without Patchburn. Note that the 825 is two generations earlier than the current 845/846 drive (whose new feature is DL burning); DVD-RAM has been available for a long time, but Apple has been using special versions of the drives without it.
    How to exactly determine the capabilities of your drive: Insert a disc (any type, CD or DVD, but not a blank recordable disc that has to be formatted), open Disk Utility, and on the left side select the drive (not the disc in the drive), then look in the lower right side of the window where it says "Capabilities". You may have to widen the window to see the whole list, as it doesn't wrap for some reason. If it says "DVD-RAM" in the list, the drive should do DVD-RAM discs as they are meant to be used: like a 4GB floppy disk, they must be formatted once, then can be used as "random access media" (RAM). Doesn't matter what kind of disc you put in the drive; any type will make the drive appear in Disk Utility, which will then show its capabilities.
    FOLLOWUP: I opened up the Mac Mini, and found the SuperDrive is an Apple label "UJ-845C", presumably a special version of the 845 with DVD-RAM disabled, unlike the UJ-845-B spec'd at the Panasonic site.
    [MacInTouch]
    We just received a middle-model Mac Mini - 80GB/512MB/AirPort+Bluetooth/Tiger - ordered from Amazon (currently $519.99 after rebate) and were pleased to find that it is one of Apple's "stealth" upgrades, where the label belies the actual specifications. Apple shows it as a 1.42GHz model, but it's actually running at 1.5 GHz, according to System Profiler.
    It has a Seagate ST9808211A hard drive, which is a 5400-RPM model (better than the dog-slow 4200-RPM drives Apple started shipping sometime after the original Mini models debuted).
    The optical drive is a Matsushita CW-8124, a Combo drive with 24X CD writing and reading and the ability to read DVD-R and DVD-RW, as well as DVD-ROM, at 8x.
    System Profiler shows 64 MB of video RAM - double Apple's specified amount - for the "ATY,RV280" graphics card (ATI Radeon 9200) on an AGP bus, supporting display rotation and Quartz Extreme but not Core Image.
    (For what it's worth, we found that we could not connect a Dell 1704FPT to the digital video port while an analog video cable was connected; after removing the analog cable, the Dell works beautifully with the Mini's DVI video. The Dell display also worked fine with analog video via the adapter included with the Mini.)
    We also tried a WiebeTech Maxelerate hard drive enclosure but found it unpleasantly noisy, even in a special reduced-RPM version the company offers customers who raise the issue. By contrast, the miniStack we previously reviewed is virtually silent with the same hard drive inside.
    Xxx Xxxxxxx
    While this isn't the first time I've seen this type of 'error' from Apple, or other firms, this particular incident seems to have gone beyond the typical example, and I'm beginning to wonder if it is more than just an overlap in an otherwise complicated process.
    I've done my share of OEM documentation, including manuals, labels and cartons. I know how hard it is to maintain reality in this regard. But in this case, it seems to me that the mismatch between the inside and the outside of the package has gone beyond the norm, and I'm wondering if someone along the line has simply decided to live with it, rather than deal with it up front. I can see this saving money...changes cost more than just the ink - it takes time and planning to overcome a spec change and cover all the bases.
    I wouldn't be surprised if someone in a position to decide hasn't simply elected to run out the materials without implementing changes. After all, the customer gets more than they expect, which can be favorable publicity, and we all know the saying "any publicity is good, and good publicity is even better".
    On the other hand, it can be a minefield to fess up. Once word gets out, customers start hand-picking the good from the better, taking the higraded units and leaving the rest as floatsom. Or they buy the downgrade for less, then return it shortly thereafter, demanding the up while refusing to pay more.
    Let's just hope the sun keeps shining on this particular parade, and no one decides to claim fraud. All it would take is one competitor with a surplus of over-eager attorneys, and Apple would be forced to apologize for over-stuffing the golden goose.

    Concluding post in relation to the earlier postings on this particular subject and thread (now officially closed by apple support) .. and to be found at SuperDrive Media Disc(s) .. Assist ... [http://discussions.apple.com/message.jspa?messageID=759874#759874]
    APPLE DVD R DISC MEDIA TRIAL
    DVD-R
    8x speed
    Certified for use with Apple DVD-R drives :: 4.7GB Media
    Made in Japan
    MAC MINI MATSHITA DVD-R UJ-845C
    Mac mini 1.42GHz PowerPC G4 | 512 MB DDR SDRAM
    Tiger OS X 10.4.3
    Finder Burn - single folder containing many sub-folders totaling about 800Mbytes and approx. 4000 files.
    Burn Speed Options : 4x(faster) : 2x : 1x(more reliable) - actual Finder media disc burn dialogue descriptions
    [default selection is 4x(faster) ]
    We choose 1x(more reliable) ..
    Observations include .. no 8x speed media disc burn available from our little Mac mini Matshita DVD-R UJ-845C burner .. and .. as this is a DVD R .. we have time .. but no going back once burned .. and we want maximum systems compatibility .. you, dear reader, already know the drama we have previously experienced with Finder burns and older Apple iMac DV SE machine DVD drive (media disc burned) read compatibilities.
    The total burn was a lengthy delay before the entire routine was completed including automatic verification.
    OUTCOME
    This disc did not verify correctly and is unreliable. Because this disc is unreliable, discard it and try again using a new, blank disc. (Error code ) 0x80020063
    Total disc burned is almost 800Mbytes and about 4000 files.
    Verification was not an available option for the burn .. a Finder burn .. meaning verification was apparently automatically included as an unseen 'yes' option at media disc burn execution time.
    Examining the resulting Apple DVD R media disc burned .. we discover that things are good .. biggest single files (.dmg's at about 100Mbytes expanding to 350Mbytes - e.g. OS X 10.4.3 update) are able to be copied from the burned Apple DVD R media disc back to the Mac mini hard disk again and verify 100% when opened for installation. Encouraging. Better than anything previously experienced.
    iMac DV SE [ DVD MATSHITADVD-ROM SR-8184 ]
    Into the Apple iMac ancient (500 MHz PowerPC G3 operating OS X 10.4.3 Tiger | 640MB SDRAM) and we are greeted with goodness .. same accessibility as the originating Mac mini machine .. satisfying.
    And yes the 'problem' of multi-session burns is yet to come on the ancient iMac and if the response is any good as now .. it may not be a problem worthy of mention. At 800 Mbytes burn and 4.7 Gbytes capacity .. one could loosely forecast up to another 5 media disc burn sessions before the DVD R is full and complete.
    XP MACHINE
    And now into the PC machine for an XP looksee and again .. more goodness. Cross compatible files are fully accessible (an entire - own - website burned). Large files copy 100%. Better than before.
    Two thumbs up for this disk and burn.
    Verification failure remains a current mystery. Anyone ?
    It is easy to figure how one may doubt one's media burning hardware is any good by now .. but the gathering volume of supporting entries at the relevant media burning and error message forums reveals that hardware is unlikely to be (entirely) at fault .. rather something else .. say firmware ?
    Apple Media DVD R discs are manufactured in Japan (stated on the disc) and the quality difference and price premium are consistent with what others have written of the place of manufacture and the Apple media disc as well. Mostly positive.
    Still .. we should like to have access to dependable RW discs from Apple too .. for reliable re-useability.
    As for the subject of burn speed ...
    Many forum readers are well aware of an ongoing and gradually escalating matter between Apple and this gentleman http://www.crc.id.au/page/2/ .. we have curiously followed the unfolding events to observe the outcome of the burn speed specification variation. As you know .. our Mac mini is rated at maximum DVD media disc burn 4x and fitted with a MATSHITA DVD-R UJ-845C which is a later edition than Mr H's UJ-835 .. however .. we are more curious to observe whether the final outcome will satisfy Mr H or not. Burn speed, primarily, and quality of burn, secondarily, on selected media by Mr H. Once the outcome is known and to Mr H's satisfaction .. then we may enquire about his satisfaction with burn quality at the chosen burn speed(s) by Mr H.
    Here is an offline forum communication that we shared with another Mac mini user about disc media burn speed. As you may read .. he is entirely dissatisfied with the Mac mini media burn speed and isn't too keen on using the Apple disc burn media either ...
    So...Have you found any dvd-r or +r media that burns reliably on the mini? (non apple media please).
    I am completely disgusted with my new mini's pathetic superdrive that I paid way too much for.
    I have purchased new & built from new parts several PC's that burn DVD after DVD on a wide variety of media reliably.
    No one has even replied to my post
    http://www.123macmini.com/forums/viewtopic.php?t=2773&start=0&postdays=0&postord er=asc&highlight=
    Thanks
    .. and at latest check .. no-one has responded to the post .. maybe no-one knows .. outside of Apple HQ .. mind you .. no-one has truly usefully responded to our post either .. we responded thusly ...
    Mac Mini SuperDrive .. burn speed .. and burn .. reliability
    Sometime I just can't get my head around the subject and have to step back and breathe in real deep .. which makes me kinda dizzy .. and wait until the focus is on the forest before
    choosing the tree(s) to climb. This particular tree is getting taller ...
    And congratulations on your Apple ownership. Small is beautiful.
    Regret your coaster experiences. Frustrating and unfortunate.
    What SuperDrive description is fitted in your new mac mini ?
    We seem to be staring into a gaping black hole of acknowledgement .. from anyone.
    PC users, windows operating system software computers, appear to have an extreme edge .. when it comes to media disc burning. i.e. successful burns.
    Re-reading that lengthy post .. which doesn't fully format as intended .. has me fully believing that less is more and small is beautiful (still). Future specific posts will probably follow as a matter of personal self-committment .. to persist until the solutions are fully to hand. For now .. may we refer to your mentioned post in our next planned post please ? Solidarity of negatory outcome experience is credibility.
    Three forums have we frequented and participated to learn more about the black hole .. we know as SuperDrive media disc burning .. only you have provided any feedback whatsoever .. post reader numbers grow but answers are missing in action .. absent from class.
    http://www.crc.id.au/page/2/
    We have thought the SuperDrive matter you have referred to in your post was of no concern to us .. but now you have us thinking again .. although model numbers differ .. (ours is a later numerical reference) the concerns appear to be similar .. or largely about performance .. we shall also refer to this domain in our planned next post. Yes, we are aware of the matter .. from another forum .. but shall now supply the link for others to weigh and hopefully dish out their two cents worth .. where a consensus could mean we are also a part of this particular action. An ideal consensus would be firmware is unsuitable .. requires immediate update .. and in particular the quality of burn is consensually unacceptable .. action could follow.
    We have progressed no further with burning experimentations .. and will be using Apple media before progressing with our findings reporting. For now, we are unable to add to your ease of mind .. frankly .. unless the burning media is made in Japan .. we doubt any burn verification success is to be had. And we cannot find any burning media made in Japan in our locale. Where is the Apple media made?
    We have come to appreciate the SuperDrive is all about the firmware .. but have no new firmware to apply .. in fact .. our research to date shows that we have been unable to find the Matshita SuperDrive at all online and cannot confirm specifications .. neither could we locate the specifications at www.apple.com.au .. which is just plain odd.
    A third look has provided ... from www.apple.com/macmini/specs.html ..
    Storage
    * One of the following optical drives:
    o Slot-loading Combo drive (DVD-ROM/CD-RW): reads DVDs at up to 8x speed, writes CD-R discs at up to 24x speed, writes CD-RW discs at up to 16x speed, reads CDs at up to 24x speed
    o Optional SuperDrive (DVD±RW/CD-RW): writes DVD-R discs at up to 4x speed, writes DVD-RW discs at up to 2x speed, writes DVD+R discs at up to 4x speed, writes DVD+RW discs at up to 2.4x speed, reads DVDs at up to 8x speed, writes CD-R discs at up to 16x speed, writes CD-RW discs at up to 8x speed, reads CDs at up to 24x speed
    Where were you able to establish your SuperDrive (burning) specifications ?
    Writer's note : .. some things change .. and so have the Apple Mac mini SuperDrive burner specs changed .. since recording those detailed above. In fact .. they read like they maybe should have all along .. 8x DVD R media burn speed. DL is a bonus. Can anyone tell us what the drive designation is please ?
    CRC says: ".. This limits burn speed to 4x for Mac Minis and 8x for Powerbooks.".
    While speed matters .. and it does .. you appear to have exactly the same media disc burning problems that we are experiencing .. failed verification(s) .. and for us .. in short .. complete DVD-R media disc burned rejection from the Apple OS X.
    Do we .. in actual fact .. have two separate operating challenges here .. speed of burn and quality of burn .. any burn ? Speed was not our first priority .. quality is .. now we figure that at any speed the burn quality is anywhere from dubious to coaster.
    CRC says: ".. The UJ-835 that Apple use is firmware limited to suit various bits of hardware that they want to put together. The burner in the Mac Mini is the exact same model as the one in the PowerBooks. Apple load a 4x firmware on the Mac Mini, and an 8x firmware on the PowerBook drives.
    My bet is that this is for marketting reasons only. ".
    One of the contributors to http://www.crc.id.au/?p=21 . . says . .
    # Moneky Boy Says:
    August 14th, 2005 at 1:03 am
    My parents have a mini and my has one of the PowerBooks. Confirmed the drives are Matsushita UJ-835. They have never had an issue burning DVDs. Confirmed it by burning DVDs last night on the wife’s 12″ PowerBook.
    As far as updating the Firmware in your optical drives, no, you do not have to remove them from the machines to update their firmware. I’ve updated the firmware on my optical drives (for Region Free and/or speed gains) via the GUI in Mac OS X. One application that will do this is called DVRFlashX I believe. The key is then finding the firmware, which is platform agnostic.
    BTW, removing the drive wouldn’t void the warranty on your Mac but messing with the firmware certainly will void the warranty on the drive.
    Our primary concern remains SuperDrive media disc burn quality .. while you do appear to share the same concern as well as speed performance. Mr Haigh's only concern appears to be speed .. and here we may have missed any opportunity .. since the MATSHITA DVD-R UJ-845C
    SuperDrive is a later designation and the speed performance specifications showing on the apple web-site are likely consistent with current performance capabilities of that SuperDrive and later .. including yours ?
    Mr H may have indeed received marketing materials that promised 8x while actually receiving a 4x SuperDrive .. which only performs at 2x unless exceptional media disc(s) .. so he does have a legitimate claim concerning performance. Do we ?
    What has us fully curious is whether he can burn quality media disc(s) with his new SuperDrive ..
    (Update 24/12/2005 07:10pm (+11 GMT)
    Well, it seems that Apple have decided to replace my hardware. I've started the proceedings yesterday and will hopefully get some news in the new year as to what they are going to replace. At the moment, I'm looking to send in the 12" Powerbook for a replacement, then see what changes in the mac mini side of things. I'm not going to accept the same DVD drive - as we all know the problems with the UJ-835. Stay tuned for more details as they come to hand.) .. http://superdrive.crc.id.au/
    .. which would likely be the same as yours .. now that should prove an interesting outcome .. which he seems likely to voluntarily report and will be the essence of any enquiries from us in the near foreseeable future assuming Mr Haigh is forthcoming in his SuperDrive computing developments.
    Mr Haigh may have begun to scratch the surface (so to speak) .. and find the more serious problem is that no matter how fast or slow the SuperDrive .. reliable media disc burns are a fantasy !
    As yet no update .. almost three months .. could the delay by Apple could have something to do with the model identification of any replacement DVD burner .. if they use an UJ-845 .. then all **** could break loose as Apple users realise (such as we) they do have the same DVD burner and (in a Mac mini) are limited to 4x maximum speed DVD media disc burning performance .. so another designation may be required .. one that already delivers 8x DVD burns .. bit of a mess really .. and the latest Mac mini SuperDrive sports 8x DVD R media burn speed.
    We are curious about you too, dear reader .. are you satisfied with your non Apple disc media burn quality ? We are able to openly admit that we are dissatisfied with our non Apple disc media burn output quality.
    We are currently satisfied with the Apple DV R disc media burn quality. However at a price of premium dollars and an unexplained media burn verification failure message.
    Burn speed, we nonchalantly confess, is not our greatest concern, and, for now, falls to a lower priority of importance with us.
    For now the matter is at rest with us.
    How about you ?
    Yours Sincerely
    Stuart
    PS. .. helping to explain the confusions surrounding the Mac mini SuperDrive is this extracted from ..
    http://en.wikipedia.org/wiki/Mac_mini
    October 2005–February 2006
    Multiple reports exist that the Mac mini was quietly upgraded in October 2005 to 64 MiB VRAM, and either a 1.33 GHz (up from 1.25 GHz) or 1.5 GHz G4 (up from 1.42 GHz) processor, with 512 MiB of PC3200 RAM while underclocking it to PC2700. The 80 GB drive is currently a Seagate Momentus 5400.2 ST9808211A, which runs at 5400 RPM with an 8 MiB cache. The SuperDrive is a MATSHITA DVD-R UJ-845, which supports +R DL burning, and may also have unofficial support for DVD-RAM. Apple did not revise the official specifications on their web site. This may be to avoid issues with discounting or discontinuing of old stock.
    Well .. whatever .. we use a MATSHITA DVD-R UJ-845C SuperDrive .. wouldn't that mean we have +R DL feature too ? .. probably not judging by the following explanations .. sort of .. and yes you could grab the mac_min.pdf service manual and do your own upgrading and overclocking as it pleases you .. try google for more info.
    PPS. .. http://www.macintouch.com/macmini11.html
    Mac Mini Part 11
    January 9, 2006
    Stealth Upgrade
    Xxxxxx Xxxxxxxx
    I recently received the SuperDrive Mac Mini that I ordered from Amazon the day after Christmas. To my delight, my Mini contains a 1.5 GHz PPC and 64MB of video RAM.
    The SuperDrive is listed as a Panasonic UJ-845. According to Panasonic's web site this drive is supposed to allow DVD-RAM writing (and I assume reading). Has anyone attempted to use DVD-RAM discs with this drive under 10.4.3?
    Xxxxxx Xxxx
    I also have a new SuperDrive mini with the same specs, and note that the UJ-845 drive doesn't include DVD-RAM capability, though as Gordon notes the OEM Panasonic drive does. However, Panasonic's spec page is for the UJ-845-B drive, and I expect that the one in the mini is instead a special version of the UJ-845 that Panasonic made for Apple with DVD-RAM disabled. For some reason Apple doesn't seem to want to support DVD-RAM, which is a pity. I believe the drive will work with DVD-RAM discs, but treat them like DVD-RW, requiring complete erasure every time they're used, rather than allowing addition and subtraction of individual files, which is what makes DVD-RAM a great backup/exchange medium, especially for travelers.
    My new PowerBook came with an Apple-labeled Panasonic UJ-825-C drive, which System Profiler saw as simply "UJ-825" and which didn't include DVD-RAM although Panasonic's specs showed it; I replaced it with an 825-B I got on eBay, which System Profiler sees as "845-S" and which now does DVD-RAM even without Patchburn. Note that the 825 is two generations earlier than the current 845/846 drive (whose new feature is DL burning); DVD-RAM has been available for a long time, but Apple has been using special versions of the drives without it.
    How to exactly determine the capabilities of your drive: Insert a disc (any type, CD or DVD, but not a blank recordable disc that has to be formatted), open Disk Utility, and on the left side select the drive (not the disc in the drive), then look in the lower right side of the window where it says "Capabilities". You may have to widen the window to see the whole list, as it doesn't wrap for some reason. If it says "DVD-RAM" in the list, the drive should do DVD-RAM discs as they are meant to be used: like a 4GB floppy disk, they must be formatted once, then can be used as "random access media" (RAM). Doesn't matter what kind of disc you put in the drive; any type will make the drive appear in Disk Utility, which will then show its capabilities.
    FOLLOWUP: I opened up the Mac Mini, and found the SuperDrive is an Apple label "UJ-845C", presumably a special version of the 845 with DVD-RAM disabled, unlike the UJ-845-B spec'd at the Panasonic site.
    [MacInTouch]
    We just received a middle-model Mac Mini - 80GB/512MB/AirPort+Bluetooth/Tiger - ordered from Amazon (currently $519.99 after rebate) and were pleased to find that it is one of Apple's "stealth" upgrades, where the label belies the actual specifications. Apple shows it as a 1.42GHz model, but it's actually running at 1.5 GHz, according to System Profiler.
    It has a Seagate ST9808211A hard drive, which is a 5400-RPM model (better than the dog-slow 4200-RPM drives Apple started shipping sometime after the original Mini models debuted).
    The optical drive is a Matsushita CW-8124, a Combo drive with 24X CD writing and reading and the ability to read DVD-R and DVD-RW, as well as DVD-ROM, at 8x.
    System Profiler shows 64 MB of video RAM - double Apple's specified amount - for the "ATY,RV280" graphics card (ATI Radeon 9200) on an AGP bus, supporting display rotation and Quartz Extreme but not Core Image.
    (For what it's worth, we found that we could not connect a Dell 1704FPT to the digital video port while an analog video cable was connected; after removing the analog cable, the Dell works beautifully with the Mini's DVI video. The Dell display also worked fine with analog video via the adapter included with the Mini.)
    We also tried a WiebeTech Maxelerate hard drive enclosure but found it unpleasantly noisy, even in a special reduced-RPM version the company offers customers who raise the issue. By contrast, the miniStack we previously reviewed is virtually silent with the same hard drive inside.
    Xxx Xxxxxxx
    While this isn't the first time I've seen this type of 'error' from Apple, or other firms, this particular incident seems to have gone beyond the typical example, and I'm beginning to wonder if it is more than just an overlap in an otherwise complicated process.
    I've done my share of OEM documentation, including manuals, labels and cartons. I know how hard it is to maintain reality in this regard. But in this case, it seems to me that the mismatch between the inside and the outside of the package has gone beyond the norm, and I'm wondering if someone along the line has simply decided to live with it, rather than deal with it up front. I can see this saving money...changes cost more than just the ink - it takes time and planning to overcome a spec change and cover all the bases.
    I wouldn't be surprised if someone in a position to decide hasn't simply elected to run out the materials without implementing changes. After all, the customer gets more than they expect, which can be favorable publicity, and we all know the saying "any publicity is good, and good publicity is even better".
    On the other hand, it can be a minefield to fess up. Once word gets out, customers start hand-picking the good from the better, taking the higraded units and leaving the rest as floatsom. Or they buy the downgrade for less, then return it shortly thereafter, demanding the up while refusing to pay more.
    Let's just hope the sun keeps shining on this particular parade, and no one decides to claim fraud. All it would take is one competitor with a surplus of over-eager attorneys, and Apple would be forced to apologize for over-stuffing the golden goose.

  • How can i find out total no of sunday in the year

    Hi Experts,
    how can i find out total no of sunday's in the particular year. please can any one help how can i do that
    Regards,
    Arun

    Just for fun (and in case this wasn't done to death in the other thread), the rule posted here states:
    Most years have 365 days, but a leap year has 366 days. That adds up to 52 weeks (where each week is exactly 7 days) PLUS 1 or 2 additional days. The year 2012 has exactly 366 days.Now if the year starts on a Sunday in a non-leap year, you end up with 53 Sundays. Or if either of the first two days lands on a Sunday during a leap year, then you can also get 53 Sundays.>
    which allows a calculation like this:
    with test_data as
         ( select rownum + 1999 as test_year from dual
           connect by rownum <= 15 )
    select test_year
         , case
              when first_day = 'SUN'
              or ( first_day = 'SAT' and leap_year = 'Y' )
                 then 53
              else 52
           end as sundays
    from   ( select test_year
                  , to_char(to_date(d.test_year||'-01-01','YYYY-MM-DD'),'DY', 'NLS_DATE_LANGUAGE=ENGLISH') first_day
                  , case extract(day from last_day(to_date(d.test_year||'-02','YYYY-MM'))) when 29 then 'Y' else 'N' end as leap_year
             from   test_data d );
    TEST_YEAR    SUNDAYS
          2000         53
          2001         52
          2002         52
          2003         52
          2004         52
          2005         52
          2006         53
          2007         52
          2008         52
          2009         52
          2010         52
          2011         52
          2012         53
          2013         52
          2014         52
    15 rows selected.

  • How can I restrict the total no. of recs. per physical page

    Hi !
    I have created a report and I am saving that in a text file. The
    problem is that when I try to take the output on the printer
    then the total no of records overflows to the next pages and the
    next page heading comes much below to it's designated place.
    Max.no of records property in the repaeting frame is for the
    logical page.
    How can I restrict the max. number of records per physical page ?
    Any pointer will be welcome,
    Thanks in advance,
    Shobhit
    null

    Just for fun (and in case this wasn't done to death in the other thread), the rule posted here states:
    Most years have 365 days, but a leap year has 366 days. That adds up to 52 weeks (where each week is exactly 7 days) PLUS 1 or 2 additional days. The year 2012 has exactly 366 days.Now if the year starts on a Sunday in a non-leap year, you end up with 53 Sundays. Or if either of the first two days lands on a Sunday during a leap year, then you can also get 53 Sundays.>
    which allows a calculation like this:
    with test_data as
         ( select rownum + 1999 as test_year from dual
           connect by rownum <= 15 )
    select test_year
         , case
              when first_day = 'SUN'
              or ( first_day = 'SAT' and leap_year = 'Y' )
                 then 53
              else 52
           end as sundays
    from   ( select test_year
                  , to_char(to_date(d.test_year||'-01-01','YYYY-MM-DD'),'DY', 'NLS_DATE_LANGUAGE=ENGLISH') first_day
                  , case extract(day from last_day(to_date(d.test_year||'-02','YYYY-MM'))) when 29 then 'Y' else 'N' end as leap_year
             from   test_data d );
    TEST_YEAR    SUNDAYS
          2000         53
          2001         52
          2002         52
          2003         52
          2004         52
          2005         52
          2006         53
          2007         52
          2008         52
          2009         52
          2010         52
          2011         52
          2012         53
          2013         52
          2014         52
    15 rows selected.

  • Error when running clone for app tier

    Has anyone seen this? I'm getting the same error on each tier (seperate servers). I get a hit on Metalink but it does not match my situation. It states I'm missing a tag in the source context file but it is there. Any assistance would be appreciated.
    $perl adcfgclone.pl appsTier
    Enter the APPS password [APPS]:
    xxxxxxxxxxx
    First Creating a new context file for the cloned system.
    The program is going to ask you for information about the new system:
    RC-50004: Error occurred in CloneContext:
    null
    Check logfile CloneContext_06280945.log for details.
    ERROR: context creation not completed successfully.
    Please check /tmp/iasit13/adcfgclone.err file for errors
    [136] appl13@green- [t13sw/oraappl01/iasicomn/clone/bin]
    $more /tmp/iasit13/adcfgclone.err
    [137] appl13@green- [t13sw/oraappl01/iasicomn/clone/bin]
    $ls -l /tmp/iasit13/adcfgclone.err
    -rw-r--r-- 1 appl13 oradba 0 Jun 28 09:45 /tmp/iasit13/adcfgclone.err
    [138] appl13@green- [t13sw/oraappl01/iasicomn/clone/bin]
    $ls -lrt
    total 318
    -rwxrwxr-x 1 appl13 oradba 27900 May 31 11:54 adclonectx.pl
    -rwxrwxr-x 1 appl13 oradba 83889 May 31 11:54 adclone.pl
    -rwxrwxr-x 1 appl13 oradba 3273 May 31 11:54 adchkutl.sh
    -rwxrwxr-x 1 appl13 oradba 34334 May 31 11:54 adcfgclone.pl
    -rwxrwxr-x 1 appl13 oradba 7396 May 31 11:54 adaddnode.pl
    -rwxrwxr-- 1 appl13 oradba 1149 Jun 27 15:28 CloneContext_06270327.log
    -rw-r--r-- 1 appl13 oradba 1149 Jun 27 16:05 CloneContext_06270405.log
    -rw-r--r-- 1 appl13 oradba 1149 Jun 28 09:45 CloneContext_06280945.log
    [139] appl13@green- [t13sw/oraappl01/iasicomn/clone/bin]
    $more CloneContext_06280945.log
    #------Log File created at: 06280945------------
    # $Header: CloneContext.java 115.167 2005/03/03 16:10:14 dvijayas ship $
    # Running CloneContext on machine - green
    Initializing the Apps Service Context varibale Hash
    DEBUG: Apps Service Status context variable extracted from the given Apps context file
    s_apcstatus
    s_apc_restrict_status
    s_apcstatus_pls
    s_tnsstatus
    s_tcfstatus
    s_concstatus
    s_formsstatus
    s_reptstatus
    s_metcstatus
    s_metsstatus
    s_icsmstatus
    s_jtffsstatus
    s_icxblkstatus
    s_discostatus
    DEBUG: Getting all the AppsContext involved in this Merging
    StackTrace:
    java.lang.NullPointerException
    at oracle.apps.ad.context.CloneContext.getAllAppsContext(CloneContext.java:6649)
    at oracle.apps.ad.context.CloneContext.initServiceStatus(CloneContext.java:6581)
    at oracle.apps.ad.context.CloneContext.doClone(CloneContext.java:489)
    at oracle.apps.ad.context.CloneContext.main(CloneContext.java:5222)
    RC-50004: Error occurred in CloneContext:
    null
    Context file creation not succesful
    TIA

    Hi there !
    In case you haven't sorted out this issue.
    Have you done cloning of the environemnt before?
    Just wonder if you have complitted steps described in
    Note:230672.1
    Subject:      Cloning Oracle Applications Release 11i with Rapid Clone
    Section 2: Clone Oracle Applications 11i
    1. "Prepare the Source System":
    Yury
    Check this out:
    A.
    http://www.freelists.org/archives/ora-apps-dba/05-2006/msg00000.html
    B.
    - Users can subscribe to the list by sending email to
    ora-apps-dba-request_at_freelists.org with 'subscribe' in the Subject field
    C.
    http://www.freelists.org/archives/ora-apps-dba/05-2006/threads.html
    http://www.freelists.org/archives/ora-apps-dba/06-2006/threads.html

  • Rebuilt IPhoto Library does not display.

    Recently my iPhoto has been crashing, probably because I unknowingly moved a file or files in the iPhoto Library with the Finder.
    Heeding the advice posted throughout this forum I trashed the existing iPhoto Preferences file, the three thumb files, and rebuilt my iPhoto Library. (I don't recall in what order.)
    I renamed my two respective iPhoto Libraries so now iPhoto automatically finds the new one.
    In the Finder, the new iPhoto Library is nearly identical to the old one; it contains over 21 GB of photos, all arranged in their respective folders organized by year, month, and day created.
    When I open iPhoto, however, neither the thumbnails nor the file names of the photos display.
    In the "Source" pane, icons for "Early Photos," "2003," "2004," "2005," and "2006" appear under "Photo Library" but selecting them does nothing.
    Nothing ever appears in the main "Organize" pane at all--it is completely blank. Below it "No photos" appears.
    iPhoto will still display the pictures in the old Library, but it crashes almost immediately after I do anything.
    Obviously there is some disconnect between iPhoto and the Rebuilt Library. Can anyone offer some insight?
    Thanks.
    Mike
    Imac G5   Mac OS X (10.3.9)  

    After considerable culling of unnecessary and redundant files I was finally able to free up enough disk space to conduct a second iPhoto library rebuild without having to delete the first rebuilt library.
    Unfortunately I've run into problems once again.
    Since the rebuild took 2 1/2 hours I wasn't watching the computer the whole time; when I returned iPhoto had crashed but the second rebuilt library seemed complete. My original library is 21.9 GB; my first rebuilt library is 21.28 GB and contains most of the photos of the original--my second rebuilt library is also 21.28 GB.
    After the second rebuild I now have 3.98 GB free space on my hard drive (and 2GB RAM).
    iPhoto will open the first rebuilt library, although as I described previously, it won't actually display any photos, rolls, or albums. In contrast, iPhoto will not open with the second rebuilt library at all.
    When I attempt to open iPhoto and select the second rebuilt library the file selection window opens and all my iPhoto libraries appear in it. None of them are grayed out (as are non-selectable files) but nevertheless I cannot select the second iPhoto library or even highlight it. It does not provide any message--it simply does not respond.
    Unlike the first rebuilt library, the second rebuilt library never contained a Dir.data file, an iPhoto.db file, a Library.iPhoto file, or an AlbumData.xml file. It did contain the three thumb data files, but after opening it failed initially I tried deleting these files thinking they might be problematic. That apparently had no effect. Right now the second rebuilt library only contains my photos organized in year, month, and day folders.
    Previously Brie Fly stated that iPhoto automatically opens the newly rebuilt iPhoto library after a rebuild, however, the first time I opened iPhoto after the second rebuild attempt and subsequent crash it automatically opened the original iPhoto library.
    I copied the error report from the iPhoto crash that occurred after my second library rebuild attempt. Please see below. Does it shed any light on the situation?
    Also, to answer your question Brie Fly, I am able to close all the open rolls in my original library before iPhoto crashes. I did that and after a short while it crashed anyway without any other action on my part. I also tried quitting iPhoto after closing the rolls, but every time I do, regardless of whether there are open rolls or not, it does not quit but crashes. It seems impossible to quit iPhoto while using the original library without crashing. Furthermore, every time I open iPhoto after a crash the rolls I previously closed are once again open, and iPhoto informs me it has recovered 17 photos and put them in a folder named "recovered photos." Since this occurs every time I try to quit while using the original library I now have 88 identical folders of 17 recovered photos. I deleted many of these before but iPhoto just keeps making new ones.
    Here is the report I received after iPhoto had crashed during/after the second library rebuild attempt:
    Date/Time: 2006-09-12 10:19:35 -0400
    OS Version: 10.3.9 (Build 7W98)
    Report Version: 2
    Command: iPhoto
    Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
    Version: 4.0.3 (4H2)
    PID: 2631
    Thread: 0
    Exception: EXCBADACCESS (0x0001)
    Codes: KERNINVALIDADDRESS (0x0001) at 0xbbffde60
    Thread 0 Crashed:
    0 com.apple.Foundation 0x90a395f0 -[NSPathStore2 stringByAppendingPathComponent:] + 0xfc
    1 com.apple.iPhoto 0x00080c48 0x1000 + 0x7fc48
    2 com.apple.iPhoto 0x000ad26c 0x1000 + 0xac26c
    3 com.apple.iPhoto 0x000ad4b0 0x1000 + 0xac4b0
    4 com.apple.iPhoto 0x0007f758 0x1000 + 0x7e758
    5 com.apple.iPhoto 0x0007f858 0x1000 + 0x7e858
    6 com.apple.iPhoto 0x00080394 0x1000 + 0x7f394
    7 com.apple.iPhoto 0x0007bc54 0x1000 + 0x7ac54
    8 com.apple.iPhoto 0x0005c2b8 0x1000 + 0x5b2b8
    9 com.apple.iPhoto 0x0005e24c 0x1000 + 0x5d24c
    10 com.apple.iPhoto 0x00044938 0x1000 + 0x43938
    11 com.apple.Foundation 0x90a27a94 nsnotecallback + 0xb0
    12 com.apple.CoreFoundation 0x901db118 __CFXNotificationPost + 0x1b4
    13 com.apple.CoreFoundation 0x901dfb7c _CFXNotificationPostNotification + 0x340
    14 com.apple.Foundation 0x90a258e0 -[NSNotificationCenter postNotificationName:object:userInfo:] + 0x74
    15 com.apple.AppKit 0x97e95328 -[NSApplication _postDidFinishNotification] + 0x70
    16 com.apple.AppKit 0x97e95214 -[NSApplication _sendFinishLaunchingNotification] + 0x5c
    17 com.apple.AppKit 0x97e95444 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 0x78
    18 com.apple.Foundation 0x90a7af18 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 0x164
    19 com.apple.Foundation 0x90a817b0 _NSAppleEventManagerGenericHandler + 0x78
    20 com.apple.AE 0x90706a10 Z20aeDispatchAppleEventPK6AEDescPSmPh + 0xd0
    21 com.apple.AE 0x90709858 Z25dispatchEventAndSendReplyPK6AEDescPS + 0x2c
    22 com.apple.AE 0x90706c50 aeProcessAppleEvent + 0x11c
    23 com.apple.HIToolbox 0x91b70224 AEProcessAppleEvent + 0x3c
    24 com.apple.AppKit 0x97d84420 _DPSNextEvent + 0x358
    25 com.apple.AppKit 0x97d9acc8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 0x74
    26 com.apple.AppKit 0x97daf048 -[NSApplication run] + 0x21c
    27 com.apple.AppKit 0x97e6b764 NSApplicationMain + 0x1d0
    28 com.apple.iPhoto 0x0011da3c 0x1000 + 0x11ca3c
    29 com.apple.iPhoto 0x000046d4 0x1000 + 0x36d4
    30 com.apple.iPhoto 0x00004554 0x1000 + 0x3554
    Thread 1:
    0 libSystem.B.dylib 0x900127f8 syscallthreadswitch + 0x8
    1 com.apple.Foundation 0x90a332d8 +[NSThread sleepUntilDate:] + 0x98
    2 com.apple.AppKit 0x97d7c3ec -[NSUIHeartBeat _heartBeatThread:] + 0x494
    3 com.apple.Foundation 0x90a6a4b8 forkThreadForFunction + 0x6c
    4 libSystem.B.dylib 0x90024990 pthreadbody + 0x28
    Thread 2:
    0 libSystem.B.dylib 0x90018e78 semaphoretimedwait_signaltrap + 0x8
    1 libSystem.B.dylib 0x9000ea14 pthread_condwait + 0x268
    2 ...ple.CoreServices.CarbonCore 0x96310570 TSWaitOnSemaphoreCommon + 0xb0
    3 ...ickTimeComponents.component 0x92a65b34 ReadSchedulerThreadEntryPoint + 0x1458
    4 libSystem.B.dylib 0x90024990 pthreadbody + 0x28
    Thread 3:
    0 libSystem.B.dylib 0x90018e78 semaphoretimedwait_signaltrap + 0x8
    1 libSystem.B.dylib 0x9000ea14 pthread_condwait + 0x268
    2 ...ple.CoreServices.CarbonCore 0x96310570 TSWaitOnSemaphoreCommon + 0xb0
    3 ...ple.CoreServices.CarbonCore 0x963103f4 _Z15AsyncFileThreadPv + 0x38
    4 libSystem.B.dylib 0x90024990 pthreadbody + 0x28
    PPC Thread State:
    srr0: 0x90a395f0 srr1: 0x0200d030 vrsave: 0x00000000
    cr: 0x44002212 xer: 0x20000000 lr: 0x90a395c8 ctr: 0x00000000
    r0: 0xbfffe7c0 r1: 0xbfffdf00 r2: 0xfbffff60 r3: 0x00000000
    r4: 0x5a35d798 r5: 0x00000074 r6: 0x00000010 r7: 0x00000020
    r8: 0x00000030 r9: 0x00000080 r10: 0x00000000 r11: 0x00000100
    r12: 0x6653d018 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0xbffff640 r18: 0x00000000 r19: 0x001be45c
    r20: 0x9089a014 r21: 0x00000001 r22: 0xbfffdf00 r23: 0x5a35d790
    r24: 0x0000003a r25: 0x27947750 r26: 0x6253d000 r27: 0x0200000c
    r28: 0x001bd86c r29: 0x02000046 r30: 0xbfffdf00 r31: 0x90a394f4
    Binary Images Description:
    0x1000 - 0x19efff com.apple.iPhoto 4.0.3 (4H2) /Applications/iPhoto.app/Contents/MacOS/iPhoto
    0x77d000 - 0x77ffff com.apple.framework.iPhoto.ContactSheetPrintFormatter 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/ContactSheetPrintFormatter.iPhotoPrin tFormatter/Contents/MacOS/ContactSheetPrintFormatter
    0x789000 - 0x78bfff com.apple.framework.iPhoto.CubeTransition 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/CubeTransition.IAPlugin/Contents/MacO S/CubeTransition
    0x794000 - 0x795fff com.apple.framework.iPhoto.DissolveTransition 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/DissolveTransition.IAPlugin/Contents/ MacOS/DissolveTransition
    0x7a2000 - 0x7a6fff com.apple.framework.iPhoto.FileExporter 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/FileExporter.iPhotoExporter/Contents/ MacOS/FileExporter
    0x7b1000 - 0x7b3fff com.apple.framework.iPhoto.FullPagePrintFormatter 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/FullPagePrintFormatter.iPhotoPrintFor matter/Contents/MacOS/FullPagePrintFormatter
    0x7bc000 - 0x7bdfff com.apple.framework.iPhoto.GreetingCardPrintFormatter 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/GreetingCardPrintFormatter.iPhotoPrin tFormatter/Contents/MacOS/GreetingCardPrintFormatter
    0x7cc000 - 0x7d2fff com.apple.framework.iPhoto.HTMLExporter 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/HTMLExporter.iPhotoExporter/Contents/ MacOS/HTMLExporter
    0x7dd000 - 0x7dffff com.apple.framework.iPhoto.MosaicFlipTransition 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/MosaicFlipTransition.IAPlugin/Content s/MacOS/MosaicFlipTransition
    0x7e9000 - 0x7ebfff com.apple.framework.iPhoto.NUpPrintFormatter 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/NUpPrintFormatter.iPhotoPrintFormatte r/Contents/MacOS/NUpPrintFormatter
    0x173d000 - 0x1743fff com.apple.framework.iPhoto.QTExporter 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/QTExporter.iPhotoExporter/Contents/Ma cOS/QTExporter
    0x1748000 - 0x174afff com.apple.framework.iPhoto.SamplerPrintFormatter 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/SamplerPrintFormatter.iPhotoPrintForm atter/Contents/MacOS/SamplerPrintFormatter
    0x1754000 - 0x1756fff com.apple.framework.iPhoto.SizedPrintFormatter 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/SizedPrintFormatter.iPhotoPrintFormat ter/Contents/MacOS/SizedPrintFormatter
    0x1760000 - 0x1762fff com.apple.framework.iPhoto.WipeTransition 4.0.3 /Applications/iPhoto.app/Contents/PlugIns/WipeTransition.IAPlugin/Contents/MacO S/WipeTransition
    0x1779000 - 0x1785fff com.apple.BookService 3.0 (3.0.1) /Applications/iPhoto.app/Contents/NetServices/Bundles/BookService.NetService/Co ntents/MacOS/BookService
    0x17c2000 - 0x17ddfff com.apple.HomePageService 3.0 (3.0.1) /Applications/iPhoto.app/Contents/NetServices/Bundles/HomePageService.NetServic e/Contents/MacOS/HomePageService
    0x17f4000 - 0x17fafff com.apple.NetSlidesService 3.0 (3.0.1) /Applications/iPhoto.app/Contents/NetServices/Bundles/NetSlidesService.NetServi ce/Contents/MacOS/NetSlidesService
    0x5799000 - 0x57a7fff com.apple.PrintsService 3.0 (3.0.1) /Applications/iPhoto.app/Contents/NetServices/Bundles/PrintsService.NetService/ Contents/MacOS/PrintsService
    0x5849000 - 0x58c8fff com.apple.NetServices 3.0.2 /Applications/iPhoto.app/Contents/MacOS/../NetServices/Frameworks/NetServices.f ramework/Versions/A/NetServices
    0x60c9000 - 0x60ccfff libMPAEncode0.1.dylib /Library/Application Support/DivXNetworks/libMPAEncode0.1.dylib
    0x62d0000 - 0x62e2fff libdpv10.dylib /Library/Application Support/DivXNetworks/libdpv10.dylib
    0x6405000 - 0x6436fff liblame3.92.dylib /Library/Application Support/DivXNetworks/liblame3.92.dylib
    0x6605000 - 0x6665fff libdpus10.dylib /Library/Application Support/DivXNetworks/libdpus10.dylib
    0x7c23000 - 0x7c25fff com.apple.PDFImporter 1.3.1 (???) /System/Library/Components/PDFImporter.component/Contents/MacOS/PDFImporter
    0x8911000 - 0x89dbfff com.divxnetworks.DivXCodec 5.2.1 /Users/Hiroshi/Library/QuickTime/DivX 5.component/Contents/MacOS/DivX 5
    0x3defc000 - 0x3e0f5fff net.telestream.wmv.import 2.1.0.33 /Library/QuickTime/Flip4Mac WMV Import.component/Contents/MacOS/Flip4Mac WMV Import
    0x80830000 - 0x8090efff libxml2.2.dylib /usr/lib/libxml2.2.dylib
    0x80a50000 - 0x80ad4fff libstdc++.6.dylib /usr/lib/libstdc++.6.dylib
    0x80c80000 - 0x80c88fff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
    0x80f20000 - 0x80f24fff com.apple.NetServices.BDRuleEngine 1.0.1 /Applications/iPhoto.app/Contents/MacOS/../NetServices/Frameworks/BDRuleEngine. framework/Versions/A/BDRuleEngine
    0x80f40000 - 0x80f4cfff com.apple.NetServices.BDControl 1.0.4 /Applications/iPhoto.app/Contents/MacOS/../NetServices/Frameworks/BDControl.fra mework/Versions/A/BDControl
    0x81c90000 - 0x81c93fff libmx.A.dylib /usr/lib/libmx.A.dylib
    0x84048000 - 0x84085fff com.apple.QuickTimeFireWireDV.component 7.1.2 /System/Library/QuickTime/QuickTimeFirewireDV.component/Contents/MacOS/QuickTim eFireWireDV
    0x84380000 - 0x84389fff libz.1.1.3.dylib /usr/lib/libz.1.1.3.dylib
    0x843a0000 - 0x843cdfff libssl.0.9.dylib /usr/lib/libssl.0.9.dylib
    0x87f60000 - 0x88096fff com.apple.vImage 1.2.0 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
    0x88d40000 - 0x88d4cfff com.apple.agl 2.5 (AGL-2.5) /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x8bde2000 - 0x8bdf2fff com.apple.Accelerate.vecLib 3.0.3 (vecLib 3.0.3) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
    0x8eea0000 - 0x8eeb6fff libJapaneseConverter.dylib /System/Library/CoreServices/Encodings/libJapaneseConverter.dylib
    0x8fd50000 - 0x8fd50fff com.apple.Accelerate 1.0.3 (Accelerate 1.0.3) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x8fe00000 - 0x8fe4ffff dyld /usr/lib/dyld
    0x90000000 - 0x9014ffff libSystem.B.dylib /usr/lib/libSystem.B.dylib
    0x901c0000 - 0x9026efff com.apple.CoreFoundation 6.3.9 (299.37) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x90490000 - 0x904adfff com.apple.audio.SoundManager 3.9 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
    0x904d0000 - 0x90588fff com.apple.audio.toolbox.AudioToolbox 1.3.4 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x90610000 - 0x9069afff com.apple.CoreServices.OSServices 3.0.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
    0x90700000 - 0x90700fff com.apple.CoreServices 10.3 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x90702000 - 0x9073afff com.apple.AE 1.4 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE
    0x907c7000 - 0x907d2fff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
    0x907f0000 - 0x907f9fff com.apple.DiskArbitration 2.0.5 /System/Library/PrivateFrameworks/DiskArbitration.framework/Versions/A/DiskArbi tration
    0x90810000 - 0x90810fff com.apple.ApplicationServices 1.0 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
    0x90830000 - 0x9089ffff libobjc.A.dylib /usr/lib/libobjc.A.dylib
    0x908c5000 - 0x90915fff com.apple.HIServices 1.4.1 (0.0.1d1) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
    0x90940000 - 0x909b3fff com.apple.DesktopServices 1.2.5 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
    0x909f0000 - 0x90a08fff com.apple.WebServices 1.1.1 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore
    0x90a20000 - 0x90b7bfff com.apple.Foundation 6.3.8 (500.61) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x90c32000 - 0x90c45fff com.apple.speech.synthesis.framework 3.2 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x90c60000 - 0x90cc2fff libGLU.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x90d00000 - 0x90d1bfff com.apple.SystemConfiguration 1.7.1 (???) /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
    0x90d40000 - 0x90d40fff com.apple.Carbon 10.3 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x90d60000 - 0x90d6bfff com.apple.opengl 1.3.8 /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x90dd0000 - 0x90df0fff com.apple.DirectoryService.Framework 1.7.2 /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
    0x90e10000 - 0x90e11fff com.apple.ServerControl 10.2.3 /System/Library/PrivateFrameworks/ServerControl.framework/Versions/A/ServerCont rol
    0x90e30000 - 0x90e36fff com.apple.ServerPrefs 10.2.3 /System/Library/PrivateFrameworks/ServerPrefs.framework/Versions/A/ServerPrefs
    0x90e77000 - 0x90e91fff libPDFRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libPDFRIP.A.dylib
    0x90ec0000 - 0x90ec0fff com.apple.Cocoa 6.3 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x91040000 - 0x91062fff com.apple.framework.Admin 1.3.3 /System/Library/PrivateFrameworks/Admin.framework/Versions/A/Admin
    0x91090000 - 0x91091fff com.apple.AFPDefines 2.0.1 /System/Library/PrivateFrameworks/AFPDefines.framework/Versions/A/AFPDefines
    0x910e0000 - 0x91134fff com.apple.bom 1.2.8 (64.2) /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
    0x91140000 - 0x911a9fff com.apple.htmlrendering 1.1.2 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
    0x911da000 - 0x911dafff com.apple.audio.units.AudioUnit 1.3.3 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x911dc000 - 0x911dffff com.apple.QuickTimeH264.component 7.1.2 /System/Library/QuickTime/QuickTimeH264.component/Contents/MacOS/QuickTimeH264
    0x91206000 - 0x9120ffff com.apple.IntlPreferences 1.1 /System/Library/PrivateFrameworks/IntlPreferences.framework/Versions/A/IntlPref erences
    0x91216000 - 0x91222fff com.apple.framework.Apple80211 3.4.1 /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
    0x91227000 - 0x91231fff com.apple.framework.machinesettings 1.3.3 /System/Library/PrivateFrameworks/MachineSettings.framework/Versions/A/MachineS ettings
    0x913a0000 - 0x9145ffff ColorSync /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
    0x914ad000 - 0x91575fff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
    0x915e0000 - 0x91699fff com.apple.QD 3.4.71 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
    0x917b6000 - 0x917cafff libCGATS.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
    0x917e0000 - 0x917f0fff com.apple.speech.recognition.framework 3.3 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
    0x91961000 - 0x91966fff com.apple.SetupAssistant.International 1.3.4 /System/Library/PrivateFrameworks/International.framework/Versions/A/Internatio nal
    0x9196a000 - 0x919d1fff com.apple.audio.CoreAudio 2.1.3 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x91a2f000 - 0x91a67fff com.apple.LaunchServices 10.3.5 (98.4) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
    0x91a7b000 - 0x91e00fff com.apple.HIToolbox 1.3.7 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
    0x924f2000 - 0x92585fff com.apple.print.framework.PrintCore 3.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
    0x925c8000 - 0x92637fff com.apple.framework.IOKit 1.3.6 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x92650000 - 0x926f3fff libcrypto.0.9.dylib /usr/lib/libcrypto.0.9.dylib
    0x92727000 - 0x9274dfff com.apple.FindByContent 1.4 (1.2) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent
    0x927b2000 - 0x927bdfff com.apple.securityhi 1.2 (90) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
    0x927c5000 - 0x927d4fff libPSRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libPSRIP.A.dylib
    0x927f0000 - 0x92827fff com.apple.CFNetwork 1.2.1 (7) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
    0x9283f000 - 0x92856fff com.apple.LangAnalysis 1.5.4 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
    0x92a50000 - 0x93426fff com.apple.QuickTimeComponents.component 7.1.2 /System/Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTim eComponents
    0x939a0000 - 0x939b4fff libcups.2.dylib /usr/lib/libcups.2.dylib
    0x939d0000 - 0x939d4fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
    0x93b3c000 - 0x93baffff com.apple.NavigationServices 3.3.3 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
    0x940c0000 - 0x940c0fff com.apple.DiscRecording 2.1.17 (???) /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
    0x9415d000 - 0x94165fff libbsm.dylib /usr/lib/libbsm.dylib
    0x94169000 - 0x94173fff com.apple.framework.AppleTalk 1.2.0 (???) /System/Library/Frameworks/AppleTalk.framework/Versions/A/AppleTalk
    0x94180000 - 0x9418ffff com.apple.frameworks.preferencepanes 10.0 /System/Library/Frameworks/PreferencePanes.framework/Versions/A/PreferencePanes
    0x94580000 - 0x9458cfff com.apple.help 1.0.1 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
    0x94596000 - 0x945a3fff com.apple.CommonPanels 1.2.1 (1.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
    0x945b0000 - 0x945b9fff libz.1.dylib /usr/lib/libz.1.dylib
    0x94610000 - 0x9462afff libresolv.9.dylib /usr/lib/libresolv.9.dylib
    0x94650000 - 0x946affff com.apple.SearchKit 1.0.2 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
    0x946ed000 - 0x946fdfff com.apple.ImageCapture 2.1.5 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
    0x94720000 - 0x94721fff com.apple.securityfoundation 1.0 (6) /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
    0x94800000 - 0x9488cfff com.apple.ink.framework 101.1.4 (55.12) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
    0x948b0000 - 0x948e1fff com.apple.securityinterface 1.0 (39) /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInter face
    0x953d0000 - 0x95403fff com.apple.DiscRecordingContent 2.1.17 /System/Library/Frameworks/DiscRecording.framework/Versions/A/Frameworks/DiscRe cordingContent.framework/Versions/A/DiscRecordingContent
    0x95420000 - 0x95495fff com.apple.DiscRecordingEngine 2.1.17 /System/Library/Frameworks/DiscRecording.framework/Versions/A/Frameworks/DiscRe cordingEngine.framework/Versions/A/DiscRecordingEngine
    0x954c0000 - 0x95ac6fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
    0x95b20000 - 0x95df0fff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
    0x95e0a000 - 0x95e24fff com.apple.openscripting 1.2.1 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
    0x95e40000 - 0x95eadfff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
    0x95eda000 - 0x95eedfff libRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
    0x95f00000 - 0x95f20fff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
    0x962e6000 - 0x9655ffff com.apple.CoreServices.CarbonCore 10.3.7 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
    0x965ba000 - 0x967a1fff com.apple.security 2.4 (177) /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x968d0000 - 0x969b2fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
    0x96a04000 - 0x96a52fff com.apple.print.framework.Print 3.3 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
    0x96aa0000 - 0x96acefff libssl.0.9.7.dylib /usr/lib/libssl.0.9.7.dylib
    0x96b08000 - 0x96b1efff com.apple.QuartzCore 1.3 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x96b50000 - 0x96bdffff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
    0x96cb0000 - 0x96d9efff libiconv.2.dylib /usr/lib/libiconv.2.dylib
    0x96e12000 - 0x96e2cfff libGL.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x96e80000 - 0x96e90fff com.apple.vecLib 3.0.3 (vecLib 3.0.3) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
    0x96eca000 - 0x971a2fff com.apple.CoreGraphics 1.203.30 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
    0x9721a000 - 0x974cefff com.apple.QuickTime 7.1.2 /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
    0x97d72000 - 0x98271fff com.apple.AppKit 6.3.11 (743.43) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0xefbef000 - 0xefcd1fff libPSIKey.dylib /Library/Application Support/DivXNetworks/libPSIKey.dylib
    Imac G5 Mac OS X (10.3.9)
    Imac G5 Mac OS X (10.3.9)

  • ORA-07445

    Hi All,
    I recenly installed Oracle 10g Release 2 on Windows 2003 Standrad Edition..
    And getting an error in my alert log file...
    ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x60518765] [ADDR:0x4] [UNABLE_TO_WRITE] []
    Wed Dec 21 16:12:19 2005
    Errors in file d:\oracle\product\10.2.0\admin\eximware\udump\eximware_ora_460.trc:
    ORA-04030: out of process memory when trying to allocate 82444 bytes (pga heap,control file i/o buffer)
    ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x60518765] [ADDR:0x4] [UNABLE_TO_WRITE] []
    How can i resolve this issue?
    Regards
    Mani

    Hi all,
    Same issue...i didnt find a solution or i didnt understand what to do...
    My sga size is 2504 M
    My pga aggregate is 1000 M
    I am running oracle 10.2.0.1 on windows server 2003. My quad has 4 processors + 8 gb RAM.
    Still i get this error...
    Mon Dec 04 11:46:48 2006
    Process startup failed, error stack:
    Mon Dec 04 11:46:49 2006
    Errors in file e:\oracle\product\10.2.0\admin\icbsprod\bdump\icbsprod_psp0_2836.trc:
    ORA-27300: OS system dependent operation:spcdr:9261:4200 failed with status: 997
    ORA-27301: OS failure message: Overlapped I/O operation is in progress.
    ORA-27302: failure occurred at: skgpspawn
    Mon Dec 04 11:46:49 2006
    Process P022 died, see its trace file
    Mon Dec 04 11:47:22 2006
    Thread 1 advanced to log sequence 4771
    Current log# 3 seq# 4771 mem# 0: P:\ORACLE\ORADATA\ICBSPROD\REDO03.LOG
    Mon Dec 04 11:47:49 2006
    Thread 1 cannot allocate new log, sequence 4772
    Checkpoint not complete
    Current log# 3 seq# 4771 mem# 0: P:\ORACLE\ORADATA\ICBSPROD\REDO03.LOG
    Mon Dec 04 11:47:50 2006
    Errors in file e:\oracle\product\10.2.0\admin\icbsprod\bdump\icbsprod_ckpt_2884.trc:
    ORA-04030: out of process memory when trying to allocate 16908 bytes (pga heap,Get krha asynch mem)
    Mon Dec 04 11:47:50 2006
    CKPT: terminating instance due to error 4030
    Mon Dec 04 11:47:50 2006
    Errors in file e:\oracle\product\10.2.0\admin\icbsprod\bdump\icbsprod_mman_2852.trc:
    ORA-04030: out of process memory when trying to allocate bytes (,)
    should i reduce my sga and pga size?
    regards,
    Mathew

Maybe you are looking for