Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Asian Errormessages when starting C1

Rodast
Hello,

when I start C1 on my notebook, there appear two Errormessages in an asian language. Sadly I cannot read them. Can someone please translate them and say if this are Errormessages from C1 or from something other.

http://www.robert-steichele.de/download/2013-05-29_112322.png

http://www.robert-steichele.de/download/2013-05-29_112331.png
0

Comments

9 comments

Date Votes
  • August Fuchshuber
    Hallo,
    I had that too, could be because I was installing a graphic update at same time.
    But than I installed C1 again and now it is ok.
    regards
    Gust
    0
  • August Fuchshuber
    Hallo once again,
    now I was looking/processing some hundred new pics and in four of them I had that messages...
    Gust
    0
  • NN110315UL2
    Hello,

    I just had the same in C1 7.1.2 after big imports. It looked like a low memory condition.

    Philippe
    0
  • Rodast
    OK, but why in an asian language?
    0
  • Paul Steunebrink
    @all posting here: I suggest you open a support case with Phase One and provide details about action and (obviously) your language setting of CO7 and Windows.
    http://www.phaseone.com/SupportMain.aspx
    0
  • NN125462
    Am gettting the same. I don't know that it is anything to do with memory available as I'm only hitting 65-70% physical memory utilisation when viewing the images. But certainly looks like it may be volume of images in the folder or catalog.

    I'll raise a support ticket shortly.

    Neil

    Edit - ticket raised.
    0
  • NN125462
    In assisting support with the ticket I have raised, I identified 2 jpeg files (and it only appears to be affecting folders containing jpegs) that had not been imported correctly and could not be displayed. By removing the jpegs in question from the catalog - I didn't delete them from the disk - the errors have stopped.

    So there seem to be two problems:

    1. Failure to import the jpeg images properly (they are fine in Windows Exporer/Viewer and IDImager)
    2. Generation of Errors using an invalid language.

    I got the idea that 2. was known about, but not sure about 1. I've sent an example of one of the jpeg files in question to support to analyse.

    Neil
    0
  • Drew Altdo
    Nothing to worry about. We found a localization error within the software. The actual presence of the error is the bug, it does not indicate anything is wrong with your images, catalog, session, etc.
    We will fix it in the next update. Until then please ignore it and accept our apologies.
    0
  • Rodast
    Thank you for this information. So iIwill wait for the next update.
    0

Post is closed for comments.