08299: pv1000, pv2000: Mazy Not loading

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
08299	Media Support	Trivial	Always	Apr 18, 2022, 21:11	Apr 19, 2022, 00:05

Tester	Kaylee	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	Open	OS	Linux (64-bit)
Status [?]	Acknowledged			Driver	casio/pv2000.cpp
Version	0.242	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	08299: pv1000, pv2000: Mazy Not loading
Description	Mazy is a new homebrew that came out this year. When loading it in mame it complains: Fatal error: Device Generic Cartridge Slot load failed: Unsupported cartridge size. The PV-1000 also gives the same error. http://inufuto.web.fc2.com/8bit/mazy/ Tested the Pyuuta version and it works in MAME
Steps To Reproduce	Download the rom, and run: mame pv2000 -cart "~/Downloads/Compressed/mazy(PV-2000).rom"
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	pv1000, pv2000

Attached Files

No.20083 kmg Senior Tester Apr 18, 2022, 22:28 edited on: Apr 18, 2022, 22:29	The PV drivers currently expect any software loaded to be either 8K or 16K. As a temporary solution you could pad the ROMs out to 8192 bytes with zeros.
No.20084 Tafoid Administrator Apr 19, 2022, 00:05 edited on: Apr 19, 2022, 00:10	As would a original hardware solution an image would need to be on an eeprom matching to traditional power of 2 sizes and a rom image should be no different. I'd say the image should comply and that MAME is not at fault (simply ensuring your image you provided is a valid size). It isn't unreasonable to expect. While the recording seems to be done on original hardware - we don't know how the image was presented to the hardware.

No.20083

kmg

Senior Tester

Apr 18, 2022, 22:28

edited on: Apr 18, 2022, 22:29

The PV drivers currently expect any software loaded to be either 8K or 16K. As a temporary solution you could pad the ROMs out to 8192 bytes with zeros.

No.20084

Tafoid

Administrator

Apr 19, 2022, 00:05

edited on: Apr 19, 2022, 00:10

As would a original hardware solution an image would need to be on an eeprom matching to traditional power of 2 sizes and a rom image should be no different. I'd say the image should comply and that MAME is not at fault (simply ensuring your image you provided is a valid size). It isn't unreasonable to expect.

While the recording seems to be done on original hardware - we don't know how the image was presented to the hardware.