31 March 2020, 19:48 | #21 |
Registered User
Join Date: Jul 2017
Location: San Jose
Posts: 688
|
I think part of the success of 3.1.4 was the notion of making things better and removing bugs without additional cost. Power without the price so to speak ;-)
This made it very attractive to people with even base or moderately accelerated 68k Amigas. On the other hand, the reason 3.9 never caught on seems to be that people perceived it as bloated and sluggish. So my wish would be: implement new features in a way that they are either usable on humble machines or give people the option to opt out of things. Don’t make them pay (In terms of ram usage or performance) for features they may not use. I guess this boils down to the question: what is are the minimum hardware requirements to settle on for 3.2 My personal wish is: better (remote) debugging facilities provided by the operating system. Bebbo implemented a GDBserver that works, but is rather limited. It would be great if exec could provide hooks and other debugging facilities (potentially utilizing the MMU) that make implementing a debugger much easier. Alternatively, the OS could come with a full gdbserver... Thanks for the hard work! |
31 March 2020, 19:53 | #22 |
Camilla, AmigaOS Dev.
Join Date: Mar 2020
Location: Frederiksberg
Posts: 350
|
First of all the non blinking block cursor was a necessity on old text terminals where you couldn't draw a line in between characters where the text is inserted.
Secondly a block signifies a selection and thus a block cursor could easily be misread as a single character selection. The block cursor is reserved for overwrite mode, where the cursor actually behaves like a 1 character selection all the time. (Overwrite mode is not implemented currently but there is plans for it mostly because the API has promised so for 20 years) The blinking could strictly speaking be turned off with a setting, but it is important to be able to find the cursor easily with your eyes and blinking helps to that end. So I thought it was not worth the time to make such a setting, as most people will end up having it blinking in the end anyway. I am aware some people like the block cursor (you being among them) but for most users it is more important to have a cursor with a meaning that is actually logical, and similar to what they work with on modern computers. |
31 March 2020, 19:54 | #23 |
Coder/webmaster/gamer
Join Date: Oct 2001
Location: Canberra/Australia
Posts: 2,716
|
|
31 March 2020, 20:08 | #24 |
Registered User
Join Date: Mar 2002
Location: Kansas City, MO, USA
Posts: 683
|
I may be a bit out of the loop on this topic, but if you look at support.Hardware forum here, there are multiple stickies around getting CF cards to work, maxtransfer, filesystems, etc.
Are there any plans to make any of that process easier? |
31 March 2020, 20:10 | #25 |
BoingBagged
Join Date: Aug 2007
Location: The South of nowhere
Age: 46
Posts: 2,358
|
@hUMUNGUs
We take all Amiga systems into account. We try to do our best not to leave anyone behind. AmigaOS 3.2 will work on any hardware/software combination that is sufficiently smilar to an Amiga. There are no special provisions for specific hardware other than what the known Commodore Amiga models provided out of the box. And speaking of the future, that really depends on you, the user. We have some ideas that we collect as a team, but it is yet to soon to elaborate on them since we have a more immediate task at hand: develop and test AmigaOS 3.2. So that is why it is of paramount importance that you have a saying in what are your likes and dislikes as a user, because these will influence directly on desision making when the time comes. @utri007 We would love to help Chris. We need to support other developers. I believe Olaf tried in the past to help him in some related matters. Our hands are tied right now because we are very few, with a lot of work ahead. But at least we now know, thanks to you, the situation regarding NetSurf annd whom to approach. @spudje The AtapiMagic module was supplied by Thomas Richter in order to test its compatibility on enabling 4 way ide interfaces. The result was not what was expected, and while it worked on some systems, unfortunately on others, like yours, it failed. We don't knowingly ship half working components, as we are commited on quality. So, it is unlikely you will see this component released, unless it gets seriously fixed. And realistically I would not bet on that for the time being. On the other hand, itt is funny that you mention those features, because they were part of our internal conversations some time ago. I will take note on those for review when the time comes to trace a path beyond 3.2. @th4t1guy After some back and forth trying to solve this issue, fortunately enough, the HDToolBox "max transfer" value is no longer required on the built-in scsi.device driver of 3.2, and also on drive interfaces made by the manufacturer formerly known as "GVP". @pipper We all agree with you to keep everyone on board, not leaving 68000 users behind is still our objective and we are succeding in that. AmigaOS 3.2 will work on humble machines. The hardware requirements of 3.1.4 are the still much the same on 3.2. Last edited by gulliver; 31 March 2020 at 20:21. Reason: Added more answers |
31 March 2020, 20:28 | #26 | |
Camilla, AmigaOS Dev.
Join Date: Mar 2020
Location: Frederiksberg
Posts: 350
|
Quote:
As for speed and requirements. The current requirement is still only an 68000 and the TextEdit application have been tested on such a system to make sure it is usable. The memory requirement is to the best of my knowledge in the same ballpark as 3.1.4 and we intend to keep it like that. A harddisk is all but required like with 3.1.4, and the diskspace used will be a bit higher, but we are not talking bloat at all. And I'm speaking like a person who never wanted to use 3.9, so I sort of know where you come from. We have people happy with 3.9 in our ranks too, so all views are respected. We murmured over this just the other day, and someone said that when 3.9 came out the thought was that new Amiga platforms would come and then those were the target. But today we want to make something for both the retro computers, as well as be there for the high end systems. So it is a different mindset. |
|
31 March 2020, 20:48 | #27 |
mä vaan
Join Date: Nov 2001
Location: Finland
Posts: 1,692
|
You have now somebody to test/ develop CDTV version of it? Have you noticed this;
https://github.com/terriblefire/cdtv.device |
31 March 2020, 21:25 | #28 | ||
Registered User
Join Date: Jun 2009
Location: Dublin, then Glasgow
Posts: 6,419
|
Quote:
Quote:
Last edited by Daedalus; 31 March 2020 at 21:31. |
||
31 March 2020, 21:34 | #29 |
Registered User
Join Date: Feb 2015
Location: Sweden
Age: 50
Posts: 3,010
|
Is a new ROM 3.2 planned or is this a pure software update that runs off 3.1.4 ROMs?
|
31 March 2020, 21:50 | #30 | |
Camilla, AmigaOS Dev.
Join Date: Mar 2020
Location: Frederiksberg
Posts: 350
|
Quote:
That does give me a headache for how to activate rectangular selections when I implement that because alt is the de facto standard for that and as you can see that is already used. Oh well it is the lesser used thing to do in a texteditor, so I will have to come up with something else. |
|
31 March 2020, 22:42 | #31 |
Registered User
Join Date: Dec 2011
Location: Poland
Posts: 166
|
Please add:
Installer: -icons style selection during instalation(standard/GlowIcons). Bootmenu: -booting from CD -possibility to disable CPU features (not only all cache) -Amiga model/CPU/Memory recognition Locale: -polish locale |
01 April 2020, 00:34 | #32 |
Registered User
Join Date: Dec 2010
Location: Norway
Posts: 845
|
Keep up the awesome work guys!
I’d love fixes to the cdtv kickstart / extended rom to accept a500 cpu cards. See utri007’s post above. Stephen Leary and Toni Wilen did some work already. (I have a spare working cdtv I can lend or sell cheaply to olaf or thor if interested) Adding features for casual retro gamers will greatly improve sales. And what they struggle with the most are prepping/formatting CF/SD cards, and transferring files to the amiga, so anything that can help those two would be nice. Perhaps these could be possible? 1: compactflash.device bundled (fat95 or crossdos) 2: Bootable pcmcia cf/sd cards. (even better: Bootable with fat format) 3: Feature in hdtoolbox to create one FAT partition after the amiga partitions, to allow access on pc/mac. (Amiga files on FAT gives problems with file attributes, but there could be a warning/disclaimer at least. Plus it might need an MBR, which has to be in front of the RDB) 4: Minimal beginner friendly file transfer tool for serial to usb with tiny matching pc app. 5: More beginner friendly HDtoolbox 6: Small button to toggle view all/only icons in window frame somewhere Last edited by fgh; 01 April 2020 at 00:50. Reason: CFD |
01 April 2020, 07:58 | #33 |
Blitter
Join Date: Aug 2017
Location: England
Posts: 50
|
Will the CD32 get any love this time as it missed out on 3.1.2?
|
01 April 2020, 08:12 | #34 |
Registered User
Join Date: Feb 2007
Location: Melbourne, Australia
Age: 41
Posts: 3,773
|
You may want to reconsider calling it TextEdit. I don't think Apple will like that.
|
01 April 2020, 08:19 | #35 |
Coder/webmaster/gamer
Join Date: Oct 2001
Location: Canberra/Australia
Posts: 2,716
|
@demon-knight:
No, for the same reason as for OS3.1.4: https://www.hyperion-entertainment.c...amigaos-update @Hewitson: I don't see how Apple or anyone could have rights over that name; it is a generic functional name. Just like the "Copy", "Delete", etc. commands. |
01 April 2020, 08:23 | #36 | |
Blitter
Join Date: Aug 2017
Location: England
Posts: 50
|
Quote:
|
|
01 April 2020, 09:38 | #37 |
Registered User
Join Date: Aug 2010
Location: Germany
Posts: 548
|
90%? Yikes. I thought that the updated memory management system I built into my clib2 'C' runtime library specifically for NetSurf should make a difference. While I do not know the details, the availability of a current clib2 build for 68k might be the cause of the problems with the 68k version.
|
01 April 2020, 09:50 | #38 | |
Registered User
Join Date: Aug 2010
Location: Germany
Posts: 548
|
Quote:
Access to real hardware for testing and those knowledgeable in how the hardware was modded are another challenge. Also, we can't really build the kind of ROMs which would be needed. The question of whether we are authorized to reuse CDTV and CD32 code aside for a moment, we currently lack the necessary knowledge to do CDTV or CD32 versions justice. Last edited by Olaf Barthel; 01 April 2020 at 09:59. |
|
01 April 2020, 09:56 | #39 | |
Inviyya Dude!
Join Date: Sep 2016
Location: Amiga Island
Posts: 2,807
|
Quote:
Thanks for the what must have been huge amount of work you put into this... |
|
01 April 2020, 09:59 | #40 |
Registered User
Join Date: Aug 2010
Location: Germany
Posts: 548
|
|
Currently Active Users Viewing This Thread: 4 (0 members and 4 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
AmigaOS 3.1.x v 3.9 | steve_mynott | New to Emulation or Amiga scene | 35 | 19 April 2020 06:23 |
AmigaOS 3.9 | PoLoMoTo | support.WinUAE | 8 | 27 August 2011 18:06 |
AmigaOS 3.5 or 3.9 | maddoc666 | support.Apps | 12 | 22 February 2010 08:02 |
AmigaOS | koncool | request.Apps | 6 | 04 June 2003 17:45 |
AmigaOS XL | sturme | New to Emulation or Amiga scene | 4 | 15 January 2002 02:13 |
|
|