Search found 43 matches

by wuffe
Sun Oct 23, 2011 1:13 pm
Forum: Support
Topic: Can KryoFlux detect drive capabilities ?
Replies: 16
Views: 5547

Can KryoFlux detect drive capabilities ?

First of all sorry if this question is plain and simple stupid - but I do not have access to my KryoFlux for the next couple of days and hence cannot test this myself. Can KryoFlux detect drive capabilities such as [SS/DS], [SD/DD/HD/QD], [48 TPI,96 TPI,100 TPI] ? I'm specifically asking in respect ...
by wuffe
Sat Oct 22, 2011 10:14 am
Forum: Feature Requests
Topic: GUI improvement - combine/reduce the tabs
Replies: 15
Views: 5487

Re: GUI improvement - combine/reduce the tabs

karadoc wrote: Thanks for the feedback!
Thank you for your quick and swift reaction :-)
by wuffe
Sat Oct 22, 2011 10:00 am
Forum: Feature Requests
Topic: GUI improvement - combine/reduce the tabs
Replies: 15
Views: 5487

Re: GUI improvement - combine/reduce the tabs

Yeah, I know what you mean. ... There is also some more info for the summary tab that has not been activated yet (e.g. estimated completion time). With that in mind, maybe we should put the summary information somewhere else? Not sure where. Perhaps on the status bar? A status bar would be a great ...
by wuffe
Fri Oct 21, 2011 9:26 pm
Forum: Feature Requests
Topic: GUI improvement - combine/reduce the tabs
Replies: 15
Views: 5487

GUI improvement - combine/reduce the tabs

Hi, I'd like to suggest an easy GUI improvement: Please combine the "Track" and "Summary" tabs into one - I find myself always flipping back and forth between these two tabs. Their contents logically belongs together. And frankly the limited amount of info on the "Summary" tab is a kind of "lonely" ...
by wuffe
Mon Jul 18, 2011 10:51 am
Forum: Support
Topic: Device does not support Reset command
Replies: 14
Views: 4147

Re: Device does not support Reset command

mr.vince wrote:See news for changelog. Apart from that, it's the same codebase (same beta, same binary). The GUI was changed.
Ah - that explains - thx :-)
by wuffe
Mon Jul 18, 2011 8:53 am
Forum: Support
Topic: Device does not support Reset command
Replies: 14
Views: 4147

Re: Device does not support Reset command

hi, I haven't found any changelog documenting the changes/fixes for the recent kryoflux release - so I cannot say if you've made an attempt to actually address this issue. Anyway this is just to let you know that problem still persists with the recent kryoflux release (Linux v1.0 Beta 10 release 4, ...
by wuffe
Mon Jun 13, 2011 9:01 am
Forum: Support
Topic: Device does not support Reset command
Replies: 14
Views: 4147

Re: Device does not support Reset command

How about changing the error message? If it said something like "Device busy, try again shortly" it wouldn't make you wonder whether something had gone wrong. "Device does not support Reset" originally made me think the firmware had locked up or something so I was power cycling the KF, until I real...
by wuffe
Sun Jun 12, 2011 7:57 pm
Forum: Support
Topic: Device does not support Reset command
Replies: 14
Views: 4147

Re: Device does not support Reset command

No, but as I said if the device (KryoFlux) refuses to do something because it's busy the correct behaviour is to bail. I could imagine a GUI or other frontend retrying in this case though, but not DTC. I don't think you understand the problem - problem is seen both with DTC and GUI. If a KF CLI/GUI...
by wuffe
Sun Jun 12, 2011 6:50 pm
Forum: Support
Topic: Device does not support Reset command
Replies: 14
Views: 4147

Re: Device does not support Reset command

DTC tries to reset the device, but it refuses to accept the command as it is busy. This is correct behaviour, otherwise the command sent would be lost. All you have to do is to wait if you see/hear the drive is moving the head. Need some clarification here before I understand what you mean with cor...
by wuffe
Sun Jun 12, 2011 10:04 am
Forum: Support
Topic: Device does not support Reset command
Replies: 14
Views: 4147

Re: Device does not support Reset command

Malvineous wrote:But IIRC this is just a timeout message, and the next dump works fine.
It is just a timeout message - but an annoying one that requires you to issue a dummy command between every dump.