68060 speedup patches + more

[Oldsmobile_Mike]

LOL.  I was thinking the same thing when I saw that list. Although I will admit that I still run a couple of those utilities, it's probably more of a placebo effect - they're not really helping anything.

Thomas - I did have one thing that I've always kind of wondered about though. Even on an RTG system, wouldn't Fblit still help for non-RTG screenmodes? For example, system-friendly games and apps that aren't promoted to an RTG screenmode (but use NTSC 640x200, for example)?

Would love to hear your thoughts on this. Thanks!

[Oldsmobile_Mike]

ah in fact you are correct in that my 1200T is NTSC and my desktop is PAL, I'll have a look at the PAL monitor tooltype in the 1200T?

Just put PAL in the tooltypes of the WHDLoad game. It helps some. I too, have problems with some games on my 2000 that work fine on my 500. Obviously much more expanded system, etc. Try disabling your TCP/IP stack and switching to a non-RTG screenmode before running the game. I've found those things can help, also.  

[Oldsmobile_Mike]

All right you guys, stop picking fights.  We already know you're not going to change Thomas's mind, and he's not going to change yours.  The original thread about patches, etc., was pretty good.  Let's get back to that, eh?  :hammer:

[Oldsmobile_Mike]

I haven't had any problem with Poseidon running in the background when I start WHDLoad games.  Obviously USB mice and keyboards aren't supported by games, but I haven't had to shut anything down.

My Spectrum card, on the other hand, some games will just start with a black screen unless I switch to a non-P96 screenmode prior to starting them.  That /bugs link looks interesting, will have to research further.  Thanks!  

[Oldsmobile_Mike]

I hope this explains a bit what is so terribly wrong about this program.

Hey now, it does work perfectly a majority of the time.  The number of games that have been successfully updated is a testament to the WHDLoad team.  And I'm sure all the programmers of those horrible, hardware-banging, non-system-friendly games certainly didn't foresee a bunch of crazy fanatics still wanting to play them, 30 years later.  :laughing:

[Oldsmobile_Mike]

Let me explain: The GVP spectrum has a video switch on its board. This switch can either switch the output from the Cirrus chip on the GVP board to the VGA output, or the VGA input comming from the pass-through cable from the chipset. The video switch is driven by a register on the GVP board, and the P96 triggers this switch whenever intuition switches between a native and a GVP (Cirrus) screen.

Now, if a program bypasses the Os and writes into the Custom chip addresses directly without using Intution (or Graphics, to be precise), then the video output switch remains in the position that redirects the Cirrus output to the VGA out.

So it's not at all related to P96 (which is not used by these games) nor Graphics (which is neither used by the games) nor by the hardware (the video switch is very much necessary for a video pass-through, and how else than by software should it be triggered?).

It is the fault of lazy programmers not using graphics and intuition - where P96 would be able to redirect video output properly.

Perfect explanation!  Thanks!  :pint:

[Oldsmobile_Mike]

And the hassle is exactly what? SetPatch keeps care of it, or LoadModule.

I've actually got so many modules patched by LoadModule that I've hit the "Line too long" error in Ed.  Not to mention that one typo could hose the entire house of cards... but other than that, meh.  It works.