----------------------------------------------------------------------------------
@MSGID:
<617c3da6-38d8-4656-b06e-9bbea05d6706n@googlegroups.com> 7b37a8bf
@REPLY:
<d14dea63-f9f0-4133-ba9c-7bff0b803b23n@googlegroups.com> 301d730e
@REPLYADDR I am Rob <gids.rs@sasktel.net>
@REPLYTO 2:5075/128 I am Rob
@CHRS: CP866 2
@RFC: 1 0
@RFC-References:
<f90f1538-dd1f-4bfe-a035-d71f21fc971an@googlegroups.com> <d14dea63-f9f0-4133-ba9c-7bff0b803b23n@googlegroups.com>
@RFC-Message-ID:
<617c3da6-38d8-4656-b06e-9bbea05d6706n@googlegroups.com>
@TZUTC: -0700
@PID: G2/1.0
@TID: FIDOGATE-5.12-ge4e8b94
> Hi Rob,
> Smartport deals with devices, not slots/drives.
> Is your mapping done once ProDOS 8 is loaded?
> Antoine
Right. But even the Smartport would need to use the softswitches to
access a slot card. Which should mean there has to be a mapping of some
kind to know which slot a device is in. I have come across an instance
where it would be a benefit to be able to translate between the two.
As far as I know the mapping has nothing to do with Prodos 8. If
you follow the routine at $C70D (entry to the Smartport), it ends in
COP 82. This co-processor routine must have a routine to map a slot to
a device number.
--- G2/1.0
* Origin: usenet.network (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441