SofaROM bug report thread

Página 6/20
1 | 2 | 3 | 4 | 5 | | 7 | 8 | 9 | 10 | 11

Por gdx

Enlighted (4693)

Imagen del gdx

27-08-2017, 14:09

The Maze Of Galious don't like too the option /Z1 when I select the Turbo R mapper or the Memory Mapper.

Por Louthrax

Prophet (2406)

Imagen del Louthrax

27-08-2017, 20:59

Hi GDX,

Can you send a screenshot of the USAS bug? In turboR mode here, I just experiment big slowdowns (plus some occasionnal sprite flickergins, caused by the slowdown). Those slowdowns are inherent to the turboR mapper, I have no solutions right now to make that faster (and probably never).

Same for Maze of Galious in turboR mode, but in Memory Mapper mode, it's not that slow here. Maybe you have disk accesses if your turboR has only 256KB RAM? Please give more details ! ("does not like" is too vague!).

Por gdx

Enlighted (4693)

Imagen del gdx

28-08-2017, 10:37

USAS with options /z1 /d1 or /z1 /d5

USAS with options /z1 /d1 /l1 or /z1 /d5 /l1

MoG with options /z1 /d1 or /z1 /d5

All works in R800 mode. All works in my ESERAM SCC even in z80 mode.

Por Louthrax

Prophet (2406)

Imagen del Louthrax

28-08-2017, 11:37

Thanks for the pictures! Still no way to reproduce that here (I tried with different SD and HD interfaces).

Can you try to make a floppy disk from this disk image (do not copy the files, make a real disk). Then boot it from your turboR with no external devices attached and try again with the same commands (SROM USAS.ROM /Z1 /D1, etc...). USAS.ROM and MOG.ROM are included on the disk.

Do not use MultiMente or load another program. That way we'll have the exact same ROM images, MSX-DOS version, etc... Let me know if you need help to create a real floppy disk from the image.

Por gdx

Enlighted (4693)

Imagen del gdx

02-09-2017, 15:12

I used PUTDISK to make the floppy disk. The problem remains exactly the same without any disk interface added.

Quote:

USAS with options /z1 /d1 or /z1 /d5
USAS with options /z1 /d1 /l1 or /z1 /d5 /l1
MoG with options /z1 /d1 or /z1 /d5

I made a mistake above, I should've written this:
USAS with options /z1 /d1
USAS with options /z1 /d1 /l1
MoG with options /z1 /d1

Metalgear1 doesn't not work right either with /z1 /d1.

Por Louthrax

Prophet (2406)

Imagen del Louthrax

02-09-2017, 18:00

Weird weird weird... Does your turboR have any internal RAM expansion (or modified BIOS)? And it's an ST model right?

To make things clear about your report: it works with /d5 but it does not work with /d1 right?

Also, have you tried lauching a RAM test on your turboR?

Por gdx

Enlighted (4693)

Imagen del gdx

03-09-2017, 10:34

Sorry about that bad feedback. Finally my partition was not destroyed and my RAM is OK! Smile
Yesterday, I did a lot of tests with my JoySNES and besides I wanted too to repartition my CF card with only one in FAT12 for the system and one in FAT16 for software instead of my 16 partitions in FAT12.
By creating batch files to make a conditional dual-boot Multi-Mente/Sofarun using MSX-DOS 2.44, I moved the command FAT16.COM. So I get a “Not a DOS disk” and Sofarun froze up. I then thought Sofarun couldn't stand the FAT16.
Sofarun works fine and now my dual-boot too. It took a lot of time but now it's much simpler to use. Smile

The issue with SOFAROM still not solved by cons.

Por Louthrax

Prophet (2406)

Imagen del Louthrax

03-09-2017, 12:13

Ah, good Smile!

This bug is still very strange, I'd really like to find the cause of it.

To summarize:

  • The same disk works fine here on my 1024KB expanded turboR ST (no extensions or anything plugged), but has graphical bugs on your turboR ST (no extensions or anything plugged).
  • The graphical bugs only appear in Z80 mode and "turboR mapper" or "Memory mapper" modes.
  • The disk is the same (with the same ROMs images), SofaROM is the same too, so that should be a hardware difference between our 2 configurations (can't think of any other explanation for now!).

So we have to identify what's the difference between our two configurations here. Some questions (maybe already asked but I want to be sure):

  • Your turboR is an ST model?
  • Does it have any internal RAM expansion?
  • Has the power supply been modified internally or do you use an external 220V->110V adapter?
  • Does it have any internal modification (modified BIOS)?

And as the problem happens only in Z80 mode, can you try TESTRAM.COM in Z80 mode?

Por Grauw

Ascended (10055)

Imagen del Grauw

03-09-2017, 12:41

I remember when I had a dozen FAT12 partitions. Just the single FAT16 partition sure was a big improvement Smile.

@Louthrax If you want me to do a few tests on my turboR GT to add a 3rd result, feel free to mail me with some files and instructions.

Por gdx

Enlighted (4693)

Imagen del gdx

03-09-2017, 13:09

- My TurboR is also a ST expanded to 1024KB with a simm RAM Module.
- The graphical bugs only appear in Z80/R800 mode with "turboR mapper" selected (by default or with /d1).
- I use same ROM as you.
- During the tests, I only used my Turbo R A1-ST + Sunrise CF interface (an original) with two or one CF.
- I removed the Sunrise CF interface to test your floppy disk. I used the internal floppy disk drive (the original) and nothing else.
- The ST is powered on 100V (not 110)
- The is not modified.

My contact have a GT also expanded to 1024KB. I do not know more. He has similar problems in Z80 and less in R800 mode.

Página 6/20
1 | 2 | 3 | 4 | 5 | | 7 | 8 | 9 | 10 | 11