Notices

X51 Hardware Troubles Axim X51 Hardware Discussions

Reply
 
LinkBack Thread Tools
Old 03-30-06, 09:19 AM   #1 (permalink)
Aximsite Prospect
 
Join Date: Mar 2006
Posts: 1
Thanked 0 Times in 0 Posts
Worried Notification Error Odyssey Client

I have an Axim X51V, and most of the time when I turn it on I get this error message: Notification Error Cannot execute\Program Files\ Funk Software\ Odyssey Client\OdClientCE.exe

I have taken the Odyssey Client out of the start up as per some instructions on this website. I still get this message everytime. And now it is stuck on this error message and I cannot close it out. I have reset it, and it still doesn't go away.

Any help with this message would be greatly appreciated.

Thanks!
Stars1021 is offline   Reply With Quote
Sponsor Ads
Old 03-31-06, 03:17 PM   #2 (permalink)
Aximsite Prospect
 
Join Date: Jan 2006
Posts: 5
Thanked 0 Times in 0 Posts
Stars
I get exactly the same error every time I switch on. I also have x51v, 512 cf and 512sd cards. I have a wireless network at home and have set up the bluetooth to access the internet through my nokia 6230i. I always disable wireless and bluetooth before switching off and dont always visit wireless or bluetooth in most sessions but I still get the error on start up. This error results in a very slow start up. if you get yours sorted please let me know in simple steps (not that bright)

Cheers
brianjreed is offline   Reply With Quote
Old 03-31-06, 03:40 PM   #3 (permalink)
Aximsite Prospect
 
Join Date: Nov 2004
Posts: 1
Thanked 0 Times in 0 Posts
The exact same thing happens to me and it's really annoying - not least because of the very slow start up. Its really embarrassing to have to wait several minutes to access my diary - particularly when the others are using paper!!!
I have also disabled wireless and bluetooth and oddessy - but the error still happens.
I used to have an Axim 5, which on start up was instantly ready.
I would dearly love a solution to this (but like brianjreed, am not too literate in computers!)
colnbrook is offline   Reply With Quote
Old 04-01-06, 03:05 PM   #4 (permalink)
Aximsite Prospect
 
Join Date: Mar 2006
Posts: 5
Thanked 0 Times in 0 Posts
I have the same problem. I hope there is a fix to this and hopefully this is the reason why my x51v is very slow to start up. I was just about to open a new thread on this issue because it is starting become agravating to me. It's gotten so bad I have been beginning to wish I had never stopped buying a Palm OS device. I have been an avid Palm owner for the past 6 years and when I somehow smashed the screen on my Palm M515 decided I would try the Pocket PC world. I read all sorts of reviews and came to the conclusion that the x51v would be my best choice. But with this slow startup problem along with the Odissey Client error I'm beginning to think that I made a big mistake in going with a Pocket PC. Again I hope that there is some sort of fix for this problem. If not then probably in the next few months my x51v will become a very expensive paper weight.
Nitsud24 is offline   Reply With Quote
Old 04-01-06, 03:47 PM   #5 (permalink)
Aximsite Rookie
 
Join Date: Mar 2006
Posts: 38
Thanked 0 Times in 0 Posts
Originally Posted by Nitsud24
I have the same problem. I hope there is a fix to this and hopefully this is the reason why my x51v is very slow to start up. I was just about to open a new thread on this issue because it is starting become agravating to me. It's gotten so bad I have been beginning to wish I had never stopped buying a Palm OS device. I have been an avid Palm owner for the past 6 years and when I somehow smashed the screen on my Palm M515 decided I would try the Pocket PC world. I read all sorts of reviews and came to the conclusion that the x51v would be my best choice. But with this slow startup problem along with the Odissey Client error I'm beginning to think that I made a big mistake in going with a Pocket PC. Again I hope that there is some sort of fix for this problem. If not then probably in the next few months my x51v will become a very expensive paper weight.
Hello,

while I don't have this problem, I have disabled the odyssey-program in the autostart folder. Odyssey is a special Wlan-accessclient for certificate-authenticated Wlan-networks, and since I use normal WPA-PSK to authenticate with my accesspoint, I have no use for it.

To disable the autostart of the odysseyclient, install a process tool like sktools, close the process odclientxyz.exe (I am not quite sure about the complete name) and delete/move the file odClientCeAutoLaunchSmart.exe from your windows\startup-folder.

Regards,

Detlev
Top_Gun is offline   Reply With Quote
Old 04-02-06, 01:43 PM   #6 (permalink)
Aximsite Prospect
 
Join Date: Mar 2006
Posts: 5
Thanked 0 Times in 0 Posts
Originally Posted by Top_Gun
Hello,

while I don't have this problem, I have disabled the odyssey-program in the autostart folder. Odyssey is a special Wlan-accessclient for certificate-authenticated Wlan-networks, and since I use normal WPA-PSK to authenticate with my accesspoint, I have no use for it.

To disable the autostart of the odysseyclient, install a process tool like sktools, close the process odclientxyz.exe (I am not quite sure about the complete name) and delete/move the file odClientCeAutoLaunchSmart.exe from your windows\startup-folder.

Regards,

Detlev
Do you know of a fix if you use a certificate-authenticated Wlan?
Nitsud24 is offline   Reply With Quote
Old 04-02-06, 02:06 PM   #7 (permalink)
drowe
Guest
 
Posts: n/a
Taking odClientCeAutoLaunchSmart.exe out of the startup with sktools or memmaid will only last until the next soft reset. First I would check to see if \Program Files\ Funk Software\ Odyssey Client\OdClientCE.exe is actually there. There are some people that advocate putting a dummy program in it's place to save 2mb ram. I don't think the benefit is worth it myself. If it isn't there, a hard reset will copy it back.
  Reply With Quote
Old 04-02-06, 03:11 PM   #8 (permalink)
bigdave240
Guest
 
Posts: n/a
the only way i know of making it stop starting up auto is to click on the icon in the toolbar at the bottom, open up the program and then use the exit inside the program. anything else will not work. if you kill it with a taskswitcher like magic button it will come back in my experience. if you need the program in normal use you need to exit it and start it up each time. sort of a pain, i need it at work too, but it is way better than waiting for so long a time each time you turn on the pda.
  Reply With Quote
Old 04-05-06, 10:14 AM   #9 (permalink)
tzi
Aximsite Prospect
 
Join Date: Mar 2006
Posts: 15
Thanked 0 Times in 0 Posts
Hi!

I have the same problem. So, it seems a real bug and therefor needs to be fixed :-) It makes my Axim nearly unuseable as it forces me to wait up to one minute until my Axim becomes responsive...

--
TZi
tzi is offline   Reply With Quote
Old 04-05-06, 11:54 AM   #10 (permalink)
bigdave240
Guest
 
Posts: n/a
Originally Posted by tzi
Hi!

I have the same problem. So, it seems a real bug and therefor needs to be fixed :-) It makes my Axim nearly unuseable as it forces me to wait up to one minute until my Axim becomes responsive...

--
TZi
did you try what I say in my reply just above your post?
  Reply With Quote
Old 04-07-06, 12:00 PM   #11 (permalink)
Aximsite Prospect
 
Join Date: Mar 2006
Posts: 5
Thanked 0 Times in 0 Posts
Originally Posted by bigdave240
the only way i know of making it stop starting up auto is to click on the icon in the toolbar at the bottom, open up the program and then use the exit inside the program. anything else will not work. if you kill it with a taskswitcher like magic button it will come back in my experience. if you need the program in normal use you need to exit it and start it up each time. sort of a pain, i need it at work too, but it is way better than waiting for so long a time each time you turn on the pda.
I figured that is what I was going to have to do. I was hoping that there was another way around this. Obviously there isn't one. Hopefully Dell will figure this one out. Thanks for your input.
Nitsud24 is offline   Reply With Quote
Old 04-07-06, 12:04 PM   #12 (permalink)
tzi
Aximsite Prospect
 
Join Date: Mar 2006
Posts: 15
Thanked 0 Times in 0 Posts
Hi!

Just "disabling" the odysee client did not help. I had to hard-reset the Axim and since then I did not touch the odysee client. The Axim has since then no resume delay .. maybe that helped...

--
TZi
tzi is offline   Reply With Quote
Old 04-07-06, 01:29 PM   #13 (permalink)
bigdave240
Guest
 
Posts: n/a
Originally Posted by tzi
Hi!

Just "disabling" the odysee client did not help. I had to hard-reset the Axim and since then I did not touch the odysee client. The Axim has since then no resume delay .. maybe that helped...

--
TZi
well... that is the hard way but as long as you don't startup Odyssey it shouln't cause you any more trouble. good luck
  Reply With Quote
Old 04-19-06, 12:24 AM   #14 (permalink)
Aximsite Prospect
 
Join Date: Apr 2006
Posts: 1
Thanked 0 Times in 0 Posts
Notification Error Odyssey Client

I also have a Dell Axim X51v with this error. By sheer luck, i found a workaround for it.
There is a tool collection, called SKTools (www.s-k-tool.com). One of them is for deleting the notification queue and since the error message says something about notification i tried it.

It worked! The error disappeared. And whenever i get the notification error again, i simply use this utility to get rid of it.

I'm not the WM5 specialist, but it seems, that the odyssey clients makes a wakeup entry in the notification queue every time it starts. The bad news is, that it looks like the notification queue can only handle a certain number of entries (don't ask me how many). So, when the queue is full, the odyssey client tries to make his entry for about one minute, before he produces the error message and i think that causes the delay.

I know, it is not really a solution, but at least for me it helped and i hope it does also for other people, owning the absolutely facinating Dell Axim X51v.

Greetings to all of them
quirken
quirken is offline   Reply With Quote
Old 04-19-06, 10:42 AM   #15 (permalink)
bigdave240
Guest
 
Posts: n/a
good catch. I will try that on my x50v WM5 and see. Welcome to Aximsite!
  Reply With Quote
Reply

Tags
client, error, notification, odyssey

Sponsor Ads

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Odyssey Client 4.0 forkyfork Mobility Site News 17 08-09-06 04:24 AM
Odyssey Client cannot .. run! csynt WiFi Talk 1 03-02-06 12:01 PM
Odyssey Client mrdinks X30 / X3 / X3i Forums 1 12-21-04 02:11 PM
Odyssey client voided X30 / X3 / X3i Forums 7 09-13-04 10:26 PM
Odyssey Client gew95001 X30 / X3 / X3i Forums 5 07-02-04 05:04 AM


All times are GMT -5. The time now is 07:46 PM.
Powered by vBulletin® Version 3.8.2
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.3.0
Copyright © 2003-09 LeckMedia, LLC