Author Topic: 3.5" drive on Amstrad CPC 464 "bad command"  (Read 252 times)

0 Members and 1 Guest are viewing this topic.

Offline littlangel

  • CPC464
  • **
  • Posts: 5
  • Country: fr
  • Liked: 1
  • Likes Given: 0
3.5" drive on Amstrad CPC 464 "bad command"
« on: 12:41, 21 June 20 »
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.

Offline Bryce

  • The Hardware Guy.
  • Supporter
  • 6128 Plus
  • *
  • Posts: 11.650
  • Country: wf
  • It's not broken, it just hasn't been fixed yet.
    • index.php?action=treasury
  • Liked: 4180
  • Likes Given: 436
Re: 3.5" drive on Amstrad CPC 464 "bad command"
« Reply #1 on: 13: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.

Offline geebus

  • Amateur Geek
  • Supporter
  • CPC6128
  • *
  • Posts: 153
  • Country: scotland
    • Gee-k.net
  • Liked: 52
  • Likes Given: 43
Re: 3.5" drive on Amstrad CPC 464 "bad command"
« Reply #2 on: 15:21, 16 July 20 »
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.

Offline GUNHED

  • 6128 Plus
  • ******
  • Posts: 1.916
  • Country: de
  • Reincarnation of TFM
    • FutureOS - The quickest OS for the CPC and Plus
  • Liked: 861
  • Likes Given: 2134
Re: 3.5" drive on Amstrad CPC 464 "bad command"
« Reply #3 on: 16:14, 16 July 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 (Recent update: 2019.08.07)
http://futureos.cpc-live.com/files/LambdaSpeak_RSX_by_TFM.zip --> Get the RSX-ROM for LambdaSpeak :-) (Updated: 2019.08.14)