openMSX about to release: testing help wanted!

Page 5/7
1 | 2 | 3 | 4 | | 6 | 7

By hit9918

Prophet (2905)

hit9918's picture

30-10-2014, 20:29

I thought the TurboR VDP brake is only on internal VDP ports and other OUT have a different brake.
The VDP brake is excessive, below MSX1 vram transfer rate.

By Manuel

Ascended (18148)

Manuel's picture

30-10-2014, 21:47

hit9918 wrote:

lol now I changed it in catapult and registy immedeately changes. things work.
I was all the time doing the unplug in openmsx console.
only catapult gui click goes to registry.
but some other variables are in settings xml.

That's why I said in my first reaction:

Quote:

Did you unplug it in Catapult or in openMSX itself?

Catapult remembers what was plugged in and will plug it in next time. So if you unplug it in Catapult, it will not automatically plug it again next time.

Tongue

By hit9918

Prophet (2905)

hit9918's picture

30-10-2014, 22:49

Ok I was a bit distracted by recursive grep and regedit, I get nervous when there are unclear things with file locations Tongue Smile

On a sidenote, another file thing, sjasm crashes when trying to write a ROM that is loaded in the emu.
Well and in the end the problem is that a file lock is held on the ROM file.
Normaly when coding diskloaders I press F12 for a speedload reset script with nice turnaround times, but coding ROMs is no fun when always needing to close the openmsx.

By Grauw

Ascended (10062)

Grauw's picture

30-10-2014, 23:30

Maybe that’s a Windows specific thing? No such problems when compiling Synthesix with Glass while openMSX is running it.

By Manuel

Ascended (18148)

Manuel's picture

31-10-2014, 11:51

Use a workaround: first eject the ROM in openMSX before writing the file?

By giuseve

Paladin (744)

giuseve's picture

31-10-2014, 15:10

News about a new version of catapult?
What do you think about FS-UAE gui ?

By Manuel

Ascended (18148)

Manuel's picture

31-10-2014, 20:00

As development on Catapult has ceased already years ago (around 2007), don't expect a lot of news on it. It is kept alive, though, so it will keep working and shipped with openMSX installer on Windows until we have a better alternative.

By hit9918

Prophet (2905)

hit9918's picture

07-11-2014, 07:55

I had issues with dir-as-disk.
A disk with many tiny files (I think they had 30 bytes, made with "echo >file" on PC), and then some of the other files was empty.
I think it was autoexec.bas, early in alphabet.

By wouter_

Champion (467)

wouter_'s picture

07-11-2014, 09:21

hit9918 wrote:

I had issues with dir-as-disk...

Did openMSX give any warnings while you were using the dir-as-disk? For example 'virtual disk image full' or 'root directory full'. (Normal MSX disk images can only contain 712kB data and max 112 files). Were there any host files with similar filenames that might map to the same MSX filename? (You also get warnings for this).

I just did an experiment where I added approx 100 small files and a few big files on a dir-as-disk. When I exported that image again all the files were identical to the originals. Or in other words: I cannot reproduce the problem. Can you provide more details? Maybe send a zip with all the host files you were using?

Thanks.

By hit9918

Prophet (2905)

hit9918's picture

09-11-2014, 17:27

ok the disk was full.
I'm not 100% sure it is the same situation, but likely that was it, I had a too big file while I thought the many little files did something.

Page 5/7
1 | 2 | 3 | 4 | | 6 | 7