I have inspected it at a friend's system in the meanwhile and both the Fast RAM as well as the graphics RAM are the biggest obstacles that I found so far. Maybe Cloanto's engagement will change this one day. I wonder why Hyperion does not do this on their own.

As I said I did not buy OS4 yet, so I cannot try CB on my own. This is why I put my questions here.

Hello everybody,

I think about trying CodeBench on OS4.1FE UAE (did not buy it yet). As far as I know, UAE only supports 128MB of RAM. How much of this is free after starting the OS? How much memory does CB need? How much does it need for compiling typical Amiga-sized sources? Can bigger projects be dealt with this limited amount of RAM? Can SDKs for AROS, MOS be included? Is there support for LaTeX projects? What is the maximum resolution that OS4.1 on UAE supports? From what I know a Picasso IV is emulated, so 1600×1200×16 would be the max, right?

Quote:
Did you try? What I experienced with locked files is that I can neither move nor delete nor rename them (which is what makes sense at most in the meaning of "locked", anyway), so all your wishes come true at once.

SuperBase is no good idea. AFAIK SuperBase is still proprietary and differs in functionality from platform to platform. Either use MUIbase which is available on all Amiga flavours plus some other platforms in the same state or use AutoDocs instead. There are AutoDoc readers available on any Amiga flavour. That way, those files can be easily integrated in every SDK.

@Wanderer

I also tried various times to persuade Mason to use higher resoluted images. There are a lot of reasons for using different sizes of images: fitting to different font sizes, usage in media center applications where you want to see bigger buttons, or just think of handicapped people who would be happy to use bigger than just tiny images for orientation. As long as we have no vector icons on our desktops the only reasonable method is to draw bigger images and rescale them on the fly for own needs. To that respect, the result of your algorithm is simply convincing. Very good quality plus the option to overlay images by various effects saves a lot of time. Only one instead of three images needs to be designed for every state.

@kvasir

That's what I did many years ago. I more think you are talking about Spitfire which made those changes necessary. AFAIR the tools that CH introduced several years later did not need this namechange but anyhow they did not work for me. I asked CH about it that time but he could not help.

@kvasir

I don't need any new Smartphone. I would be happy to sync my Zire with any Amiga application via USB. The tool that CH provided sadly never worked for me although we both have the same Palm device. Good luck for your work.

@Antique

Here you'll find buttons for nearly everything: http://www.masonicons.info/aiss/

@afxgroup

Yes, please! This is no waste of time but very much wanted as Amiga has a big gap here for years.
Is it likely that you also may put out a 68k or AROS version later? Both are very portable and can play on so many x86 devices such that you can directly compare results to the original.

@klesterjr

Nice pictures again, thank you for that.

@Mason

Quote:
So I guess you have some more time for a new Wunschkonzert ignition plese.

@joerg

> DOSType SFS\2:
> Max. partition size: 1 TB * blocksize/512.

If I understood you correctly, you completely integrated the former SFS2 into SFS >= 1.275 by using the DOSType CFS\02 now. That way I should be able to format a harddrive of 500GB with OS3.x to its whole size into single partition. I tried so with Amithlon (OS3.9.2) on my ASUS A8V Deluxe which has a supported SATA controller onboard. The drive shows up correctly in HDToolBox and can be fully prepared there. But I am not allowed to make any partition bigger than 128GB. Did I understand the Changelogs and your calculation wrongly? Can it be addressed in future versions to make use of the whole drive as one single partition?