Hardware and OS Specifications for the KODAK PROFESSIONAL HR 500 Film Scanner

DP2 Systems Requirements and Guidelines

Due to the dynamic nature of systems available, it is difficult to give a fixed set of requirements and still have such a system available in a few months. Therefore, this document is to be used as a guide when selecting a workstation for running DP2.

DP2 has been tested with Windows 2000 and Windows XP Pro and Server 2003 operating systems. Currently no testing has been done with the newly available 64-bit operating systems.

As a guideline, it is expected DP2 will work with new Microsoft operating systems within a year of their release and testing will only be done on the two most prevalent operating systems available at the time.


DP2 uses multiple threads to perform many tasks at the same time. In doing so it utilizes multiple processors and hyper threading to quickly perform all requested tasks, such as creating order items, rendering images, updating the database, etc. Depending on the required task and the processor capacity available, DP2 may saturate the processor at 100%. This would indicate that the processor is a bottleneck, and will slow the system performance. Depending on the lab workload this may be acceptable. However, if the workstation performance needs to be improved a processor of a higher clock speed, a second processor, or processor with hyper threading should be considered. To view the % of system CPU capacity DP2 is utilizing, you can use the Task Manager built into Microsoft’s operating systems. To view the % of system CPU capacity DP2 is utilizing, you can use the Task Manager built into Microsoft’s operating systems. The Performance tab displays a dynamic overview of your computer's performance. The Processes tab shows information about the processes running on your computer. It can be helpful to evauluate "CPU time" on this tab. Care must be taken to keep the information in context. For example – if a system is turned on and the Processes tab is viewed 24 hours later. It might show that “System Idle Process” has 16 hours of time logged and DP2 has 8 hours. If the lab is running 24 hours a day this means that DP2 is using 30% of available capacity. However. if the lab is running one 8 hour shift and the system is left turned on for 24 hours – DP2 is using 100% of the available capacity during the working shift.

Running an HR 500 scanner and rendering are the two most processor intense tasks that DP2 performs.

RAM Memory

For a workstation that will be used for scanning or rendering, we recommend 1GB of RAM. On a cost-benefit basis additional memory is most likely to be the best investment for improved performance up to 1GB .


Hard Drive

With the wide range of specific lab needs and options for storage; the best we can offer are some guidelines.

  • Have several gig of free space available before installing DP2.
  • Practice good house keeping techniques by cleaning up unused files on your drives.
  • Defragment your drives at regular intervals.


Disaster Recovery

DP2 provides tools for backing up or archiving the database. These tools are intended to help you put a disaster recovery plan in place. By themselves they do not provide a complete plan, nor were they intended to. Due to all of the configuration options available and variations among labs, it is impossible for us to backup images, layouts, subject info tables or other lab specific information, which should all be included in a complete disaster recovery plan.

You need to create a complete disaster recovery plan in order to ensure that all your systems and data can be quickly restored to normal operation in the event of a natural disaster (for example, a fire) or a technical disaster (for example, a two-disk failure in a RAID-5 array). When you create a disaster recovery plan, you prepare all the actions that must occur in response to a catastrophic event. It is recommended that you verify your disaster recovery plan through the simulation of a catastrophic event.

Consider disaster recovery planning in light of your own environment and business needs. For example, suppose a fire occurs and wipes out your lab. Are you certain you can recover? How long will it take you to recover and have your system available? How much data loss can your lab tolerate?

Ideally, your disaster recovery plan states how long recovery will take and the final database state the users can expect. For example, you might determine that after the acquisition of specified hardware, recovery will be completed in 48 hours, and data will be guaranteed only up to the end of the previous week.

A disaster recovery plan can be structured in many different ways and can contain many types of information. If you need to learn more about this, please search the web or find a local consultant.



Individual lab needs vary and must be handled on a case by case basis.