Previous Thread
Next Thread
Print Thread
Page 1 of 2 1 2
Joined: Mar 2010
Posts: 147
S
Senior Member
OP Offline
Senior Member
S
Joined: Mar 2010
Posts: 147
I wanted to test disk access (specifically write options) in the mame apple2e driver with .woz images. Using the mame UI, i mounted a .woz image in the file manager, and it gave me options to write to a separate image or to a diff. The diff option is unsupported, so I tried writing to an image and gave writeable image a new name. I launched the disk, saved within the apple2e instance, and quit out of mame. I discovered the resulting new image is a 0-byte-length file (clearly bad). Does anyone have any suggestions or know what if anything I may be doing wrong here? Thanks!

Joined: Mar 2001
Posts: 16,614
R
Very Senior Member
Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,614
MAME cannot write to .woz images. Complain to OG ;-)

Joined: Mar 2010
Posts: 147
S
Senior Member
OP Offline
Senior Member
S
Joined: Mar 2010
Posts: 147
Thanks, well there's the answer I guess (help me OG Wan). One thought though, I'm actually writing to a new image, not back to the original .woz (even if i named the new image foobar.woz). Does that matter?

Joined: Mar 2001
Posts: 16,614
R
Very Senior Member
Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,614
If you name it foobar.woz then that matters, yes.

Joined: Mar 2010
Posts: 147
S
Senior Member
OP Offline
Senior Member
S
Joined: Mar 2010
Posts: 147
Thanks. Assuming you meant that the driver is sensitive to the extension used, I renamed the write image to foobar.dsk (and I selected 16-sector disk image format to write to) but I'm still getting a 0-byte-length image result after hitting escape to exit mame. I take it then that if I'm reading from a .woz source, mame will try to write to a destination file in .woz format regardless of any other factors?

Joined: Feb 2014
Posts: 505
G
Senior Member
Online Content
Senior Member
G
Joined: Feb 2014
Posts: 505
I tried to create a new image from the UI, gave it a somename.dsk and chose the first image type and got a 0 byte size file as well. Then tried the same and initialized the disk with INIT HELLO ,D2 and still got a 0 byte size file.

Joined: Mar 2001
Posts: 16,614
R
Very Senior Member
Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,614
Make a copy of an existing .dsk and format it, that works.

Joined: May 2009
Posts: 1,879
J
Very Senior Member
Offline
Very Senior Member
J
Joined: May 2009
Posts: 1,879
That's great, it doesn't change the fact that the internal UI seems to be broken. So let's figure out why.

Joined: Mar 2010
Posts: 147
S
Senior Member
OP Offline
Senior Member
S
Joined: Mar 2010
Posts: 147
Update: I tried loading a .woz file and then saving contents to an actual formatted .dsk but that resulted in a 0-byte-length image as well. The .woz image format is really nice, just wish you could do useful things with it. In time I suppose.

Joined: Jun 2001
Posts: 422
O
Senior Member
Online Content
Senior Member
O
Joined: Jun 2001
Posts: 422
I really need to do a pass over the floppy UI stuff, it's not very good and very incomplete...

Page 1 of 2 1 2

Link Copied to Clipboard
Who's Online Now
2 members (Pernod, MAMEBase), 42 guests, and 3 robots.
Key: Admin, Global Mod, Mod
ShoutChat
Comment Guidelines: Do post respectful and insightful comments. Don't flame, hate, spam.
Forum Statistics
Forums9
Topics8,837
Posts116,231
Members4,921
Most Online890
Jan 17th, 2020
Powered by UBB.threads™ PHP Forum Software 7.7.5