Missing Index Error

Post by **mr.vince** » Tue Nov 09, 2010 9:15 pm

Ok, this one here won't do anything to the index (we mailed about it), but maybe... just give it a try:

viewtopic.php?f=3&t=29

Post by **mr.vince** » Mon Nov 15, 2010 7:20 pm

Pix wrote:Hi,

I've tried my Kryoflux with several different drives including a Teac FD-55GFR which has been confirmed working on these boards. When I attempt to read the maximum track using dtc -c2 it returns maxtrack correctly. However when I've attempted to read a disk on any of the drives I always receive the following error:-

00.0 : The streaming device reported missing index - no disk in drive
00.0 : Read operation failed

What am I doing wrong?

Ok, for the record... the board was broken (guess something wrong with the index line?

). One off the list...

jossa · Post by **jossa** » Wed May 11, 2011 8:47 pm

Hi,
i just got my kryoflux REV c and a floppy drive (84) track which i ordered with the kryoflux. After setting things up (triple checking cables)
and then running dtc -c2 (drive seeking and all) and the drive was reported as max 83 track
everything was gonna be fine - or so i thought.
I then experienced the exaxt error as described in this thread when trying to create an amigados copy.
"However when I've attempted to read a disk on any of the drives I always receive the following error:-

00.0 : The streaming device reported missing index - no disk in drive
00.0 : Read operation failed"

I tried this a couple of times.
Then I tried dtc -c2 again , but now the drive wont start calibrating, dtc just reports "Device does not support Reset command"

Any suggestions on what to do next?

EDIT: ok, i reseted the kryoflux, and now it can happliy do calibration with dtc -c2
and then i get 00.0 : The streaming device reported missing index - no disk in drive
00.0 : Read operation failed"
again
(running on Ubuntu 64, latest updates)

EDIT2: log

sudo ./linux/dtc64 -ftest.asdf -i4 -l15
creaf: test.asdf
0006f81b: status=0
0006f82f: status=0
0006f843: reset=0
0006fc25: descriptor=KryoFlux DiskSystem/version=1.00/date=Nov 9 2010/time=20:17:35
0006fc39: device=0
0006fc4d: density=0
0006fc61: min_track=0
0006fc75: max_track=83
KryoFlux DiskTool Console, v1.00 beta 10, uiv.1, Feb 5 2011
(c) 2009-2010 KryoFlux Products & Services Ltd.
Developed by The Software Preservation Society, www.softpres.org
Licensed for private, non-commercial use only.

0006fc89: motor=1
0006ffd7: side=0
0006ffeb: track=0
0006ffff: stream=1
00070433: stream=0
00.0 : The streaming device reported missing index - no disk in drive
00.0 : Read operation failed

Enjoy your shiny new disk image!
Please consider helping us to preserve media and continue development:
www.softpres.org/donate

00070447: motor=0

Post by **mr.vince** » Wed May 11, 2011 9:14 pm

Could be damaged drive or board. Or stuck disk. Can you try another drive?

jossa · Post by **jossa** » Wed May 11, 2011 9:36 pm

Thanks for the quick reply - Dug out the drive from my ancient pc, and it works with -c2 (reported as 81 track) and dtc64 -ftest -i2 -l15 on an old amiga pd-disk
Or, it creates an image and logs doesnt report any error message at least:)
Indicates its the 84-track drive then?...

Post by **mr.vince** » Wed May 11, 2011 9:38 pm

Probably, yes. Or contact problem with the cable. Or disk. Please try some configs. If the drive is dead, email me (just answer to a shop email) and I'll sort it out. No worries.

jossa · Post by **jossa** » Wed May 11, 2011 9:44 pm

Thanks, ill try switching cables, and disks, and some more verifying with the drive that seems to work for comparison. Ill get back after that. Ltr!

Post by **mr.vince** » Wed May 11, 2011 10:27 pm

If you have an Amiga disk please try

DTC -i5

This should display valid readouts for AmigaDOS.

jossa · Post by **jossa** » Thu May 12, 2011 6:01 pm

Success!
After using old drive (same cables/settings) to generate an amiga adf (tried in emulator), i tried the 84-track again, and it seems it this time successfully could dump a raw image and and adf after another calibration. I dont know what the issue was, but now it seems to work. Thanks for the help. I need to order another kryo at somepoint in the future, these devices are just so cool.

Post by **mr.vince** » Thu May 12, 2011 9:27 pm

Well, the old cable trick... these ribbon cables and molex adapters just suck. Really, these connections are a nightmare. I can't count the times I was working on it, testing new boards or running new betas and things went sour. Then minutes later I found out it was a cable. Again...

KryoFlux^® Support Forums