Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: CU_AMiGA on August 26, 2003, 04:04:38 PM
-
Hello!
I own an Amiga 1200 with a Blizzard PPC 160/060@50mhz. Can anyone tell me how to set up Warp Up properly? Everytime i boot up and the Workbench screen comes up i get some stupid "termination" window. I know what this is about, Warp Up and Power Up running parrallel. I have heard of running Power Up emu under Warp Up (using BlizzFix), but how do you set it all up?
-
How I did it...use BlizKick.
This is a ROM kicker which you can set up to run modules...one of which is BlizFix040 - or something...this removes the old 68040/060 library from memory - which IIRC is put there by the ROM in the Blizzard. This is what is giving you grief.
It did take quite a lot of messing around to get this to work but just read and re-read the instructions on getting BlizKick to work and you'll get there.
HTH
Allen
-
i need a whole lot more info before i can tell you , what os are you running and what gfx card etc.
beyond that...
getting wos to work on my setup required me to update the rom ...
(old one wasnt mediator compatible)
cheers
-
To remove the termination requester you need to remove ppc.library from memory before WarpUP is started. This can either be done by running BPPCfix in the startup-sequence or by adding the patch to BlizKick.
Get BPPCfix (and the ppc.lib emulation) from here: http://devnull.owl.de/~frank/ppcemu_e.html
Get BlizKick from Aminet: http://www.aminet.net/aminet.cgi?string=blizkick
Well, you can also set the Termination variable to 2, but then the ppc.lib emulation does no longer run.
Bye,
Thomas
-
Hi everyone,
Many thanks for the replies and advice. Sorry, i forgot to mention that i have Amiga OS 3.9 and have a Blizzardvision with CybergrahX 4.2! I have also got Warp OS 4 and Warp 3D on that Wipeout 2097 CD, and i also have Warp OS 5 on Amiga OS 3.9. I have already tried using BPPCfix, but i cant seem to get it right. (The line i use is: BPPCfix Install 040 Reboot - is this right?). And i also installed the ppc lib emu as well.
But when i do this, the termination window no longer appears, but i either get the Power Up stuff to work and not the Warp stuff, or i get the Warp stuff to work but not the Power Up stuff. (ie: i try to run Wipeout 2097, but a requester comes up saying 'unable to open file .tmg' or something.) And after that, the system grinds to a sniverling halt! :( Having said that, when i reinstall the Warp libs, without resetting, the Warp stuff and the Power Up stuff seem to work okay!
I have also tried the termination settings, but i dont really no what i am doing.
Well anyway, thats enough blabbering, i haven't yet tried BlizKick yet, so i will download that and have another bash!
Thanks!
-
should be the same with and witout blizkick aslong as you have bppcfix installed..
this is a "madmatt" call really.. i will message him and let him help you :)
cheers
-
Once you get blizzkick installed, install the BPPCFix module and any others you wish to utilise, you do not require the bppcfix040 module or require a seperate bppc fix command. It is normal for blizzkick to reboot once its done its stuff.
Make sure the latest WarpOS5 is installed and in its settings set Terminator to "0" andenable "NOPatch".
Get the latest PUPEmu lib from link below and install it to libs.
http://devnull.owl.de/~frank/ppcemu.html
you do not require the beta wos lib or the bppcfix command. I must stress again you must use latest WarpOS and not this beta lib for full working functionality.
In The frogger Archive (Or at least it used to be) theres a command called "InstallPPCLib" which you can put anywhere in your startup sequence and in my opinion is the best command of its type as other cause all sorts of weird troubles.
Hopefully the above has got you mostly sorted just keep posting if not ;)
-
Many thanks for the replies! :)
As i said, i will have a bash at it tonight and let you know how i get on. I will download the necessary files and that and follow the instructions.
-
That's what I meant! :)
Sorry for the confusion! Its been a long time since I messed with an Amiga startup script...or even turned a real Amiga on.
Hope you have sorted it even with my mad ramblings confuddling the solution :)
Although I am pretty sure I couldn't get it to work without using the 040 module - memory is fading tho'
Allen
-
Hi everyone, (again)
I had a go at it this morning, but again no luck. I have BlizzKick, PPClibs and BPPCFix, but i cant get them to work. (BPPCFix does reboot the machine though).
What instruction would i use for BlizzKick and BPPCFix? I currently use BPPCFix Install 040 Reboot, but i dont seem to get any success. Either one or the other works, but not both of the Warp and Power Up stuff. :-(
As for Warp Up, i have version 5 on Amiga OS 3.9 and Warp Up 4 on Wipeout CD, are they good enough, or are they considered as beta?
What about this update on Aminet:-
http://www.aminet.net/biz/haage/WarpUP_V51Upd.readme
My specs are:
Amiga 1200T
Blizzard PPC 160/060@50mhz
Blizzardvision
Amiga OS 3.9
3.1 ROM
128meg Fast Ram
I will have another go at it and see if i followed the instructions/advice correctly, but i am going through hell here! :evil:
-
If WarpUP programs run without the termination requester, the first hurdle is taken.
Now check that you installed the emulation ppc.library instead of the original one. In the archive there should also be a program called LoadLib or something like that. You should copy the program to C: and add the line LoadLib libs:ppc.library into your user-startup. After that PowerUp-Programs can be run from Workbench and from the Shell, without having to run them manually with RunELF.
Bye,
Thomas
-
by Thomas on 2003/8/27 13:40:58
To remove the termination requester you need to remove ppc.library from memory before WarpUP is started. This can either be done by running BPPCfix in the startup-sequence or by adding the patch to BlizKick.
Well, you can also set the Termination variable to 2, but then the ppc.lib emulation does no longer run.
Read carefully WarpUP doc. (PoweuUpEmu/README)
Note for the last flasRrom update for BlizzardPPC:
BLIZZARD PPC NOTES
You will get some problems on a BPPC with a new flash ROM, because
the original ppc.library is a resident module and will be initialized during reset.
The only chance is to use BPPCFix (should be included in the WarpOS V4 distribution) and install another resident module, which
removes the ppc.library from the system before it can initialize itself. Refer to INSTALLATION for further informations.
Afterwards you have a 'clean' system, which allows you to start WarpOS without using a Terminator (as on a CSPPC). Please use a
Terminator setting of '1' or '0'. WarpOS will not work with the emulation in terminator-mode '2'.
I suppose that if you own a Mediator, you have installed the last flashRom update.
Ciao
-
What is the difference from what I wrote ?
Bye,
Thomas
-
Thomas wrote:
If WarpUP programs run without the termination requester, the first hurdle is taken.
Problem is though, that i can get that far, but Warp OS dont work properly, the ppc emu works perfectly.
ie: on Wipeout, the settings screen loads up but i cant get the screen settings to work/come up. But if i reinstall Warp without rebooting, it seems to work, - both of them!
Anyhow, i have now reinstalled Amiga OS 3.9, and am about install Warp os 5.1 update off aminet. But when the options come up:
Warp OS 5
Power Up compatible version 7
Which one of them should i choose?
-
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 :)
-
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....
-
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! :-)
-
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?)
-
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!
-
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.
-
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
-
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
-
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! :-)
-
@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
-
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?
-
Hi,
Can someone please tell me if my sounds as if its running okay! It will put me out of my misery! :-)
Cheers!
-
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
-
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
-
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
-
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! :-)
-
Hi,
Sorry to be a bother again guys but can someone please send me (email) a small program/demo for Power Up that they know that should certainly work under emu. I just want to be certain that i have everything up and is running A OK. I have got AmigaAmp PUP and Frodo PUP to work but MAME and ADoom PPC doesn't seem to work. If someone could finally put me out of my misery then i would be most gratefull.
Thanks.
-
email sent.
though u should try and grab any demos etc from ppc demo database (the one i am maintaining..)
cheers
-
Many thanks for the file lempkee! :-) I will download it and try it out ASAP and let you know how i get on!
Cheers!
-
Just an update. I couldn't get that file to work lempkee. But i will have a check on the website and download some more files to check whether or not my system is set up properly or not.
Also, concerning the Warp Up prefs, when you said set the termination settings to "0" i couldn't get this so i set it to "off". Is that right?
Cheers!
-
0 = off yes .
in the gui anyway, but if u check the text file it generate , then it will say 0 ...
about your pup issues , well heh arrgh :) is the first word that pop's into my head.
many things can be the reason really, but if u got all settings correct then it should work , so then it might be other problems like...not enough mem/rtg etc and ofcourse wrong versions of libs etc , also you never told me what that error was,
do that..
remeber u normally need Runelf and such to start a pup ####e :)
goodluck..
-
InstallPPCLib from the frrogger package is the best ElfLoadseq patch/command ive found, slap it in ya user startup with the powerup emu fully installed and ya should be able to run powerup stuff as if they were normal wos files.
-
doh! ofcourse...i forgot about that one....have it installed though ... heh!
-
@Mad-Matt,
I installed the InstallPPClib (from the frogger archive), just like you said and followed the instuctions you gave (BlizzKick, conig, etc). The situation is that some PUP stuff work and others dont, which is a little annoying, as the ones i want to work (PUP MAME) dont work!
@lempkee,
Sorry, i forgot what the error mesage was, but i click on that .elf icon and nothing happened. The screen just flashed (dark) and gave a message. Let you know. Also i will try out some other demos soon when i have the time.
Cheers!
-
@lempkee
The error message was "icon has no default tool" or something like that.
Cheers,
-
dood , use shell / cli :)
works fine then ..
beyond that..if u want to use icons , go to icon information and set correct info in it ..
and read the readme :)
cheers
-
@lempkee,
I tried the walkir program but i had no luck. I tried it under shell but i got a flash screen and then a message saying "icon(s) have no default tool(s)". Any ideas why this happened or what it means? As i said earlier, i may give the other programs a go as well.
Cheers,
-
@lempkee
I have just downloaded some other demos from that site. So i'll try them out later and let you know what happened.
Thanks,
-
Ahh! Mistake!
I was meant to say the error message was "file not executable", when started under shell! The former error message i said was when started from workbench! Silly me!
-
@CU_AMiGA
error message was "file not executable"
Let me translate it for you. ;-)
It tries to tell you "Your LoadSeq() patch is not working. Do something about it or use 'runelf'".
-
PiR wrote:
@CU_AMiGA
error message was "file not executable"
Let me translate it for you. ;-)
It tries to tell you "Your LoadSeq() patch is not working. Do something about it or use 'runelf'".
Thanks. But how can i solve this. I take it i type runelf under shell then.
-
@lempkee,
The demo now works. :-) I forgot to install the InstallPPCLib file. Also ADoom PPC now works but MAME pup still doesn't function correctly.
-
great , but i could always send you mame pup ...but ERRK its big so email me and say its ok to get a 5+ meg email..
cheers
-
@lempkee,
I don't think my email will accept it cos i only have 6meg and have used 10% already. If its the one of aminet or triumph then i most likely already have it. Give me a link where you got it from as it would be easier. Can't wait till i get my Amiga on the 'net. No ####ty limitations!
Regards,
-
Hi!
You skill full guys, why don´t write a little HOW TO?
Many many amigan will be glad to have this.
Best Regards!
-Frank
-
Mad-Matt wrote:
Once you get blizzkick installed, install the BPPCFix module and any others you wish to utilise, you do not require the bppcfix040 module or require a seperate bppc fix command. It is normal for blizzkick to reboot once its done its stuff.
Make sure the latest WarpOS5 is installed and in its settings set Terminator to "0" andenable "NOPatch".
Get the latest PUPEmu lib from link below and install it to libs.
http://devnull.owl.de/~frank/ppcemu.html
you do not require the beta wos lib or the bppcfix command. I must stress again you must use latest WarpOS and not this beta lib for full working functionality.
In The frogger Archive (Or at least it used to be) theres a command called "InstallPPCLib" which you can put anywhere in your startup sequence and in my opinion is the best command of its type as other cause all sorts of weird troubles.
Hopefully the above has got you mostly sorted just keep posting if not ;)
That is basically how you do it! Thats what i done, followed these instructions and i think i may have finally solved the problem! :-)
@lempkee,
Where did you get your MAME PUP from?
Another question:
Why are there 2 PPC Kernals? Why can't we just have Warp Up or Power Up, not both?
Regards,
-
@CU_AMiGA
Why are there 2 PPC Kernals? Why can't we just have Warp Up or Power Up, not both?
Because PowerUp is (was) supplied with phase5 PPC boards (the first PPC boards for Amiga), so it was the kernel for everyone to start with.
In a meanwhile H&P managed to create WarpOS, their own PPC kernel, which appeared to be better and more Amiga-like. But you have to download and install it first (and to disable embeded PowerUP with all the troubles you also had...). The last nail to PowerUP coffin gave ppcemu.library, which made possible to run PowerUP compilations under WarpOS.
-
PiR wrote:
@CU_AMiGA
Why are there 2 PPC Kernals? Why can't we just have Warp Up or Power Up, not both?
Because PowerUp is (was) supplied with phase5 PPC boards (the first PPC boards for Amiga), so it was the kernel for everyone to start with.
In a meanwhile H&P managed to create WarpOS, their own PPC kernel, which appeared to be better and more Amiga-like. But you have to download and install it first (and to disable embeded PowerUP with all the troubles you also had...). The last nail to PowerUP coffin gave ppcemu.library, which made possible to run PowerUP compilations under WarpOS.
Yeah but surely Power Up is better then Warp Up. Most of the stuff (3D) seems to run a bit faster and smoother (MAME, ADoom). Many people also prefer Power Up as well. Don't get me wrong, Warp Up is still good just not as good.
I am keepeing my system the way it is, Warp Up and Power Up emulation, cos most of the things i have installed make use of the Warp Up Kernal.
Would it have been possible to make the stuff that are Warp Up only onto Power Up, (Wipeout, Amidogs emulators, etc).
Bye!
-
In the end WarpOS won out as al the good stuff and dev tools were comming out for warpos. and witht he benefit of warp3d it bcame a complete system to base ya games on. also the aos doesnt get patched under wos like it does for pup. Speedwise, theres minor differences. some stuff faster for pup, some for wos but when pup stuff stopped being developed it was just easier to emulate pup for the few apps that might still need it since the rest of the os evolved to include warpos into its system. As a user it doesnt matter to me one way or the other which is actually the best. now theres just one kernal (warpos) everything runs without hassle, no need to keep pup in the system (and the emu is there if needed). to a developer pup might have been easier but to a developer thats only knows wos, warpos is probably easier.
to sum up WarpOS won so theres no broblem in choosing which kernal should take prominance on the system.
-
CU_Amiga wrote:
Yeah but surely Power Up is better then Warp Up.
No, it's not. WOS is not perfect either, and cross-compiling stuff for it is still very difficult.
Most of the stuff (3D) seems to run a bit faster and smoother (MAME, ADoom).
WOS stuff often used MMU hacks. PUP stuff didn't.
Don't believe the stuff about WOS having less context switching - that's in hardware and can't be fixed. The example programs that came with WOS to show better performance were rigged.
Would it have been possible to make the stuff that are Warp Up only onto Power Up, (Wipeout, Amidogs emulators, etc).
Yes. All PUP lacked was Warp3D. And as others said, the emulation lib killed it.
MorphOS is doing just fine with the same ELF format, so it's not that which made PUP unpopular.
-
Yeah but why did Warp Up come out? Weren't everyone satisfied with Power Up? Also if Power Up had Power 3D (or equivalent to Warp 3D) then would it have been just as popular if battled face to face with Warp Up? And more importantly, ran the same stuff as Warp Up?
(edit)
Would it have been possible to run Warp Up emu under Power Up? :-)
-
CU_Amiga wrote:
Yeah but why did Warp Up come out? Weren't everyone satisfied with Power Up? Also if Power Up had Power 3D (or equivalent to Warp 3D) then would it have been just as popular if battled face to face with Warp Up? And more importantly, ran the same stuff as Warp Up?
You missed all the flame wars from 1997-1999 about the subject of PUP vs. WOS. It's quite interesting, since its a sort of forerunner of the MOS vs. OS4 war. All sorts of nasty things were said about both sides. If I remember rightly, WOS was called a ripoff and a bad hack, and PUP was called buggy and too closed. Probably both are a little right: WOS isn't reknowned for stability and uses a weird register setup (which will make it very hard to emulate under OS4), and early versions of PUP did have bugs, and indeed was very closed (intentionally, since the authors didn't want coders using hacks that would break in future hardware releases).
As to what was really better... I don't know. I like aspects of both. It doesn't really matter now, WOS "won". Don't take it so simple as the best option won, since when did that ever happen? VHS beat Betamax, PC beat Amiga.
Would it have been possible to run Warp Up emu under Power Up?
I don't think so. WOS allowed "hacky" things that PUP never would. Although MOS emulates WOS and is better at it than the original, so maybe it wouldn't have been impossible.
-
@KennyR
Did these flame wars happen on these forums or elsewhere? Is it possible for me to still read them?!