Пікірлер

• 
  @raveltammeleht62782 күн бұрын

  Well that is ironic.... I tried to recompile this source on OSX .. seems as if it was originally developed under OSX, but its impossible to compile it with original libs...Xcode gives me some seriously odd errors. It succeeds to compile with GL3, but when it reaches the glCreateProgram() it gives me "Thread 1: EXC_BAD_ACCESS (code=1, address=0x0)". I just want to create a treeview/hierarchy with source and subsequent nodes to interact with my scene and taught this would be a perfect fit, but after a day of messing around, I couldn't get it to work under OSX.

• 
  @Nunya582945 күн бұрын

  Notepad++ is great

• 
  @ThatOSDev5 күн бұрын

  Yea, I can't believe I didn't make this video sooner. As it stands, I am hoping this is the first of many videos to come. I am just getting situated for it first. Cheers

• 
  @Nunya5829410 күн бұрын

  I ended up just getting a VPS for $11 a month with 80GB storage. It'll be good enough for my code

• 
  @ThatOSDev10 күн бұрын

  yea I don't have the money for that right now. I am having to buy another vehicle since the last one broke down. So I am saving everything I can for it. Being homeless tends to do that to ya. Cheers

• 
  @Nunya5829410 күн бұрын

  I hear ya there man! I hope all goes well for ya! - Cheers ​@@ThatOSDev

• 
  @SonicJoshua2411 күн бұрын

  I am going to move my SEOSBL bootloader to codeberg. I had wanted to move away from github for a while and was tempted to make my own. Glad this is another option.

• 
  @ThatOSDev10 күн бұрын

  Awesome ! :D

• 
  @bing888614 күн бұрын

  The github repository has been removed. Could you re-upload it?

• 
  @ThatOSDev13 күн бұрын

  The source code has been migrated to codeberg.org/ThatOSDev Enjoy

• 
  @Nunya58294Ай бұрын

  Oh heck yeah man

• 
  @localhost-renanjsАй бұрын

  See you later!!

• 
  @ThatOSDevАй бұрын

  Take Care.

• 
  @Nunya58294Ай бұрын

  Good stuff! 👍

• 
  @Nunya58294Ай бұрын

  I seem to be unable to join the Discord. Either the invite link is invalid or I'm just unable to find the server in general..

• 
  @ThatOSDevАй бұрын

  I don't have a server. You can find my name in the little arrow at the top of my channel. Click it and you will get more info, including my discord name.

• 
  @Nunya58294Ай бұрын

  ​@@ThatOSDevohhh gotcha! If you do end up making a discord server I would love to come help everyone as much as possible

• 
  @ThatOSDevАй бұрын

  @@Nunya58294 Look up Queso's channel. He shares his discord link in there somewhere. I am in his channel, although I don't talk much in there. Cheers

• 
  @Nunya582942 ай бұрын

  I'll do what I can to contribute to the ARM64 osdev stuff since I've been messing with it for a while

• 
  @ThatOSDev2 ай бұрын

  I welcome that. Thank you for your support. 👍

• 
  @Nunya582942 ай бұрын

  @@ThatOSDev Absolutely good sir! 😁

• 
  @TMMachadovsky2 ай бұрын

  Do you have discord?

• 
  @ThatOSDev2 ай бұрын

  In the ABOUT description my friend. 👍

• 
  @Nunya582942 ай бұрын

  ​@@ThatOSDevI don't seem to see an invite link at all... Unless I'm overlooking it haha

• 
  @ThatOSDev2 ай бұрын

  @@Nunya58294 It's there. MyLifeOfStones

• 
  @ThatOSDev2 ай бұрын

  @@Nunya58294 Look in the ABOUT of the channel. YT keeps deleting my comments.

• 
  @Nunya582942 ай бұрын

  ​@@ThatOSDevohhh I see!

• 
  @TMMachadovsky2 ай бұрын

  Hey man im getting this error efimain.c: In function ‘efi_main’: efimain.c:75:60: error: passing argument 2 of ‘SystemTable->ConOut->OutputString’ from incompatible pointer type [-Werror=incompatible-pointer-types] 75 | SystemTable->ConOut->OutputString(SystemTable->ConOut, L"Testing... "); | ^~~~~~~~~~~~~~~~~ | | | int * efimain.c:75:60: note: expected ‘CHAR16 *’ {aka ‘short unsigned int *’} but argument is of type ‘int *’ cc1: all warnings being treated as errors gcc-9: error: efimain.o: No such file or directory im using linux althought im using -mabi=ms

• 
  @ThatOSDev2 ай бұрын

  It's the L. Replace it with U, or u. I always forget if it's capitalized or not. the ABI you are using to make the EFI file is exactly as it should be. The L works on GCC c99 and c11. But not other compilers or versions. so if you are using clang or GCC C17, use the u in front of text. I didn't realize this fact until way AFTER I made that video. Hope it helps. Cheers

• 
  @ThatOSDev2 ай бұрын

  I just double checked, it's lower case U. I put this info into my description just now. Cheers

• 
  @Nunya582942 ай бұрын

  Oh hell yeah finally folks are finally doing ARM64!!!! If you want to build with Clang then use `aarch64-unknown-windows` target triple for compiling and linking Here's the required linker and build flags: ``` Compiling: -target aarch64-unknown-windows -ffreestanding -fno-stack-protector -fshort-wchar Linking: -target aarch64-unknown-windows -nostdlib -Wl,-entry:efi_main -Wl,-subystem:efi_application -fuse-ld=lld-link ```

• 
  @ThatOSDev10 күн бұрын

  Sorry I misse your reply, I didn't see this for some reason. Cheers

• 
  @Nunya5829410 күн бұрын

  @@ThatOSDev That's alright boss man!

• 
  @TMMachadovsky2 ай бұрын

  Thank you so much, me and my friend are creating an os for a final assessment of a vocational course, you re helping us so much ❤❤❤❤❤

• 
  @ThatOSDev2 ай бұрын

  Happy to be of help. Thank you for the kind words. Cheers

• 
  @TMMachadovsky2 ай бұрын

  How can i contact you

• 
  @ThatOSDev2 ай бұрын

  Click the MORE on this youtube channel. You will find ways to contact me.

• 
  @QuesoFuego2 ай бұрын

  There's not a lot of info out there for this, to be fair. Took some hunting down. GCC devs are working on a patch for an aarch64-w64-mingw32 target, as of april 2024 gcc.gnu.org/pipermail/gcc-patches/2024-April/649261.html but not sure when that will be merged in. Clang is also the sound my forehead makes when it hits the keyboard.

• 
  @ThatOSDev2 ай бұрын

  🤣 Yea, we need more info on ARM64 and making an OS for it. Videos, Tutorials, PDFs, anything we can get our hands on to make it a reality. Cheers

• 
  @Nunya582942 ай бұрын

  ​@@ThatOSDevA lot of stuff I've found in my year of osdev is usually aimed towards the rpi3. This can easily be done on the virt board for QEMU too... A lot the ARM64 stuff I've been working on had to go research about and learn it on my own since osdev focuses on x86[_64]

• 
  @reecechannel20132 ай бұрын

  nice to see that this channel is still going, it really helps by answering a lot of the little questions as i work on my own project.

• 
  @ThatOSDev2 ай бұрын

  Thank you for the positive feedback. It's been a long time coming to make this code happen. Being homeless has delayed a lot of my work. I am trying my best to catch up. Cheers

• 
  @reecechannel20132 ай бұрын

  @@ThatOSDev well hopefully you will find a nice place that good value for money so you can catch up with your work.

• 
  @ThatOSDev2 ай бұрын

  @@reecechannel2013 I am finally getting a vehicle at end of next month. Almost done paying for it. So that's a start at least. ☺

• 
  @NatureRaph2 ай бұрын

  Hey, I saw your youtube series about making EFI Based Bootloader and I think its honestly a very good series. But I have a lot of gaps in my knowledge and hope you can help me fill them. I would appreciate it very much if you could take some time helping me :). So firstly I wanna ask: So you are writing the EFI Calls yourself right? So using gnu-efi for example makes it easier? Also I would like to use Arm64/Aarch64 instead of x86. Is there a big difference in writing the Bootloader except writing the Assembly code of course? So I reached the point that I could use Print methods from gnu-efi for Arm64 running with qemu but the print didnt display anything. So it didnt give an error after some fixes but I think it just displayed a blank line and I dont know why. So basically I made an EFI Application but I can just rename it so it gets bootet from UEFI automatically and then it can load the Kernel right? Sorry for bothering you and thanks for reading it! The point where the Kernel gets loaded and I can make calls to EFI would be the point where I wouldnt need help anymore. But till then I find it a bit hard to actually find tutorials or docs that fit my needs.

• 
  @ThatOSDev2 ай бұрын

  I see you on discord. Chat with you on there.

• 
  @mihaicotin32612 ай бұрын

  thank a lot for your amazing work ! Amazing tutorial series that really got me understanding some solid things. much love!

• 
  @ThatOSDev2 ай бұрын

  I appreciate your kindness. Thank you for leaving a comment. Cheers

• 
  @user-nf3jr3wl9v3 ай бұрын

  Love your content, I am trying to learn c myself. I hope your situation gets better, I really love your channel! Keep your head up ❤

• 
  @ThatOSDev3 ай бұрын

  I appreciate the kind words. Thank you. 👍

• 
  @user-nf3jr3wl9v3 ай бұрын

  Hi, I really want to learn C. Could you suggest any books for beginners. I have no experience in programming but willing to put in the work!

• 
  @ThatOSDev3 ай бұрын

  Greetings. C is a very easy language believe it or not. It's a lot simpler then it looks. The issue is, there is false information out there about it, that you have to have experience to know what is true and what is not. This URL has a list of C books. The one I started on though is the 1988 2nd edition - The C Programming Language. It's the besst book on that list in my opinion. www.guru99.com/best-c-books.html

• 
  @ThatOSDev3 ай бұрын

  On another note, I am considering making a mini tutorial series on learning C. But that might be a few months before I do. Nothing etched in stone yet. Cheers 👍

• 
  @user-nf3jr3wl9v3 ай бұрын

  @@ThatOSDev thank you very much

• 
  @user-nf3jr3wl9v3 ай бұрын

  @@ThatOSDev Wow thank you so much, I would love this. God bless you ❤️

• 
  @Nunya582944 ай бұрын

  Cheers man!

• 
  @ThatOSDev4 ай бұрын

  And a Cheers 🥂 to you as well. ☺

• 
  @SonicJoshua244 ай бұрын

  I have been improving my bootloader to the point where I am at a point where I can make what I call a boot driver to load a kernel. I still need to make an example boot driver, but things are slowly getting there.

• 
  @ThatOSDev4 ай бұрын

  Well done. Keep up the good work. Cheers

• 
  @forceofphoenix4 ай бұрын

  Hey there

• 
  @ThatOSDev4 ай бұрын

  Hi there. 🤪

• 
  @x86debug4 ай бұрын

  Welcome back

• 
  @ThatOSDev4 ай бұрын

  Thank you very much. Cheers

• 
  @localhost-renanjs4 ай бұрын

  You coming back!!!!

• 
  @ThatOSDev4 ай бұрын

  Not exactly "back" per say. But I am working on my OS again. Will I post the code ? I DO plan on it yet. With everything going on, living in the desert while being homeless, I just had the urge to get back into programming since I have a LOT of time on my hands again. So time will tell. I DO want to make videos again, it's just a matter of "when". Not "IF". I might even make a kernel dev series. I am still working on making tools for when I don't have internet. I use Raylib to make them. Anyhow, thanks for the comment. Cheers

• 
  @localhost-renanjs4 ай бұрын

  @@ThatOSDev The important of you don't dead forever this channel, you make the first step for a future OS, I will finish? I don't know, but I try. Welcome again.

• 
  @smallcube-zn2mm5 ай бұрын

  Thanks for the tutorial

• 
  @ThatOSDev5 ай бұрын

  Thank you for the kind words. Cheers

• 
  @adrianvornicu5 ай бұрын

  Is it possible to offload all this drawing logic to the GPU so that the CPU can focus on more important tasks? I have actually seen some slow console output when using the EFI shell on a new laptop probably because of an implementation like this

• 
  @ThatOSDev5 ай бұрын

  You are correct, it is slow. Why ? Because we are drawing directly to the screen buffer of the GOP. (Graphics Output Protocol) The proper way around it would be to make a separate buffer, set up a routine that you can draw to it instead, and then copy that buffer to the GOP Buffer. You could setup a timer to "flip" it. Meaning, you can setup a double buffer, and on the timer it will take the buffer your pointer is pointing to, and copy only that. Then swap your target drawing buffer. And you go back and forth, back and forth. You can even setup a lock mode, so that it will not copy until it's finished. This way you prevent tearing. There are a lot of techniques. The reason I did it the way I did was do to trying to share the idea that you can make your own font. It's a trick I learned from Game Engine design ideas. Anyhow, your comment is most welcome. I love it when people think outside the box. Cheers my friend.

• 
  @ThatOSDev5 ай бұрын

  Also, to answer your question of can you offload to the GPU, yes it is possible. Just not in EFI that I am aware of. Once you are out of the EFI, and running your own loader or kernel, you could talk to the graphics card ports, or functions, to send data to it. However, that is not something I have done. Yet. You would be entering into the VBE or DirectX or OpenGL world at this point. Look up MESA OpenGL. They have the source code on how they use OpenGL to talk to the graphics card. There are only a few people that have actually succeeded in making it work in their OS. Why ? Because there is a LOT to setup before you get to that point. It's why in my series, I am just trying to get text on the screen, even if it is a bit hacky. Without text, it's hard to move forward. Cheers

• 
  @adrianvornicu5 ай бұрын

  Is there any way to access the VGA text-only mode, where you put the characters directly in the video memory?

• 
  @ThatOSDev5 ай бұрын

  Accessing the VGA Text was only in the Legacy 16-Bit way of doing things from the past.The Modern Way is to use the built in EFI while you are in the EFI environment, and then load a kernel and a font or bitmap or some other method you want to use, that gives you text ability once you enter the kernel or a loader of your choice. This is why in my other video about text, I made my own font. From there, I could use the GOP address to write directly to the screen, even after leaving the EFI world. Hope this helps. Sorry for late reply. I'm still homeless living in the desert with no internet. Cheers

• 
  @Nunya582946 ай бұрын

  I'm late to this one, but this is exactly what I've been trying to research about!!!

• 
  @ThatOSDev6 ай бұрын

  Glad it could help. Thanks for the comment. Cheers

• 
  @Nunya582946 ай бұрын

  @@ThatOSDev Cheers good sir

• 
  @user-tj9qf4tl2g6 ай бұрын

  ❤❤❤❤❤❤❤❤❤❤

• 
  @Blodstream6 ай бұрын

  Hey, thank you very much! But I ran into some other problems: in win32_window.c file, in the function "updateCursorImage", on the first else there's a "SetCursor" with a "LoadCursorW" giving an warning, and in function "createNativeWindow" too, so I just changed the 'W' to an 'A'. And, on the same file, in the function "createNativeWindow", there's a "LoadImageW" giving the same type of error, so I changed the 'W' to an 'A' too, and the Raylib runs perfectly. I hope this helped someone :)

• 
  @ThatOSDev6 ай бұрын

  Thanks for the input. What you are changing is the WIDE character to ANSI character of those functions. Wide takes in 16-Bits ( 2 Bytes ) while Ansi takes in 8-Bits (1 Byte). All of this is in relation to STRINGS, namely the UNICODE. So giving you a heads up that if you are having issues with the cursor, it's because you might need those UNICODE functions, by swapping it back to W. To enable UNICODE, just put #define UNICODE in your main.c file. Although, that might not work for all compilers. So you would need to check your compiler specs. I use GCC and that define works for me. Cheers

• 
  @billybrown79746 ай бұрын

  thank you very much

• 
  @ThatOSDev6 ай бұрын

  Happy to help.

• 
  @ganchimegganbaatar55157 ай бұрын

  thank you very much for the tutorial

• 
  @ThatOSDev7 ай бұрын

  I'm just happy it's useful to some folks. Thank you for the comment. 👍

• 
  @sjtr55638 ай бұрын

  this helped a lot! i thought i'd give an update since version 5.0 is out. btw i've done mine in c, but figured it shouldn't be that different of a setup from c++, so here are some differences i had to do: thankfully i haven't had to check boxes in compiler settings, but i did have to change .exe's in toolchain, since the most recommended i've read was w64devkit instead of MinGW. so x86_64-w64-mingw32-gcc.exe and the g++ version replace both, other exe are normal, just those 3 in the build options and linker setting, i had to add -lraylib and -lopengl32, this is from me comparing build script from notepad++, figured i'd add that and it worked. search dir are the same and here is when i finally got on the same page with this video and all the warnings, Not errors. strange difference though, i had only 2 warnings. same file, similar functions. having to do with "image resizing" and me new to programming "inline, what is that? wow, and it works!? cool" i did the same for those 2 warnings, and it worked. i have no idea if others will run into same warnings i did, but this is what i ran into, and hope it helps others. seriously, thank you for the video!

• 
  @ThatOSDev6 ай бұрын

  Sorry my reply took so long. Being homeless is a pain. Also youtube is not showing me your comment on the normal channel view. I found your comment in my studio section. Not sure why. Yea I just grabbed 5.0. I already reported that one of the examples didn't work, but of course no reply from anyone in their channel about it. Anyhow, thanks for the reply. Some day I hope to get back online in a more perminant manner. Cheers.

• 
  @joee-kp7qt8 ай бұрын

  welcome back :3

• 
  @ThatOSDev8 ай бұрын

  Thank you. Not exactly back. Yet. Working on it though. Thanks for the comment. Cheers

• 
  10 ай бұрын

  hello! very good series so far! but now im experiencing an error, i included all libs to my main.c (efimain.c) but in this line: EFI_STATUS Status = SystemTable->BootServices->LocateProtocol(&EFI_GRAPHICS_OUTPUT_PROTOCOL_GUID, 0, (void**)&gop); it says EFI_OUTPUT_PROTOCOL_GUID Expands to: { 0x9042a9de, 0x23dc, 0x4a38, {0x96, 0xfb, 0x7a, 0xde, 0xd0, 0x80, 0x51, 0x6a } } i found that there is a struct in efi.h: struct EFI_GUID EFI_GRAPHICS_OUTPUT_PROTOCOL_GUID = {0x9042a9de, 0x23dc, 0x4a38, {0x96, 0xfb, 0x7a, 0xde, 0xd0, 0x80, 0x51, 0x6a}}; but even though it doesnt work, please help love your series <3

• 
  @ThatOSDev10 ай бұрын

  I'm not sure why, but your comment is not showing up. I just now found it. Also, I'm homeless, so no internet most of the time. With that said, Looks like the GUID you are using is correct. Check the source code that you wrote and see if there is something misstyped. Also, you can use the code off my git and it will allow you to compare your code with mine. Hope this helps. Cheers.

• 
  @x86debug11 ай бұрын

  Hello, quick question: How come you chose to use .hdd? Why not something like vhdx?

• 
  @ThatOSDev11 ай бұрын

  Good question ! At the time I had no idea how to setup any other files from scratch. An HDD file I figured out was nothing but a raw file. And there was no pre-setup needed in order to use it. How I came to that conclusion at the time is because I was trying to find a common file extension that RUFUS would allow, because RUFUS was a pain in the butt trying to get something that works with everything. I even spoke to the creator of RUFUS, but he didn't understand what the problem was. HDD works with everything. VirtualBox, QEMU, OSFMount and RUFUS. So I stuck with it. All operating systems have a way to allow you to mount and use it as well, even if you have to download a tool to use it. HOWEVER, with that said, Now that I was able to talk Queso into it, he made a video series on using VHD. And he shares how to write the software that will allow you to create a VHD that has a UEFI / GPT partiion already presetup for you. I highly recommend watching his video series on it, since VHD is used on all software that I mentioned in the previous paragraph. CHEERS

• 
  @x86debug11 ай бұрын

  @@ThatOSDev Thank you so much for replying. I will definitely be checking out his series. Do you have a discord server or IRC chat? I'm interested in connecting with like-minded people to learn more about OS dev.

• 
  @ThatOSDev11 ай бұрын

  @@x86debug Since i'm currently homeless, I do not have my own server. I do have an account, which with a little effort you can find. I can't post it because YT would just delete my comment if I did. Good luck, and have fun programming.

• 
  @x86debug11 ай бұрын

  @@ThatOSDev I hope your situation gets resolved sooner rather than later. 🙏

• 
  @ThatOSDev10 ай бұрын

  @@x86debug Working on it. hahaha Thanks for the comment. 👍

• 
  @x86debug11 ай бұрын

  This is very helpful, thank you for making this series. My friend and I are attempting to make our own OS, we've gotten bored of our other projects. Hopefully this wont end up as another dead project. We don't expect our OS to be the "next big thing" or stable. We're just doing for the shits n giggles and to learn more about OS Dev. It is very fascinating. I've given you credit in our repo's README. I'll post the repo link when I'm farther along in the series. We're probably gonna use this OS for testing some weird and unorthodox things.

• 
  @ThatOSDev11 ай бұрын

  Happy to help, and thanks for the credit. Yea, although what I have listed here is how to boot an OS, using the EFI, I don't have an OS. But you should have enough videos here to get you started with your OS.Also, the channel I am sharing has a good OS series, even though he is just starting out with the EFI series. His channel is better then mine. With that said, My channel is also a source for opengl graphics programming. At least what I have of it. Currently, I'm homeless, so I can't do much until I get that resolved. Thinking outside the box is what my videos is all about. Cheers, and I wish you the best in your OS.

• 
  @x86debug11 ай бұрын

  Thanks!

• 
  @ThatOSDev11 ай бұрын

  Happy to help

• 
  @shubhanshutomar7940 Жыл бұрын

  For the variable sized integer types on different operating systems, I think that using 'stdint.h' would be a much better solution. Since it is much reliable in case of cross platform. Thank you for you content. Hope to see you back in action again soon.

• 
  @ThatOSDev Жыл бұрын

  You are absolutely correct. The reason I did this was to share that you CAN actually totally write everything from scratch. But yes, you can still use standard header files for most things. Thanks for the comment. Cheers

• 
  @shubhanshutomar7940 Жыл бұрын

  The thing with ELF is, it is the format used for nearly all POSIX compliant binary executables. The compiler assumes this because most of the time people would be developing application to work on an actual operating system and not a whole operating system. This is the reason for it being opt-out rather than opt-in on Linux. The mingw and MSys2 ports are designed to use the MS ABI by default because... well... they are being used to compile windows binaries. It just happens to be that Microsoft had an influential role in development of UEFI, thus EFI requiring the MS-ABI to work, and since the ports are developed for windows anyway they do not have to be modified, but on Linux the compiler has to be tweaked slightly to allow the MS-ABI. That is at least my gist of things. Feel free to correct me.

• 
  @ThatOSDev Жыл бұрын

  There is nothing to correct. You said it better then I did. THANK YOU for posting this. Sorry for my late reply. I'm current homeless. So I try to get on the net when I can.

• 
  @shubhanshutomar7940 Жыл бұрын

  @@ThatOSDev sorry to hear about your current situation. I hope that you find some light in your dark times. Thank you for your brilliant content.

• 
  @Nunya58294 Жыл бұрын

  I had found your project and was able to get file creation and directories working, but apparently I still can't write data to a file. I don't get any errors and no data is written. The file size ends up being zero so I'm still forced to support raw partitions for now for storing data needed by my bootloader. If anyone has resolved this let me know

• 
  @ThatOSDev Жыл бұрын

  This video didn't help ? kzread.info/dash/bejne/n5d2spihdczMkrg.html

• 
  @Nunya58294 Жыл бұрын

  Its because of your UEFI stuff i finally figured out adding write support to my bootloader project. Before this it was read-only

• 
  @ThatOSDev Жыл бұрын

  I appreciate the kind words. Cheers

• 
  @Nunya58294 Жыл бұрын

  @@ThatOSDev of course good sir!

• 
  @duskcus Жыл бұрын

  I recently subscribed and feel terrible to hear this. I wish you the best of luck in your current situation, and hope to see your videos when everything has settled down.

• 
  @ThatOSDev Жыл бұрын

  Thanks for the kind words. The way I see it, I'm still breathing. So it's no time to give up. Sure I'm in my 50s, but there's other adventures to be had. Even if I loose all marbles in my brain and can't program anymore, at least I can use a shovel and dig holes in the dirt. 🤣

• 
  @rubiks7196 Жыл бұрын

  all video modes return unsupported status

• 
  @ThatOSDev Жыл бұрын

  What kind of graphics card / CPU / computer are you using ? EDIT : Or are you using a VM, like VirtualBox ? Also, what is your MaxResolutionModes count ? You can get it from gop->Mode->MaxMode

• 
  @rubiks7196 Жыл бұрын

  @@ThatOSDev I use qemu, there are only 30 modes set Mode on any of them returns 3 | error_bit

• 
  @ThatOSDev Жыл бұрын

  @@rubiks7196 Although this question shouldn't make a difference, are you on windows or linux when building your code ? The reason I ask is, if you are on windows, have you tried my code from my github yet ? If you have not, go into tutorial 27, and run the bat files. Make sure your GCC and QEMU is in your path. Let me know what happens. EDIT : Also, can you use OBS and record what you are doing so I can see if I can spot the issue. Post the video on your channel.

• 
  @ThatOSDev Жыл бұрын

  @@rubiks7196 Or, if you would rather we chat 1 on 1, my about section has my discord info.

• 
  @rubiks7196 Жыл бұрын

  @@ThatOSDev unfortunately, my code is very different from yours, besides I use msvc

• 
  @hampus23 Жыл бұрын

  5:11 Hopefully his channel goes down 😅

• 
  @Nunya58294 Жыл бұрын

  I tried to report the channel, but KZread apparently makes you jump through hoops for it

• 
  @ThatOSDev Жыл бұрын

  CORRECTION : 8 Minutes and 30 seconds in, I said 3.459 - 1.459 = 2.459. That is wrong, it would equal 2.0. Getting old sucks. 🤣

• 
  @guckesksk5895 Жыл бұрын

  Have you considered joining some small gamedev company? You said in video that you worked on professional project so you should consider joining some successful gamedev companies too. I wanna say that your plan is very risky, what will you do if your plan fails?, what if the other guy suddenly loses interest? What if he betrays you? What if he steals your code? Well I’m young so I don’t have much experience at how life works as you and I’m just paranoid. I will keep my fingers crossed for you and I hope that your plan will work out. Last question How much is rent in US? Is it really that bad?

• 
  @ThatOSDev Жыл бұрын

  Don't sweat it. I used to be paranoid of people too. But I'm old enough to not worry to much about it anymore. The way I see it, if he / she is that bad, then I can just move on. Life is too short. As for rent, yes. After what our current president has done to our country, Rent is tripple what it used to be. And now people are getting killed over racism nonsense. So yea, it's pretty bad. To be honest, I'll be happy to move out of this city I am currently in. I have plans and goals, so whom ever I work with, I would prefer they were on the same page. I don't want to sit behind for walls for the rest of my life, with nothing to show for it. If nothing happens, well I could always get a motorcycle, strap my guitar to my back, drive off into the sunset, like a nomad.

• 
  @ThatOSDev Жыл бұрын

  Also, I love that song on your playlist "Major Lazer - Be Together feat. Wild Belle (Vanic Remix)". On that Trap Nation chan. I used to listen to that channel all the time.

• 
  @guckesksk5895 Жыл бұрын

  @@ThatOSDev Yea, when I was playing games 24/7 I collected a lot of music so I decided to make small playlist of some of my favorites. Glad someone noticed.