Support of 32bit .pst

[GoogleCodeExporter]

As I understand, from the last releases of java-libpst was removed the 
exception:

PSTException("Only 64bit PST files are supported at this time")

It's a very good news! Thank you!

In the attached 32bit .pst database I've got following messages in console:

Unknown message type: I  P  M  .  N  o  t  e
        49 50 4d 2e 4e 6f 74 65

String under debug is: "I  P  M  .  N  o  t  e  \n\t49 50 4d 2e 4e 6f 74 65 "

What steps will reproduce the problem?

PSTFile pstFile = new PSTFile("archiv32bit.pst");
PSTMessage message = (PSTMessage)PSTObject.detectAndLoadPSTObject(pstFile, 
2097188); 
PSTMessage message = (PSTMessage)PSTObject.detectAndLoadPSTObject(pstFile, 
2097220); 

What is the expected output? What do you see instead?

"I  P  M  .  N  o  t  e" or "IPM.Note"

What version of the product are you using? On what operating system?
Last, from SVN. Windows XP.

Please help me with this issue.

Regards,
Maxim

Original issue reported on code.google.com by justpdat...@gmail.com on 13 Oct 2010 at 9:07

Attachments:

• archiv32bit.pst

[GoogleCodeExporter]

Thanks for bringing this to our attention, I'll check it out and let you know 
what I find out!

Original comment by rjohnson...@gmail.com on 13 Oct 2010 at 9:34

[GoogleCodeExporter]

Okay, I could not replicate this after a quick test, so I'm thinking it may be 
something to do with your default charset being different to mine.

The library falls back to the default charset for the occasional string when 
performing operations like determining what type of message it's dealing with.  
It does a "IPM.Note".equals(messageIdentifier) to check for a normal email, and 
in your instance this is not matching.

I've committed a quick patch to SVN which makes the library use UTF-8 for these 
strings.  Could you possibly check it out and let me know if this has resolved 
the issue?

Thanks,

Richard

Original comment by rjohnson...@gmail.com on 15 Oct 2010 at 9:47

[GoogleCodeExporter]

Thank you! All works fine with default charset and with UTF-8.
Now I could not repeat this issue too, so you may return code to previous state.

Regards,
Maxim

Original comment by justpdat...@gmail.com on 18 Oct 2010 at 9:21

[GoogleCodeExporter]

Cool, marking this as closed...

Original comment by rjohnson...@gmail.com on 18 Oct 2010 at 10:09

• Changed state: Done