When using instant copy V8 I receive the message "Access violation at address 004A4CAF in module 'ICopy.exe'. Read of address" I have tried unistalling and then re-installing the software but the error remains. Does anybody know how to fix this?
I've tried to help him as much as I can on the phone but have run out of ideas. He has done everything that I've done on all my PC's to set it up but for some reason this error comes up. We've tried renaming the skinfile to skinfile1 in the registry which fixed mine, although that didn't help in this case. Google doesn't seem to come up with any suggestions so I suggested he post here.
My Instant Copy stopped working today, too. When I installed SP2, it stopped working. Then I found teh fix to rename teh registry key for the "skinfile". I did. and it worked fine. I just installed a new DVD drive today, and I am getting the same error again, eventhough the "skinfile" is still renamed. I tried to rename again and even delete it, but I got the same error. If anyone has the answer please post it here, or send it to [REMOVED] Thanks in advance!! - Dan
It's just a programming error where the operation required is not permitted programmatically - usually a bug, but it can also mean that you don't have rights, or a disk error, insufficient open files, memory. In this case, I'd suggest a bug. You might have to get an early version of the program and install that http://translate.google.com/transla...7ICopy.exe%27.+Read+of+address&hl=en&lr=&sa=G
heres a little more infomation for you guys that need a clearer explanation on this problem. From what I can make out, there is a programmatical conflict with a skin setting, where the skin setting is set to "NONE. The author of the note on that forum has suggested opening up the registry (THIS IS DANGEROUS FOR THE INEXPERIENCED), finding the relevent registry setting, and changing the name of the skin file to another skin name - presumably one that exists. The problem seems to occur with a version of Icopy and WinXP SP2. Early version or probably later version. The author suggested the registry fix as a possiblity. There is considerable risk involved in mucking around with the registry settings if you dont know what you are doing - Check the link out above but be cautious if you attempt there fix. iF THE PROBLEM PERSISTS YOU WILL NEED TO TAKE YOUR COMPUTER INTO A SPECIALIST.
