My reply is at the bottom. Please put your reply there too.
On Wed, 9 Oct 2019, Tom Ehlert wrote:
Yesterday I tagged and released the first beta test of DOS Frotz 2.50.
Most of the work that went into the DOS interface focus on improving
stablity. I think I've corrected the two outstanding problems with DOS
Frotz: locking up upon exit and crashing with a "dos mem corrupt" error.
This only happened with certain games.
could you please be more specific like
what games were this?
do you you think the problems are fixed or is more testing needed?
These bugs are described at
https://gitlab.com/DavidGriffith/frotz/issues/8 and
https://gitlab.com/DavidGriffith/frotz/issues/58. The crashing problem
(issue 8) happens with at least Lost Pig, Uninvited, and Sherlock. Issue
58 happens at least with Advent and Lost Pig.
are there replay sessions available?
Not necessary as the bugs show up almost immediately
as I understand it Frotz should be able to reproduce bugs (and fixes).
Please hammer on it, especially on
real hardware. I'd like to get some solid figures on speed, memory usage,
and minimum hardware requirements.
how exactly would we 'hammer on it'
Try out large games on weak hardware and see how fast/slow things go or
how a crash happens.
how do we obtain solid figures?
speed of what?
and - please : THIS IS NOT THE LIST TO HAVE DISCUSSIONS OF FROTZ
PERFORMANCE.
I should have been more specific -- something like "Running $GAME on an
IBM 5150 brought the machine to a crawl" would suffice. I'm trying to
make sure Frotz works tolerably on a 5150 for at least Infocom's games.
Newer V8 games written in Inform7 I'm sure would cause trouble.
--
David Griffith
[email protected]
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user
