When reading up on the PROTECT command I realised that there are switches for USER, GROUP, OTHER.

Why is the concept of UGO in AmigaOS?

===

I see now the GROUP command. But no USER command. I am not even sure "whoami" at the moment.

Surpised by this a little, I guess.

I understand that, but what I do not want to have is a computer (even a RP) running at all times to capture the output.

I have have my X5000 connected to my A600 via Serial and I use the TERM program on the A600.

To me it just seems more preferable and convenient to capture the serial to a file without the need to have another machine turned on, although, I seem to be in a minority so there must be something I do not understand.

Okay, thanks for the information. So, when we say "cold" in this context we mean the fact that the OS is flushed out - not that there is no longer power being supplied to components.

The reason I wanted this was to have a background Sashimi process logging all debugging to a file. I felt like having a RAD: would be appropriate in the case of a freeze since there would be no overhead with writing to a disk.

I guess I will have to just log the output of Sashimi to a disk.

The reason I want to use Sashimi is because I want to be able to capture the serial output in the case of any freezes. This is not happening often, but I just want to be able to see what happened.

Is there a better way to capture the output of the serial in the case of a freeze?

RAD is meant to surive warm restarts.

If your RAD: is not in devs:dosdrivers



CNTRL-ALT-ALT



I would have expected to see "theFile" in the listing after the CNTRL-ALT-ALT?

If it worked on a classic machine and not the AmigaOne, then the AmigaOne CNTRL-ALT-ALT is a cold reboot versus a classic amiga warm reboot?

I get the same issue if instead of CNTRL-ALT-ALT I use Workbench>Shutdown>Restart Computer.

I also get the same issue if I copy the RAD: to devs:dosdrivers which saves me the manual mounting.

If the only "warm" reboot is by Workbench>Shutdown>Restart Amiga OS, then AmigaOne users using Polaris cannot use RAD: effectively.

Can someone draw a Christmas hat for

<----- LIL' EVIL VARTA ?

My uboot version: molsen 2018-10-05. Whether that is MM-DD or DD-MM I am not sure.

Thank you so much for your monthly report. Please never stop.

AMIGA IS.

To add, I use sfs.

yeah, debug level added a few seconds (no more than a few) to my bootup. i think i was using level 5. now it is just completely turned off.

i use an ssd.

good luck.

33 seconds on my X5000, but that is with the disabled animations and also debugging completely turned off.

Shouldn't use also use the FILE switch if you are quering a file?

I am not at computer right now.

Solved with latest string.gadget.

Work around before that was to run Prefs->power at startup

@Raziel

I just sent you a message.

Thanks, but that does not make any difference since it is just a wrapper for DOSBOX anyway.

Someone out there has Duke3D Atomic Edition and someone out there has tried to run BUILD.EXE using DOSBOX. I have searched for the answer, but cannot find it.

For once, I would just like to get the answer, rather than looking at porting over the source code for BUILD - which requires a really old compiler for a start.

It does seem to have a negative theme.

I have a version of 2.7.3 running on the X5000 at the moment.

I need to do some more testing and see if I can improve the PYTHONPATH / PYTHONHOME situation.

Hi.

When running "build.exe" for Duke3d Atomic Edition in DOSBOX I get the error:


But, when I run setup for "duke3d.exe" I choose 320 * 200 and the game works.

In any case, can someone tell me how to run "build.exe" in DOSBOX?

@samo79

The Italian documentation (README) will always be one version behind the English documentation. I am not sure how I feel about this, since otherwise I would have to rely on your input before updating a new version. If you are happy you can translate the following: "The Italian documentation is likely to be a revision behind the English documentation. You should also consult the English documentation".

@mufa

Thanks for the information wrt. a test-able ROM. I notice that CLIB2 on my X5020 does not seem to show any noticeable difference in terms of FPS CLIB2 1.186 version VS the previous 0.135 newlib version.

Perhaps I will upload a new version that will include:
1 - Fix to the minimise gadget (thank you Capehill)
2 - Inclusion of the SS module, despite it being ridiculously slow and requiring a quad core CPU
3 - Improvements to the English documentation which removes some redundant/false information and additions to other options to possibly improve performance.

If anyone is using 1.186 and seeing bad performance with PSX I would be interested to know because - for me - the PSX is playable. I did say before, though, that the X1000's performance is not so great at all.

When I get around to it I will attempt a port of Python 2.7 since if anyone is running Py scripts from version 2, it is generally at least 2.7. As you know, we only support 2.5 right now.

ArgParse is also in version 2 I believe.

Unless someone else is thinking about it, version 3 is just not on the horizon right now. I do think - though - that a version of 2.7 will be good for us.