🚀 go-pugleaf

Dave Sparks (Dave.Sparks.doesnt-want-junk-mail.$@sisyphus.demon.co.uk) wrote:
> >>>>> "DB" == Dave Beames <dave@beames.demon.co.uk> writes:
>
>   DB> Can anyone PLEASE tell me what the instruction MOVE.L #$258,$20(A0)
>   DB> would look like in hex after assembly?
>
> After assembling and disassembling two lines of code:
>
>	 217C 0000 0258 0020   MOVE.L #00000258,0020(A0)
>
>	 217C 0140 0000 0020   MOVE.L #01400000,0020(A0)
>
> (I would have looked it up in the book, but assembly/disassembly
> was quicker and more reliable.)

I'd have done that if I'd had an assembler :-)
But I haven't -- nor a book that actually works.

This leaves me looking even sillier than usual.
I'd searched everywhere (with NewZAP) for hex 258, and hadn't found it,
which is why I asked what the assembled instr would look like -- after
all, for all I knew the 258 might have been offset 1 or 2 or 3 bits.

What I *didn't* know was that NewZAP insists on being asked for 0258. 
This strikes me as unreasonable -- the search requester says clearly that
it is looking for hex, not bytes, so *why* does it insist on bytes?

Never mind .... :-)

Many thanks, Dave,  all fixed now, and it works.  I still need to get rid
of a startup requester asking me to register, but that can wait.

Thanks, too, to Chris for the Deksid suggestion.  It's quite good, isn't
it, with the built-in converter an' all.  A bit fragile -- click in the
wrong place and it hangs -- but worth keeping alongside NewZAP.

Cheers ... DaveB