Quote:
Originally Posted by dosraider
The game is meant to run from floppy drive, in those times the compy was also booted from floppy, remember(or not)?
|
First off
X 3. Some of my first programs were written by blacking out the correct indexes on punch cards, feeding those into a translator mahicne, which would then spit out a perforated length of paper tape. This tape was then fed into another machine which would load the computer with your program. It was a nightmare to debug and run multiple times. So yeah, I fondly remember the floppy drive days.
One of the statements from my original post and the first line of the snippet you quoted still remains: drive letter designation does not matter in this instance. Thank you for the image and feedback though. Both just reaffirmed what I thought may have been a problem but actually isn't. I still stick with the c/d drive naming standard unless I feel that may be part of the problem. Then I experiment with different drive letters.
The elements for this particular game:
- You need to have a legitimate
img file imgmounted as a
-t floppy drive if you want to write or overwrite your save games. Using a regular directory as a
-t floppy does not work.
- The
img file used can be anything, as long as it is a legitimate
img file. This file is read from but never written to.
- You do not need to have a
img - t floppy drive mounted to load save games, just to write or overwrite saves.
- The file named "
game" (no extension) must exist in order to load or save any game, otherwise the application does not recognize the existence of a save disk.
- The size or content of the
img file does not seem to matter, just that it is imgmounted as a
-t floppy.
The file size for your
mist.img is 1.44m, which is fine and it works as it should. However, since the last line in the list above is true, I found it is just much smaller and simpler to use a 160k empty
img file since it is not written to anyway. I tried using an
img file with the "
game" file and even some actual previously saved games written to it, but the application still wouldn't touch it. I mean it worked, but the game still insisted I needed to initialize my save disk.
To me, the most humorous thing about this was that I've spent more time trying to work this out in my head and with my computer than I actually spent playing and solving The Mist. Although, come to think of it, I never would have finished the game if I hadn't been able to save in the first place.
One last thing: Is what r.u.s.s. posted actually true? You ARE responsible for dosbox not being able to natively support mounting of multiple floppy images
?
Thanks!