Bronco Posted June 28, 2003 Report Share Posted June 28, 2003 After Retro stops I have to reboot to get started again. Retro gobbles up 40-55% of cpu apparently doing nothing and taskmgr can not stop it. This happens with several files, but for this discussion I only talk about one. Using a selector (confirmed by looking in the test selector run) I exclude this file from a backup but while the snapshot is being done, when Retro gets to this file it freezes and requires a reboot. any ideas. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.