Warp Up And Power Up Problems

[lempkee]

warpos 5 is what you choose , then forget PUP for a while.

boot the system up (in working WOS)then you put the ppc.library up in Libs: and open blizkick with bppcfix.

before you reboot now , go to sys:prefs/warpos   and set terminators to what madmatt said.

hope that helps, also dont go crazy over pup, alot of the pup stuff doesnt even work .
but some stuff works, so i know pup is up

[darksun9210]

one thing you may find is some warp up apps don't like powerup. i only switched on the powerup emulation to run UAE on workbench to play the old games.

also, i don't know if it was just me, but i had hells own problems with warpup version 5. dunno if 5.1 is any better, but to get wipeout to be playable, ie work, used to install version four. ok it was old, but it worked.

sorry to say but it was the one thing that naffed me off with my miggy, the fact that the software upgrades seemed to just make it more and more unstable. oh yeah, and wipeout doesn't like some of the higher versions of warp3d either. fun huh. :-P

the only reason i had for running warpos 5 was for the iMAC emulation....

[CU_AMiGA]

darksun9210 wrote:

sorry to say but it was the one thing that naffed me off with my miggy, the fact that the software upgrades seemed to just make it more and more unstable.

Agreed. If its one thing that will make me abandon ship and get an eMAC (not a bloody PC :-)  ), it would be because of that. Maybe i should have stuck with my Blizzard 1260 and AGA. lol

Just one more point, what modules would i put after BlizzKick and BPPCFix?

Well anway, i am armed with some good advice now, so i will have another few goes at it. Thanks lads! :-)

[lempkee]

Blizkick * EXTRESBUF=1225943 QUIET MODULE SpeedyIDE SpeedyChip bootmenu romfixes NoClick romupdate.idtag filesystem.resource FixGetMsg console.device ram-handler exec.library BPPCFix


here is an example of my line , but anyway
u need to check closely as this is a patch/hack to be suited best for every system , ie some systems will be damned slow with my setting...or great (like mine)

cheers

(i messaged u earlier, didnt u get it?)

[CU_AMiGA]

lempkee wrote:
Blizkick * EXTRESBUF=1225943 QUIET MODULE SpeedyIDE SpeedyChip bootmenu romfixes NoClick romupdate.idtag filesystem.resource FixGetMsg console.device ram-handler exec.library BPPCFix

Ha! Ha! I will try out that line and see what happens!

(i messaged u earlier, didnt u get it?)

I did get your message, but it wasn't about the Blizzkick modules! (It was Warp!).

Well anyway, thanks again, i will try that and see the results!

Cheers!

[CU_AMiGA]

I have installed BlizKick and put a line like this:-

Blizkick * EXTRESBUF=1225943 SpeedyIDE SpeedyChip romfixes NoClick FixGetMsg BPPCFix

On the startup-sequence, i put this just after the Setpatch SCSI part. The machine now boots up 3 times but on the 3rd time i get a window saying "Inuitation is attempting to reset workbench screen. Please close all windows except drawers."

And then nothing happens, nothing closes and no Workbench screen appears, apart from when i click cancel, and if i minimise the window. Oh yeah, the output on this bit is only on the native Amiga RTG output (before, you could see the results on both the Blizzardvision and RTG output, but then messes up.)

I have tried, putting the line in different places in the startup-sequence but no luck yet. Can anyone tell me if that is the right line or not for my machine (see earlier for Amiga spec). I get the impression that i am fairly close, so i will have another go at it and see the results.

Cheers.

[lempkee]

that line "MUST" be before SETPATCH!!!

and setpatch must have this line:


C:SetPatch QUIET NOROMUPDATE


in an example , this is how my startup-sequence looks like.



; $VER: Startup-Sequence_HardDrive 45.2 (19.1.2001)
; Startup-Sequence for AmigaOS 3.9

Blizkick * EXTRESBUF=99943 QUIET MODULE scsi.device SpeedyIDE SpeedyChip shell romfixes NoClick romupdate.idtag filesystem.resource FixGetMsg console.device ram-handler exec.library BPPCFix


C:CheckLMB
IF WARN
SYS:Prefs/ATA3Prefs
ENDIF
C:ATA3.driver QUIET



PsdLoadModule DEVS:input.device QUIET ;Added by Poseidon-Installer

resident run remove
resident c:run ADD PURE


C:SetPatch QUIET NOROMUPDATE

C:mcpramlibpatch
C:StackAttack MIN=150960 ADD=150960

[lempkee]

forgot to say, this way it will require 1 reboots.


first 1 is blizkick installing , then it will reboot auto , then it will load up my fastata prefs and setpatch , but since i dont use update (have all in blizkick) it wont reboot again.

also , you should make sure that you can actually use speedyide , also speedychip is for 060 systems ONLY.

hope my posts helps u.

cheers

[CU_AMiGA]

Okay thanks. I will try that ASAP. I have an 060 system so i am okay on that. I think i am coming near to the end of this problem, well i hope so anyway. Let you know tomorrow people! :-)

[Framiga]

@lempkee

Hi lempkee,

can you explain me the "mcpramlibpatch" line?

Someone told me that it is no more useful with the last rev of MCP. . .is it true?

Thanx

[CU_AMiGA]

Good news guys! I think we have finally made progress! I followed the instructions and changed my startup-sequence.

Wipeout now runs without any problems. As for the Power Up stuff, i am not too sure, i had Amiga Amp running under Power Up and it was working fine, but when i tried MAME Power Up i got as far as the menu with the games, but when i tried running the game i got a Power Up exception screen or something.

I think someone said that Power Up emu is still quite incompatable, so i am guessing that i have cracked it and its the best you can do. Can someone confirm this?

[CU_AMiGA]

Hi,

Can someone please tell me if my sounds as if its running okay! It will put me out of my misery! :-)

Cheers!

[lempkee]

framiga: well ermm mcp ramlib patch is for thoose who doesnt run MCP  , you missed the whole point i guess..

i dont run mcp so i run the ramlib patch.

easy as that.

cheers

[lempkee]

cu: pup is hard, ppc is hard....

amiga amp works best in wos mode, mame pup is the fastest we got and works fine under pup emu.

also i think i have found maybe...10-20 prods that aint wos pup emu ready (working) , but there is alot to take care of before you know for sure that it wont work..

about mame , that crashed here also in the start , dont know why..but i downloaded a new file from the mame site and now it works fine (with menu etc).

the best way to test pup emu is by running pup tools , but seriously i can't recomend much.

why i said wos is what u want to use anyway...

be sure you have enough free mem when you run mame + make sure you have unzip ppc version if you dont ...well it will crash or be very slow..

cheers

[lempkee]

sorry , was abit fast...

i meant RTG + FAST RAM , if any of theese go below "what ever the Minimum is" then it will give you an WOS EXCEPTION under pup emu..

REALLY Annoying...

on CGFX this is impossible to tell as there aint any RTG mem indications , so when you run it for a testing , use low res on wb and no backdrop and make sure your mem is as clean as possible.

cheers

[CU_AMiGA]

I have several versions of MAME already so i will try all of them or look for others. The reason why i used Amiga Amp in Power Up mode is cos i wanted to test to see if it worked okay. I now use it in Warp Up mode! :-)