@Raziel

If you read my previous version of this post disregard it. I overlooked an old version of saved prefs which caused AmigaAmp 3.27 to use mpega.library which doesn't appear to work on my system.

My mpega.library is version 2.4 and is the mpega.library clone v 1.7. Is there another version that I should use??

This "too wide to read" issue when using Odyssey makes Amigans.net almost unusable on an Amiga. Hopefully we can find a fix. I'm writing this to see if the "Preview" is also too wide. The preview is wrapping the text to fix the window and adjusts to the window size on the fly when I change the Odyssey window size.

I see that the above text was wrapped at 200 characters. If there is some
default line wrapping setting, maybe lowering it to 80 could be a temp fix?

@salass00
Does that mean some of the current OS4 programs on OS4Depot will not work or become noticably slower on a Tabor?

Is it really necessary to specifically target the Tabor processor for an OS4.x program to work on Tabor? If not, why bother. None of the OS4 programs I've worked on specifically target any one PPC processor.

@Raziel & Capehill
I'm not sure why the test doesn't make any sound on my X1000 but it could be my settings. Here are my AHI settings:

Driver: hdaudio.audio version 6.22
Music unit: Unit 0:Hifi 16 bit stereo++ (44100 Hz)
Unit 0: hdaudio:HiFi 16 bit Stereo++ (44100 Hz)

The device.audio that shows 'Unit 0' in the AHI 'Music unit' settings is version 6.22.

I also have the Mixer docky installed in AmiDock.

@Capehill
I'm using an X1000 with the builtin sound (hdaudio.audio) and I don't hear any sound at all. I'm running the "a.out" program from a shell and the output in the shell indicates that it's playing sound but I don't hear anything. AmigaAMP, TuneNet, Multiview and other players work fine on my system.

@Capehill
You could check out "audioevolution" at OS4Depot. It's primarily a mixer but the PDF docs have a "real-time" section. I've never used it but it might be worth a look.

@samo79
You need to run the debug version of the program and provide the crash log using that version in order to show the the program function and line number of the crash. The normal version of the program has too much data stripped in order to make the program smaller.

@Capehill

Quote:
Yep. That could be a problem if it's NULL.

Quote:
That's a good reason to switch to more modern "strlcpy". It always terminates the copy with a NULL.
Maybe something like:
strlcpy(lied.phonolithprojekt, str, sizeof(lied.phonolithprojekt)); (https://linux.die.net/man/3/strlcpy)

Since "lied.phonolithprojekt" appears in a number of program files, it might be a good idea to initialize it in the structure declaration with something like "unnamed project".

@MickJT
The Dopus4 sources are at Sourceforge with the name "diropus4". There are OS3, MOS & OS4 versions there. The OS4 code is at:
https://sourceforge.net/p/diropus4/code/HEAD/tree/dopus4-os4/trunk/

I uploaded binaries for OS3 & OS4 versions to the repository but can't even navigate the repository very well with OS4 browsers any more. You can D/L a snapshot of the OS4 code and fix your own version if you want but it's just easier to use external AmigaDOS commands for most things.

@daveyw

Here's solutions I found in an ARexx guide:

OPTIONS RESULTS
ADDRESS COMMAND
rxset reqres '`requeststring title "URL Downloader" body "Enter URL to download"`'
myresult=getclip(reqres)
call setclip(reqres,'')
say myresult

rxset reqres '`c:requestfile SAVEMODE NOICONS TITLE "Enter download filename"`'
myresult=getclip(reqres)
call setclip(reqres,'')
say myresult

NOTE:
rxset is an external arexx utility in C: (Included in the OS)
The scripts contain backward quotes produced by the keyboard key below "Esc". They are easily confused with the single quote.

@Jack
Years ago Jens Maus recovered the lost NList sources from a hard drive with burnt electronics by purchasing a new drive identical to the burnt one and moving the circuit board to the burnt drive.

@white

There are simple examples in the SDK. Assuming you have installed the SDK and all the assignments and startup are done by the lines that should have been added to your user startup, you can try this:

Open a shell.

Copy SDK:Examples/GUI/Integer/IntegerExample.c to RAM:

Change the shell current directory to RAM:

Enter "gcc -o IntegerExample IntegerExample.c -lauto" in the shell.

The program should compile (ignore the warnings; the example programs need to be updated).

Enter IntegerExample in the shell and the example window should open on Workbench.

@MickJT
I tried your solution and it was accepted in the Screenmode Prefs 'Monitors' tab. Even though the mode file was set in the 'Moditors' tab and all the resolution setting showed, the new modes didn't show up in the 'Available Modes' tab. However White's files worked and I now have all the UAE graphics modes available. Now I need to install OS4.1FEupdate1. Is there anything I need to know about intalling that or is it just a normal install?

I only have 2 partitions showing on my OS4 Workbench. The FlowerPot disk is my system partition but I don't know about the WinDH_C disk. It appears that I have all my remaining Windows disk space available for WinDH_C.

I also don't see any way to save the UAE setting from the UAE GUI. Is there a way to save the settings?

@white
I installed your files and it worked! I now have UAE screenmodes. Thanks a lot. Maybe I made a mistake in the OS4.x install that resulted in an incomplete installation. I increased the resolution and got a tiny but clear Workbench screen. I thought that increasing the resolution would give me a bigger window but I'll need to see what I can do with the UAE settings. I'll check out your video and see if that helps.

Once again, thanks a lot. The installed OS4 was almost unusable without the UAE screen modes.

@MickJT
Thanks for the help. The Flower Pot UAE config already has 'UAE Zorro III' set; which is a good thing because there is no Save button (Just Start, Cancel and Quit.

The SYS:Storage/Monitors directory in the installed OS4 only has NTSC, PAL and Multisync files so I copied the PicassoIV (and info) files from the Classic OS4 install ISO. There is no BOARDGFX variable in the PicassoIV info file but there is a BOARDTYPE variable. Should I add the BOARDGFX variable and setting or use the BOARDTYPE variable that's already there and change the setting to uaegfx for that?

@white
I appreciate you trying to help but I already have OS4 installed with "Flower Pot" and I'll worry about other configuration when I can get an OS4 Workbench screen that I can read and use. I guess what I really need is some Flower Pot help. I've seen some posts in the past where users suggested using Flower Pot to install OS4 and I assume they got a good install and could help with my problem.

I recently installed AmigaForever on my laptop and it works great. I then installed OS4 classic with Flower Pot and ended up with what appears to be OS4 on an AGA screen. Most of the screen text is unreadable, colors are limited and AmiDock is a white band across the bottom of the screen with some icons. The OS4 Screenmode prefs only show PAL and Multisync screenmodes; all of which are ugly. There are no UAE screenmodes.

Can anyone tell me how to get the UAE screenmodes to show up in Screenmode prefs so I can get better screen?

If I can't get a better screenmode is there a safe way to uninstall Flower Pot?

@orgin

O.K. I misunderstood what the example was for.

@orgin
I'm color blind and have poor vision in general (due to age) so the text on that page is very difficult to read. I usually avoid WEB sites that use dark (especially black) backgrounds. I'm probably in the minority but I have to give your example page a thumbs down.