I am using beta 5 and have run in to a problem trying to work with the Command line Interface with Folding@Home. I can open the Command console fine but when I try to type in it, it takes a minute or so for each keystroke to appear in the window. Anyone else? Ideas? Rick
Is this in Windows? Are you running 'command' or 'cmd'? If you are running Win2kX or XP, use 'cmd', not 'command'. As an experiment though, if you type a bunch of characters and then go wave the mouse around, do the keystrokes all show up all of a sudden? I had some behavior like that trying to run 'edit'.
That's it! Been away from Windows too long, thankfully! cmd works fine. BTW, for those "Folders" out there, Parallels works fine for running Folding@Home. I am able to run about the same points as I get running one process in Boot Camp and don't have to reboot at night. Thanks Brian
