Hi,
Glad I could help, I'll be interested to see how it goes!
Have fun.
Wolfgang
On 19/05/2018 16:31, Martyn Hill via Ql-Users wrote:
Great observation, Wolfgang!
So, that adjustment to a3 comes out to $1E (30) bytes /*later */in the
DDB - so rather, once the ndt_ctab offset of $50 is
Great observation, Wolfgang!
So, that adjustment to a3 comes out to $1E (30) bytes /*later */in the
DDB - so rather, once the ndt_ctab offset of $50 is added, we need to
look at $6E through $8E for the timing constant table.
I now see:
$6E: 134
$70: 13570
$72: 19
$74: 328
$76:
Hi,
This is what you can find in the NET driver i/o code:
nd_io
pea ndd_test(a3)push pseudo return address
lea ndd.leni(a3),a3 normal linkage ***
move.w io.serio,a2 and do serial IO
jmp (a2)
As you can
Thanks Wolfgang (and Jan via the Forum)
Having now found what looks like the DDB - taking in to account the -$18
offset from the entry in the CDB - the resultant list of words at offset
ndt_ctab ($50) looks suspicious, thus:
50: 0
52: 124
54: -18236
56: 0
58: 36
5A:
Hi,
The best way would be to get the channel definition block (CDB) for a
channel to the device. I don't know offhand of a Basic keyword that will
do it for you, Toolkit III used to have such a function, I don't know
whether that still available, though.
If you have that, then the pointer
Hi everyone
In the spirit of double-posting between here and the QL Forum :-) I
thought I'd ask my question here, too...
I'm continuing to explore the QL network across a range of platforms -
now with my refurbished QXL2 card (thanks, Derek!)
The bit-timings on the QXL under SMSQ/E v3.33
