search

jackjones2220 / cfg-loader

Automatically exported from code.google.com/p/cfg-loader
0 stars 0 forks source link

Saving corrupts settings.cfg!!! #140

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Seagate 500GB USB2 Drive NTFS
2. cIOS's are D2Xv4,v3,v2,v1 Final,& Waninkoko Rev.21 [all problematic]
3. cIOS245[38],246[53],247[55],248[56],249[57],250[58]
4. Covers do not load unless I boot with 249[57] or 250[58]<- i boot 250
5. Whatever, Got the covers working no biggy.
6. Most games i want to boot on 248[56] so i go into options and change IOS to 
248 and click save.
7. Exit loader and reenter. check the game and it still says 250.
8. Unplug HDD from Wii, plug into PC and edit settings.cfg
9. Gives an error. file corrupt, empty, blank, undeleteable.
10. Gotta run Scandisk on the drive to delete it.
11. I had to had write settings for 200 games, and if i change and save in 
loader, corrupts the damn file again.
What is the expected output? What do you see instead?
Saved Settings. A blank, undeleteable corrupt settings.cfg file

What version of the loader are you using?
68d

What is your System Menu version (e.g. 4.2u)?
4.3U

What is your media type (HDD, USB Flash, SD/SDHC)?
USB HDD

How is your media formatted (wbfs, fat32, ntfs)?
NTFS

Which cios are you using, which version, which base (222,249,...)?
(Please try both 249 and 222 with cfg-222.dol)
look above

Does it work with other loaders?
yes

Does it work with the latest or an older version?
issue since 66

Please provide any additional information below.

Original issue reported on code.google.com by RussianB...@gmail.com on 23 May 2011 at 3:13

GoogleCodeExporter commented 8 years ago 
i also have this same exact issue, it continues in the rev69's as well

Original comment by golfd...@gmail.com on 3 Jun 2011 at 4:35

GoogleCodeExporter commented 8 years ago 
Should be fixed by:
v69a7 (alpha)
 * revert to ntfs-3g-2010.10.2 (libntfs-wii r4+r7)
Please confirm if it's fixed or not.

Original comment by ogg...@gmail.com on 4 Jun 2011 at 3:15

GoogleCodeExporter commented 8 years ago 
Will check tonight ok?

Original comment by RussianB...@gmail.com on 4 Jun 2011 at 4:55

GoogleCodeExporter commented 8 years ago 
Seems to be fixed with v69a7+

Original comment by ogg...@gmail.com on 9 Jun 2011 at 4:30