01684: Does not write save states to mapped drive

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
01684	Save/Restore	Minor	Always	Apr 6, 2008, 19:51	Apr 9, 2008, 02:25

Tester	xbskid	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	Unable to reproduce	OS	Windows XP/Vista 64-bit
Status [?]	Closed			Driver
Version	0.124u1	Fixed in Version		Build	Normal
		Fixed in Git Commit		Github Pull Request #

Summary	01684: Does not write save states to mapped drive
Description	For my convenience, I've mapped my MAME directory to M: (The actual path is T:\MAME\Mame32, which is shared as \\ra\MAME. I have also tried the Administrative share \\ra\T$\MAME\Mame32). I can load games just fine (I'm specifically using DDR games; I'll be using ddr3mj in this example), but if I try to create a savestate (Shift+F7), it touches the file location M:\sta\ddr3mj\7.sta, but it doesn't write anything to the file. File size is always 0bytes. Thus when I try to load the state, MAME crashes with the following error: Attempted to malloc zero bytes (src/emu/state.c:848)
Steps To Reproduce
Additional Information	I thought it would be a permissions issue, but after explicitly granting the Everyone group Full Control for both the Share and File permissions, I ruled that out. I don't know what would cause this at all. I consulted smf, and he recommended I file this as a bug.
Github Commit

Flags
Regression Version
Affected Sets / Systems

Attached Files

No.00613 Fujix Administrator Apr 8, 2008, 11:44	Does anyone confirm or duplicate this report?
No.00617 Tafoid Administrator Apr 8, 2008, 15:34 edited on: Apr 8, 2008, 16:09	I tried to reproduce with another driver since the DDR stuff was not working in 0.124u1. I have on my other computer a setup on C:\MAME on another computer in my local network. I mapped a network drive as I: to this folder. I adjusted my INI to use the I drive for STA files: state_directory i:\sta as well as ROMS: rompath i:\roms. I started my build without a game and the UI listed the 5 romsets I had placed there with no problem. I tried each one and they all loaded and played. Then I loaded up 2 games in particular, CRYSTALC and MAPPY and attempted a save state on both of them (one officially supports save and one does not). In each instance I made a save state successfully. I then restarted MAME for both games and used SHIFT-F7 to reload a state for each - they both worked fine. I then tried -autosave for CRYSTALC which also saved and reloaded the state file correctly. Not sure what else I can test.. I don't have any permissions to set really, using Windows 2000. It'd be helpful if someone with Win XP/Vista test this to see if this is an issue with MAME or a setting with computer.
No.00621 Fujix Administrator Apr 9, 2008, 02:25 edited on: Apr 9, 2008, 02:26	I setup a local network on xp and looked into this. I assigned M: for the shared directory, updated mame.ini accordingly and tested some games supports save state such as system1.c games. State saving both by manual and by -autosave worked correctly.