"Hard Drive on Fire!" error message

[nshram]

I'm using a ported 2.43 version on a Kindle, using its inbuilt Linux.
I get a "Hard drive on fire!" error message when trying to run frotz.
What does this error indicate and how to avoid it at runtime?
Browsing through the code, I see that it has something to do with the HOMEDIR environment variable.

[DavidGriffith]

I never expected "Hard drive on fire!" to actually appear in a functional system. It was intended as a test to check to make sure something hadn't gone horribly wrong with the operating system, specifically, the $HOME environmental variable being absent. Where did you get this port of Frotz?

[nshram]

I got the port here: https://www.mobileread.com/forums/showthread.php?t=186007
Have fixed the error by defining $HOME in a script which calls frotz.

[DavidGriffith]

I posted to that thread asking for whoever packaged up Frotz to contact me so we can work out what went wrong and to see what changes I can make so that the Kindle port works better.

[nshram]

That port was made by the thread starter: fvek. But it's an old thread and I don't know if he's still active.
Also, the error doesn't occur in the older kindles(KT, PW1, PW2). "echo $HOME" gives /tmp/root.
But in some of the newer kindles(PW3, KT3), $HOME is undefined. So, this error pops up. The fix, as mentioned above, is to define $HOME in a shell script which then calls frotz.