Maarten ter Huurne wrote:
>
> At 11:06 PM 7/8/99 +0200, Jon wrote:
>
> >2. a way to figure out of which type a connected drive is and to figure
> >out if a diskrom supports this standard.
>
> If the DiskROM doesn't support a drive,
??
a diskrom does support at least one type of device. That's why it is
called a diskrom.
(note: in many cases there is more than one diskrom in a msx. In most
cases this diskrom contains also the DOS kernel code. The slot with the
most recent version of this kernel, becomes *the* master diskrom)
> how do you even know that the drive
> is present?
at startup, a diskrom installs some driveletters for its devices
connected to it. (table at #FB21, etc.) so, you can always know how many
'drives' are present. But next, you need to know which kind of device is
associated with a drive. (CDROM/DVD (2048bytes/sector and ISO9660
filesystem) or a 'direct-access' device like floppy, HD, ZIP, LS120
(512bytes/sector and a DOS filesystem) This info should be obtained by
new standardized extended diskrom functions.
>
> >3. Creation of new entry somewhere in the area of #7Fxx ?
>
> Won't this conflict with the memory mapped I/O in some systems?
don't know; no problem for IDE and MegaSCSI, but I don't know about
other interfaces. Most of them use port I/O.
>
> Bye,
> Maarten
cu,
Jon
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****
