okay so / represents 63 which translates too 0xFF so what ever was being fed to the base64 decoder is the random offset 0xFF and not the real kernel sooo why is bzImage all 0xFF and also data-seabios.
Tetstack
okay so / represents 63 which translates too 0xFF so what ever was being fed to the base64 decoder is the random offset 0xFF and not the real kernel sooo why is bzImage all 0xFF and also data-seabios.
It was because the curl download, i used raw github and it redirected me to the html 404 and it downloaded the 404 and said it worked instead of the real kernel
Tetstack
Okay not an image problem, it's how the kernel is being embedded and parsed.
Oh yeah sorry I didn't explain this, so I am implementing a real working Linux inside my portfolio. Spolier: it's all inside a 22.8Mb html file .
Tetstack
Oh yeah sorry I didn't explain this, so I am implementing a real working Linux inside my portfolio. Spolier: it's all inside a 22.8Mb html file .
This media is not supported in your browser
VIEW IN TELEGRAM
Tetstack
Nothing more scary than your girl calling you by your full name. @Tetstack
Governmental name means I am dead.
π6π1
This media is not supported in your browser
VIEW IN TELEGRAM
So about the terminal on a single html file the baes64 is too long for the browser to prase and there were other limitation so restructured it so that it works structuring the files some where and running the index.html using python server to avoid XMLHttpRequest being blocked and it's progressing, but seem there are some errors.
Pros: there are no errors.
Cons: I can't see what's wrong.
Pros: there are no errors.
Cons: I can't see what's wrong.