Hacking picross ds freeze

[crunchbot]

doesn't go past the first screen (nintendo/jupiter). neither did PoR, on m3 ds simply with kingston 1gb taiwan. other games seem fine. probably worth importing if it's acting funny, but anybody else having problems?

also tried both clean and trimmed versions. thanks.

 

[cpm]

picross is the rom i've really noticed a problem with, that first screen (nintendo/jupiter) lasts for ~40 seconds, the rest of the game plays fine tho :/

 

[BlueStar]

Under 5 seconds on the jupiter screen for me.

- R4 DS
- Sandisc 1 GB card formatted with FAT16, 64k clusters
- trimmed clean rom of Picross DS (J) (WRG)

 

[tama_mog]

Under 5 seconds on the jupiter screen for me.

- R4 DS
- Sandisc 1 GB card formatted with FAT16, 64k clusters
- trimmed clean rom of Picross DS (J) (WRG)

Same results, except m3 simply. Same settings of format as well.

 

[Destructobot]

My results:

Kingston (Japan) 1GB FAT 64k clusters: 40 seconds
Kingston (Japan) 1GB FAT32 8k clusters: 40 seconds

A-Data 512MB FAT 64k clusters: 18 seconds
A-Data 512MB FAT32 4k clusters: 18 seconds


edit: That's with a clean trimmed rom on an M3 Simply 1.02b.

 

[krdvmus]

It takes 20 seconds after the jupiter screen.

- M3 simply v1.02 beta
- kingston 1G (japan) with normal FAT format on winXP
- not trimmed

UPDATE: After playing some time, the loading time changed! It takes 40 seconds from the jupiter screen. I wonder why...

 

[MaHe]

W00t, I defragmented my card and it loads instantly now.
Go figure.

 

[krdvmus]

Here's another result.

It takes 65 seconds after the jupiter screen.

- M3 simply v1.02 beta
- Apacer 1G with normal FAT format on winXP
- not trimmed

It confirms again that Apacer sucks.

 

[crunchbot]

impatient me! thanks for sticking it out and the tips!

 

[cpm]

delay is gone w/ M3 simply v1.02 final, at least for me.

 

[Destructobot]

I can confirm that this is fixed in 1.02 final on my A-Data & Kingston cards.

 

[krdvmus]

Yup, the problem is fixed in firmware v1.02 final!

 

[MaHe]

So it wasn't the defragmentation that fixed mine ... ;D