Closed GoogleCodeExporter closed 9 years ago
Get the last jar bluecove-2.1.0-20081122.060125-15.jar from build server.
http://www.pyx4me.com/maven2-snapshot/net/sf/bluecove/bluecove/2.1.0-SNAPSHOT/
The main site has a link: "Nightly BlueCove Build" http://snapshot.bluecove.org/
The Nightly build site has a left menu "Download" -> "Snapshot"
And please use "Attach a file" when uploading stack traces!
Original comment by skarzhev...@gmail.com
on 26 Nov 2008 at 2:44
[deleted comment]
The answer is simple:
I don't have IPaq so I can't test the BlueCove build on this hardware.
So I can't say it runs or not.
If you would be so kind to join the project and report every now and then the status
of IPaq support then it would be helpful.
Also the version 2.0.1 and 2.0.2 should be identical to 2.1 from Windows CE point
of view. Simple 2.0.3 had glitch in build, I'm changing this...
Vlad
Original comment by skarzhev...@gmail.com
on 26 Nov 2008 at 1:56
[deleted comment]
[deleted comment]
The project is hosted on sf.net and google code. So you need sf.net to Edit WIKI
pages on sf.net and google account to commit to SVN and edit WIKI pages on
google site.
All talking should be done in Groups/mailing lists.
The build system is maintained on build server by Pyx Software Services, Only
Me and
Michael has access to the build system https://pyx4j.com and this is not
negotiable
now since this is private system.
For you I can suggest to use http://bluecove.wiki.sourceforge.net/
The google code does not give a different privileges to developers and testers
now.
So for all the testing docs the sf.net should ne used.
Original comment by skarzhev...@gmail.com
on 27 Nov 2008 at 2:19
[deleted comment]
You can always remove the dll from the jar and place it them in folder
accessible by
JVM all should work if the stack is working.
So what you should do is:
1. Identify the stack your system has.
Use intelbth_ce.dll or bluecove_ce.dll
-Dbluecove.native.resource=false
-Dbluecove.stack=widcomm
-Dbluecove.stack=winsock
(I think that Windows Mobile 5 has MS stack NOT widcomm)
2. Try different JVM, Different JVM version I used Mysaifu JVM Version 0.3.4
on my
Dell AXIM X30.
3. Try compiling dlls using different MS SDK.
I would probably have a budget and time to buy Mobile 5 device next year. And
see for
myself, until then ... I only know what have been reported in mailing list by
users.
Original comment by skarzhev...@gmail.com
on 27 Nov 2008 at 4:11
[deleted comment]
[deleted comment]
1) Motorola MPx220, Windows Mobile 2003 Phone Edition
Microsoft Bluetooth stack
Used Mysaifu JVM Version 0.3.4
2) Dell AXIM X30, Windows Mobile 2003 SE (WinCE 4.21)
Broadcom Bluetooth stack BT-PPC 1.5.0.4300
Used Mysaifu JVM Version 0.3.4 and 0.3.6
Tested the BlueCove 2.0.2, In version 2.0.3 I made an error during final build
so it
will not work on ms stack.
Original comment by skarzhev...@gmail.com
on 27 Nov 2008 at 7:05
[deleted comment]
[deleted comment]
You can't take BlueCove DLL from one version and use it with classes from jar
from
another build.
e.g. 2.0.3 dlls will not work for 2.1 classes.
Every dll has a version inside just look Using Windows Explorer. Also each jar
has
manifest. That contains the version information.
The 2000277 is the dlls from 2.0.2 build the classes you have are 2000399
2.0.3
This was specialy done becuase we are changing signatures of some functions
from time
to time and wnat to avoid the Runtime errors.
Original comment by skarzhev...@gmail.com
on 27 Nov 2008 at 11:18
[deleted comment]
PLEASE Please, Please, Please, Please STOP this! Use E-mail.
The bug is not a place for general discussions.
I can't help you to find the dlls or jars on your computer. Just see what is in
the
path or do a general search for the dll. You know the name.
If Does not help reinstall windows.
Then start from scratch, Recording in some text file what you are doing and what
version of which files you are placing in what location.
When you copy the dll to Windows XP in explorer you can see the dll version.
Also If you open the jar using Winrar or Winzip you can see the context of
manifest file.
!!!!!!! DO NOT REPLY TO THIS BUG REPORT ANYMORE !!!!!!!!
Original comment by skarzhev...@gmail.com
on 27 Nov 2008 at 11:42
Attachments:
[deleted comment]
Hi André
I would reply to your e-mail but I don't know it so I will repeat myslef!
As I told Use: skarzhevskyy@gmail.com or group bluecove-users@googlegroups.com to
ask the questions.
I can't teach you how to use Windows CE. And I see this what you want from the
thread! The HOWTO use Windows was never a topic for BlueCove project support!
If you want to discuss the best way to work with Windows CE you are welcome. But not
here! The benefit of using googlegroups is that they are search able and it
would be
easy for others to find the problem and solution.
Also in googlegroups somebody else will help you with advice.
In the issues only I will answer. And so on.....
Yes I made the fatal mistake by not testing the version 2.0.3 build. But previous
version 2.0.2 and next version 2.1 are all OK and tested by users. And this bug
is
all about this! And I can't close the issue because the current Release 2.0.3
has
this build problem. And only once next version is released the bug would be
closed.
So André I value your persistence but.
!!!!!!! DO NOT REPLY TO THIS BUG !!!!!!!!
!!!!!!! De ne pas répondre !!!!!!!!!
!!!!!!! НЕ ОТВЕЧАЙ БОЛЬШЕ !!!!!!!!!
Original comment by skarzhev...@gmail.com
on 28 Nov 2008 at 12:16
Original comment by skarzhev...@gmail.com
on 22 Dec 2008 at 8:22
Original issue reported on code.google.com by
kou...@telfort.nl
on 26 Nov 2008 at 2:07