Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Playing Galagon/Galaga on my dad's slow-ass toshiba company laptop. I still sometimes boot it just to play again
So I've got my first sort of proper gig. I'm tasked with writing...
A goddamn minecraft plugin in java.
Well, it's actually rather fun strangely enough. My ideas of payment were not declined but rather accepted, the other devs are nice and everything is going well for now.
Also: Do expect a mental breakdown post next week or so8
Fix my depression
Learn C++ properly
Fix my life's future
Try to pick up a relationship which I've dropped out of stupidity again.6
Just got told that there will be a 5KM run in march by my teacher.
I will either break my foot a day before or simply fucking refuse.
I'm ill enough already.6
Yo Vanessa? I like, appreciate your interest but can you not let your bots run wild?
On a more serious note: This has happened about 10 times already.
I met a guy on another friend's birthday (lan)party.
We started randomly coding bullcrap. Fun times.1
I mean, as I don't have a job in that way yet I can't really say much.
Let's presume I have a job.
"My condolences, may god grant me mercy."
I really would like to post something deep here to harvest internet points, but instead I'll give you following quote.
"I have no fucking clue" -Me, 09/11/2021 18:19PM EST.
Well it all started in grade six I believe and it's all downhill from there.2
VESA is driving me crazy.
I'm trying to set my video mode via VESA functions which works, the QEMU window size changes, ton of more space.
Problem now however is that I have no idea where in the name of god the goddamn framebuffer starts.
Apparently it's address is located withing the mode info block which I have successfully queried and stored in ES:DI.
Problem now is getting this info block into my 32-bit kernel.
I tried smacking it on the stack which only produces hot garbage.
Essentially it goes like this
[...make sure pointer to block is stored within ES:DI...]
mov ebx, [ES:DI]
[Switch to 32 bit mode, ebx is not erased by doing so]
;Set up stack
mov ebp, 0x90000
mov esp, ebp
kernel_main takes this pointer as an argument, hence why I've pushed it onto stack:
When I try accessing it however by doing the following:
vbe_mode_info_block* info_block = (vbe_mode_info_block)ptr;
And then try accessing the in the member 'framebuffer' using 'info_block->framebuffer' it's giving me hot garbage.
I'm probably doing something obvious wrong.
I'm gonna try passing ES and DI seperately and converting them to a real mode address by doing addr = (ES*0x10)+DI;
MAYBE MAYBE MAYBE2
No CS teacher in my federal state since the teaching plan absolutely sucks ass.
Basically it attempts to teach you java without actually explaining it.
So people now know how algorithm XY works and looks in java, but are unable to differentiate between a float and an int.
My CS teacher is awesome tho in the regard that he single-handedly advanced our school digitally by about 15 years.
We now have tablet classes, 3D printers, more CS courses for lower grades etc. etc.
You get the picture.
So a friend came up with this funny idea today to make a discord bot which translates input to a custom morse alphabet consisting of E's.
Instead of .- ..- ...---...
We got eE eeE eeeEEEeee
I'm fucking done with that psychopath. So much for proper moderation.
Fucking hell I don't even have to say his name and you will know who I mean.
I love this platform but that person belongs in a psychiatric ward.10
So I'm writing this shitty kernel/os/abomination with Soldierofcode and I noticed that, to do essentially anything further than a shell, I should use UEFI.
FUCK I CAN RESTART THE ENTIRE CHING CHONG FUCKING PROJECT3
Right, so either Intels CPUID manual is fucking stupid or my qemu CPU has brain cancer in it's fucking silicon head.
x80000004 contains not ascii stuff but x8000003 and x80000002 fucking do.
I'm stranded with two thirds of a CPU brand string.
On the kernel/os project I'm working on with @SoldierOfCode.
It's a side project but I *need* to refactor the normal text based functions to vga graphics compatibility.3
Y'all know when you first hear about interrupts? Maybe on an arduino or something when you're just getting started and learning?
Yea after suffering enough trying to get ISRs running on an x86 just to get keyboard input going, I can safely and securely confirm it's all going downhill.
I love you all.8
So about nine days ago I've stopped recieving @-notifs without having anything disabled. Apparently other users have similar issues.