English Amiga Board


Go Back   English Amiga Board > Support > support.Apps

 
 
Thread Tools
Old 05 June 2021, 15:30   #1
SpeedGeek
Moderator
SpeedGeek's Avatar
 
Join Date: Dec 2010
Location: Wisconsin USA
Age: 57
Posts: 599
Lightbulb Unofficial AIBB v6.8 patch

Unofficial AIBB Version 6.8 patch
© SpeedGeek 2021

INTRODUCTION:
This an update to the previous AIBB v6.7 patch. It has
some new code to report the CPU Revision when a 68060
is detected.

FEATURES:
- New code reports CPU revision on 68060 systems
- Runs all original AIBB code on 60000-68040 systems
- 100% PC relative Assembler code
- Patched executable is only 52 bytes larger than v6.7
- Updates version to 6.8

REQUIREMENTS:
- Amiga with 68060 CPU
- AIBB v6.7 "Update" version!
- SAS spatch tool

WARNINGS:
This patch does NOT update AIBB to fully support the
68060 CPU in the way a benchmark program written
specifically for that purpose would do. It does NOT
functionally affect MOST of the limitations of the original
AIBB code except for allowing it to run on 68060 systems.

NOTES:
The CPU Revision is reported in the System Information screen.
This patch can NOT be applied to the older non-update v6.7
version.
Attached Thumbnails
Click image for larger version

Name:	AIBBV68_IMA.png
Views:	70
Size:	19.3 KB
ID:	72204   Click image for larger version

Name:	AIBBV68_SYS.png
Views:	62
Size:	15.9 KB
ID:	72205  
Attached Files
File Type: lha AIBBV68_PATCH.LHA (994 Bytes, 55 views)
SpeedGeek is offline  
Old 05 June 2021, 16:11   #2
klx300r
Registered User
klx300r's Avatar
 
Join Date: Oct 2007
Location: Toronto, Canada
Age: 51
Posts: 1,046
Thumbs up

thanks
klx300r is offline  
Old 08 June 2021, 02:51   #3
gdonner
Ancient Amiga User

gdonner's Avatar
 
Join Date: Mar 2018
Location: Elkhart / United States
Posts: 161
Not sure what I'm doing wrong(?), but for the life of me, I can't get the patch to 'take'...

Using Spatch from: http://aminet.net/dev/misc/spatch.lha

AIBB 6.5 from: https://bigbookofamigahardware.com/b...falcon1240.adf (as someone suggested as an alternative to try).

I've also tried http://aminet.net/util/wb/Spatcher1_0.lha and AIBB from http://aminet.net/util/moni/AIBB_65.lha ... all to no avail.

For idiots like me, may I suggest that someone with a gracious spirit post the updated executable to The Zone?
gdonner is offline  
Old 08 June 2021, 12:20   #4
BLUELiGHT
Registered User

 
Join Date: Feb 2016
Location: Asylum
Posts: 54
If I understand correctly, you need AIBB v6.7 for this patch to be applied.

So you should first update AIBB v6.5 to v6.6, then to v6.7, and finally apply the v6.8 patch in the current thread.
BLUELiGHT is offline  
Old 08 June 2021, 12:55   #5
AMIGASYSTEM
Registered User
AMIGASYSTEM's Avatar
 
Join Date: Aug 2014
Location: Brindisi (Italy)
Posts: 6,709
Yes in fact there is no information about it, I don't understand why these patches are used when many users don't know how to apply them, on Aminet there are GUIs to do it but in many cases they fail or you need an engineer to use them.
AMIGASYSTEM is offline  
Old 08 June 2021, 14:23   #6
SpeedGeek
Moderator
SpeedGeek's Avatar
 
Join Date: Dec 2010
Location: Wisconsin USA
Age: 57
Posts: 599
Quote:
Originally Posted by BLUELiGHT View Post
If I understand correctly, you need AIBB v6.7 for this patch to be applied.

So you should first update AIBB v6.5 to v6.6, then to v6.7, and finally apply the v6.8 patch in the current thread.
Finally, someone who can RTFM and use simple logical steps to solve a problem. Good work!

Quote:
Originally Posted by AMIGASYSTEM View Post
Yes in fact there is no information about it, I don't understand why these patches are used when many users don't know how to apply them, on Aminet there are GUIs to do it but in many cases they fail or you need an engineer to use them.
Unfortunately, the AIBB distribution license makes no exceptions for any user's technical incompetence and likewise the SAS spatch tool makes no exceptions either.

Last edited by SpeedGeek; 08 June 2021 at 15:06.
SpeedGeek is offline  
Old 08 June 2021, 15:31   #7
gdonner
Ancient Amiga User

gdonner's Avatar
 
Join Date: Mar 2018
Location: Elkhart / United States
Posts: 161
Let's just say (if you're not used to using it frequently) the Spatch syntax isn't the most user-friendly. "Fiendly" might be more appropriate. lol

Last edited by gdonner; 08 June 2021 at 17:53.
gdonner is offline  
Old 08 June 2021, 15:44   #8
AMIGASYSTEM
Registered User
AMIGASYSTEM's Avatar
 
Join Date: Aug 2014
Location: Brindisi (Italy)
Posts: 6,709
@SpeedGeek

Ok thanks was not directed at you personally, usual Amiga problem always full of obstacles.

You could put in the readme a ready to use script, the "technical" formulas are not good for those who don't know them or can't use them

Last edited by AMIGASYSTEM; 08 June 2021 at 16:12.
AMIGASYSTEM is offline  
Old 08 June 2021, 16:17   #9
BLUELiGHT
Registered User

 
Join Date: Feb 2016
Location: Asylum
Posts: 54
You're probably starting from the hacked 6.5 version of AIBB instead of the original one.

If you follow the original 6.5/6.6 patches threads, you'll see that the correct version was posted in an a1k.org forum thread.

Once you get that executable, you can successfully apply the patches - check you are using the correct commands as per the attached screenshot.
Attached Thumbnails
Click image for larger version

Name:	aibb.png
Views:	61
Size:	301.9 KB
ID:	72237  
BLUELiGHT is offline  
Old 08 June 2021, 17:56   #10
gdonner
Ancient Amiga User

gdonner's Avatar
 
Join Date: Mar 2018
Location: Elkhart / United States
Posts: 161
Thanks BLUELiGHT--what was throwing me off was the tacky Spatch syntax not including those spaces, which are critical for a successful patch.

Last edited by gdonner; 09 June 2021 at 02:45.
gdonner is offline  
Old 22 June 2021, 10:32   #11
Romanujan
Registered User
 
Join Date: Dec 2007
Location: Szczecin/Poland
Posts: 390
It would be easier if there was only one patch needed - from the last official binary to the target unofficial one (plus always place a warning that Aminet release is not the official binary).

The need to perform the whole chain of patches plus a policy to change the versions retrospectively (releasing fixes without bumping version number, and even posting a new 6.(n) patch, while the 6.(n+1) was already released) is a very confusing mix - you can’t even trust the files you have succesfully created yourself (or the previous patches you have downloaded and placed in your private storage), and everytime you have to re-read previous threads to understand what actually happened.
Romanujan is offline  
Old 22 June 2021, 14:43   #12
SpeedGeek
Moderator
SpeedGeek's Avatar
 
Join Date: Dec 2010
Location: Wisconsin USA
Age: 57
Posts: 599
Of course, it would be easier if there was only one patch. But the feature updates and the bug fix occurred at different times and things just didn't work out that way.

It was just not worth doing a version change for a simple bug fix, and at least there is some consistency in doing version changes for feature updates only. The problem is not all users will want all the feature updates, but they will want the bug fix for which ever version they prefer.

Unfortunately, there are users posting already patched versions in various locations but they will not always bother to update their postings. However, you can trust the files you create yourself as BLUELiGHT has just demonstrated.
SpeedGeek is offline  
Old 22 June 2021, 15:23   #13
Romanujan
Registered User
 
Join Date: Dec 2007
Location: Szczecin/Poland
Posts: 390
Quote:
Originally Posted by SpeedGeek View Post
It was just not worth doing a version change for a simple bug fix
I can’t believe this. Every released version has to be identifiable - you can’t release version 6.6, afterwards another 6.6, after some time yet another 6.6, and claim everything is OK. This is a terrible, terrible practice, against all the quality standards. Tertiary version numbers, version suffixes, etc., were invented for a reason.

Users who post patched versions do not bother to upgrade, because they have much more interesting things to do than to closely watch the development of a tool which is normally usefull twice a year. If they knew they were posting 6.6.0, and the 6.7.1 patch documentation would imply that it is the 6.6.1 binary which has to be patched, there would be no confusion at all.

Last edited by Romanujan; 22 June 2021 at 15:33.
Romanujan is offline  
Old 22 June 2021, 17:55   #14
SpeedGeek
Moderator
SpeedGeek's Avatar
 
Join Date: Dec 2010
Location: Wisconsin USA
Age: 57
Posts: 599
Quote:
Originally Posted by Romanujan View Post
I can’t believe this. Every released version has to be identifiable - you can’t release version 6.6, afterwards another 6.6, after some time yet another 6.6, and claim everything is OK. This is a terrible, terrible practice, against all the quality standards. Tertiary version numbers, version suffixes, etc., were invented for a reason.

Users who post patched versions do not bother to upgrade, because they have much more interesting things to do than to closely watch the development of a tool which is normally usefull twice a year. If they knew they were posting 6.6.0, and the 6.7.1 patch documentation would imply that it is the 6.6.1 binary which has to be patched, there would be no confusion at all.
You should now find an MD5 checksum posted on both the AIBB v6.6 and v6.7 threads. Regarding the quality standards issue, this is freeware and you don't have to use any of it if you don't like it.
SpeedGeek is offline  
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
Unofficial AIBB v6.7 patch SpeedGeek support.Apps 17 08 June 2021 17:29
Unofficial AIBB Version 6.6 patch SpeedGeek support.Apps 21 23 May 2021 17:48
Unofficial AIBB v6.5 68060 Compatibility patch SpeedGeek support.Apps 8 03 February 2017 17:02
Understanding AIBB Marchie support.Other 0 28 October 2016 07:48
three in one? (SCSI Patch,Mac Patch,MapRom) RogerWilco09 support.Apps 0 05 May 2009 16:56

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 16:04.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, vBulletin Solutions Inc.
Page generated in 0.09678 seconds with 14 queries