Hello, I maintain Gnumeric and have run into a problems when writing xls files larger than 13-14 meg. MS excel can read them, but promptly corrupts them. I had hoped this was a windows bug, but just in case I installed an older copy of cross over office with office 2k. That combination produced exactly the same sort of corruption. That is likely good news to wine developers, your emulation is excellent. It also means that the problem is clearly on my end.
A sample file is http://www.gnome.org/~jody/bigfile.xls.bz2 (bunzip2 and keep a copy because it gets corrupted)
Loading it into MS Excel works smoothly, but subsequent reloads fail and the file is corrupt. It seems like the extended meta block allocation tables are being lost for some reason.
Are there any OLE2 file format experts about that might have some insight ?
Many Thanks Jody
PS Please CC me on responses, I am not subscribed to the list.
On Wed, 2003-12-10 at 08:10, Jody Goldberg wrote:
Hello, I maintain Gnumeric and have run into a problems when writing xls files larger than 13-14 meg. MS excel can read them, but promptly corrupts them. I had hoped this was a windows bug, but just in case I installed an older copy of cross over office with office 2k. That combination produced exactly the same sort of corruption. That is likely good news to wine developers, your emulation is excellent. It also means that the problem is clearly on my end.
Be very careful here - if I recall correctly CrossOver uses Microsofts OLE implementation, not ours. I'd check in the config file that Excel is definately using native ole32, oleaut32, and rpcrt4 before coming to any conclusions about where the bugs lie.
I assume Excel can write files >14mb and read them back again fine yes?
thanks -mike
On Wed, Dec 10, 2003 at 07:36:45PM +0000, Mike Hearn wrote:
On Wed, 2003-12-10 at 08:10, Jody Goldberg wrote:
Hello, I maintain Gnumeric and have run into a problems when writing xls files larger than 13-14 meg. MS excel can read them, but promptly corrupts them. I had hoped this was a windows bug, but just in case I installed an older copy of cross over office with office 2k. That combination produced exactly the same sort of corruption. That is likely good news to wine developers, your emulation is excellent. It also means that the problem is clearly on my end.
Be very careful here - if I recall correctly CrossOver uses Microsofts OLE implementation, not ours. I'd check in the config file that Excel is definately using native ole32, oleaut32, and rpcrt4 before coming to any conclusions about where the bugs lie.
Good thought. When using wine's builtin ole32 things work smoothly. It looks like we're back to calling this a win32 bug, rather than a feature. The problem is likely related to the fact that I put all of the extended block allocation tables at the end of the file.
I assume Excel can write files >14mb and read them back again fine yes?
yes It can also load larges files generated by OO without corrupting them (although it brought my machine to its knees generating one).
-
Jody Goldberg -
Mike Hearn