SetPatch v43.6 non-beta? - Page 2

daxb · 29 October 2013, 01:57

I did not disable anything. Just launch "SetPatch Quiet". There isn`t much to disable btw.: QUIET/S,NOCACHE/S,REVERSE/S,NOAGA/S:

Photon · 29 October 2013, 02:05

Hopefully it adapts to your hardware and does exactly the things it outputs

And yes, the Gateway one was a rebranded 43.6. Yet again the cynic survives. :P

One interesting question is whether the Gateway one can be patched to 43.7? Then it would truly be a pure rebrand

ShK · 29 October 2013, 02:59

Quote:

Originally Posted by daxb

I did not disable anything. Just launch "SetPatch Quiet". There isn`t much to disable btw.: QUIET/S,NOCACHE/S,REVERSE/S,NOAGA/S:

But does it allow to disable all the patches what it does contain?

Quote:

Originally Posted by Photon

One interesting question is whether the Gateway one can be patched to 43.7? Then it would truly be a pure rebrand

Wasn't able to, I tested it already.

ShK · 29 October 2013, 03:20

Doesn't seem to be an easy way to see what patches the Setpatches contain?

Which one would choose for the AmigaOS 3.1, SetPatch97 or SetPatch v43.6b with the MMULib/Fixes?

( AmigaOS 3.5+ uses SetPatch v44+ )

ShK · 29 October 2013, 12:04

Quote:

Originally Posted by Photon

I'm going to go out on a limb and say Setpatch97 is 43.7 rebranded with Gateway...

(Kill the cynic!!) Anyway.

I think you're right. I did a comparison between the SetPatch v43.6b and the SetPatch97:

SetPatch97 appears to be SetPatch v43.6b, of which only the names have changed...

zipper · 29 October 2013, 18:22

That's the usual Gaz quality...

daxb · 29 October 2013, 23:24

In the most cases it doesn`t make sense to disable the both switchable patches what are "Enable AGA" and "Enabled data cache". If you want to disable the other patches you can just don`t run SetPatch.

As far as I know on demo parties the usual launch is "SetPatch" then "Demo".

SetPatch V44+ (OS3.5+) has more options. OS3.1 is just quite simple and we have to live with it but there exists a lot of other patches.

I would recommend to use the offical SetPatch 43.6. Some may want to use the MMULib patch.

Photon · 29 October 2013, 23:46

Yes, it seems MMUlib changes for 43.7 in changelog was for add-on programs/drivers.

There is no 43.6, only 43.6b, and 43.6b is still a good baseline for demo makers and compo orgas.

All is clear!

ShK · 31 October 2013, 17:42

Quote:

Originally Posted by daxb

Quote:

Originally Posted by ShK

Is the first intended to be used only with the mmu.library?

In the mmu.guide you can read this:
"This patch is independent of the mmu.library or the 68040.library or the 68060.library in this archive, even though their installation is recommended if this is possible."

We should not to use the MMULib/Fixes SetPatch43.7 as stand alone, because it doesn't load 68040.library:

Code:

AMIGA ROM Operating System and Libraries
Copyright © 1985-1997 Amiga International, Inc. 
All Rights Reserved.

SetPatch (V43.7) has been installed.  Patch list:
	BOOL CheckIO() workaround
	Enabled Advanced Graphics Modes
	AmigaOS Copyright
	HWG IEEE Single Precision Mul/Div/FPU Fix
	Graphics WritePixelLine8
	graphics/WriteChunkyPixel() patched
	Memory Pools
	Enabled data cache

Count Process Name       Action     Target Name                 Options Res.
----- ------------       ------     -----------                 ------- ----
1     ramlib             Load       LIBS:680x0.library                  Fail
2     ramlib             Load       680x0.library                       Fail

daxb · 31 October 2013, 18:58

680x0.library schould load the correct CPU library. Of course it has to be in libs folder.

Photon · 31 October 2013, 19:08

I always run the vendor CPU command before SetPatch (and never use the AmigaOS one), I don't see another way to get MapROM and Copyback cache off? (What I'm asking is, isn't that how you should do it and this would load the correct library for the accelerator, so 43.6b is enough?)

I only saw application-specific MMU patches in MMUlib? I guess you might need it if you plan to run Unix or OS 3.5+, but then you'd already have much newer libs and drivers anyway?

ShK · 31 October 2013, 19:26

Yes, SetPatch43.6b loads the correct CPU library as stand alone. The MULib/Fixes SetPatch43.7 is not independent of the MMULib.lha package.

Code:

AMIGA ROM Operating System and Libraries
Copyright © 1985-1997 Amiga International, Inc. 
All Rights Reserved.

SetPatch (V43.6) has been installed.  Patch list:
	68040 Support Code Loaded
	BOOL CheckIO() workaround
	Enabled Advanced Graphics Modes
	AmigaOS Copyright
	HWG IEEE Single Precision Mul/Div/FPU Fix
	Graphics WritePixelLine8
	graphics/WriteChunkyPixel() patched
	Memory Pools
	Enabled data cache

Count Process Name       Action     Target Name                 Options Res.
----- ------------       ------     -----------                 ------- ----
1     ramlib             Load       LIBS:68040.library                  OK  
2     ramlib             Load       LIBS:68060.library                  OK

daxb · 31 October 2013, 19:49

If you mean with MapROM that ROM is mapped to FastRam then SetPatch 43.6 doesn`t do it. Later versions (OS3.5+) will do it. I don`t know why you want to switch Copyback cache off at startup but you can disable it anytime if you wish.

SetPatch 43.6 (OS3.1) doesn`t load the correct library for the accelerator. The mmu.guide say it loads 68040.library. If you use SetPatch.pch from MMULib it does this:

Code:

Patches "SetPatch" to load the 680x0.library instead of the 68040.library on startup, regardless of the processor available.

Code:

680x0.library
This is the master CPU dependent library. If the SetPatch update has been installed, SetPatch will load this library on startup. It's then the matter of the 680x0.library to check for the CPU type and load the correct processor support library, e.g. the 68040 or the 68060.library.
                
This library is for the CPU and FPU what the mmu.library is for the MMU: The abstraction level for CPU and FPU control. For example, it is required by the "FPU" command to setup the exceptions the FPU might generate.

MMULib packet contains a lot of stuff. Nobody will need/use all of them. You just pick what you want. E.g. it depends on which OS you have running. Almost everything is explained in the guide. So if you have time just have a look.

For example I use OS3.1 with mmu.library, 680x0.library, disassembler.library, SetPatch patch, FastIEEE, MuScan, MuEVD (for ShapeShifter), MuForce (enforcer), MuGuardianAngel.

Bamiga2002 · 01 November 2013, 15:14

I could also be using it, but MMULib doesn't like BlizzardPPC much according to the docs.

gulliver · 02 November 2013, 06:49

Not only that, but it has a naming problem.
MacroSystem created a mmu.library back in 1995!

31 October 2013, 19:49	#33
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,310	If you mean with MapROM that ROM is mapped to FastRam then SetPatch 43.6 doesn`t do it. Later versions (OS3.5+) will do it. I don`t know why you want to switch Copyback cache off at startup but you can disable it anytime if you wish. SetPatch 43.6 (OS3.1) doesn`t load the correct library for the accelerator. The mmu.guide say it loads 68040.library. If you use SetPatch.pch from MMULib it does this: Code: Patches "SetPatch" to load the 680x0.library instead of the 68040.library on startup, regardless of the processor available. Code: 680x0.library This is the master CPU dependent library. If the SetPatch update has been installed, SetPatch will load this library on startup. It's then the matter of the 680x0.library to check for the CPU type and load the correct processor support library, e.g. the 68040 or the 68060.library. This library is for the CPU and FPU what the mmu.library is for the MMU: The abstraction level for CPU and FPU control. For example, it is required by the "FPU" command to setup the exceptions the FPU might generate. MMULib packet contains a lot of stuff. Nobody will need/use all of them. You just pick what you want. E.g. it depends on which OS you have running. Almost everything is explained in the guide. So if you have time just have a look. For example I use OS3.1 with mmu.library, 680x0.library, disassembler.library, SetPatch patch, FastIEEE, MuScan, MuEVD (for ShapeShifter), MuForce (enforcer), MuGuardianAngel.

02 November 2013, 06:49	#35
gulliver BoingBagged Join Date: Aug 2007 Location: The South of nowhere Age: 46 Posts: 2,358	Not only that, but it has a naming problem. MacroSystem created a mmu.library back in 1995! Last edited by gulliver; 02 November 2013 at 06:56.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
scsi v43.47 beta need testing	Cosmos	Coders. General	3	22 October 2011 22:18
scsi v43.46 beta need testing	Cosmos	Coders. General	131	22 October 2011 22:14
Cybervision 64/3D and setpatch	JackLeather	support.Hardware	23	19 April 2009 23:27
SetPatch: Unloading possible?	mrleeman	support.Apps	1	21 July 2008 10:06
where can i find setpatch 44.38	turrican3	request.Apps	5	07 May 2007 19:46

29 October 2013, 01:57	#21
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,310	I did not disable anything. Just launch "SetPatch Quiet". There isn`t much to disable btw.: QUIET/S,NOCACHE/S,REVERSE/S,NOAGA/S:

29 October 2013, 02:05	#22
Photon Moderator Join Date: Nov 2004 Location: Eksjö / Sweden Posts: 5,694	Hopefully it adapts to your hardware and does exactly the things it outputs And yes, the Gateway one was a rebranded 43.6. Yet again the cynic survives. :P One interesting question is whether the Gateway one can be patched to 43.7? Then it would truly be a pure rebrand

29 October 2013, 03:20	#24
ShK Registered User Join Date: Mar 2013 Location: Lahti / Finland Age: 53 Posts: 456	Doesn't seem to be an easy way to see what patches the Setpatches contain? Which one would choose for the AmigaOS 3.1, SetPatch97 or SetPatch v43.6b with the MMULib/Fixes? ( AmigaOS 3.5+ uses SetPatch v44+ )

29 October 2013, 18:22	#26
zipper Registered User Join Date: Mar 2004 Location: finland Posts: 1,844	That's the usual Gaz quality...

29 October 2013, 23:24	#27
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,310	In the most cases it doesn`t make sense to disable the both switchable patches what are "Enable AGA" and "Enabled data cache". If you want to disable the other patches you can just don`t run SetPatch. As far as I know on demo parties the usual launch is "SetPatch" then "Demo". SetPatch V44+ (OS3.5+) has more options. OS3.1 is just quite simple and we have to live with it but there exists a lot of other patches. I would recommend to use the offical SetPatch 43.6. Some may want to use the MMULib patch.

29 October 2013, 23:46	#28
Photon Moderator Join Date: Nov 2004 Location: Eksjö / Sweden Posts: 5,694	Yes, it seems MMUlib changes for 43.7 in changelog was for add-on programs/drivers. There is no 43.6, only 43.6b, and 43.6b is still a good baseline for demo makers and compo orgas. All is clear!

31 October 2013, 18:58	#30
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,310	680x0.library schould load the correct CPU library. Of course it has to be in libs folder.

31 October 2013, 19:08	#31
Photon Moderator Join Date: Nov 2004 Location: Eksjö / Sweden Posts: 5,694	I always run the vendor CPU command before SetPatch (and never use the AmigaOS one), I don't see another way to get MapROM and Copyback cache off? (What I'm asking is, isn't that how you should do it and this would load the correct library for the accelerator, so 43.6b is enough?) I only saw application-specific MMU patches in MMUlib? I guess you might need it if you plan to run Unix or OS 3.5+, but then you'd already have much newer libs and drivers anyway?

01 November 2013, 15:14	#34
Bamiga2002 BlizzardPPC'less Join Date: May 2004 Location: Finland Age: 46 Posts: 3,210	I could also be using it, but MMULib doesn't like BlizzardPPC much according to the docs.

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