Date : Tue, 16 Apr 2002 09:45:12 +0100
From : owner-bbc-micro@...
Subject: Re: Patched !65Host - Break Key
Sorry, there isn't any response from Scroll Lock/Print Scrn/F12 but thanks
for the tip on Alt-Break from Sprow!
I was given 6502Em for a present a while ago now but it's taking me this
long to get used to it, having got used !65Host, I suppose. I don't like the
way keys are mapped onto other keys so that the keyboard operates like (but
certainly doesn't look like) a BBC keyboard layout. I am altering the
keyboard map file so that all keys map onto themselves - hopefully!. I found
the 'Virtual DFS' system strange at first, which has a more contrived feel
than the 'ADFS' on !65Host.
I disliked the way that Warm Silence advertised 6502Em as compatible with
RISC OS2+. OK, it *worked* on my old A3010 but too slow to be of any
practical use. Still, I suppose that depends on what you mean 'compatible',
do you want to just look at a program or be able to use it?. I prefer 65Host
for my programming, 6502em for playing games that do naughty tricks with the
hardware that 65host doesn't support.
No discredit to Mike Borcherds there - 6502Em is an achievement in itself,
but everyone has their own preferences ;-)
CD.
-----Original Message-----
From: Michael Borcherds [mailto:mrb@...]
Sent: 15 April 2002 17:40
To: Christopher Dewhurst Clerical Assistant SS
Subject: Re: [BBC-Micro] Patched !65Host - Break Key
> Can anyone help with this - I use the patched version of !65Host running
on
> my RiscPC but the Break key doesn't work. So if a BBC program freezes I
have
> to restart the entire computer and run the emulator again. (The Break key
> works otherwise, it doesn't work under emulation.)
buy 6502Em from www.wss.co.uk for 15ukp+VAT
cheers,
Mike (the author :)
This e-mail (including any attachments) is intended only for the
recipient(s) named above. It may contain confidential or privileged
information and should not be read, copied or otherwise used by any other
person unless express permission is given. If you are not a named
recipient, please contact the sender and delete the e-mail from your system.
It is the recipient's responsibility to ensure that appropriate measures are
in place to check for software viruses.