Problem with running the midlet class (Error with Installation suite )

hi everyone...
i have problem with running the midlet class(BluetoothChatMIDlet.java)
it keep showing me the same kind of error in the output pane of netbeans...
which is:
Installing suite from: http://127.0.0.1:49296/Chat.jad
[WARN] [rms ] javacall_file_open: wopen failed for: C:\Users\user\javame-sdk\3.0\work\0\appdb\delete_notify.dat
i also did some research on this but due to lack of forum that discussing about this,im end up no where..
from my research i also find out that some of the developer make a changes in class properties..
where they check the SIGN DISTRIBUTION...and also change the ALIAS to UNTRUSTED..after that,click the EXPORT KEY INTO JAVA ME SDK,PLATFORM,EMULATOR...
i did that but also didnt work out..
could any1 teach me how to fix it...
thanx in advance... :)

actually, i do my FYP on bluetooth chatting...
and there will be more than two emulators running at the same time..
one of my frens said that if u want to run more than one emulator u just simply click on run button..
and it will appear on the screen..

Similar Messages

Problems build/running the tux8 corba simpapp with g++

Dear All,
I am trying to build and run the tux8 corba simpapp in $TUXDIR/samples/corba/simpapp
on my solaris box. The docs
say that I should be able to just run runme.ksh but it doesn't
work. The problem seems to be that I am using g++ rather than
the expected sun C++ and g++ doesn't recognise buildobjclient
or buildobjservers -mt flag. I can strip that out, but I still
always get link errors. After much searching I found the
-G -fPIC flags for g++ which zaps the link errors but the binary
won't run.
Given that we won't change compiler, what is the clean solution?
Thanks in advance
Michael Shaw

I've had some correspondence with Micheal on this and it resolves
to "You can't link a g++ object with a SUN CC compiled library
(M3's) due to name mangling". Name mangling is the way a C++ compiler
ensures that a compiled object name is unique although the Method
(or member function) may be polymorphic and the same Method name
may exist in a number of Classes. The GNU g++ compiler deliberately
mangles differently with good reason, see this URL
http://www.delorie.com/gnu/docs/libg++/g++FAQ_49.html
Although I think of a number of ugly ways around this the easy
answer is to invest in a supported compiler.
You can of course use GNU compilers for regular C and C++ that
links to non-C++ libraries (such as ATMI). Martin.
On 21 Jan 2002 08:04:19 -0800,
Michael Shaw <[email protected]> wrote:
:Dear All,
:I am trying to build and run the tux8 corba simpapp in $TUXDIR/samples/corba/simpapp
:on my solaris box. The docs
:say that I should be able to just run runme.ksh but it doesn't
:work. The problem seems to be that I am using g++ rather than
:the expected sun C++ and g++ doesn't recognise buildobjclient
:or buildobjservers -mt flag. I can strip that out, but I still
:always get link errors. After much searching I found the
:-G -fPIC flags for g++ which zaps the link errors but the binary
:won't run.
:Given that we won't change compiler, what is the clean solution?
:Thanks in advance
:Michael Shaw
Martin Sullivan. The reply-to e-mail address is temporary to thwart spam.
If viewing from an archive try sullivan at zois &c. There is more on
Open OLTP at http://www.zois.co.uk.

Could not find the main class error with executable jar

Hello,
I have troubles creating an executable jar file and I ran out of ideas how to solve it so I would appreciate some help.
I have created a jar file with the export function in eclipse
the Manifest.MF file contains:
Manifest-Version: 1.0
Main-Class: view.AppTennisViewI tried starting the file with a batch file which contains following code:
@echo off
javaw -classpath c:\TennisHSQLDB_GC2\tennisApp.jar
@start javaw -jar tennisApp.jar
exitthe batch file and the jar are both located in c:\TennisHSQLDB_GC2.
When i try command line I get the same result.
I also tried alternate statements such as SET CLASSPATH iso javaw -classpath and including the classpath in the manifest file but no luck. It keeps given me the error: could not find the main class. program will exit
Anyone any suggestions for my problem?

nevermind, found it.
classpath in manifest was incorrect

Since installing Lion I keep getting the error message 'there was a problem connecting to the server. URLs with the type 'file:" are not supported"' How can I fix this?

since installing Lion I keep getting the error message 'there was a problem connecting to the server. URLs with the type 'file:" are not supported"' How can I fix this?

A Davey1 wrote:
Not a nice answer!
Posting "Check the 'More like this'" area and not simply providing the answer is a great way to make these groups worthless.
You're ignoring context. On the old Apple Discussion Groups I never posted replies like that, instead giving people relatively detailed answers. The new Apple Support Communities made things worse by introducing certain inefficiencies. Then came Lion. The flood of messages that came with Lion required a painful choice for any of the people who had been helping here: (1) Give quality responses to a few questions and ignore the rest. (2) When applicable, give a brief answer such as the one that you found objectionable. (3) Give up all the other normal activities of life and spend full time trying to answer questions here.
People who needed help with Lion problems seemed to have trouble discovering existing message threads that described how to solve their problems. I never posted the suggestion of "Check the 'More like this' area" without verifying that the help that the poster needed could be found there. Even doing that, what I posted saved me time that I could use to help someone else.
The people helping here are all volunteers. None of them is being paid for the time they spend here. They all have a life outside of Apple Support Communities. It's arrogant of you to demand that people helping here spend more time than they already do.

I'm being shown an error pop-up message periodically saying "There was a problem connecting to the server. URLs with the type 'file:' are not supported." I have a brand new MacBook Pro, and at no time am I actually having trouble connecting to the server.

I'm being shown an error pop-up message periodically saying "There was a problem connecting to the server. URLs with the type 'file:' are not supported." I have a brand new MacBook Pro, and at no time am I actually having trouble connecting to the server, but this message continues to pop-up several times a day at random intervals. Is there something I'm doing wrong? Or is my computer just having a glitch? Other than that, and a mildly sticking caps lock button, it's working perfectly.
Thank you!

Alright it didn't solve it. Any other suggestions?
I haven't suggested a solution yet. I want to know whether you still get the messages while Time Machine is disabled. Do you? If so, try any or all of the solutions proposed in this thread:
There was a Problem connecting to the...: Apple Support Communities

I keep getting an error message saying "There was a problem connecting to the server. URLs with the type "file:" are not supported." Can someone help me get rid of it.

I keep getting an error message saying "There was a problem connecting to the server. URLs with the type "file:" are not supported" Can someone help me locate and get rid of this error.

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

Since updating to mountain line, error message "There was a problem connecting to the server. URLs with the type "file:" are not supported" keeps popping up

Since updating to Mountain Lion in the last week, an error message keeps popping up. The graphic is the button with 3 stick men holding hands and the message is "There was a problem connecting to the server. URLs with the type "file:" are not supported". Any solutions found?

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

I upgraded to Lion yesterday. Now I keep getting and error message: there was a problem connecting to the server. URLs with type "file:" are not supported. What server?

I upgraded to Lion yesterday. Now I keep getting and error message: there was a problem connecting to the server. URLs with type "file:" are not supported. What server? How do I get rid of this.

Take a look at this link, https://discussions.apple.com/message/16156214#16156214

Running JAR files (Could not find the main class error)

Hi all,
I'm having a bit of a problem with my app. I created an application with the current Netbeans edition, containing multiple .class files, and a few .jar libraries that are needed too.
Now I'm having problems with running the .jar that the Netbeans creates, so I figured I'd make a one on my own.
Okay, this is what I have going on:
C:\MyApp\ <--- root for the application
C:\MyApp\src\ <--- this is where the .class files are
C:\MyApp\lib\ <--- here are the .jar libraries which are needed
C:\MyApp\jar.exe
C:\MyApp\Manifest.txt
Now I have a couple questions.
1. Is it ok that the .class files all have a "package MyPackage; " thing in the beginning?
2. How should I proceed on making the Manifest.txt file correctly? I have tried various different outputs and read a few topics here from how it should be done, but I just can't nail it. Currently my Manifest looks like:
Main-Class: MyPackage/Myapp
Class-Path: lib/xxx.jar lib/xxx2.jar lib/xxx3.jar
Any help would be appreciated! Thanks.

Oh, almost forgot:
3. The right way to create a jar? I used this:
C:\MyApp\jar cmf Manifest.txt MyJar.jar src\*.class
And system is Windows XP.

Getting an error msg while trying to run the java class from CMC

Hi All,
I am getting an error, while trying to run the java .class file, that which is imoported into CMC.
Error msg:
Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file
     at java.lang.ClassLoader.defineClass1(Native Method)
     at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
     at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
     at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
     at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     at com.crystaldecisions.sdk.plugin.desktop.program.internal.ProgramWrapper.main(ProgramWrapper.java:49)
I have imported .class file into CMC and trying to invoke the .class file by another java program from eclipse..When i tried to invoke the .class in cmc, i am getting an error msg, mentioned above. I thought there might be version conflict. So i changed the java complier version to 1.5 in my Eclipse. After that is done again i am facing the same problem.
Can anyone help me to resolve this issue?
Thanks in Advance.

i have installed BO SDK 3.1 , Service pack 3. It comes woth JDK 1.5 version. i have not done any chnages to it. I impoprted all the jar files related to BO into eclipse.
1) Actually, i am writing java code on eclipse. When i run code from the eclipse, it creates a session to cmc and creates folder structure what i need.
2) But the thing is, that code needs to run, when i import the .class file into cmc. The process how i imported the .class file to cmc.
Manage> Add> Program File-->Java (Check Box). In this way i added java class file from the eclipse workspace (class file from the bin directory).
3) So when i run the .class file externally by another java program or also when i log in to CMC and run that .class file, the instance shows sucess, but when i see the logfile i am getting an exception that which i mentioned above.
If my method is worng can you please let me know the stepts how to run java program in cmc.
Thanks in Advance

"there was a problem connecting to the server. URLS with the type 'file' are not supported"

i have a new macbook pro 13" and every 6 minutes or so it pops up a window that says "there was a problem connecting to the server. URLS with the type 'file' are not supported". it never seems to cause any problems but is supremely annoying. how can i make this come to an end?

I tried someone's solution of taking another external disc and plugging it in, then when it showed up and time machine asked if I wanted to use it or that someone might be trying to trick me, I chose not use it. Then I shut down my computer, plugged in the original Lacie, and rebooted the computer and all seems to work fine now-- the Lacie appears on my desktop and all seeems to be in working order. Who knows why or anything else,- as weird as it gets- but for now things seemed fixed--- maybe others can try this too-- it worked for me so far.

"There was a problem connecting to the server. URLs with the type "file:" are not supported. Why? What can be done to eliminate it?

After upgrading to Mountain Lion, I repeatedly get this message: "There was a problem connecting to the server. URLs with the type "file:" are not supported.
Why?
What can be done to eliminate it?

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

Message - There was a problem connecting to the server. URLs with the type "file:" are not supported

new macbook pro receving this message: There was a problem connecting to the server. URLs with the type "file:" are not supported. What is causing this and how do

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

There was a problem connecting to the server. URLs with the type "file:" are not supported. OK

I have just upgraded to Mountain Lion from Leopard, but now I keep getting this message when I open some web-pages and every time I wake the Mac up after going to sleep. For some odd reason I get it in Swedish sometimes (installed language) and some times in English...
There was a problem connecting to the server.
URLs with the type "file:" are not supported.
OK
What is this and how can I get rid of it. I use Firefox and have updated to latest version.

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

My Mac suddenly started getting a pop up message saying "There was a problem conecting to the server. URLs with the type "file" are not supported." My internet is working fine,no problem connecting. I just keep getting this message which I click off .

My Mac suddenly started getting a pop up message saying "There was a problem conecting to the server. URLs with the type "file" are not supported." My internet is working fine,no problem connecting. I just keep getting this message which I click off and continue working.

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

Problem with running the midlet class (Error with Installation suite )

Similar Messages

Maybe you are looking for