@LiveForIt

Yes, exactly, if you code something for a specific CPU, you can sometimes take advantage of the caches being automatically flushed due to, for example, running a large piece of unrolled code. That will save you the hassle of actually doing the flushing programatically. It might even be faster, depending on how the actual cache flush has to be performed.

I have always assumed that the CPU cache is on by default since there's an option in the early startup menu to disable it. But perhaps that option only affects SetPatch somehow, I really don't know.

Yes, FPSE will, for each write, check if that write does modify a compiled block or not. That might seem very slow, but it is only a single table lookup.

@LiveForIt

Self modifying code may be a pain in the you-know-where for a JIT/recompiler, but you still need to handle it to some extent when emulating a CPU with a cache. It's quite simple to design your code in such a way that the cache is automatically flushed as need, without using any of the cache control opcodes. (Silly example for the 68020: Store 256 bytes of NOPs somewhere and jump through them to flush the cache.) There is also a lot of older software, designed for the A500, which runs just fine on an A1200 with the cache enabled.

By implementing some simple cash coherency, only forward modifications within a compiled block will fail to work. This is the approach used by FPSE for example, it simply ignores the special register setup and writes which are normally used to flush the cache, and instead handles the flushing itself as needed, i.e. when a compiled block is modified.

@kas1e

Had a quick look at the sources and started by searching for the setting of w, as I had issues with that myself in the past. Anyway, if I remember correctly it should basically be set to 1.0-z, but you are setting it to 1.0/z. Don't know if that's the issue here though (not in front of my A1 right now)...

@kas1e

FPSE is using DrawElements and is working with 4.1 update 1 and the Radeon 9250. I'm guessing something isn't setup correctly and just happends to work on the Radeon 7000 (and "lesser") but not on the 9250.

(I wouldn't use the FPSE Warp3D plugin with a Radeon 9250 though, as all textures will be rendered at half intensity (too dark), as there's something wrong with the colorscaling in the R200 driver.)

Gloom as well as other games and lots of demos back then, used the copper to change the palette on each line of the display. This gave a kind of chunky mode with a horizontal resolution of about 100 pixels. Much faster than any chunky to planar conversion on slow CPUs. This can't work on non-AGA machines though...

@nubechecorre

3.1 is not required, 3.0 works fine.

@Futaura

Gnash seems to be progressing quite well these days. Still has a long way to go though. But in combination with ffmpeg it should apparently handle youtube quite well atleast.

Too bad there's no public SDK for IBrowse plugins

@Mikey_C

Have you tried pressing the spacebar? You will have to look really hard to find a game which doesn't work with VICE, and I'm sure I've played Flimbo's Quest without problems.

Maybe you have a bad crack or you have forgotten to enable true drive emulation? Really, better always keep true drive emulation enabled and just enable Warp mode in case the loading is too slow for your taste. Flimbo's Quest is definately a game which does not work if you disable it.

@RacerX

Quote:
And remember to have it enabled for multi-load games or they will most likely fail to load levels etc.

@Lio

The config contains the IDs reported by AmigaInput, so it's not possible for me to tell if there's something wrong there or not.

As for the analog/digital switch, it's probably not recognized by AmigaInput and thus can't be used by joyai, so you need to use a button on the keyboard instead. (This button is used to change the type of PAD reported from the plugin to the PSX game.)

If I remember correctly, when I set my USB pad in analog mode, the digital pad will end up being treated like a hat by AmigaInput.

One thing is for sure though, you must always keep your USB pad in the same mode when configuring as when playing, you can not switch between analog/digital mode as that will change the IDs reported by AmigaInput for the very same button on the pad, which will confuse the plugin.

@Lio

There's do dual shock support in FPSE currently. It might be easy to add to the PSX Port plugin (OS3 only currently).

I don't remember if there's any support in AmigaInput yet.

@Lio

The cdrom plugin isn't very clever (yet). There is no read-ahead buffer in there, and when streaming audio from the CD it doesn't take much before the audio buffer runs empty and the audio begins to stutter.

@MamePPCA1

I've tried to set sensible defaults. Just start with a fresh install, select gpupeops, cdrom or cdimage and joykey for joy0. If using cdrom you need to set correct device and unit, but other than that, don't change any settings (other than maybe disabling the BIOS emulation if you have a BIOS dump).

@Amigamancer

If something is destroying your ADSL modem, it's most likely a spike on the telephone or electric wire and/or a problem with the splitter. I've abused ADSL and network equipment a lot and the only time something has broke is in relation to a thunderstorm.

@rwo

I may be totally wrong here, but I found this page which seems to indicate a TolerANT 53C710 might be used. If that's correct, I guess it's the same chip as the A4091 and WarpEngine SCSI controllers. Linux drivers sources seems to be available here for example.

But then I know absolutely nothing about SCSI

@MamePPCA1

IMHO Bochs is way too slow to be of much use currently.

@agafaster

The RR-Net should work in the Amiga clockport, although Jens doesn't recommend it. Don't know if anyone tried to write drivers for it.

@nubechecorre

Looks like your monitor decides not to scale the image to fit the monitor screen, but rather just places it pixelmapped somewhere or something. I assume you have some kind of "auto adjust" button on your monitor, does pressing it make any difference?

@MamePPCA1

The CD32 has problems reading burned CDs, just like the PSX and others. Better use originals only.

@Ferry

Well, if you put a CF card in an IDE adapter to make it act like a HDD in every way (that's the point of doing so), then it isn't any more (or less) removable than any other HDD. It's just flash based rather than using some megnetic media of some kind. But still a non-removable HDD...

So, a CF card in a CF2IDE adapter better report itself as non-removable, if it doesn't, then I understand there may be issues...