Hi, and thanks for the replies. Your support is really valued.
There must be something else wrong.
I have read those three threads, and fully understand that it is the pixelsizes, not the filesizes that matters.
(Though the error message states it was the filesize.) Being a developer myself (newbie in PHP though...), I fully recognize these issues.
But, as I said, I have allocated 64MB memory to each process in my php.ini. That should be enough, shouldn't it? Even though the pixels are 2272x1704x16M. (I successfully upload 1600x1200x16M without problems.) I will try to increase this setting, but I hope the memoryhandling of the convertutility is a bit more memoryefficient than that? I use ImageMagick (as recommended by hyperion in http//coppermine.sourceforge.net/board/viewtopic.php?t=3417), the majority of issues in these treads deal with GD?
Of course I can resize the images before uploading them, but I can't make that demand of my familymembers that want to upload their pictures. They haven't got the computerskill to do that, it's a pain teaching them how to use a browser... Bandwidth isn't an issue, as I don't care for people with less than 1Mbit. ;-)
The fact that the errormessage states the 2048kB limit (which I can't find anywhere in any setup, since I have set this to 4096kB in the Coppermine setup), makes me suspect this is a limit set in the code somewhere? Perhaps for debugging purposes, and perhaps forgotten? Not very probable though, since this then would have been discovered earlier.
Nevertheless I suggest this error to be found and caught, and that a more relevant errormessage is displayed in 1.3?
Another possible reason is that I use mySQL4.1.1. I know that other similar software projects don't yet support this new mySQL version?
There could of course also be a setting in php, Apache, Coppermine or where ever , that I don't know about, being a php newbie?
I know Apache has a POST size setting, but I have left that unlimited.
regards
John