Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Magnnus]

With the newest version (27_176_38a) nearly all of my save files have ended up corrupted. I have either received a message that they cannot be opened by the dll (or something to that effect) or more commonly the world simply does not appear when I select continue world, or if all the worlds are corrupted I do not have the option to continue. I have only been able to create one successful world and that was on another computer, I then transfered it with a flash drive and played it on my normal computer, after which the save was corrupted and disappeared from the continue list after saving my fortress.

Save: http://dffd.wimbli.com/file.php?id=17

[Toady One]

There are a bunch of 0 byte files in the save folder.  How much memory does your computer have?  Did the last version work?

[Javewa]

Same thing here. DF either crashes after world generation (CTD) or gives the error "One of the compressed files on disk has errors in it. Restore from backup if you are able.".
I've tried over a dozen worlds. Only two were created successfully and saved. While I was in DF, I could start playing on those worlds, save and reload, but once restarted, I got above error.

The 'errorlog.txt' just got an entry once: "Impoverished Word Selector".
When the update in that file occurred, the region wasn't created, but some files remained in the 'current' directory. I have a backup of that, if you need it.
All other crashes neither produced a region folder, nor anything in the 'current' dir.

Tried with modded DF and vanilla, graphics and pure, with prospector and without. Can't see a pattern, though.
The previous version works fine.

[Magnnus]

quote:Originally posted by Toady One:
<STRONG>There are a bunch of 0 byte files in the save folder.  How much memory does your computer have?  Did the last version work?</STRONG>

Although I don't remember offhand how much memory it has I think that it has about 4 GB, enough that nothing has ever used half of it, ill try to get you a more accurate number when I have access to that computer. As for your second question, I have never had any problems with the last version.

quote: "One of the compressed files on disk has errors in it. Restore from backup if you are able.".

Ya, thats the same message that I get (don't know where i got dll from   :roll: )

[Magnnus]

I just tried generating another world while keeping an eye on memory. DF used about 500 MB of memory and I have 4 GB of memory, a total of 600 MB out of 4 GB of memory was used by the computer. Stranger still is that nothing was even saved, I checked the saves folder and there was only an empty current folder.

Save: http://dffd.wimbli.com/file.php?id=19

[Jifodus]

Are you using Vista? If you are did where did you put it?

(In general)
Is your system using any virtual path mapping? Does DF have the permission to write to where it's located? Do you have enough disk space?

[Magnnus]

quote:Originally posted by Jifodus:
<STRONG>Are you using Vista? If you are did where did you put it?

(In general)
Is your system using any virtual path mapping? Does DF have the permission to write to where it's located? Do you have enough disk space?</STRONG>

I think you may have just nailed it >.<. I'm playing on an XP but I usually run DF off of a flash drive, and I just realized that i only had about 10 MB of space left. I'm deleting some things and then ill check if it works.

Edit: SUCCESS! I just generated the exact same world that didn't work before and everything went smoothly. And I was starting to think that my dwarfs where getting revenge for years of flooding and starvation.

[ February 19, 2008: Message edited by: Magnnus ]

[Lord Nightmare]

Maybe DF should complain like 'error creating save file (no space on device?)' or something...

LN

[numerobis]

quote:Originally posted by Lord Nightmare:
<STRONG>Maybe DF should complain like 'error creating save file (no space on device?)' or something...

LN</STRONG>

It should, but checking every write and properly handling failures is usually a giant pain in the ass.  So almost all writes should be checked, and almost no writes actually are checked.