Re: [hatari-devel] Two problems

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

On 05/06/2018 12:15 AM, Van Snyder wrote:
> I'm trying to use hatari 2.1.0 in KDE on Scientific Linux 6.9.
>
> I launch it using
>
> hatari -m --cpuclock 32 --memsize 14 -k keymap.st ./ &
>
> The mouse sometimes can't get to most of the emulated screen.  In
> particular, it can't get up to the disk drive icons, or all the way
> to the right-hand edge.  I can sometimes get the mouse to work in
> the entire emulated screen by putting another window over the hatari
> window, and then putting the hatari window back on top.  I can
> sometimes get the mouse to work by running the shell using ^Z and
> then exiting from it.

You can enable Hatari window mouse grab either by:
- switching to fullscreen (by default, bound to F11 keyboard shortcut)
- using mouse grab toggle keyboard shortcut (default: AltGr + M)
- using the mouse grab command line option: --grab
- using either of above through the Hatari remote control API

You can change keyboard shortcuts from the Hatari GUI "Keyboard"
settings (just remember to save the changes).


> From the desktop, not the shell, I launched a program that wants a
> command line (ZOO21.TTP).  I want to extract an archive named HDX-5.ZOO.
> The hyphen key on a PS-2 keyboard (next one to the right from zero)
> results in /, not -. With shift, it results in ?, not _.

I assume you already know this, but just in case:

* What keys are printed on your physical PC keyboard depends on
  which region keyboard you've bought.

* To what keys those correspond on your host PC, depends on which
  region you've selected in Linux.  Normally you would set this
  to correspond to your physical keyboard, but that's not always
  an option (e.g. Clear Linux doesn't even seem to have options
  for anything else than US keyboard layout).

* Atari TOS language dictates the keyboard key layout that TOS uses.
  If you use TOS for different language, some of these change
  (this is easiest to test with different EmuTOS 256k versions).


> I had to change it using the following keymap:
>
> -,12
>
> This also works to change the underscore.  It took me a long time to find
> the correct number.  Better reference to the keycode list in
> the example keymap file would be helpful.

Here's one:
	http://eerott.mbnet.fi/hatari/img/st-keymap.png


> There are also some messages produced when the program is launched.

Next Hatari version will reduce these.


> I don't know whether these are important, but here they are:
>
> Hatari v2.1.0, compiled on:  May  4 2018, 22:08:16
> CPU cycleunit: 256 (0.500)
> CPU cycleunit: 256 (0.500)
> 1870 CPU functions
> cpu table lvl=0 , mode=4
> Building CPU, 44274 opcodes (0 -2 1)
> CPU=68000, FPU=0, MMU=0, JIT=0. prefetch and cycle-exact 24-bit
> GEMDOS HDD emulation, C: <-> /home/vsnyder/Atari.
> CPU cycleunit: 256 (0.500)
> CPU cycleunit: 256 (0.500)
> Illegal instruction: 4e7b at 00E0005E -> 00E00062
> Bus Error at address $ffff8006, PC=$e0006a addr_e3=e0006e op_e3=4a78
> CPU reset PC=e00076 (ROM memory)..
> Illegal instruction: 4e7b at 00E0009C -> 00E000A0
> Illegal instruction: 4e7b at 00E000D4 -> 00E000E8
> Bus Error at address $ffff8282, PC=$e00156 addr_e3=e0015a op_e3=4a38
> Bus Error at address $ffff8400, PC=$e00170 addr_e3=e00174 op_e3=4a38
> Illegal instruction: 7300 at 00E0C546 -> 00E0C54E
> Illegal instruction: 42c0 at 00E0045E -> 00E004B2
> Bus Error at address $fffffa40, PC=$e00542 addr_e3=e00546 op_e3=4a78
> Bus Error at address $ffff8400, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $ffff8282, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $fffffa81, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $ffff8c80, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $ffff8e09, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $ffff8961, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $ffff8901, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $ffff9201, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $ffff8a3c, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $fff0001d, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $fff0005d, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $fff0009d, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $fff000dd, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> Bus Error at address $fffffe00, PC=$e00c24 addr_e3=e00c26 op_e3=4a10


Bus errors & illegal instructions shown before TOS desktop is visible,
are TOS probing the availlable hardware.  E.g. testing whether FPU
instructions are present etc.


> I'm running with 14 MiB, but hatari sometimes says there isn't enough
> memory to run the program.  When I had an ST, it was 4.5 MiB, and it
> never produced this message when I ran some of the same programs that
> today did produce it.

With which exact Hatari configuration and program these happen?

E.g. if you enable VDI screen emulation for larger screen sizes,
some TOS versions cannot detect the memory amount correctly.


	- Eero