[oculto][14:48] <+mastag22> so what happened since yesterday
[14:49] <+repmovsb> just thinking, how do we call hvcall 114 then?
[14:50] <@flukes1> graf has sent some info
[14:50] <@flukes1> we're still asking him questions
[14:51] <+mastag22> wtf
[14:51] <+mastag22> you had to patch lv1?
[14:52] <@flukes1> yep
[14:52] <+mastag22> you found the routine finally?
[14:52] <@flukes1> no
[14:52] <@flukes1> graf just hinted a way to patch lv1 for full r/w access in lv2
[14:52] <+mastag22> ok
[14:53] <+mastag22> so no lv2 patch
[14:53] <@flukes1> once we got that working, we dump lv1 RAM
[14:53] <+mastag22> lv1is patched now
[14:53] <@flukes1> search for lv2 hash
[14:53] <@flukes1> and find the hash code
[14:53] <+mastag22> right or no
[14:53] <@flukes1> im patching lv1 now to allow us to edit it via lv2
[14:53] <+mastag22> you meant edit lv2 via lv1
[14:53] <@flukes1> no
[14:53] <@flukes1> edit/view
[14:53] <@flukes1> i should've said
[14:54] <@flukes1> so we'll be able to dump lv1
[14:54] <@flukes1> in theory, there will be some hash of lv2 code stored somewhere
[14:54] <@flukes1> we find where its stored and then use that info to figure out where the hash is being checked
[14:54] <+mastag22> ok
[14:54] <+mastag22> so you are keeping lv2 and lv1 patched then
[14:54] <+mastag22> but you are using an lv1 call to enable it?
[14:54] <@flukes1> eh?
[14:54] <+mastag22> im confused
[14:55] <+mastag22> or are you patching lv2 commands INTO lv1
[14:55] <+mastag22> and calling them from lv1
[14:56] <@flukes1> no
[14:56] <@flukes1> we are patching the equivalent of peek/poke into lv1
[14:56] <@flukes1> its not actually peek poke but it allows us to do exactly what peek/poke does
[14:56] <@flukes1> and we are keeping our peek/poke patch in lv2
[14:56] <@flukes1> we can then make an app to write a syscall to lv2 in memory
[14:57] <@flukes1> which will call the peek/poke-similar thing in lv1
[14:57] <@flukes1> and pass the result back down to our app running in gameos
[14:57] <@flukes1> which will use it to dump lv1[/oculto]