Archived from groups: rec.games.roguelike.nethack (More info?)
> No, I just have a single processor Athlon XP 2400. It is underclocked a
> little bit. I've had this system for a year, with no other file
> read/write problems.
>
>
There are some more possibilities that occur to me after some research.
Note: these are the linux/unix variables involved and only apply if 1) you
compiled in linux or similarly another OS that nethack is ported to (in which
case the file names change or course).
1) there is a variable in unixconf.h called HLOCK which is where the level
is stored when the player changes levels (this would be the problem if you
could NEVER get successfully to second level).
2) Make ABSOLUTELY sure that the battery for your computer's clock is still
good, as this will yield to inconsistent times when saving files and could
cause this problem very easily.
3) there is a variable called NETWORK in the aforementioned file that defines
that this computer is running on a network. Make sure that it is #defined or
#undef'ed (line commented out) as appropriate.
If these Do not apply then I would think that either disk caching is still
present in some wierd form, a virus/trojan is active or you are running from
a ramdrive (that last is a reach). Let us know the circumstances a bit more
as to when it happens if this does not fix it, And maybe it can be solved.
BTW I don't work for the developer's, I just have seen a lot of VERY wierd
thing happen on computers and fixed most of them.
> No, I just have a single processor Athlon XP 2400. It is underclocked a
> little bit. I've had this system for a year, with no other file
> read/write problems.
>
>
There are some more possibilities that occur to me after some research.
Note: these are the linux/unix variables involved and only apply if 1) you
compiled in linux or similarly another OS that nethack is ported to (in which
case the file names change or course).
1) there is a variable in unixconf.h called HLOCK which is where the level
is stored when the player changes levels (this would be the problem if you
could NEVER get successfully to second level).
2) Make ABSOLUTELY sure that the battery for your computer's clock is still
good, as this will yield to inconsistent times when saving files and could
cause this problem very easily.
3) there is a variable called NETWORK in the aforementioned file that defines
that this computer is running on a network. Make sure that it is #defined or
#undef'ed (line commented out) as appropriate.
If these Do not apply then I would think that either disk caching is still
present in some wierd form, a virus/trojan is active or you are running from
a ramdrive (that last is a reach). Let us know the circumstances a bit more
as to when it happens if this does not fix it, And maybe it can be solved.
BTW I don't work for the developer's, I just have seen a lot of VERY wierd
thing happen on computers and fixed most of them.
Facebook
Twitter
Instagram