I have had problems with importing older files and adding websites/bookmarks to DT 2. I am using a MacBook Pro with 2 GB memory. Any thoughts on what to do or how to reinstall the new DT 2?
Thanks in advance,
Patrick
Managing two versions of an application: I have DT Pro Office 1.5.4 and the current public beta of DTPO 2 in separate folders in my Applications folder, each folder containing the additional files for that version including the Extras folder, user documentation, etc.
I don’t recommend having both applications available at the same time, in case of possible confusion by Services and scripts that might open the “wrong” application in order to send data.
So I use the contextual menu option to zip (compress) the application that I’m not going to be using for a while, then delete the application file afterwards and empty the Trash. When I need to use that application again, I don’t have to re-download it; just unzip it (and zip the other version, then delete it from Applications). Then a logout/login will assure that Services are set for the application to be used.
I do need to switch back and forth occasionally, for example, to check out a Support issue in the version 1.x applications. But I’ve actually switched to using DT Pro Office 2.0 for my working databases, beginning several pre-release betas ago.
Depend on the beta for work? The decision as to whether to depend on a beta application for important work is up to the user. The public beta release has undergone internal testing, then gone through a series of betas released to a volunteer group of users. But no amount of testing in these ways can cover all the possible variables of hardware and software environments in the larger user community. That’s why this is a beta release, and the developers are seeking information that can lead to improvements for the final release. Some problem reports may be useful for that purpose; others may indicate problems at the user’s end, and can be helpful for diagnosing and recommending best practices. User comments and suggestions about features and operations are also welcomed.
There will be a final release of version 2.0 of DEVONnote and the DEVONthink applications. But that won’t be the end of development. There will be continuing improvements over time through free updates in the 2.x series, including responsiveness to user suggestions. But not each and every suggestion made by kalisphoenix. 
Back it up! It’s always a good idea to do frequent backups when using beta software. And it’s a good idea to keep that practice up when the application is released in final form, as well. Just finished writing the Great American Novel, or added something that’s very important? Don’t wait for a scheduled backup; do it now. Don’t assume that your important data is completely protected by an internal backup, or another backup on your hard drive, or even a Time Machine backup on an external drive. What happens if your hard drive fails, your laptop is stolen, your home is burglarized, your house burns down? Would you lose everything? If it’s important, “buy insurance” by managing offsite storage on physical media or a trusted online storage.
How to submit feedback:
-
The user forum - a good vehicle for user discussions. There’s a lot of information (and a bit of noise at times) here. Take a look at the recent thread topics that may relate to your interest. Experienced users can be very helpful to newcomers. Civility of discourse is encouraged.
- Bug reports - as suggested in the DEVONthink 2.0 UPGRADER’S GUIDE (link on page 7), the ticket system can be used to report possible bugs. Try to provide as much specific information as possible, but as concise as possible. If there is a related crash report and/or Console messages, please include them.
- Support queries (Help > Support) - feel free to ask questions, report problems and make comments. We’ll respond as quickly as possible. Most queries are answered within a day (sometimes in minutes). At the moment, Eric, Annard and I are wading through hundreds of queries, most of which deal with upgrading and license code issues. Tricky issues are referred to Christian, especially those with substantial included information such as crash reports, and it may take him a while to diagnose a problem.
Bill:
Please make your post into the sticky/FAQ it deserves to be.
Another benefit, besides being easily referred to, is updating outdated information in a single location, if necessary.
Less redundancy helps reduce the support load for everyone’s sake, too.