English Amiga Board

English Amiga Board (http://eab.abime.net/index.php)
-   project.ClassicWB (http://eab.abime.net/forumdisplay.php?f=61)
-   -   Is it OK to use these patches with CWB39? (MCP, PatchControl, Blizkick, Executive) (http://eab.abime.net/showthread.php?t=85782)

rikbliz 31 January 2017 12:19

Is it OK to use these patches with CWB39? (MCP, PatchControl, Blizkick, Executive)
 
(deleted)

ancalimon 08 February 2017 22:58

As far as I know, there is no other patch that replaces mcpramlibpatch.

MCP is perfectly safe to use but some options cause problems. It is one of my essential patches. patchcontrol is a need but there is also another similar patch whose name I forgot. I think I use it together with patchcontrol. I will check later.

blizkick rom modules are trial and error. I do not use any of them and use it only to softkick patched rom modules.

rikbliz 08 February 2017 23:03

(deleted)

Retrofan 09 February 2017 00:59

Well, have you got getmouseinput in C?

rikbliz 09 February 2017 09:13

(deleted)

idrougge 09 February 2017 09:18

Do you have the correct MaxTransfer setting?

rikbliz 09 February 2017 09:20

(deleted)

daxb 09 February 2017 15:13

Does it mean you use an old version of MCP? I`m not sure but mcpramlibpatch might be obsolete if you use MCP 1.48. What does mcpramlibpatch?
PatchControl is safe to use. An equivalent is SaferPatches.

If you use FastATA with ata3.driver (or similar named) then make sure that is used and not "killed" by SetPatch or BlizKick. Else data can be destroyed.

rikbliz 09 February 2017 15:15

(deleted)

daxb 09 February 2017 16:56

I have not experiences with OS3.9 but maybe its SetPatch loads scsi.device "over" ata3.driver patch. I would at least check that to be sure nothing goes wrong.

rikbliz 09 February 2017 16:57

(deleted)

ancalimon 09 February 2017 20:35

Rule number 1: Always have at least one spare boot partition which you can fall back to.

Possible problem:

pio setting could be too much for your cfcard to handle. You may need to cold boot without startup-sequence and reduce the pio setting by running ata3prefs inside SYS:Prefs

Use the command that comes with blizkick (romupdatesplit or splitromupdates) to extract all the rom modules from AmigaOS ROM Update file that comes with boingbag2 and use them with blizkick. Don't forget to patch them further.

On my system the second port of FastATA MKIV for some reason sees my cfcards as 2gb and my harddrives as 2tb. Might be a bad cable...

emufan 09 February 2017 20:39

Quote:

Originally Posted by rikbliz (Post 1139815)
Using latest MCP from Aminet.

MCP 1.48

rikbliz 09 February 2017 20:42

(deleted)

rikbliz 09 February 2017 20:45

(deleted)

rikbliz 11 February 2017 13:50

(deleted)

ancalimon 16 February 2017 17:44

Quote:

Originally Posted by daxb (Post 1139814)
Does it mean you use an old version of MCP? I`m not sure but mcpramlibpatch might be obsolete if you use MCP 1.48. What does mcpramlibpatch?
PatchControl is safe to use. An equivalent is SaferPatches.

If you use FastATA with ata3.driver (or similar named) then make sure that is used and not "killed" by SetPatch or BlizKick. Else data can be destroyed.

Quote:

Q: Is MCP safe to use with 3.9, and do I still need mcpramlibpatch in my startup?
A:
Yes, but there are two things you should be aware of with MCP:

First, make sure that you don't have any options in MCP that patch diskfont.library, as this will prevent 3.9's font cache from working correctly. You still need mcpramlibpatch in your startup as the ramlib problem is caused by third-party libraries performing too complicated/stack-hungry tasks (opening other diskresident libs) within their init function. These libraries are therefore breaking certain programming rules; and it's not a bug in ramlib itself. [Stephan Rupprecht]
Lastly, activating the "Processor" feature of MCP removes the ability of the RAD: device to be resident, so switching this off in MCP will restore it.
[Philippe 'Elwood' Ferrucci]
http://www.gregdonner.org/os39faq/compatibility.html
It is essential for everyone. So we will always need mcpramlibpatch because there are many old libraries still being used that do not play by the rules. I think I have the one from rtgmaster archive and run it in my startup*sequence just before the first stackattack command.

The one I have is MCPRamLibPatch V1.1 (24.04.98)

Akira 16 February 2017 17:52

Try MultiCX instead of MCP:
http://aminet.net/package/util/cdity/mcx256

Bit of a cleaner patch.

Zeph 16 February 2017 19:17

Quote:

Originally Posted by rikbliz (Post 1140183)
So interesting development on the disk problems... I reseated the Gayle chip adapter of the FastATA (just on a whim) and now everything is back to normal. That would explain why it was working in WinUAE OK. Bit concerning though as the Amiga hasn't been moved for a long time!

Heat/vibration/a combination cöuld lösen that

daxb 16 February 2017 20:36

@ancalimon:
The RtgMaster Library guide from 1998 says:
Quote:

Note: If you use MCP, i recommend using at least Version MCP131B8. Earlier
versions might use up too much ramlib stack. According to a user, this was
fixed with Version MCP131B8. So i recommend at least this version. If problems
still appear, i recommend installing MCPramlibpatch. This might also apply
to MCP-Clones like MCX.
I would say this patch is outdated and obsolete now if it comes to use a newer MCP version. I`m sure what mcpramlibpatch does but guessing it just increases stack size of ramlib. I use romfixes patch what already increase ramlib stack size from 2k to 8k.

You can use "Cachefont" from MCP or OS3.9 build in cachefont. At least the MCP docs say so.

Processor function from MCP has several options. If option "SSP to fastram" is used RAD isn`t reset proof.


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

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2018, vBulletin Solutions Inc.

Page generated in 0.04235 seconds with 11 queries