On Wed, 2007-12-05 at 23:24 +0100, Guido Diepen wrote: > > Aha, ok that applies easier and compiles cleanly, but I get errors with > > the new synce-registry tool. > > What kind of errors? > > > > > Top of my head, I'm on WM2003, which if I understand rapi correctly uses > > the version 1 calls. Would your changes have affected these badly ? > > You are correct, from wm5 on automatically the rapi2 ops are used. > > I looked into the code, but rapi_buffer_read_string is not used in rapi, only > in rapi2. > > The only thing that I can think of is that handling certain NULL parameters, > for values you are not interested in goes wrong. > > Does anybody know whether what is actually sent over the wire differs a lot > between rapi and rapi2? > > If you could provide me some info of what exactly goes wrong I might be able > to figure out what is causing the errors in your case. (Problem is that I > don't have WM2003 device, only WM6....) >
Short answer is error code 31 from CeRegEnumValue in list_key() using synce-registry tool. I think there may actually be a problem with CeRegQueryInfoKey and CeRegEnumValue (in registry tool) in rapi1, the results I got back from a bit of testing were unexpected. In fact I've written myself a reminder comment in my gtk registry tool about CeRegEnumValue not being reliable. I've had a quick look, I don't really know enough about rapi though, want to give me any tips from when you fixed the rapi2 versions ? Mark ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
