I never used TABBED when starting a shell. These are my window parameters: WINDOW=CON:1055/31/673/484/AmigaShell/SHELL/CLOSE/ALT1055/31/673/969
I still have strange freezes when selecting, pasting or quickly entering text into the Shell. Also, starting a new Shell window while another one moves (like a notification that flies in), will also freeze the system.
I had a similar experience on my X5000 that was pre-installed by Alinea Computer.
It had a number of strange issues (StormC5 forgetting its registration, strange crashes while playing music, ...).
In the end it seemed to be a combination of the installation and just buggy programs.
A fresh installation solved the StormC5 issue, and most of other crashes where indeed bugs by other software: - CONSOLE (newshell) is still unstable (but not as bad as on Update 2) - AmigaGuide datatype is trashing memory when loading AmigaGuide files with links to external files (e.g. RKMs on the Developer CD) - IMP3 really need to be run on its own screen - IMP3's MOD replay is very fragile with the currently available ptreplay and ptplay libraries - Some of the Enhancer replacements are not 100% compatible (CLI commands, datatypes)
Regarding the network issues, there is indeed an issue with the default network configuration. Run CheckRoadshowConfig and remove the duplicates from your config. But make a backup.
If I understand you correctly, you want to separate/sandbox legacy 68k code more than it is done with Petunia now. So, instead that 68k code is directly accessing the system, it should access an emulation layer in the future.
I guess this will break more legacy 68k programs. I cannot imagine that Vinced or tools like GoSnap will work anymore in such an environment.
If I understand you correctly, you mean ditching old 68k stuff from the APIs/libraries. IMHO this is even worse, because this makes maintaining software for all Amiga flavors (3.x, MorphOS, AmigaOS 4.x) much more compliate than it needs to. And it is pretty bad with the interfaces for libraries calls already.
Sorry, I do not see the benefit of having an "Amiga NG" with an "Amiga OS" that does not support 68k programs.
I personally use a lot of 68k programs that have no PPC port: - CubicIDE - ArtEffect - StormC 4 - IMP3 - AmIRC - VinCED (because CON is seriously buggy)
And no, running them in UAE is not an option for me.
Thank you for your continued effort to make Xena work.
This is the output of XTools 1.7g:
> XenaStatus
Warning: This set of XTools currently only tested on X1000
Setting up x5000
The support for X5000 is UNTESTED!
----------------------------------
If you'd like to continue, a few tests will be performed.
They will be performed with a varying delay
betweeen the read and writes.
The only reason you would want to run these tests is to
inform the developer on your progress.
You can abort this process by entering 'q' at any testpoint.
You will be asked to enter something to continue before each test.
YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!
Creating Xena memory space for INDEX reg: e0000000
Creating Xena memory space for DATACHANNEL reg: e0008000
About to do some tests.
Enter 'q' to quit, anything else to continue... a
--- 8 memtest: reg: 0001, SIG2 should be 0xbeef
0xe0008000: dead dead dead dead dead dead dead dead
0xe0008010: beef beef beef beef beef beef beef beef
0xe0008020: dead dead dead dead dead dead dead dead
0xe0008030: beef beef beef beef beef beef beef beef
memtest done ---
--- 8 memtest: reg: 0000, SIG1 should be 0xdead
0xe0008000: dead dead dead dead dead dead dead dead
0xe0008010: beef beef beef beef beef beef beef beef
0xe0008020: dead dead dead dead dead dead dead dead
0xe0008030: beef beef beef beef beef beef beef beef
memtest done ---
--- 8 memtest: reg: 0002, HWREV should be 2210 perhaps?
0xe0008000: dead dead dead dead dead dead dead dead
0xe0008010: beef beef beef beef beef beef beef beef
0xe0008020: dead dead dead dead dead dead dead dead
0xe0008030: beef beef beef beef beef beef beef beef
memtest done ---
--- 8 memtest: reg: 000c, XDBG bit 7=1 if xorro, bit 8=1 if xtag detected
0xe0008000: dead dead dead dead dead dead dead dead
0xe0008010: beef beef beef beef beef beef beef beef
0xe0008020: dead dead dead dead dead dead dead dead
0xe0008030: beef beef beef beef beef beef beef beef
memtest done ---
--- 8 memtest: reg: 0004, LBALIVE should be 0001
0xe0008000: dead dead dead dead dead dead dead dead
0xe0008010: beef beef beef beef beef beef beef beef
0xe0008020: dead dead dead dead dead dead dead dead
0xe0008030: beef beef beef beef beef beef beef beef
memtest done ---
--- 8 memtest: reg: 0021, DATELB should be low bits of some date
0xe0008000: dead dead dead dead dead dead dead dead
0xe0008010: beef beef beef beef beef beef beef beef
0xe0008020: dead dead dead dead dead dead dead dead
0xe0008030: beef beef beef beef beef beef beef beef
memtest done ---
--- 8 memtest: reg: 0031, SCRATCH2
0xe0008000: dead dead dead dead dead dead dead dead
0xe0008010: beef beef beef beef beef beef beef beef
0xe0008020: dead dead dead dead dead dead dead dead
0xe0008030: beef beef beef beef beef beef beef beef
memtest done ---
Tests done.
Exiting since its all very unclear.
Xena setup failed
> version xena.resource full
xena.resource 53.2 (08.10.2015)
> XenaStatus
Warning: This set of XTools currently only tested on X1000
Cannot open xena.resource.
> XenaStatus
Warning: This set of XTools currently only tested on X1000
Setting up x5000
The support for X5000 is UNTESTED!
----------------------------------
If you'd like to continue, a few tests will be performed.
They will be performed with a varying delay
betweeen the read and writes.
The only reason you would want to run these tests is to
inform the developer on your progress.
You can abort this process by entering 'q' at any testpoint.
You will be asked to enter something to continue before each test.
YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!
Creating Xena memory space for INDEX reg: e0000000
Creating Xena memory space for DATACHANNEL reg: e0008000
About to do some tests.
Enter 'q' to quit, anything else to continue... a
loop-check check1: dead, check2: dead, waits: 25383, i: 5000
-----------------------------------------------------
Performing test with ITimer->MicroDelay 10, with read/write to 0x8000
with read/write to 0x8000. Res in SIG1 is: 0xdead. Should be 0xdead
with read/write to 0x8000. Res in SIG2 is: 0xdead. Should be 0xbeef.
with read/write to 0x8000. Res in REG_HWREV: 0xdead.
with read/write to 0x8000. Read scratch1: 0xdead (don't know what it should be)
with read/write to 0x8000. Read scratch2: 0xdead (don't know what it should be)
with read/write to 0x8000. REG:0x0000 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0000 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0001 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0002 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0003 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0004 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x000c is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x000d is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0010 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0020 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0021 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0022 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0023 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0024 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x002f is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0030 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0031 is 0xdead 1101111010101101
Tests done.
If you got good values back from test, things seem to work.
If there were good results for the delay 10 test, then you could continue to run
and stuff might work. If no good results were seen then you might as well abort now.
Enter 'q' to quit, anything else to continue... a
fatal: chain too long returned 128
Could it be that xena.resource.kmod is the issue? The X5000 pre-release CD came with "xena.resource.kmod 53.2 (08.10.2015)". I currently have "xena.resource.kmod 53.3 (16.12.2016)". I think it was installed by an update. I will try the older xena.resource.kmod and see if that changes anything.
These are the results on my X5000/20 after a fresh boot:
3. > Workbench:Utilities/XTools > XenaStatus
Warning: This set of XTools currently only tested on X1000
Setting up x5000
The support for X5000 is UNTESTED!
----------------------------------
If you'd like to continue, a few tests will be performed.
They will be performed with a varying delay
betweeen the read and writes.
The only reason you would want to run these tests is to
inform the developer on your progress.
You can abort this process by entering 'q' at any testpoint.
You will be asked to enter something to continue before each test.
YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!
Creating Xena memory space for INDEX reg: e0000000
Creating Xena memory space for DATACHANNEL reg: e0008000
About to do some tests.
Enter 'q' to quit, anything else to continue... a
-----------------------------------------------------
Performing test with delay 5, with read/write 0x8000
with read/write 0x8000. Res in SIG1 is: 0xdead. Should be 0xdead
with read/write 0x8000. Res in SIG2 is: 0xdead. Should be 0xbeef.
with read/write 0x8000. Res in REG_HWREV: 0xdead.
with read/write 0x8000. Read scratch1: 0xdead (don't know what it should be)
with read/write 0x8000. Read scratch2: 0xdead (don't know what it should be)
with read/write 0x8000. REG:0x0000 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0000 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0001 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0002 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0003 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0004 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x000c is 0xdead 1101111010101101
with read/write 0x8000. REG:0x000d is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0010 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0020 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0021 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0022 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0023 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0024 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x002f is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0030 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0031 is 0xdead 1101111010101101
Tests done.
If you got good values back from test, things seem to work.
If there were good results for the delay 10 test, then you could continue to run
and stuff might work. If no good results were seen then you might as well abort now.
Enter 'q' to quit, anything else to continue... a
fatal: chain too long returned 128
Warning: This set of XTools currently only tested on X1000
Setting up x5000
The support for X5000 is UNTESTED!
----------------------------------
If you'd like to continue, a few tests will be performed.
They will be performed with a varying delay
betweeen the read and writes.
The only reason you would want to run these tests is to
inform the developer on your progress.
You can abort this process by entering 'q' at any testpoint.
You will be asked to enter something to continue before each test.
YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!
Creating Xena memory space for INDEX reg: e0000000
Creating Xena memory space for DATACHANNEL reg: e0008000
About to do some tests.
Enter 'q' to quit, anything else to continue...
a
-----------------------------------------------------
Performing test with delay 2, with read/write 0x8000 Delay(1)
with read/write 0x8000 Delay(1). Res in SIG1 is: 0xdead. Should be 0xdead
with read/write 0x8000 Delay(1). Res in SIG2 is: 0xdead. Should be 0xbeef.
with read/write 0x8000 Delay(1). Res in REG_HWREV: 0xdead.
with read/write 0x8000 Delay(1). Read scratch1: 0xf0cc (should be 0xf0cc)
with read/write 0x8000 Delay(1). Read scratch2: 0xd1d0 (should be 0xd1d0)
with read/write 0x8000 Delay(1). Again scratch1: 0xa12f (should be 0xabcd)
with read/write 0x8000 Delay(1). Again scratch2: 0xa12f (should be 0xa12f)
with read/write 0x8000 Delay(1). REG:0x0000 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0000 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0001 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0002 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0003 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0004 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x000c is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x000d is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0010 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0020 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0021 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0022 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0023 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0024 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x002f is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0030 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0031 is 0xa12f 1010000100101111
-----------------------------------------------------
Performing test with delay 5, with read/write 0x8000 Delay(1)
with read/write 0x8000 Delay(1). Res in SIG1 is: 0xa12f. Should be 0xdead
with read/write 0x8000 Delay(1). Res in SIG2 is: 0xa12f. Should be 0xbeef.
with read/write 0x8000 Delay(1). Res in REG_HWREV: 0xa12f.
with read/write 0x8000 Delay(1). Read scratch1: 0xf0cc (should be 0xf0cc)
with read/write 0x8000 Delay(1). Read scratch2: 0xd1d0 (should be 0xd1d0)
with read/write 0x8000 Delay(1). Again scratch1: 0xa12f (should be 0xabcd)
with read/write 0x8000 Delay(1). Again scratch2: 0xa12f (should be 0xa12f)
with read/write 0x8000 Delay(1). REG:0x0000 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0000 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0001 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0002 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0003 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0004 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x000c is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x000d is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0010 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0020 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0021 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0022 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0023 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0024 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x002f is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0030 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0031 is 0xa12f 1010000100101111
-----------------------------------------------------
Performing test with delay 10, with read/write 0x8000 Delay(1)
with read/write 0x8000 Delay(1). Res in SIG1 is: 0xa12f. Should be 0xdead
with read/write 0x8000 Delay(1). Res in SIG2 is: 0xa12f. Should be 0xbeef.
with read/write 0x8000 Delay(1). Res in REG_HWREV: 0xa12f.
with read/write 0x8000 Delay(1). Read scratch1: 0xf0cc (should be 0xf0cc)
with read/write 0x8000 Delay(1). Read scratch2: 0xd1d0 (should be 0xd1d0)
with read/write 0x8000 Delay(1). Again scratch1: 0xa12f (should be 0xabcd)
with read/write 0x8000 Delay(1). Again scratch2: 0xa12f (should be 0xa12f)
with read/write 0x8000 Delay(1). REG:0x0000 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0000 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0001 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0002 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0003 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0004 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x000c is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x000d is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0010 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0020 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0021 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0022 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0023 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0024 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x002f is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0030 is 0xa12f 1010000100101111
with read/write 0x8000 Delay(1). REG:0x0031 is 0xa12f 1010000100101111
Tests done.
If you got good values back from test, things seem to work.
If there were good results for the IDOS->Delay(1) test, then you could continue to run
and stuff might work. If no good results were seen then you might as well abort now.
Enter 'q' to quit, anything else to continue...
I tried the latest XTools from your blog on my X5000/20.
This is the output. It does not seem to work fully and the tools can only be run once:
3. > Workbench:Utilities/XTools > XenaStatus
Warning: This set of XTools currently only tested on X1000
Setting up x5000
The support for X5000 is UNTESTED!
----------------------------------
If you'd like to continue, a few tests will be performed.
1. The first test is according to the X5000 Curys TRM.
It seemed to work for one test. But then not.
2. The second test is based on loose assumptions on how
AEons Tabor motherboard works.
The only reason you would want to run these tests is to
inform the developer on your progress.
You can abort this process now by pressing Ctrl-C and enter.
You will be asked to enter something to continue before each test.
YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!
About to setup mem space. Enter something to continue...
asd
Creating Xena memory space for INDEX reg: e0000000
Creating Xena memory space for DATACHANNEL reg: e0008000
About to do test 1. Enter something to continue...
asd
--- Performing Test 1 ---
Res in SIG1 is dead. This is good.
Res in SIG2 is dead. It is not 0xBEEF. That's wrong.
Res in REG_HWREV (2) is dead.
Writing D00F to scratch1
Writing BABE to scratch2
Read babe from scratch1 (should be D00F)
Read babe from scratch2 (should be BABE)
About to do test 2.
Enter something to continue...
asd
--- Performing Test 2 ---
Res in SIG1 is babe. It should be 0xDEAD.
Res in SIG2 is bebe. It is not 0xBEEF. That's wrong. You should not continue.
Res in REG_HWREV (2) is beef.
Writing F0BB to scratch1
Writing D00D to scratch2
Read f0d0 from scratch1 (should be F0BB)
Read d00d from scratch2 (should be D0DE)
If you got good values back from test 1, things seem to work.
If you got good values back from test 2, things in the code have to change!
If you didn't get good values, stuff will NOT work.
Press Ctrl-C to abort...
*** BREAK
3. > Workbench:Utilities/XTools > XenaStatus
Warning: This set of XTools currently only tested on X1000
Cannot allocate XTAGPORT resource: already used by XTAG Command line tools.
Okay, I figured it out. I have also HunoPPC's libegl wrapper installed.
It has its only set of configuration files in ENV/ENVARC:EGL_wrap directory. But SDL3 scans all sub directories it also picks up ENV:EGL_wrapper/SDL_RENDER_DRIVER and overwrites ENV:SDL_RENDER_DRIVER.
My suggestion is to call ScanVars with the flag GVF_SCAN_LEVEL (do not recurse into sub dirs).
News feed
OS4 Feedback forum
OS4Depot Feedback forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
