Hacking AKAIO 1.2 Released

  • Thread starter Thread starter Smiths
  • Start date Start date
  • Views Views 66,179
  • Replies Replies 420

Well?

  • Tonic Water

    Votes: 0 0.0%
  • Resolve

    Votes: 0 0.0%

  • Total voters
    0
no problem, i'm glad someone is using the internal reader. it was really just based off the fact I unintentionally created it making the "what's new" displaying messagebox for cheat updating. I said "hmm, i think this could potentially be used to just load a TXT file".

Technically the line wraps at 230 pixels. That's why it takes longer to parse; it loads up a line of text, calculates how wide it is in pixels, then trims off characters one at a time until it hits a trim that is
 
Minox_IX said:
Devante said:
By the way, isn't it true defragging flash drives doesn't work and is actually BAD for your flash drive?

Since it is a solid state drive and defragging was meant for disk drives.
Defragging flash drives does work, but it shortens it's life.


The commandline option are not needed for normal use of JKDefrag but with flash drives you can use -a 2 ( = Defragment only, do not optimize ) to avoid excessive writes.

QUOTE(Giovannin @ Sep 3 2008, 05:45 PM)
Using the last release of AKAIO I've found that lunching hombrews will randomly give me white screens so I've to power off the DS.
Any other with this issue?

I notice this with DSO but no others so far
 
Umm sorry to disapoint ya Smiths but I wasn't using the Internal text reader. I was actually using the text reader plugin, the internal one takes forever to parse a large FAQ,
 
yes it does
smile.gif

like i said.. it was just for whatsnew displaying
 
I don't know if this has been reported before, but I have problems copying things with my Ak2. When trying to copy any file on my Ak2 I get an error-message stating "Error not enough Space, memory allocation error" and when I click Ok the "copying bar" stays so that I have to restart my DS so that it disappears. This error wouldn't be so annoying if it wasn't for that fact that it hinders me from backing up my .sav:s as .bak:s.
Reformatting doesn't seem to help solve the problem either.
 
Minox_IX said:
"Error not enough Space, memory allocation error"
It isn't anything directly to do with the microSD card (though it only seems to happen on large or oddly formatted sdhc cards which require a larger memory commitment from libfat - did you by chance format your card with >32k cluster size?), it is an internal error (trying to allocate more memory than the DS has.) Hopefully they will fix it by either freeing up some memory (putting some resources external which are currently statically built into the binary), finding any free()'s that are missing, or reducing the alloc to fit available memory - at least 3in1 stuff works now though (it was a similar problem.)
 
cory1492 said:
Minox_IX said:
"Error not enough Space, memory allocation error"
It isn't anything directly to do with the microSD card (though it only seems to happen on large or oddly formatted sdhc cards which require a larger memory commitment from libfat - did you by chance format your card with >32k cluster size?), it is an internal error (trying to allocate more memory than the DS has.) Hopefully they will fix it by either freeing up some memory (putting some resources external which are currently statically built into the binary), finding any free()'s that are missing, or reducing the alloc to fit available memory - at least 3in1 stuff works now though (it was a similar problem.)

It's formatted with FAT 16 with 32K cluster size, but I've tried with FAT 32 with 32K cluster size and that doesn't work either.

QUOTE(logical thinker @ Sep 9 2008, 01:33 AM)
More info needed. AK2 version, AKAIO version, memory card model...
I'm using AKAIO 1.2 and a Kingston Class 4 microSDHC (Taiwan).

AK2 version, what do you mean?
 
Minox_IX said:
It's formatted with FAT 16 with 32K cluster size, but I've tried with FAT 32 with 32K cluster size and that doesn't work either.

I'm using AKAIO 1.2 and a Kingston Class 4 microSDHC (Taiwan).
You've the same model SDHC I have here then, try formatting it with panasonic SD formatter (link), I haven't had a single problem with my own when copying anything (big or small) and that is all I have ever used to format it (read the info at the top of that page I just linked to.)
 
cory1492 said:
Minox_IX said:
It's formatted with FAT 16 with 32K cluster size, but I've tried with FAT 32 with 32K cluster size and that doesn't work either.
I'm using AKAIO 1.2 and a Kingston Class 4 microSDHC (Taiwan).
You've the same model SDHC I have here then, try formatting it with panasonic SD formatter (link), I haven't had a single problem with my own when copying anything (big or small) and that is all I have ever used to format it (read the info at the top of that page I just linked to.)
Same here. Actually, the only difference is that I use an AKRPG.
 
I see from the dev project site that z.gelu(
bow.gif
the unsung RPG hero) is hard at work fine tuning the DMA on his loader,

just wondering if AKAIO 1.3 is waiting on his optimizations before release.

I'm just excited to have the DMA option included W/AKAIO.

rolleyes.gif
Dum-dum question: Is there any other benefits to adding direct memory access other than no game slow down?
 
only thing DMA mode does is reduce slow downs (virtually to the point of no slow downs).

1.3 is still coming along. Gonna be a major update again. I'm still trying to work on the AK+ side of AKAIO but without an AK+ and no one to test things for me it isnt going well
tongue.gif
 
DMA will only work on AKRPG, but I will probably port it to the AK2 4.07 engine AKAIO uses. the 4.08 engine does DMA patching but they are keeping that engine private atleast for now. I have yet to even add the DMA mode to AKAIO.
 

Site & Scene News

Popular threads in this forum