Author Topic: Saving in Doom  (Read 2577 times)

massivebasset

  • Guest
Saving in Doom
« on: December 19, 2009, 04:38:48 am »
I think theres some problem with my file system not being able to be written to, but the end result that I am seeing is that I cannot save games with prboom.

Im using the 0.33b local pack, with updated to 12-8-09 Elta Filesystem, and updated my Doom to use CZ's prboom.

In game I get a message saying "Game Save Failed!"  and in the console after quitting doom, i see the message src/main.c   (126)[msg] Unable to open filesystem for writing.  Any changes made to system will not persist.

Though, thats repeating everytime I check the terminal, so maybe thats more of a demenu issue?  Ill repost there.
« Last Edit: December 19, 2009, 04:42:46 am by massivebasset »
Logged

zear

  • * Moderator
  • Posts: 2379
Re: Saving in Doom
« Reply #1 on: December 19, 2009, 09:29:52 am »
Dingux automatically switches to read only if there is a filesystem corruption.
A solution would be to either repair the partition, or reformat it.
Logged

santino

  • Guest
Re: Saving in Doom
« Reply #2 on: December 19, 2009, 10:05:30 am »
Im playing prdoom, too and I can save like everytime. Think your FS is crippled, too.
Logged

massivebasset

  • Guest
Re: Saving in Doom
« Reply #3 on: December 19, 2009, 01:44:06 pm »
Quote from: zear on December 19, 2009, 09:29:52 am
Dingux automatically switches to read only if there is a filesystem corruption.
A solution would be to either repair the partition, or reformat it.

Hrm, I didnt know that, certainly sounds like the culprit.  Running a check disk in Windows XP now, hopefully that will get it.  THanks for the help!

Update:   That did it, wow thanks guys!
« Last Edit: December 19, 2009, 01:54:29 pm by massivebasset »
Logged

massivebasset

  • Guest
Re: Saving in Doom
« Reply #4 on: December 19, 2009, 02:16:24 pm »
Aaaaaand my filesystem is corrupt again.

Is there anyway to prevent this from happening so darn quickly?
Logged

darfgarf

  • Guest
Re: Saving in Doom
« Reply #5 on: December 19, 2009, 02:18:21 pm »
when you format, select 32 Kilobyte block size, that seems to reduce it at least

and personally i'm using dinguxmb as it doesn't write anything to the sd card, things will only get corrupted if a game writes to it etc, so save the game less often maybe

and eltas new rootfs apparently decreases it, but i just corrupted mine using it :D (developing though, mine gets corrupted almost constantly)
Logged

massivebasset

  • Guest
Re: Saving in Doom
« Reply #6 on: December 19, 2009, 02:24:45 pm »
Yeah Im just running through the games on the local pack seeing which I want to remove right now.  Either Dmenu or Dingux-Go is at fault this time it seems.

Ill try the reformat, and if thats no good, Ill look into using the other menu system.  My only reluctance is my unfamiliarity with it, but Im fairly competent, so hopefully I can learn how to use it   ;D
Logged

santino

  • Guest
Re: Saving in Doom
« Reply #7 on: December 19, 2009, 03:09:32 pm »
Do you poweroff the dingux using the menu or do you just restart it with the sliderbutton? I think poweroff per menu is very safe, because linux writes everything on sdcard and then unmounts it.
Logged

massivebasset

  • Guest
Re: Saving in Doom
« Reply #8 on: December 19, 2009, 03:34:39 pm »
Quote from: santino on December 19, 2009, 03:09:32 pm
Do you poweroff the dingux using the menu or do you just restart it with the sliderbutton? I think poweroff per menu is very safe, because linux writes everything on sdcard and then unmounts it.

I do it through the menu.  However, since i was going in and out of programs, I can pretty safely attest that its Dmenu thats killing it.
Logged
Pages: [1]