I had Pocket e-Sword installed and I used it several times, but last night when I went to start it, it just showed the little twirly thing that you see every time a program starts, and then it dumped me back to the desktop… no error, nothing. Nothing shown in the running programs either.
Tonight I tried several uninstall/reinstall routines, including a complete uninstall from the PC, soft reset, and reinstall… still no go. I tried installing it every which way… built-in storage, CF, and SD card. Nothing worked.
Any other suggestions?
(I have since installed the OliveTree BibleReader, but I still prefer e-Sword because I'm used to it from using it on a PC.)
I had Pocket e-Sword installed and I used it several times, but last night when I went to start it, it just showed the little twirly thing that you see every time a program starts, and then it dumped me back to the desktop… no error, nothing. Nothing shown in the running programs either.
Tonight I tried several uninstall/reinstall routines, including a complete uninstall from the PC, soft reset, and reinstall… still no go. I tried installing it every which way… built-in storage, CF, and SD card. Nothing worked.
Any other suggestions?
(I have since installed the OliveTree BibleReader, but I still prefer e-Sword because I'm used to it from using it on a PC.)
It's possible that something lower level (like the .Net Framework) got corrupted somehow. What you might want to do is uninstall e-Sword (if you can) and also remove the .Net Framework. I'm not 100% certain here so do a backup first.
In my case I've found that I *can't* uninstall Pocket e-Sword because some other process on the device has the font files locked. Doesn't matter, I'll just leave it on there I guess until I rebuild the device next time.
I use the OliveTree also. Much faster. I like the User-Interface better in Pocket eSword but the search engine is incredibly SLOW. Were it not for that I'd use eSword.
Yes, I'm sure it's very possible. I'll give that a try. Otherwise, I think a hard reset might be a good move in the near future anyway. This is my first PPC and I have been installing and uninstalling a ton of software while I figure out what I want and need.
Yes, I'm sure it's very possible. I'll give that a try. Otherwise, I think a hard reset might be a good move in the near future anyway. This is my first PPC and I have been installing and uninstalling a ton of software while I figure out what I want and need.
Well howdy to you there too! Near Ocala ... yeah, not far from Deland at all.
Sounds like a hard reset might be the best way to deal with that problem, then. I'll probably do that again one of these daze - but my PPC is so stable the way it is I'd just assume leave it alone until I *really* need to reload it.
Originally I installed it on CF and it worked fine for a while. When it stopped working I tried removing all traces of it and installing it in BIS, but no go. I have since tried all possible options — CF, SD, BIS — with no luck.
Have you tried installing directly to the device memory? Put the books you use on SD, CF or BIS memory and direct the program to where the resources are.
Yes I did. (When I said BIS I thought that meant the device memory, but apparently this term only applies to older Axims?) Anyway, the point is, I tried every possible option for installing it. I can't direct the e-Sword program to look for the books elsewhere because it won't open at all.
If I were you I would contact e-sword. He is really good about emailing back with solutions. I know it runs on NCF. So updating the .netcompactframework might make a difference.
I finally got eSword working again. Here is what worked for me:
Hard reset
Set up all other essential software except games
disabled Wisbar Advance 2 from loading after soft reset
soft reset PPC
removed eSword from PC using Add/Remove Programs
Got a fresh download of eSword
installed eSword to device from PC installer
installed Bibles
verified that eSword worked
Ran WA2, re-enabled loading after soft reset
soft reset
verified that eSword still worked… it did, hooray!
Now, it might have just been the soft reset prior to installing that did the trick… who knows. But I decided to disable WA2 for the install because it was after I installed Wisbar that I initially had the problem, and I also saw in another thread where someone else who couldn't get it working suspected a conflict with Wisbar.
At this point I'm going to do a backup, install my games, then do another backup.