Problem reading INI files ??
-
- Registered: Oct 09, 2008
- Last visit: Jun 13, 2009
- Posts: 2
Posted: Jun 01, 2009 - 01:27 PM
Hi all, this is not really a bugreport, but a request of help for a strange issue I am having on my system (eCS 1.2MR).
The problem is that every (WD)Sybil application I have on my system is suddenly unable to read his INI files. This is true both for those apps that store settings in their own INI file and for those that use the system INI files.
Example applications are: eBurnIt, USBCfg, IAI, UnimixPM.
The error message is invariably: Exception occurred: . at $0002FB19 Program is terminated.
IAI (that stores its setting in the system INI files) doesn't fail but it is unable to read the settings and so starts with blank settings everytime.
I have been unable so far to understand the cause.
Can somebody help?
Thank you in advance!
Bye
Cris -
- Registered: May 30, 2008
- Last visit: Dec 26, 2011
- Posts: 22
Posted: Jun 06, 2009 - 02:48 PM
Hi Cris!
Does the error occur when an application is started or when it is closed?
Did you try to delete (or better rename) an ini-file and then start the application again?
The error message "... . at $0002FB19 ..." is maybe in conjunction with a memory problem. Do you have other problems on your system? Maybe you should try to check your memory with a test-utility or remove/change your memory.
Try testing without any other application started on your system.
Did you install some software, drivers, updates, ... ?
Did the WDSibyl-applications ever work on your system?
A lot of questions for you - but maybe there is also an answer to you problem included ;-))
Bye
Hanno -
- Registered: Oct 09, 2008
- Last visit: Jun 13, 2009
- Posts: 2
Posted: Jun 13, 2009 - 07:42 PM
Hi Hanno!
hanno
Hi Cris!
Does the error occur when an application is started or when it is closed?
When it is started.
hanno
Did you try to delete (or better rename) an ini-file and then start the application again?
Yes, no change. Moreover, the INI file does NOT get created.
hanno
The error message "... . at $0002FB19 ..." is maybe in conjunction with a memory problem. Do you have other problems on your system? Maybe you should try to check your memory with a test-utility or remove/change your memory.
Try testing without any other application started on your system.
That's not possible. I have an eCS 2.0 RC6a on another partition in the same PC, and everything is working if I boot from there.
hanno
Did you install some software, drivers, updates, ... ?
No that I can remember. But this is what I am trying to determine.
hanno
Did the WDSibyl-applications ever work on your system?
Yes, they worked in a not so distant past.
hanno
A lot of questions for you - but maybe there is also an answer to you problem included ;-))
Bye
Hanno
Thank you Hanno for trying! :-)
Bye
Cris -
- Registered: May 30, 2008
- Last visit: Dec 26, 2011
- Posts: 22
Posted: Jun 19, 2009 - 07:21 AM
Hi Cris,
good answers - bad result ;-)
Seems to me, it is a problem with incompatible (or old) dll or driver. Maybe it would be a good idea to ask Wolfgang, which dll's are used by the applications. As a first suggestion I would mention to check libc (libc-0_6_3-csd3.wpi).
Bye
Hanno
Remark: You stated to have also an installation with eCS2 RC6a which is working correctly, so maybe you do not really need to have the WDSibyl-applications running on eCS 1.2? -
- Registered: Apr 02, 2009
- Last visit: Sep 17, 2009
- Posts: 1
Posted: Sep 17, 2009 - 03:42 PM
Hanno, you're right, I don't need to have them running on eCS 1.2. But I'd like to determine what went wrong there, so that I can be prepared should it happen on v2 as well.
Thank you!
Bye
Cris
- Moderated by:
- Admins-Forum
Users on-line
- 0 users
This list is based on users active over the last 30 minutes.