#1 can't boot images with .saves feature

[Anonymous]

I'm using pogoshell 1.2 on my FA256M card. I tried to upload a savefile through the .saves folder in the root but after flashing my gba doesn't go further than the Gameboy logo. I tried it with shell.bin from 1.11 with the same result. Flashing without any file in the .saves directory works without a problem.

I'm using WinME and the 'create and flash.bat' for flashing my card.

This bug is not so important as I can upload save files with the old procedure (start game in pogoshell; turn gba off; flash sram bank0; turn gba on).

Best regards,
daviduck

for more information contact me at: david 'at' upcs 'dot' at

[Nobody/Anonymous]

Logged In: NO

If i put a savegame (.sav) in my .saves directory and startup
pogoshell (on my 256 f2a card) i can't write the .sav games to
my ram memory

i write the rom.bin with littlewriter.

[Nicklas Holmgren]

Logged In: YES
user_id=657865

-old option turns the file to 16.2 MB large.
I have the old cartrigde, but I haven't got a 128Mbit cartrige.
I just have a 64Mbit Turbo from Visoly. So I want to be able to
run Pogoshell too, that means the max_file_size is 8 MB for
me.

However I can flash without the -old option, & I can see the
files, but when I try running ANY of the files, like .gba or .nes
or .nsf, the GBA hangs.
When I start my GBA again, I'm in the same folder but I can
move again, it just locks when I run any of the files.
Though .txt & .bmp files work fine to view, also changing
fonts.

So I want the -old option to support my small 64mbit
cartridge.
Right now, the -old option just makes the total rom size 16.2
mb large. =/