Moderators: simonsunnyboy, thothy, Moderator Team
helmut wrote:Is C:\CLIPBRD somewhow connected to the host-clipboard?
This is very likely totally unrelated, but I receive Bus-Errors in XaAES
from various clients on aranym, when I open the the clipboard and the
host-clipboard is empty. Of course only when clipboard is set to
u:/host/clipboard in xaaes.cnf.
I always make sure there's somthing in the clipboard before running
aranym.
-Helmut
helmut wrote:Well Eero said:
"The weird thing is that this happens only with the CLIPBRD folder, but I don't know whether that's just due to timing."
Now what?
I just ran my old hatari on my old XP-PC and in XaAES opening any empty folder on C: using the fileselector does not crash, but I can't open the folder, i.e. it keeps displaying C: with all titles greyed. Something seems wrong. Guess I'll have to install hatari finally ...
If you can build MiNT try to build a DEBUG-kernel, maybe that sheds some light.
-Helmut
helmut wrote:Is C:\CLIPBRD somewhow connected to the host-clipboard?
helmut wrote:Does TOSFS provide . and ..-links?
helmut wrote:Got it: some dlls from the distribution lacked the x-bit. Works now in 64 and 32-bit. Even with key-click! And even with an XaAES-crash ...
-rw-r--r-- 1 hk None 157184 Jun 18 2014 capsimg.dll
-rw-r--r-- 1 hk None 84616 Oct 15 2014 zlib1.dll
In hatari 1.9 XaAES can't open the virtual workstation - it crashes inside v_opnvwk (Addr=0).
helmut wrote:The same works in hatari 1.7.
TOS is 2.06.
In hatari 1.7 I can open any empty folder on C: without a problem.
Sorry, no results from me.
helmut wrote:./hatari-win64-release
Illegal instruction
My C: stripped down: http://home.arcor.de/zabruder/atari/hatx.zip
Hope I didn't forget anything. It boots into ash, then type xaloader.prg.
Code: Select all
XaAES v1.8.4 Beta (m68000, Sep 11 2016 19:56) (MultiTasking AES for MiNT)
Part of freemint (http://sparemint.org).
home_path: 'u:\c\mint\1-19-cur\xaaes\'
Reading `u:\c\mint\1-19-cur\xaaes\xaaes.cnf' ... 9488 bytes done.
[u:\c\mint\1-19-cur\xaaes\xaaes.cnf:70] unknown variable 'GRADIENTS', skipped.
moose_w.adi not found
Wrong kentry-version (kernel-version too high)
Module moose.adi error, reason: Nothing (possibly from other kernel)
AES call 10 appl_init()
AES call 19 appl_exit()
VDI call 1/ 0 (v_opnwk)
pBank flags mismatch: 0x2 & 0x1 (RAM = 0x1)
GEMDOS Fwrite() failed due to invalid RAM range 0xe3ea38+4
VDI call 100/ 0 (v_opnvwk)
VDI call 104/ 0 (vsf_perimeter)
VDI call 108/ 0 (vsl_ends)
VDI call 16/ 0 (vsl_width)
VDI call 106/ 0 (vst_effects)
VDI call 19/ 0 (vsm_height)
VDI call 12/ 0 (vst_height)
Illegal instruction: 4a8d at 00172DB4 -> 0005DA58
Illegal instruction: 4a8d at 00172DB4 -> 0005DA58
GEMDOS 0x40 Fwrite(64, 105, 0x74fa8) at PC 0xFA002A
GEMDOS 0x40 Fwrite(64, 2, 0x22ce5) at PC 0xFA002A
Code: Select all
> m 0x74fa8
00074FA8: 70 69 64 20 20 20 34 20 28 41 45 53 53 59 53 29 pid 4 (AESSYS)
00074FB8: 3a 20 49 4c 4c 45 47 41 4c 20 49 4e 53 54 52 55 : ILLEGAL INSTRU
00074FC8: 43 54 49 4f 4e 3a 20 55 73 65 72 20 50 43 3d 31 CTION: User PC=1
00074FD8: 37 32 44 42 34 20 28 62 61 73 65 70 61 67 65 3d 72DB4 (basepage=
00074FE8: 31 36 30 45 34 2c 20 74 65 78 74 3d 31 36 31 45 160E4, text=161E
00074FF8: 34 2c 20 64 61 74 61 3d 36 30 39 44 38 2c 20 62 4, data=609D8, b
00075008: 73 73 3d 36 34 31 32 34 29 00 00 00 00 00 00 00 ss=64124).......
> d "0x172DB4-6"
- '0x172DB4-6' -> $172dae
$00172dae : 303c 0073 move.w #$73,d0
$00172db2 : 4e42 trap #2
$00172db4 : 4a8d tst.l a5
> info vdi 1
...
70 vsf_udpat 71 vsl_udsty 72 vr_recfl 73 vqin_mode
...
Code: Select all
XaAES v1.8.4 Beta (m68000, Sep 11 2016 19:56) (MultiTasking AES for MiNT)
Part of freemint (http://sparemint.org).
stack is long-aligned:FBE40
PRG: km=FE000, base=FE160, text=FE260 -> 1734A0(479808), kentry:0.21,dos_version=40
home_path: 'u:\c\mint\1-19-cur\xaaes\'
Loading config u:\c\mint\1-19-cur\xaaes\xaaes.cnf
keyboard#0=aradenum
sysfile_exists: 'u:\c\mint\1-19-cur\xaaes\moose_w.adi'
moose_w.adi not found
sysfile_exists: 'u:\c\mint\1-19-cur\xaaes\moose.adi'
lang='en' (from AKP) code=0.
load adi modules
Loading AES Device Drivers:
load_adi: enter (0x185304, 0x185204, moose.adi)
Module moose.adi error, reason: Nothing (possibly from other kernel)
load_adi: return -1
adi_load: done
Creating XaAES kernel thread
AESSYS:Installed 'nAES' cookie in readable memory at C1A00
apid=-1,P_handle=0,next_res=0
k_init: videomode=0.vm=0
could not determine nvdi version
could not determine fvdi version
k_init:vdo=0 vm=0 video=0
Default screenmode
Screenmode is: 1
Physical work station opened: 1
opening vwk:v=17F0A8
exception 4 for AESSYS pc:172DB4 addr:0
helmut wrote:I don't have any linux, but OpenBSD
Eero Tamminen wrote:
Thanks. As you said, xaloader.prg doesn't start up properly.
In my case, it:
- opens & closes XA_BOOT.LOG file over 30 times
- opens & closes MOOSE.ADI twice before telling that loading it failed
- Gives illegal instructions error twice and after that doesn't continue booting, just shows white screen with blinking cursor
This output on console and AES+VDI trace ("hatari --conout 2 --trace vdi,aes ..."):Code: Select all
...
Wrong kentry-version (kernel-version too high)
Module moose.adi error, reason: Nothing (possibly from other kernel)
AES call 10 appl_init()
AES call 19 appl_exit()
VDI call 1/ 0 (v_opnwk)
pBank flags mismatch: 0x2 & 0x1 (RAM = 0x1)
GEMDOS Fwrite() failed due to invalid RAM range 0xe3ea38+4
VDI call 100/ 0 (v_opnvwk)
VDI call 104/ 0 (vsf_perimeter)
VDI call 108/ 0 (vsl_ends)
VDI call 16/ 0 (vsl_width)
VDI call 106/ 0 (vst_effects)
VDI call 19/ 0 (vsm_height)
VDI call 12/ 0 (vst_height)
Illegal instruction: 4a8d at 00172DB4 -> 0005DA58
Illegal instruction: 4a8d at 00172DB4 -> 0005DA58
GEMDOS 0x40 Fwrite(64, 105, 0x74fa8) at PC 0xFA002A
GEMDOS 0x40 Fwrite(64, 2, 0x22ce5) at PC 0xFA002A
Fwrite() after physical workstation opening trying to overwrite ROM looks suspicious, but it happens only with EmuTOS so I'm going to ignore it.
Is moose.adi ABI mismatch & loading failure problem for XaAES running? And could you provide setup with a working one?
For completeness, XA_BOOT.LOG contains:
Code: Select all
~~~~~~~~~~~~ XaAES start up ~~~~~~~~~~~~~~~~
XaAES v1.8.4 Beta (m68000, Sep 16 2016 13:34) (MultiTasking AES for MiNT)
Part of freemint (http://sparemint.org).
stack is long-aligned:F2C40
PRG: km=F2E00, base=F2F60, text=F3060 -> 168404(480164), kentry:0.21,dos_version=40
home_path: 'u:\c\mint\1-19-cur\xaaes\'
Loading config u:\c\mint\1-19-cur\xaaes\xaaes.cnf
keyboard#0=aradenum
sysfile_exists: 'u:\c\mint\1-19-cur\xaaes\moose_w.adi'
moose_w.adi not found
sysfile_exists: 'u:\c\mint\1-19-cur\xaaes\moose.adi'
lang='de' (from AKP) code=1.
load adi modules
Loading AES Device Drivers:
load_adi: enter (0x17E304, 0x17E204, moose.adi)
load_adi: return 0
adi_load: done
Creating XaAES kernel thread
AESSYS:Installed 'nAES' cookie in readable memory at B8800
apid=-1,P_handle=0,next_res=0
k_init: videomode=0.vm=0
could not determine nvdi version
could not determine fvdi version
k_init:vdo=0 vm=0 video=0
Default screenmode
Screenmode is: 1
Physical work station opened: 1
opening vwk:v=1740A0
vwk openend :v=1740A0,handle=2
Virtual work station opened: 2
lookup-support:0, planes:1
Video info: (1280/960),1, colours 2 pixel-format 8
loading palette:'u:\c\mint\1-19-cur\xaaes\pal/gem.pal'
palette not found:-33
stdfont: id = 1, size = 9, cw=8, ch=8, dev=0
smlfont: id = 1, size = 8, cw=6, ch=6, dev=0
Display Device: Phys_handle=1, Virt_handle=2
size=[1280,960], colours=2, bitplanes=1
Loading system resource file 'xaaes016.rsc'
xaaes_sysfile: check if 'u:\c\mint\1-19-cur\xaaes\xaaes016.rsc' exists - return = 0
open lang-file 'u:\c\mint\1-19-cur\xaaes\xaaes016.rsl'
system resource = 185A04 (u:\c\mint\1-19-cur\xaaes\xaaes016.rsc)
xaaes_sysfile: check if 'u:\c\mint\1-19-cur\xaaes\xa_xtobj.rsc' exists - return = 0
xaaes_sysfile: check if 'u:\c\mint\1-19-cur\xaaes\xaaeswdg.rsc' exists - return = 0
AESSYS:Installed 'BGEM' cookie in writeable memory at B8C00
AESSYS:read_inf:u:\c\mint\1-19-cur\xaaes\xaaes.inf
alert:6, KBD:7,pferr=0
No wheel support
Using moose adi
Loading AES modules...
loading accs ---------------------------
loading accessories from 'C:\'
loading shell and autorun ---------------
helmut wrote:I don't have any linux, but OpenBSD
That should be fine. Have you tried building latest Hatari / did you encounter any errors?
helmut wrote:Is it possible that these VDI-calls come from the VDI itself?
helmut wrote:I don't understand how an Fwrite() can write into ROM.
helmut wrote:XaAES does not call vqin_mode directly.
Code: Select all
XBIOS 0x26 Supexec(0x527BC) at PC 0x5305C
Illegal instruction: 42c1 at 000542D8 -> 00054324
M68000 Bus Error reading at address $fffa40 PC=$543b2.
Code: Select all
$0005d602 : 42c1 move ccr,d1
Code: Select all
VDI call 100/ 0 (v_opnvwk)
VDI call 104/ 0 (vsf_perimeter)
VDI call 108/ 0 (vsl_ends)
VDI call 16/ 0 (vsl_width)
VDI call 106/ 0 (vst_effects)
VDI call 19/ 0 (vsm_height)
VDI call 12/ 0 (vst_height)
Illegal instruction: 4a8d at 00169D18 -> 0005472E
GEMDOS 0x4E Fsfirst("C:\MINT\1-19-CUR\XAAES\XA_BOOT.LOG", 0x37) at PC 0xFA002A
Code: Select all
GEMDOS 0x40 Fwrite(64, 2, 0x199bb) at PC 0xFA002A
Illegal instruction: 4a8d at 00169D18 -> 0005472E
GEMDOS 0x40 Fwrite(64, 103, 0x6bc7e) at PC 0xFA002A
Code: Select all
$00172f12 : 303c 0073 move.w #$73,d0
$00172f16 : 4e42 trap #2
$00172f18 : 4a8d tst.l a5
helmut wrote:I rebuilt libgem and now XaAES runs on hatari 1.9.
Code: Select all
$ ls -l gemsys/ldg/screen.ldg gemsys/myaes/libs/screen.ldg
163816 gemsys/ldg/screen.ldg
163812 gemsys/myaes/libs/screen.ldg
Users browsing this forum: No registered users and 2 guests