GOLD 2.10 Release | page 1 2 3
|
---|
|
---|
| | Renaud Schweingruber (Apollo Team Member) Posts 381 22 Jul 2018 21:28
| GOLD2.10 released on 22.07.2018 Changes : * Added 4 different IDE speeds (V500) * Fixed SBCD instruction * Fixed ChipRAM detection * Improved CIA timings (V600) FlashBINs and JICs for V600 and V500 are available on : EXTERNAL LINK SAGA Drivers package also got an update : EXTERNAL LINK Changes : * Updated VControl to 1.6 * Updated VampireSN for Vampire V4 * Updated SDNet to 1.92 * Updated V2ExpEth to 1.92
| |
| | Leigh Russ
Posts 151 22 Jul 2018 22:27
| Any word on FastIDE for the A600? I know it has been discussed before and reasons were given against its reliability, but there are quite a few people now who would like this. We understand that it's going to be nowhere near the A500 speeds but any little gain is a bonus.. even if it's just 1mb/s or so improvement
| |
| | Knight Stone (Needs Verification) Posts 136/ 1 23 Jul 2018 02:41
| it's not gonna happen, not at least until you use the EIDE channel, that's on the V4. The IDE port on the A600 was never really meant to go above a few MB's a second, and as such, is probably pretty near maximum throughput on an accelerated A600 anyway. The only way to get faster, is to use an EIDE addin board, and maybe a mechanical PIO mode 4/5 drive, but even then, the gains will be minimal. Wait for the V4, that's the only way to get 20MB's on the A600
| |
| | Renaud Schweingruber (Apollo Team Member) Posts 381 23 Jul 2018 08:29
| As Gunnar said regarding A600 IDE, stability of FastIDE on A600 wasn't yet good enough for a mass release. If you want to squeeze some more performance on A600, you can give a try to this tool written by nonarkitten. I got nearly +10% improvement depending on configuration. EXTERNAL LINK
| |
| | Niclas A (Apollo Team Member) Posts 219 23 Jul 2018 09:10
| A500 x12?
| |
| | Renaud Schweingruber (Apollo Team Member) Posts 381 23 Jul 2018 09:37
| Gunnar is working on it :-) needs to achieve "green" timings and it takes lot of time and recompiles to reach them..
| |
| | Niclas A (Apollo Team Member) Posts 219 23 Jul 2018 10:04
| Ok :)
| |
| | Renaud Schweingruber (Apollo Team Member) Posts 381 23 Jul 2018 12:30
| V500 x12 is online now
| |
| | 8bit Dude
Posts 21 23 Jul 2018 12:45
| Thanks for this! I am trying to update my Vampire for the first time, but the Quartus software is not available anymore from Altera's website (cannot create new accounts). :'-(
| |
| | Gunnar von Boehn (Apollo Team Member) Posts 6258 23 Jul 2018 13:03
| 8bit Dude wrote:
| Thanks for this! I am trying to update my Vampire for the first time, but the Quartus software is not available anymore from Altera's website (cannot create new accounts). :'-(
|
You can use the EXE update files from AMIGA OS - without Quartus.
| |
| | Peter Weuffen
Posts 42 23 Jul 2018 14:07
| nice to see fpu off/on now functioning :)
| |
| | 8bit Dude
Posts 21 23 Jul 2018 14:33
| Yeah, but I gotta get AmigaOS working first! Anyhow, I managed to download Quartus with a to***nt, update done! (only x11 worked, x12 got workbench freezing).Next step: install coffin!
| |
| | David Wright
Posts 373 23 Jul 2018 14:43
| How does 2.10 or 2.1 become the name for the next release after 2.9? I am no whiz kid in math but it seems wrong to me. 2.95 perhaps?
| |
| | Gunnar von Boehn (Apollo Team Member) Posts 6258 23 Jul 2018 15:07
| David Wright wrote:
| I am no whiz kid in math but it seems wrong to me.
|
Lets count together: 1,2,3,4,5,6,7,8,9 .... and now comes
In computers and programming version numbers are 2 numbers separated by a dot. This means the 2nd number just counts up from 0 .... 9999999
| |
| | Peter Heginbotham
Posts 214 23 Jul 2018 15:09
| No is the short answer Version numbers would be with a minor number for new licences numbers so something like this 2.9 2.9.1 2.9.2 2.9.3 2.10 2.11 3.0
| |
| | Pedro Cotter (Apollo Team Member) Posts 308 23 Jul 2018 15:12
| Lol!
| |
| | David Wright
Posts 373 23 Jul 2018 20:55
| everything in software updates to rounding off my tax payment means the second digit after the decimal effects the first digit after the decimal. 2.8, 2.9. 2.95 then 3. or whatever. You coders do it different?Make a joke about it but the sequencing doesn't make sense. Just saying, never seen this before.
| |
| | Niclas A (Apollo Team Member) Posts 219 23 Jul 2018 21:00
| EXTERNAL LINK
| |
| | Tim Trepanier
Posts 135 23 Jul 2018 21:51
| As a kid learning to program i found the best way to understand versions was to read them out loud with each number between the "." as separate numbers. So: 2.9 - two point nine 2.9.1 - two point nine point one 2.9.2 - two point nine point two 2.9.3 - two point nine point three 2.10 - two point ten 2.11 - two point eleven 3.0 - three point zero The separation designates how large the change is from the previous version. First number is major revision (has major new features and/or major structural differences to the code) Second number is minor revision (some features added) Third number is minor change (bug fixes, code readability)
| |
| | Stephen A.
Posts 24 24 Jul 2018 02:08
| peter weuffen wrote:
| nice to see fpu off/on now functioning :)
|
agreed! fpu on/off working again :))
| |
|