I'm sorry, due to the recent loss of my father I was not in the mood
to participate in any discussions. Just a short answer:
I'm very sorry to hear of your loss, Marcel. Please accept my condolences.
Dilwyn
___
QL-Users Mailing List
http://www.q-v-d.de
On 25 Jan 2013, at 12:34, Norman Dunbar wrote:
> None of mt assembly books bother to mention this fact either, I've spent the
> last hour or so looking up everything that could be possibly related. Sigh!
My THOR 21 came with Motorola's manual MC68020. The information about
instruction and data
Op 25/01/2013 12:53, Marcel Kilgus schreef:
Norman Dunbar wrote:
In QPC, version 3.33, the above works without any exceptions. PRINT
PROCESSOR gives 20, I must assume that either a 68020 doesn't barf at a
long word access to an odd address or something is not working correctly
any more!
Only 68
Thanks all for the information. It seems my Motorola books don't mention
this fact!
I'll need to change the code then. It's supposed to work with a bare
bones QL and hence, 68008.
None of mt assembly books bother to mention this fact either, I've spent
the last hour or so looking up everythi
On 25/01/13 11:53, Marcel Kilgus wrote:
I'm sorry, due to the recent loss of my father I was not in the mood
to participate in any discussions. Just a short answer:
Please accept my sympathies.
Cheers,
Norm.
--
Norman Dunbar
Dunbar IT Consultants Ltd
Registered address:
Thorpe House
61 Richa
Norman Dunbar wrote:
> In QPC, version 3.33, the above works without any exceptions. PRINT
> PROCESSOR gives 20, I must assume that either a 68020 doesn't barf at a
> long word access to an odd address or something is not working correctly
> any more!
Only 68000 and 68008 had this limitation.
Mar
I'm sorry, due to the recent loss of my father I was not in the mood
to participate in any discussions. Just a short answer:
SMSQE wrote:
> The keyboard functions correctly in absolutely every piece of software I
> have, except QPC2.
This is probably because you do not play any games, as many of
On 25 Jan 2013, at 10:47, Norman Dunbar wrote:
> Morning all,
>
> I'm doing a bit more work on the next exciting episode of QL Today's LibGen
> utility. I have spotted a huge pair of bugs in my code, viz:
>
>
> li_libfile equ $03
> ...
>
> li_unavmove.l #$,ws_litem+li_libfile(a1)
I'm pretty sure odd address access is perfectly acceptable with a 68020,
but could be wrong.
On 25/01/2013 10:47, Norman Dunbar wrote:
Morning all,
I'm doing a bit more work on the next exciting episode of QL Today's
LibGen utility. I have spotted a huge pair of bugs in my code, viz:
li_l
Morning all,
I'm doing a bit more work on the next exciting episode of QL Today's
LibGen utility. I have spotted a huge pair of bugs in my code, viz:
li_libfile equ $03
...
li_unavmove.l #$,ws_litem+li_libfile(a1)
bra.s li_rdrw
...
li_avail move.l #$01011101,ws_litem
Le 25/01/2013 01:55, Timothy Swenson a écrit :
I tested both 720K and 1.44M floppy images (in the simplest of tests). I
can do some further testing with 1.44 (read, write, etc) and see if I
can get any failure.
Ah yes, contrary to the documentation (I'll amend this) SMSQmulator should
handle
11 matches
Mail list logo
