Re: [OCF] Problem loading the right terminal class

2004-06-17 Thread Carl Youngblood
Steven Ihde wrote: strace java [...whatever...] 21 | grep -E 'stat|open' This technique worked well. I got a little farther. I got it to find pcsc-wrapper-src.jar and also found out which opencard.properties file was being used. Now I'm getting an error related to the OCF-PCSC bridge.

Re: [OCF] Problem loading the right terminal class

2004-06-17 Thread Carl Youngblood
Christophe Muller wrote: Also, I would advise to test the environement step by step in order to see whether or not using the RAD or using OCF is the problem. To check the OCF installation, see my FAQ at: http://www.gemplus.com/techno/opencard/faqs/install-faq-qna.html The links for the various

Re: [OCF] Problem loading the right terminal class

2004-06-17 Thread Carl Youngblood
Sorry to duplicate this message. My mistake. On Thu, 17 Jun 2004 18:19:53 -0700, Carl Youngblood [EMAIL PROTECTED] wrote: Steven Ihde wrote: --- Visit the OpenCard web site at http://www.opencard.org/ for more information on OpenCard---binaries, source code, documents. This list is being

RE: [OCF] Problem loading the right terminal class

2004-06-17 Thread Arief Hamdani Gunawan
in your system. Please let me know your progress, Thank you, Arief Hamdani Gunawan -Original Message- From: Carl Youngblood [mailto:[EMAIL PROTECTED] Sent: Friday, June 18, 2004 6:18 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [OCF] Problem loading the right terminal class

Re: [OCF] Problem loading the right terminal class

2004-06-11 Thread Christophe Muller
Hello, Steven Ihde wrote: On Thu, Jun 10, 2004 at 04:26:09PM -0700, Carl Youngblood wrote: Is there a way that I can figure out which opencard.properties file is being used? strace java [...whatever...] 21 | grep -E 'stat|open' Also there is a small program from Jan Peter Hecking, from

Re: [OCF] Problem loading the right terminal class

2004-06-10 Thread Steven Ihde
strace java [...whatever...] 21 | grep -E 'stat|open' should give you a pretty good idea where it looks for opencard.properties and which one it ultimately winds up using. Look towards the end of the output; there will be a barrage of JVM-related stuff at the beginning. This can also help you