Sorry to bring this up again but I'm still not able to successfully run OCN4 on my X50V. I've installed OCN4 to my SD card but keep getting the corrupted file problem screenshot
I've:
-reinstalled, changed the registry entry (HKEY_LOCAL_MACHINE\System\StorageManager\PnPUploa dDelay) to 3000. After 1 or 2 uses have the same corrupted file problem.
-performed a hard reset, reinstalled, changed registry still have corrupted file problem after a few uses
-performed another hard reset, reinstalled on a different SD card, changed registry. Still corrupted file
-hard reset, reinstalled, changed registry to 5000 versus 3000. Guess what, corrupted file problem after a few uses.
Procedure for using OCN:
1. Turn on X50V
2. Go into Bluetooth Manager and establish connection
3. Start OCN
When done repeat steps 1-3 in reverse order.
Does anyone have any other suggestions? All I wanna do is use GPS. Also, here is a recap of my talks with OCN support, is there a step or piece that I should tell them to that might help this problem.
The only workaround I can think of is to copy the langENG.dll that is the problem to another location, then when the copy in the OCN install directory gets corrupted, copy the good version back and start again. Not pretty but it would work.
Thanks Jake. I was thinking about that on the way home. Alright I can give that a try. Just not sure why it doesn't work. There aren't that many variables and it seems like I've covered all of them.
Thanks Jake. I was thinking about that on the way home. Alright I can give that a try. Just not sure why it doesn't work. There aren't that many variables and it seems like I've covered all of them.
smiffer, Have you found any resolution to this problem? For some odd reason, I am also getting the same corrupted Legal Notice screen.
Everything was working perfectly fine till today. I took OCN out for a spin, closed down OCN/BT/GPS in the proper sequence. Now when I am trying to start it, I keep getting that corrupted screen. I changed the registry setting from 1500 to 3000 to 5000. Did lots of soft-reset. No use. I have around 35MB free RAM for running programs. My OCN is also installed on a SD card.
Well the "solution" I found was to install OCN into Main Memory. Thus far it's been working fine. KNOCK ON WOOD. Hoping OCN5 changes a few things so that I can install it onto my SD card. But for now it seems to working. Like you I tried everything but kept getting the corrupted file. Try installing OCN into Main Memory and see if that helps.
OCN did take a little longer than I liked in getting my answer to me (2.5 business days) but their answers were at least informative and you could tell they actually read my question unlike every one of my tomtom inquiries when I had that program. I was also surprised that the folks at buygpsnow.com also were trying to help me with my problem, I purchased OCN from them. Online retailers should really take lessons from buygpsnow.com on customer service.
Well the "solution" I found was to install OCN into Main Memory. Thus far it's been working fine. KNOCK ON WOOD. Hoping OCN5 changes a few things so that I can install it onto my SD card. But for now it seems to working. Like you I tried everything but kept getting the corrupted file. Try installing OCN into Main Memory and see if that helps.
OCN did take a little longer than I liked in getting my answer to me (2.5 business days) but their answers were at least informative and you could tell they actually read my question unlike every one of my tomtom inquiries when I had that program. I was also surprised that the folks at buygpsnow.com also were trying to help me with my problem, I purchased OCN from them. Online retailers should really take lessons from buygpsnow.com on customer service.
smiffer, thanks a lot for your response. Yesterday I just could not get it running. Today I unistalled OCN and installed it back to the same location in the SD card and now everything is working fine. Knock on wood. I am holding my breath and hoping that it will continue working. If it stops working again then I might have to install OCN into RAM.
I had to reinstall OCN couple of times till I got the whole thing right. What I believe I have found is that if put X50v on the cradle and start OCN, that's when I get the corrupted legal screen. Don't ask me why, but it happened to me two times. The first time when it stopped working, my X50v battery was going low, and so I thought I will put it in the cradle for charging and meanwhile play with OCN for some time. That's when I got the first legal screen corruption. Once you get the corruption, then it does not matter what you do with it, the only option is to reinstall OCN. It happened to me one more time and now since my OCN is working fine, I don't have the heart to see whether my theory is right or wrong. I hope my theory is right at least then we will have a reason for this corruption and there is a way we can avoid it.
BTW, you mentioned in one of your thread that when you had to reinstall OCN into your PPC, you had to reinstall OCN on your PC too. This need not be the case. I found this article in OCN's knowledgebase, which allows you to install only the PPC component of OCN without touching the PC component. Using this I was able to install OCN multiple times. The article can be found at this link.
Now every time I start OCN, I am holding my breath, crossing my fingers and hoping that OCN will start without any hiccups.
I don't have an x50 (I have and x30) and it runs fine in BIS. You might want to give that a try before installing into main memory, where it will take up a lot of space.
smiffer, thanks a lot for your response. Yesterday I just could not get it running. Today I unistalled OCN and installed it back to the same location in the SD card and now everything is working fine. Knock on wood. I am holding my breath and hoping that it will continue working. If it stops working again then I might have to install OCN into RAM.
I had to reinstall OCN couple of times till I got the whole thing right. What I believe I have found is that if put X50v on the cradle and start OCN, that's when I get the corrupted legal screen. Don't ask me why, but it happened to me two times. The first time when it stopped working, my X50v battery was going low, and so I thought I will put it in the cradle for charging and meanwhile play with OCN for some time. That's when I got the first legal screen corruption. Once you get the corruption, then it does not matter what you do with it, the only option is to reinstall OCN. It happened to me one more time and now since my OCN is working fine, I don't have the heart to see whether my theory is right or wrong. I hope my theory is right at least then we will have a reason for this corruption and there is a way we can avoid it.
BTW, you mentioned in one of your thread that when you had to reinstall OCN into your PPC, you had to reinstall OCN on your PC too. This need not be the case. I found this article in OCN's knowledgebase, which allows you to install only the PPC component of OCN without touching the PC component. Using this I was able to install OCN multiple times. The article can be found at this link.
Now every time I start OCN, I am holding my breath, crossing my fingers and hoping that OCN will start without any hiccups.
I run it in the cradle and it's just fine. Normally, I would suspect that there is something else running on your device that I don't have running on mine that is creating the problem. Not 100% sure of that, but it's a prime candidate.
Thanks CdSlc. Wish I'd have found that knowledgebase article earlier. I can't tell you the number of times I uninstalled/reinstalled OCN on my PC & PPC.
Well yesterday was a true test. I went for a motorcycle ride with some guys. I created an 89 mile route in the morning and saved the iteniary. Shut off OCN. When I got ready to leave turned on OCN, had it route me to my friends house (althought I know where he lives). Turned off OCN once I got there. Turned on OCN once we left to meet up with everyone else at a local greasy spoon. When we left on our ride I loaded the saved iteniary and she worked fine through most of the trip.
The last 15 miles or so were a problem but it wasn't with OCN. On my motorcycle I have a tankbag and on top of the tankbag is a flat pouch with a clear front in which you can put a map. Well since the RAM mounting bracket I want isn't out yet I rode most of the trip with the X50V inside of my tankbag and just used the voice guidance to route me. Well for the last little bit I thought it would be nice to be able to see the screen so I slid the X50 inside of the mappouch at one of our smoke/rest breaks. Well about 10 minutes after we got going the X50 just locked up. Not too big of a deal as I was close to home and knew the route. As I was riding home I was trying to figure out why she locked up. I think I know why, when I got home I parked the bike in the sun, put a meat thermometer inside of the map pouch and waited. 15 minutes later I went out and checked and the temperature said 155 degrees. Basically the map pouch in direct sunlight was just like a greenhouse. Well I won't be doing that again.
Well that ended up being a long rambling post but the jist of it was that OCN does seem to be working fine for me in Main Memory. I might try BIS later on but for now I'll leave it.
I run it in the cradle and it's just fine. Normally, I would suspect that there is something else running on your device that I don't have running on mine that is creating the problem. Not 100% sure of that, but it's a prime candidate.
After updating my X50v to A03, I have been very selective of what I am installing on my X50v. The only Today Plug-ins that I have installed and have running are Pocket Breeze, Contact Breeze, iLauncher, Pocket Weather and PowerCheck. Also, I have Magic Button running in the background. Other than that, I don't have any other program running in the background.
The odd thing is that OCN was working fine till 7pm when I used it for my drive. I shut it down the correct way. And then when I started OCN at 9pm, it started with this error. I am hoping it will not misbehave anymore during my long drive for the July 4th long weekend. Keeping fingers crossed.