Welcome, Guest. Please login or register.

Author Topic: Internal a1200 IDE interface  (Read 11635 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline mongo

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 964
    • Show all replies
Re: Internal a1200 IDE interface
« on: March 19, 2011, 01:04:12 PM »
Quote from: Franko;621982

The scsi.device is a bit of a misnomer, most likely named by CBM as at that time IDE was not popular and scsi was used by CBM instead... :)


scsi.device was named scsi.device for software, such as HDToolBox that by default assumes hard drives are using scsi.device.

Quote from: Franko;621982

Without going into too much technical detail, all call/functions go through the scsi.device even if you have an IDE, EIDE , ATA, P-ATA drive. They all use SCSI commands at their core the only real main difference between IDE & SCSI are the physical connecters used ... :)


Not true. IDE hard drives don't use SCSI commands at all. ATAPI devices such as optical drives use SCSI commands.
 

Offline mongo

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 964
    • Show all replies
Re: Internal a1200 IDE interface
« Reply #1 on: March 19, 2011, 05:48:54 PM »
Quote from: Franko;623093
I was about to say I've only ever written utils for ATAPI/EIDE DVD & CD drives which of course use SCSI (even though they are connect to the IDE port) commands and then say you are of course correct... :)

But, I have also written one piece of software for EIDE/IDE HDs for reading and writing the RDB block and this uses SCSI commands, so now I'll have to say your incorrect... :)


Nope. scsi.device includes limited emulation of some SCSI commands, so even though your program might be using SCSI commands, the hard drive isn't.