Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

It could also be a memory leak somewhere, or saving little and often causes issues?

I don’t really think so, because if it were a fault with Bow Commander, the disk wouldn’t be readable even in EsxDos (which you said it is). So I reckon that EsxDos does something non-standard with that volume of disk operations, which causes problems for Windows and other operating systems, but not for EsxDos itself, because it’s something it’s designed to handle...

The problem is that, until now, there hasn’t been a programme for EsxDos that would use such a large number of disk operations at once (bulk copying, deleting, etc… and I think this is where EsxDos’s bugs and lack of fine-tuning come to the fore…). I don’t mean any harm by this; nobody writes flawless programmes, but it would be good to fix this behaviour at the OS level… . 

(+1)

A friend also gave me some advice:

- Which version of EsxDos are you using? Are you using the latest version, 0.8.9?

- And which FAT are you using? 16 or 32? If it’s 16, please try 32, and if it’s 32, please try 16...

I know this probably isn’t the answer you want to hear, but this is likely a problem unrelated to Bow Commander.

I am using 0.8.9 yes. And it's FAT 32.

Could you please replicate the procedure with FAT16… if possible?