"INVALID BLOCK" or"NO POWER"keeps appearing

[SoukinOKATU]

I have a physical FDS drive and a FDSKEY,And I have "The Legend of Zelda" and "Link's Adventure"(double side game),I first started duplifds with FDSKEY,then connect the RAM adapter to the physical drive to read the physical disk.
First is Zelda, but only the first time it read side A of the game correctly，then I changed to FDSKEY to prepare to write to the image, but the "NO POWER" error kept appearing,after many attempts, the image was indeed written, but the image was read error(dump failed).After restarting duplifds, I can no longer read any physical games. The prompt is always "INVALID BLOCK". Trying again and again has no effect.
I can confirm that my physical drive and original FDS games are fine, I can read and play them normally with the physical drive, and I can also use Disk Hacker to dump the games, but duplifds always thinks my disk has an "INVALID BLOCK" and refuses to read

[ClusterM]

Hi!
Can you say:

• Your console version (original Famicom, AV Famicom, etc.)
• DupliFDS version
• FDSKey firmware version
• Amount of blocks read before error

[SoukinOKATU]

Thank you for your reply. My situation is as follows:

1. I use both AV Famicom and third-party homemade "RGB FC" (fc that supports rgbs and vga video output), commonly using RGB FC

2. The duplifps I use are built with v1.1 and interim builds

3. fdskey firmware is v1.3

4. All blocks are not read at all, just stop reading and report an error

[ClusterM]

Please try old DupliFDS version - 1.0 (who knows, maybe it will work?) I'll try to test DupliFDS on those Zelda games. Can you take a photo of the error screen?
But the "NO POWER" message is very weird. FDSKey always reports that power is ok. I can remove this check if it continues...

[SoukinOKATU]

To be honest, there's nothing special, and screenshots don't make much sense. Just read➡️INVALID BLOCK➡️retry-a➡️INVALID BLOCK

[ClusterM]

Please try current interim version.

[SoukinOKATU]

Please try current interim version.

interim builds test result.

1.Test game: Zelda A-side

2.The first read was successful, and the number of blocks read was 11/16. Then, I connected to FDSKEY, and the data was successfully written.

3.After writing on 11/16,Software prompt:“Insert source disk”,connect the RAM adapter to the FDS drive and insert the disk,software prompts' Reading... ',then the magnetic head keeps resetting and cannot read the disk.

4.Restart the software, insert the disk again, and still prompt 'Reading...'. The magnetic head keeps resetting and cannot read the disk.

[ClusterM]

3.After writing on 11/16,Software prompt:“Insert source disk”,connect the RAM adapter to the FDS drive and insert the disk,software prompts' Reading... ',then the magnetic head keeps resetting and cannot read the disk.

Can you wait until timeout message? Error "READY TIMEOUT" or "READ TIMEOUT" should appear during 10-20 seconds.

[SoukinOKATU]

3.After writing on 11/16,Software prompt:“Insert source disk”,connect the RAM adapter to the FDS drive and insert the disk,software prompts' Reading... ',then the magnetic head keeps resetting and cannot read the disk.

Can you wait until timeout message? Error "READY TIMEOUT" or "READ TIMEOUT" should appear during 10-20 seconds.

I conducted some tests again:

First, the dump of the Zelda A side was successful. The first read was 11/16（It's strange that the image I dumped by DISK HACKER only has 7 files）, then it was connected to the FDSKEY and successfully written. After that, it was connected to the FDS drive and inserted into the disk. This time, it was successfully read to 16/16 and successfully copied to the FDSKEY. There were "Checking CRC" and "Success" messages.

But when I tried the B side, there was another problem: The B side first read 21/29, then connected to the FDSKEY and successfully wrote.

After receiving the FDS drive again, inserting the disk B side, the software was stuck in a "reading...", as if the head was still reading the track and resetting. I waited for about a minute, but it was still reading. Also, after ejecting the disk, the head and motor seemed to still be running with no sign of stopping.

After restarting the software, the reading returned to normal and 29/29 was read. However, when I connected to FDSKEY to write, although FDSKEY wrote 29 files, the software's "WR" always stopped at 21/29, and FDSKEY kept repeating the write operation without stopping.

That is to say, the software seems to suddenly fail to recognize the disk and will keep trying to read without stopping，I also tried v1.0 and the result was simple - 'INVALID BLOCK'

Occasionally successful 1-2 times, but most of the time it is constantly 'reading...' (interim version) or 'INVALID BLOCK' (V1.0-V1.1)

Also, I heard that some FDS drives in the later stage will prevent players from dumping the game by preventing a large amount of data from being read and written at once. I'm not sure if this is related to this reason

[ClusterM]

It's strange that the image I dumped by DISK HACKER only has 7 files

It's because DupliFDS shows blocks, not files. Blocks = 2 + files * 2.

Also, after ejecting the disk, the head and motor seemed to still be running with no sign of stopping.

Seems like application totally crashes :( Some power problem maybe? Which DC adapter(s) are you using?

[SoukinOKATU]

It's strange that the image I dumped by DISK HACKER only has 7 files

It's because DupliFDS shows blocks, not files. Blocks = 2 + files * 2.

Also, after ejecting the disk, the head and motor seemed to still be running with no sign of stopping.

Seems like application totally crashes :( Some power problem maybe? Which DC adapter(s) are you using?

Are you referring to the console AC adapter or the FDS drive AC adapter?

The console AC adapter is a nomal 6V 2A adapter (because it is a home made RGB FC, not an AV Famicom), and the FDS drive AC adapter is a 9V 2A adapter（Famicom model,internally negative）. Of course, I also use 6 batteries to drive it

I am now using AV-FAMICOM and testing again using a battery driven FDS (which should eliminate all interference):

Zelda A-side, The following situations have occurred

1.Successfully read 1-11 blocks，but FDSKEY does not write, prompt 'bad block, CRC error'

2.Successfully read 1-11 blocks and write to FDSKEY，Then reading blocks 12-16 failed,it has been 'reading...' and the motor and magnetic head are constantly moving,Software screen freezing

3.Occasionally, the software screen only contains your name and version, and it reaches the top of the screen, causing the screen to freeze

Overall, I only tested the Zelda A-side and successfully read and write 16 blocks once, and performed CRC verification. Afterwards, I only read and write 1-11 blocks or did not read them directly.

Zelda B-side, 29 blocks, only successfully read and write 1-22 blocks once, and has never been successful since 22-29.

（However, it's incredible that I actually succeeded just now. Both sides A and B were successful, which is strange）

[SoukinOKATU]

It's strange that the image I dumped by DISK HACKER only has 7 files

It's because DupliFDS shows blocks, not files. Blocks = 2 + files * 2.

Also, after ejecting the disk, the head and motor seemed to still be running with no sign of stopping.

Seems like application totally crashes :( Some power problem maybe? Which DC adapter(s) are you using?

I may have discovered some clues
Previously, when the software read half of the block and needed me to connect to FDSKEY, I would directly unplug the RAM adapter and insert it into FDSKEY. At this time, the disk did not exit the floppy drive. If the drive was read again in this state, it is likely to cause strange problems in the software (even if I unplug and then exit the disk)

I just tried again. As long as I enject the disk every time and plug it in and out, the copying process will end normally,

[ClusterM]

Are you referring to the console AC adapter or the FDS drive AC adapter?

Both of them.

The console AC adapter is a nomal 6V 2A adapter

6V? I don't know how your homemade FC is designed. At least it's not enough for original Famicom.

I may have discovered some clues
Previously, when the software read half of the block and needed me to connect to FDSKEY, I would directly unplug the RAM adapter and insert it into FDSKEY. At this time, the disk did not exit the floppy drive. If the drive was read again in this state, it is likely to cause strange problems in the software (even if I unplug and then exit the disk)
I just tried again. As long as I enject the disk every time and plug it in and out, the copying process will end normally,

Looks totally as power problem for me. I'll add delay between disk insertion and motor start. Maybe it will help. Please try current interim version.

[SoukinOKATU]

I later encountered similar issues when using av famicom and 9V power supplies. I will continue testing the new version and give you a response later (I am located at UTC+8 and currently working)