On 5/21/2015 8:00 PM, David Griffith wrote:
> What do you mean by saving the game progress? All Z-machine
> implemenations allow you to save your progress.
The steps/answers/instructions in the game to get to the point where it
crashes...
Ralf
---
This email has been checked for viruses by Avas
On 22/05/2015 05:00, David Griffith wrote:
> The "FROTZ" that appears in the crash message is from the
> filename of the executable. If I rename
> it to FOO.EXE, the crash message will contain "FOO".
Yes, that's because the 'system halt' message prints out the MCB when
MCB corruption happens (w
On 21/05/2015 21:43, Ralf Quint wrote:> Is there a way to save the game
progress, so someone else could try it
> on different hardware?
Hi Ralf,
No need for a save state - the game crashes within a minut or so after
starting playing, so the crash is rather easy to reproduce :)
Mateusz
-
On Thu, 21 May 2015, Ralf Quint wrote:
> On 5/21/2015 1:04 AM, David Griffith wrote:
>> I guess my next step is to bring one of my older machines home, clean
>> it up, install FreeDOS, and get to work with Turbo C++'s debugger. Can
>> anyone offer any explanation why a program would run fine in DO
On 5/21/2015 1:04 AM, David Griffith wrote:
> I guess my next step is to bring one of my older machines home, clean
> it up, install FreeDOS, and get to work with Turbo C++'s debugger. Can
> anyone offer any explanation why a program would run fine in DOSbox
> and crash on real hardware?
DOSBox
Hi,
On Thu, May 21, 2015 at 4:18 AM, David Griffith wrote:
> On Wed, 20 May 2015, Rugxulo wrote:
>
>> At risk of asking the obvious, what major DOS version / vendor is the
>> OP (David) developing on? Is it MS-DOS or FreeDOS? Does this mean it
>> works for him in MS-DOS but not in FreeDOS?
>
> I'
Hi,
On Thu, May 21, 2015 at 4:04 AM, David Griffith wrote:
> On Wed, 20 May 2015, Mateusz Viste wrote:
>
>> My guess is that you have a fishy memory usage in newer versions of
>> frotz - following an invalid pointer, or writing to non-allocated
>> memory, or so...
Presumably yes. A very quick te
On 05/21/2015 10:18 AM, David Griffith wrote:
> I guess I won't know
> just where the crash occurs until I can get real hardware running or if I
> can get a crash in a VirtualBox environment.
You could also try pin-pointing the problem the good old way - ie. lots
of printf() outputs at every bigg
On 05/21/2015 10:04 AM, David Griffith wrote:
> I guess my next step is to bring one of my older machines home, clean it
> up, install FreeDOS, and get to work with Turbo C++'s debugger.
You could also try running it on Linux through valgrind, it's usually
pretty decent when it comes to finding b
On Wed, 20 May 2015, Rugxulo wrote:
> Hi,
>
> On Wed, May 20, 2015 at 1:38 PM, Mateusz Viste wrote:
>>
>> Here the result with Frotz v2.43. Same computer, same game:
>>
>> http://s11.postimg.org/y8fknk0rn/frotz_v2_43_lost_pig.jpg
>
> At risk of asking the obvious, what major DOS version / vendor
On Wed, 20 May 2015, Mateusz Viste wrote:
> Good news is that Frotz v2.32 works fine. I played the "Lost Pig" game
> for about 20 minutes and I didn't experienced any crash.
>
> My guess is that you have a fishy memory usage in newer versions of
> frotz - following an invalid pointer, or writing t
Hi,
On Thu, May 21, 2015 at 12:40 AM, Mateusz Viste wrote:
>
> I don't know details, but I guess the OP is developing on some emulation
> machine, like DOSemu or DOSBox, and it works fine for him there. This
> happened to me in the past - emulated environment are apparently more
> resilient to bu
I don't know details, but I guess the OP is developing on some emulation
machine, like DOSemu or DOSBox, and it works fine for him there. This
happened to me in the past - emulated environment are apparently more
resilient to bugs than a real machine.
I doubt that using a DJGPP version is a sol
Hi,
On Wed, May 20, 2015 at 1:38 PM, Mateusz Viste wrote:
>
> Here the result with Frotz v2.43. Same computer, same game:
>
> http://s11.postimg.org/y8fknk0rn/frotz_v2_43_lost_pig.jpg
At risk of asking the obvious, what major DOS version / vendor is the
OP (David) developing on? Is it MS-DOS or
On 5/20/2015 1:08 PM, Dario Roncone wrote:
> Yes i know it... 8080 Intel 2x86 3x86 Dx/Sx intel MMX amdSSE SSE2.
>
Doesn't look like it...
Ralf
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
--
Shell CMD 4dos its a storry about computers.
2015-05-20 22:10 GMT+02:00, Dario Roncone :
> Fuck youself...
>
> 2015-05-20 22:01 GMT+02:00, Ralf Quint :
>> On 5/20/2015 12:59 PM, Dario Roncone wrote:
>>> Great Stuff! GNU OpenSource
>>>
>> You really need to work on the way you are trying to expre
On 5/20/2015 1:10 PM, Dario Roncone wrote:
> Fuck youself...
>
Sorry, don't play your games. But might have a try with the Infocom stuff...
Ralf
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
Fuck youself...
2015-05-20 22:01 GMT+02:00, Ralf Quint :
> On 5/20/2015 12:59 PM, Dario Roncone wrote:
>> Great Stuff! GNU OpenSource
>>
> You really need to work on the way you are trying to express yourself. I
> don't understand one bi of your comments in regards to the Infocom game
> engine..
Yes i know it... 8080 Intel 2x86 3x86 Dx/Sx intel MMX amdSSE SSE2.
2015-05-20 21:48 GMT+02:00, Ralf Quint :
> On 5/20/2015 12:46 PM, Dario Roncone wrote:
>> Yes Software diden´t work!
>>
> That's not an explanation. And it's DOS for crying out loud. There can't
> be any hardware too old to run a D
On 5/20/2015 12:59 PM, Dario Roncone wrote:
> Great Stuff! GNU OpenSource
>
You really need to work on the way you are trying to express yourself. I
don't understand one bi of your comments in regards to the Infocom game
engine...
Ralf
---
This email has been checked for viruses by Avast anti
Great Stuff! GNU OpenSource
2015-05-20 21:46 GMT+02:00, Dario Roncone :
> Yes Software diden´t work!
>
> 2015-05-20 21:41 GMT+02:00, Ralf Quint :
>> On 5/20/2015 12:22 PM, Dario Roncone wrote:
>>> Sorry! too Old hardware.
>>>
>> ? Care to explain WHY?
>>
>> Ralf
>>
>> ---
>> This email has been c
On 5/20/2015 12:46 PM, Dario Roncone wrote:
> Yes Software diden´t work!
>
That's not an explanation. And it's DOS for crying out loud. There can't
be any hardware too old to run a DOS program on...
Ralf
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.co
Yes Software diden´t work!
2015-05-20 21:41 GMT+02:00, Ralf Quint :
> On 5/20/2015 12:22 PM, Dario Roncone wrote:
>> Sorry! too Old hardware.
>>
> ? Care to explain WHY?
>
> Ralf
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> http://www.avast.com
>
>
> ---
On 5/20/2015 12:22 PM, Dario Roncone wrote:
> Sorry! too Old hardware.
>
? Care to explain WHY?
Ralf
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
--
One dashboard for ser
Sorry! too Old hardware.
2015-05-20 20:38 GMT+02:00, Mateusz Viste :
> Here the result with Frotz v2.43. Same computer, same game:
>
> http://s11.postimg.org/y8fknk0rn/frotz_v2_43_lost_pig.jpg
>
> Mateusz
>
>
>
> On 19/05/2015 23:25, David Griffith wrote:
>> On Tue, 19 May 2015, Mateusz Viste wrot
Good news is that Frotz v2.32 works fine. I played the "Lost Pig" game
for about 20 minutes and I didn't experienced any crash.
My guess is that you have a fishy memory usage in newer versions of
frotz - following an invalid pointer, or writing to non-allocated
memory, or so...
good luck :)
M
Here the result with Frotz v2.43. Same computer, same game:
http://s11.postimg.org/y8fknk0rn/frotz_v2_43_lost_pig.jpg
Mateusz
On 19/05/2015 23:25, David Griffith wrote:
> On Tue, 19 May 2015, Mateusz Viste wrote:
>
>> Hello David,
>>
>> First of all thanks for still caring about DOS in 2015, a
On Tue, 19 May 2015, Mateusz Viste wrote:
> Hello David,
>
> First of all thanks for still caring about DOS in 2015, and on top of
> that, caring about how your app works on real hardware :)
>
> I tested the version of frotz you submitted to us, and I must disappoint
> you - it's buggy.
>
> I test
Hello David,
First of all thanks for still caring about DOS in 2015, and on top of
that, caring about how your app works on real hardware :)
I tested the version of frotz you submitted to us, and I must disappoint
you - it's buggy.
I tested it using the "Lost Pig" game from the gopher repo you
I'm the one who maintains and develops Frotz these days, a program that
emulates the Z-machine[1] for modern computers. I worked to make sure the
old DOS interface code works with the current core code. Release 2.44 is
coming up Really Soon Now and I was wondering if I could get some of you
30 matches
Mail list logo
