Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development

Reply
Developer
Developer
gtj
Posts: 319
Registered: ‎07-20-2008
My Device: Not Specified

Issues with simulators from 4.5.0 Component package

Anyone else having these issues...

 

The simulators won't exit cleanly.  I have to kill fledge.exe from the task manager, then also kill bbdevmgr.exe or when I restart the simulator, I won't have USB connectivity.  Using the 4.5.0 jdwp, I can start and stop the standalone simulators (8830-Sprint, 8300-Rogers, 8130-Verizon)  and they work fine.  It's the 4.5.0 embedded sims that seem to be the problem.

 

The 8830-JDE simulator only responds to the EDGE network and then only with SOS.  I can't figure out how to get the radio to work.  It also doesn't seem to have GPS although it does in real life.

 

Finally, when starting jdwp, I always get a popupthat states "Cannot find RIMIDEWin32Util.dll.  This is a required component of the IDE."  

 

Running the 4.5.0 Component package on Vista Ultimate 64bit.

 

Thanks...george

 

Please use plain text.
Administrator
MSohm
Posts: 14,429
Registered: ‎07-09-2008
My Device: BlackBerry Z30, BlackBerry PlayBook
My Carrier: Bell

Re: Issues with simulators from 4.5.0 Component package

The RIMIDEWin32Util.dll should be present within the installation directory of the BlackBerry JDE Component Pack.  Can you verify if it is present?

 

We have heard other reports of issues with the version 4.5.0 BlackBerry JDE Component Pack on Vista.  This is under investigation.  As a work around you can use the stand alone simulators and simulator and JDWP that is included with the version 4.5.0 BlackBerry JDE. 

Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
Found a bug? Report it using Issue Tracker
Please use plain text.
Developer
Developer
gtj
Posts: 319
Registered: ‎07-20-2008
My Device: Not Specified

Re: Issues with simulators from 4.5.0 Component package

Hi Mark,

 

Yep it's present but it just dawned on me that I'm running the 64bit JVM and it's a 32bit library.  Sure enough, when I run jdwp from a 32bit jvm, it doesn't complain about the missing dll.  It's an easy work around but do you guys have plans to start distributing 64bit versions?

 

george

 

 

 

Please use plain text.
Administrator
MSohm
Posts: 14,429
Registered: ‎07-09-2008
My Device: BlackBerry Z30, BlackBerry PlayBook
My Carrier: Bell

Re: Issues with simulators from 4.5.0 Component package

Unfortunately we are not able to comment on possible future releases.
Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
Found a bug? Report it using Issue Tracker
Please use plain text.
New Developer
nophadon
Posts: 1
Registered: ‎05-12-2009
My Device: Not Specified

Re: Issues with simulators from 4.5.0 Component package

I am running Max OSX, have Eclipse Ganymede installed and installed the Blackberry JDE. When i try to launch Eclipse I get the same error message:

 

Cannot find RIMIDEWin32Util.dll. This ia a required component of the IDE

 

Am I not able to build BB apps via the Mac? Is there something else I need to install.After seeing this error, my Mac is completely dead and I am forced to restart... not good....

 

Thanks for your help!

Please use plain text.
Developer
babygodzilla
Posts: 275
Registered: ‎03-10-2009
My Device: Not Specified

Re: Issues with simulators from 4.5.0 Component package

i am also having the same problem on OSX and Ganymede. What do I do?
Please use plain text.
New Developer
eazyigz
Posts: 2
Registered: ‎12-24-2009
My Device: Curve
My Carrier: verizon

Re: Issues with simulators from 4.5.0 Component package

I'm also getting an error "Cannot find RIMIDEWin32Util.dll. This ia a required component of the IDE" in Windows 2008 Server x64.  It used to work fine yesterday.  I don't know what changed!

Please use plain text.