@levellord

yours is an X5000 right?

This was removed in 53.34 SDK. It is causing a build issue for cross compiler.

Hi, in preparation for a fresh install I want to know what other people do.

Do you install Enhancer Core, Enhancer 1 and then Enhancer 2 or do you just install Enhancer 2 on its own?

Yes, works on my x1000 fine too.

Can you also test out SSHTerm with a password and press enter or return instead of pressing okay.

I am definitely thinking I have some corrput gadget somewhere. I think a fresh install will be worth doing anyway.

Actually, for me DefIcons just seems totally broken. Even clicking on an existing pattern and then pressing enter results in garbage being appended to the final Action Pattern string.

1. Open DefIcons
2. Go to any filetype entry (with a "PATTERN" Actions")
3. Click on pattern and enter the text box
4. Make a modification
5. Move the cursor to the end of the pattern text and then press "Enter" or "Return"
6. Notice that the PATTERN has appended an "n" character

Let me guess, this is not happening for anyone else?

This could possibly explain why I also have to click on "OK" when I use SSHTerm to enter a password VS just entering the password and pressing enter otherwise I get an unauthentication error due to a bad password. Possibly I have a corrupt gadget?

Yes, I run Amiga OS4.1 Final Edition Update 2 + the two hotfixes, on both X1 and X5. I do not have a crash on the X1, but I have a crash on the X5.

@nbache

Thanks for the tips. I agree with the comments wrt. simplification, but if I was to run the script from a shell already vs just double clicking the icon I made, then the unsetting of the locals and setting stack to original would be beneficial when I was finished with mame and decided to continue using the very same shell to do more and different things, right?

That is my belief, if I am wrong then please let me know.

I mean, it is like saying: don't worry about cleaning up memory at the end of your program, or setting a pointer back to NULL once you have freed it since the OS will take care of everything, yet in every book you read it is encouraged. In fact, for the Amiga, you better make sure to release everything manually, otherwise the OS will complain. But, what I just said is a program vs a script and a little pedantic.

In anycase. I am not as seasoned as people on here wrt. Amiga, so let me know otherwise.

Regards,

My X1 is a little loud. Not too bad, but compared to, my X5 is silent.

Anyone have any good recommendations for a replacement and quiet fan for the X1 CPU? That is the thing causing most of the noise.

Hi,

public update 2? I do not know what you are referring to. Surely not FE update 2.

Yes. I am using the one from os4Depot.

Now, I replaced my "spotless" binary with this one: https://drive.google.com/file/d/1SD-sX ... At7fyC3O/view?usp=sharing (this is the latest link I could find). File size: 8699013.

I then followed @kas1e's steps from the first post in this thread.

One of those steps is to load his "test" executable. When I do this on both the X1 and X5 machines I see the assembly instructions. From there, I place the BP on line 30. When I hit start on the X5 though I see this in the "Disassembler" tab/section:



And, in the "Console" tab/section:



I can keep on clicking "Start" but nothing happens.

The difference on the X1 machine is that when I click start the PC does get to line 30 as expected, and I can still see the instructions.

===

I am not sure if there is an equivalent command to ldd on the Amiga? I would like to know which shared objects have been linked with so that I can compare the versions on the X1 and X5 machine. All I know is that I have both the latest SDK versions on both machines and that I use https://github.com/sodero/adtools/rele ... cc11.1.0-20210531-743.lha those tools and replace that whole thing as my "gcc" directory since I use that instead of the 4.2.4 version that comes with the SDK today. So, if it is a linking with some libc/++ shared object then both the versions on the X1 X5 should be the same.

Reason for the cursor appearing on the script version was due to a console window opening for capturing output. For whatever reason that caused this ESC issue.

Just *>NIL: from mame program seems to have fixed it.

Running Mame in fullscreen I press ESC to quit. It does quit, but the fullscreen window just freezes there.

The OS is active. I can bring up a shell with my shortcut keys and clearly everything still works, but the screen is frozen on whatever the last frame was.

Non-fullscreen works fine.

This is SDL mame: http://os4depot.net/share/emulation/gamesystem/sdl_mame.lha

==

Seems to be the scripts I have wrote.

I have a script file specificially for one game:

This was just to create an icon image. That is has:
Execution mode: Shell
Ask for input is enabled

"mame" is another script:

Execution mode: Shell
Ask for input is disabled



When I run it this way (double clicking the ssf2t script, first one above): ssf2t script > mame I notice that the full screen appears, but there is the AmigaOS mouse cursor. I need to click once on the screen. I can play, but pressing ESC causes the frame freeze - the window does not close.

If, instead, I do all of thise just invoking the actual "mame" binary and avoid all scripts then the fullscreen shows and there is no mouse cursor. It is already the active window/screen. Then, ESC for fullscreen does work.

I do not know what the difference would be?

Woah,

you can actually just set this variable in uboot:

setenv amigabootmenu_animate 0
saveenv

power on, and see how fast you can boot into workbench.

Actually, I think my issue is exactly post #1 from this thread: https://www.amigans.net/modules/newbb/ ... id=129743#forumpost129743.

Guess I will have to RTFT.

But, do we have now a working debugger for C code at least?

On my x1000 the test program works with both the shell version and the gui version.

On my x5000 it does not. I get a crash; I performed the same steps for the shell version as I did on the X1000, but I get:

FYI: this is the version of spotless from Os4Depot.

Great report. Keep them coming.

Just for clarity, the reason we need our own copy is because the only thing we get from Huno is the AOS4 binary and we need drop that binary into the Doom 3 folder?

Maybe it is also worth picking up Resurrection of Evil too.

It will remind me of 2003 all over again, when my Doom 3 arrived with my 6800 nVidia card. God knows where that CD is now though.

Odyssey installation directory, Conf folder, rename the "font" to something else or just delete it. Start Odyssey.

Tomorrow I will check the battery voltage and check the cables.

I have heard of cables being an issue in these machines, which I find confusing. I mean, why is it that these NG machines are so susceptible to loose cables? Think of our PCs. Never once have I needed to really reseat a cable due to inconsistent behaviour.

Still, I will do this tomorrow.