don't click here

GraphicsGale

Discussion in 'Technical Discussion' started by Hez, Jan 22, 2012.

  1. Hez

    Hez

    Oldbie
    [​IMG]
    Then this
    [​IMG]

    Deleted everything in the registry and then all the files and reinstalled, still happens. It only happens when I close it. It's not a huge deal, but super annoying because I have to kill the application whenever I want to close it. Anyone else have this problem?
     
  2. Sik

    Sik

    Sik is pronounced as "seek", not as "sick". Tech Member
    6,718
    1
    0
    being an asshole =P
    OK, looked around to see what that error code is. Honestly no idea, but here are two things you could try:

    • Where are you running Graphics Gale from? With what permissions? Because apparently this error may happen if the program is unable to open a file for whatever reason. Is it possible to try to run it from elsewhere?
    • MSDN lists error 103 as a semaphore problem. Multithreading issue, essentially. What happens if you limit Graphics Gale to a single core?
     
  3. Hez

    Hez

    Oldbie
    Tried everything except the limiting it to one core. How the hell do you do that?
     
  4. Sik

    Sik

    Sik is pronounced as "seek", not as "sick". Tech Member
    6,718
    1
    0
    being an asshole =P
    Task manager. There's one tab that lets you choose on which cores it can run.
     
  5. Hez

    Hez

    Oldbie
    Nothing....weirdest thing.
     
  6. Flygon

    Flygon

    Member
    [​IMG]
    [​IMG]
    Nothing like this?
     
  7. Sik

    Sik

    Sik is pronounced as "seek", not as "sick". Tech Member
    6,718
    1
    0
    being an asshole =P
    Welp, not a tab I guess. I don't have a multicore processor so I couldn't check, was just trying to recall some instructions I had found somewhere.
     
  8. Hez

    Hez

    Oldbie
    no I mean that I changed the processors and it still had the error.
     
  9. Sik

    Sik

    Sik is pronounced as "seek", not as "sick". Tech Member
    6,718
    1
    0
    being an asshole =P
    Then I have absolutely no idea. I/O error 103 is everything but descriptive, and it could pretty much mean anything.

    EDIT: also I had managed to stumble upon an error claiming a trojan ended up causing that error in some program. I really doubt that's the case, but knowing you... :v:
     
  10. Hez

    Hez

    Oldbie
    I installed ubuntu for porn now =3