#2007 closed defect
WINCE: Config file gets corrupted
| Reported by: | SF/animalangel | Owned by: | SF/arisme |
|---|---|---|---|
| Priority: | high | Component: | Port: WinCE |
| Version: | Keywords: | ||
| Cc: | Game: |
Description
I have a Bsquare Power Handheld running Windows CE.NET(4.1). I can get the program to run but I have to delete the config file everytime before running the program. If the config file exists I get an error message.
Config file Buggy: Junk found in line 16: ' '
This will continue to pop up and nees a soft reset to get rid of the error.
I havent tried many games when it works but DOTT seems to run really well, except it seems to create loads of 'tentacle' files in the ScummVM root directory. Also saved files appear in DOTT seem to be damaged.
Ticket imported from: #1189386. Ticket imported from: bugs/2007.
Change History (21)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
| Owner: | set to |
|---|---|
| Status: | new → pending |
| Summary: | HandheldPC ARM - Config file Buggy → WINCE: Config file gets corrupted |
comment:3 by , 19 years ago
| Status: | pending → new |
|---|
comment:4 by , 19 years ago
HandheldPC ARM binary 0.7.1 - USED
FIXED DOTT SAVE FILE PROBLEM: if you make save directory diffrent to the root e.g 'ScummVM/Saved Games' then they will work fine.
comment:7 by , 19 years ago
I confirm the same/similar bug on an Ipaq 6365.
Version: v0.7.1 (March 27 2005), English language version Platform: Windows Mobile 2003
After launching ScummVM for the first time a config file is created. Once the program launches again it attempts to read the config file but reports error message "Config file Buggy: Junk found in line 3". Deleting the config file allows the program to run successfully.
I also find that the program creates 'tentacle' files in the root directory.
Unable at this stage to confirm whether the bug also occured in the earlier release.
comment:8 by , 19 years ago
Hello, I have the same problem with a BlueMedia BM6300 (Handheld with WinCE .NET 4.2). I've looked at the config file with a text editor and the problem seems to depend on the line feed/carriage return interpretation of the config file. If I run dos2unix and remove all empty lines in this file and copy it back to the device ScummVM is able to read it (but if you end ScummVM it is broken again ...)
Hope that helps a little bit.
comment:9 by , 19 years ago
Just to check, are all of you who experience the problem using ScummVM 0.7.1 ?
Arisme, I wonder if File::gets() could be the culprit?
comment:10 by , 19 years ago
I'd say either this or if it only happens for Handheld PCs a bad stdio-wrapper implementation in missing.cpp. I'll recheck the Handheld PC implementation to be sure.
(note : the 6365 is not an Handheld PC ... I'll review File::gets() but I've never had the problem on my device)
comment:14 by , 19 years ago
Hello, Is it possible that isspace from backends\wince\missing\missing.cpp should test for \r, \n, \t, too? Unfortunately I wasn't able to compile it myself ...
comment:15 by , 19 years ago
| Priority: | normal → high |
|---|
comment:17 by , 19 years ago
Not yet, I'm trying to rebuild the head version but some recent changes seem to have killed EVC 4 for good :) I'll see what I can do ...
comment:19 by , 19 years ago
| Status: | new → closed |
|---|
comment:20 by , 19 years ago
I have the same problem too. I'm running the HPC SH3 version of 0.7.1 on a Jornada 690. If I use version 0.6.1b, the problem does not occur.
comment:21 by , 5 years ago
| Component: | --Unset-- → Port: WinCE |
|---|
To process your bug report appropriately, we need you to provide the following additional information:
* ScummVM version (PLEASE test the latest CVS/Daily build) * Bug details, including instructions on reproducing it * Language of game (English, German, ...) * Version of game (talkie, floppy, ...) * Platform and Compiler (Win32, Linux, MacOS, ...) * Attach a save game if possible * If this bug only occurred recently, please note the last version without the bug, and the first version including the bug. That way we can fix it quicker by looking at the changes made.
This should only take you a little time but will make it much easier for us to process your bug report in a way that satisfies both you and us.
Thank you for your support!