Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: orange on August 03, 2006, 10:27:18 PM
-
I've noticed that some games run too fast in WHDLoad, is there a program to slow down '060 to A500 speed?
-
You can try turning off the CPU caches with the NOCACHE tooltype. But, I'm not sure how to really slow the thing down. What game are you runing, and what is the slave version.
-
For WHDLoad just use the tool types, RTFM... ;)
FOR NON WHDLOAD: There are plenty of degraders, like no4060, tude, degrader, jst, embedder etc. If you want them email me and I can send them to you.
The way they work is you run the command first in a shell, then you run the game. Usually you create a script file to launch the game. You usually have to reboot after, even if the game allows to quick back to WB as it patches the system to make it run slower.
-
How do you access the NOCACHE tooltype? I've tryed this myself but can't. I have a full registered WHDLOAD install.
Thanks..
-
It's for the Setpatch command in sys:s/startup-sequence.
Look for the line
SetPatch SKIPROMUPDATES "scsi.device" QUIET
and change it to
SetPatch NOCACHE SKIPROMUPDATES "scsi.device" QUIET
But I don't think this is really what you want. Try booting you Amiga with the "2" key held down. This disables the 060 entirely. (Unless like me, it doesn't work, probably due to my keyboard adaptor and Windows Keyboard)
Cheers
-
Akiko wrote:
How do you access the NOCACHE tooltype? I've tryed this myself but can't. I have a full registered WHDLOAD install.
Thanks..
Just add the tooltype to the icon of whatever game it is. (Icon->Information from the Workbench). By default there's usually SLAVE=game.slave and PRELOAD. Make sure the correct video mode is set too - NTSC or PAL. Running PAL games in NTSC can cause timing problems.
-
lurkist wrote:
It's for the Setpatch command in sys:s/startup-sequence.
Look for the line
SetPatch SKIPROMUPDATES "scsi.device" QUIET
and change it to
SetPatch NOCACHE SKIPROMUPDATES "scsi.device" QUIET
Cheers
but scsi.device update or not, does not has to do anything with the cpu cache/data/burst/superscalar or any else mode.
-
Akiko wrote:
How do you access the NOCACHE tooltype? I've tryed this myself but can't. I have a full registered WHDLOAD install.
Thanks..
If you try typing "CPU ?" into a shell, it will print the template for the CPU command, and you can then disable/enable the instruction and data caches.
-
The CPU command in AmigaDOS should let you turn caches on and off as well as other functions. I'm not sure if it is up to date enough for an '060 though.
-edit- Wow! Posted the same solution at the very same second
-
Whoa, this thread spun out of control really quick. I'd like to clear some things up.
The OP said HE IS RUNNING WHDLoad. The ONLY thing he needs to do to disable caches in the WHDLoad game is add the NOCACHE tooltype to the particular games icon. (Thanks Matt for mentioning this...)
Since WHDLoad sets up it's own emulation environment degraders/system hacks/etc. generally don't work, or end up causing trouble for the emulated environment.
This ones a bonus clarification, as it's really not on topic...
Using the SETPATCH option NOCACHE DOES disable the CPU's data cache. But, again, I don't think that will help here.
-
My bad I did not see he said WHDLoad, post corrected.
Akiko, do you know how to edit tooltypes on the icons in WB? You have to add the tooltype NOCACHE to the game icon. If you do not know how to do this you really should purchase an Amiga DOS 2 or 3.x manual and it. :)
-
I have tried enabling NOCACHE in icon and deleting PRELOAD, but it makes no difference.
-KGB still runs fast, with sound skipping.
-Syndicate seems faster than normal too.
-Gobliins run ok, but the screen between levels goes away to quickly.
any other tooltypes?
-
Strange, with my Apollo 060, KGB runs fine without any tooltype change.
-
The install for Syndicate has been updated a lot over the past year or two. Make sure you're using the latest version (of WHDLoad as well). Other timing troubles can be traced back to the nature of the game's slave - it's just the way they operate when hacked to run from HD.
Screens that display for just the right amount of time on floppy are usually to mask a loading operation. Since a hard drive or RAM (if PRELOADed) is infinitely faster, those screens just flash by. This happens in the Superfrog Intro as well. ButtonWaits or BlitWaits might help here. Check the WHDLoad docs for details on those options.
I usually like the NOAUTOVEC tooltype as well.
If the timing seems grievously wrong, report it as a bug to the author of the install.