I’ve driven myself batty – not a long trip – trying to convert a large existing project to 2.0. It’s a huge project, with lots of research files in it – 1.93gb. I exported a great deal of the research and got it down to 900 gb. No matter. It always conks out at some point. It’s not running out of ram. Checked that. It just seems to get to a certain point, then hangs on one file (different files each time) and just churns on forever with no progress; either that, or it crashes.
2.0 looks wonderful, but I’ve wasted a lot of time trying to convert to it. I’m going back to the old version for now. Have to, since I need to get my work done.
If you have some time to give it another shot check to see if console shows any errors. Also if you can provide OS version that might help. If you do see a console log put it up and we might be able to see a pattern to get you working while KB and crew get to the lower levels of the problem.
Thanks for the feedback. There is an awful lot of processing that needs to be done to upgrade a project, and some of it can be very time consuming if the project is physically large. It has to first make a backup copy, so that’s going to take a while just based on how fast your disk can run, then parse and reformat the entire internal structure of the project.
If you do get some time, if you could do some console checking like Jaysen suggests, that would help pin-point the failure and hopefully get the upgrader optimised for large projects.
By the way, once you do move into 2.0, you’ll want to familiarise yourself with the File/Backup/Exclude from Automatic Backups project option! You would not want a 2gb project to backup to zip every single time you quit a Scrivener session.
You can post them to support AT literatureandlatte DOT com, or paste them here in the forum. They are just error messages and do not contain private information.
