Closed GoogleCodeExporter closed 8 years ago
problem appears to be solved. i disconnected the link and relinked to dropbox.
i don't know if any other actions were taken by frotz, but all is well now.
thanks!
Original comment by agordon...@gmail.com
on 2 Jul 2012 at 5:10
There's a known issue with saved-game compatibility of games which are in
.zblorb files that will be fixed in the next release. However, anything in a
regular .z3, .z4, .z5, .z8, or original Infocom .dat should already work fine
between PC/Mac and iphone using interpreters which use the Quetzal save format.
What game in particular were you having the issue with?
It seems odd to me that relinking Dropbox could have affected this; it would
mean the file was formerly being copied but somehow corrupted, and I can't
imagine how that could happen.
Original comment by spath...@gmail.com
on 2 Jul 2012 at 6:06
I have been using ZORK1.DAT where I had experienced the problem. I had also
tried it out with one of the other titles that was preloaded in the iPad
version. Nothing worked, and I was trying a number of different variations.
I finally closed the Dropbox link.
This morning, I decided to try again and restored the link. Surprisingly,
everything worked. I was able to play, save, and restore Zork from iPad to
PC and from PC to iPad.
I am 57 years old and haven't played IF for many years, but loved it in my
college days. I had been thinking about it recently, and few web searches
located the DAT files available as well as your program for both iPad and
PC. I have also viewed the titles on the IF Database site. I am looking
forward playing more titles once I re-acquaint myself with Zork. I am very
excited about this.
Thanks for your attention to this difficulty.
Sincerely,
Andy Gordon
Original comment by agordon...@gmail.com
on 2 Jul 2012 at 6:59
Dropbox has made several extensions to their API recently, and I think this
glitch might have been a compatibility problem on their end interoperating with
older versions of their API. Several people reported Dropbox problems all at
the same time, after over a year with no issues. It looks like the problem
resolved itself, so I'm going to close this out.
Original comment by spath...@gmail.com
on 28 Jul 2012 at 7:18
Original issue reported on code.google.com by
agordon...@gmail.com
on 1 Jul 2012 at 2:28