News:

Printed Amstrad Addict magazine announced, check it out here!

Main Menu
avatar_littlangel

3.5" drive on Amstrad CPC 464 "bad command"

Started by littlangel, 10:41, 21 June 20

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

littlangel

Hello there.

So I got a NEC FD1231H 3.5 drive that I connected to a DDI-1 interface with the following modification http://www.cpcwiki.eu/index.php/DDI_Modification and the ready signal enabled.
However, when I try "cat" or "|B" I see the drive spinning, then "bad command".
Any help with this issue? Thanks in advance.

Bryce

If you are getting "Bad command" it means that the ROM in the DDI-1 hasn't initialised. Possibly it's not getting power. Can you post a picture of your mod (PCB and DDI-1 cable)?

Bryce.

geebus

I just tried to add a 3.5" drive to my ddi-1 interface too. Didn't work on either of my 464's.
I made a test board so that I wouldn't have to try modify either the drive or the DDI-1. When that didn't seem to work, I thought it was my board, so I done the internal 5v mod on the ddi-1. Still nothing.
Getting Syntax error or something. will need to check again.
Must not be getting power or just isn't working.

GUNHED

Quote from: Bryce on 11:06, 21 June 20
If you are getting "Bad command" it means that the ROM in the DDI-1 hasn't initialised. Possibly it's not getting power. Can you post a picture of your mod (PCB and DDI-1 cable)?

Bryce.


If the ROM wouldn't be there, then the error would be "Unknown command".
In case of "bad command" the following reasons could be:
- Power supply too low
- Drive spinning too slow
- Format unknown


How to solve the problem? One way could be to format a disc and then try again. Even better: Check if CPC and floppy get enough power (volts here).
http://futureos.de --> Get the revolutionary FutureOS (Update: 2023.11.30)
http://futureos.cpc-live.com/files/LambdaSpeak_RSX_by_TFM.zip --> Get the RSX-ROM for LambdaSpeak :-) (Updated: 2021.12.26)

geebus

I've been getting the same issue using my DDI-1 with a 3.5" drive too.
Tested multiple drives, a couple that I have working as a B drive on my 6128 and one that I was going to use for the 464.
I've tested the power to the drive and the disks. Something else going on in my case. not sure what it is yet.
Strange we're both having the same result at the same time.

Powered by SMFPacks Menu Editor Mod