Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

1 Follower

About Breadpudding

  • Title
  • Birthday 2000-04-25

Contact Methods

  • Discord
  • Steam

Profile Information

  • Gender
  • Location
    Planet Earth
  • Interests
    Programming(Rust/Assembly), Hacking, Music from the 60s/70s/early 80s, Anime, Cards against Humanity, Team Fortress 2, Good food, and Linux.
  • Occupation
    Dual Major Student


  • CPU
    Intel i7-8086K
  • Motherboard
    MSI Z370-A PRO
  • RAM
    Ballistix Sport 8GB
  • GPU
    Nvidia GeForce GTX 1650
  • Case
    Corsair Carbide 100R
  • Storage
    Silicon Power 500GB m.2-2280
  • PSU
    EVGA 500W 80+ Bronze
  • Display(s)
    DELL ST2320LF
  • Cooling
    Cooler Master Hyper 212 Evo
  • Keyboard
    CM Storm Devastator
  • Mouse
    Cherry M5400
  • Operating System
    OpenSUSE Tumbleweed with i3

Recent Profile Visitors

355 profile views
  1. As long as you have some kind of protocol in place to pass information back and forth, the two parts can communicate with each other. The type of connection used depends on what you hope to achieve and how you want them to communicate.
  2. I'm not worried about that since I use Debian as my main operating system. My only goal here is to read from floppies. Writing to them would be more of a luxury than a necessity. I don't have the old computer unfortunately. My father has a nasty habit of getting rid of anything that he deems to be simply taking up space. That includes the RGBI monitor that came with the computer. Without RGBI, that made the computer useless. All I have left of it is an i8088, BIOS chip from the video card, and the 5.25" floppy drive.
  3. Let me explain. Each character is 16 bits wide since that's what UEFI wants(hence the u16). C had a simple way of doing this by simply appending a string with the letter L. With Rust however, it seems to be more complicated as it doesn't seem to have UTF-16 support out of the box. What I'm trying to figure out is how I can turn a Unicode string into a pointer to an array of 16 bit characters.
  4. Because I have an actual 5.25" floppy I salvaged from an old computer.
  5. Discontinued. I have a feeling that this is going to be a fun journey.
  6. You just made the same mistake I did. While you have the correct cable(I do too), you have the wrong controller(which is the reason I made this thread)! These are the things I bought: https://www.amazon.com/gp/product/B07KDJTMGP/ref=ppx_yo_dt_b_asin_title_o01_s01?ie=UTF8&psc=1 https://www.amazon.com/gp/product/B000YAX13Y/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
  7. If you're new to Linux I'd recommend Debian over Ubuntu server. Just get the standard system utilities so you don't have a GUI hogging resources. ~Breadpudding
  8. The first thing you should do is make sure you're booted via UEFI still. One of the updates may have broken that. If you have confirmed that you are booted via UEFI you can add this to your grub.cfg: menuentry 'System setup' $menuentry_id_option 'uefi-firmware' { fwsetup } Reboot and the option should appear. Let me know how it works! ~Breadpudding Edit: This was found in the grub.cfg on my Debian system. Compatibility may vary with Mint.
  9. If you look at the following diagram they're identical minus the PWM pin which is useless since your fan doesn't support it anyway. (Credit to whoever posted it on this site before)
  10. So I recently made a purchase on Amazon to put together an adapter for my 5.25" floppy drive. However, when I received the package today, I realized that the cable I ordered wasn't an IDE cable, but rather IDC34. This meant that my PCIe to IDE adapter(which I tested with an older drive and is working) would ultimately do nothing. Would it be possible to find a similar device for IDC34? I have PCIe, PCI, and SATA ports available. Thanks in advance, Breadpudding
  11. The title says it all. How would one create a UTF-16 string in Rust and pass it to C as a *const u16? Thanks in advance, Breadpudding
  12. I haven't thought about velcro. That's a pretty good idea and I might do that.
  13. Unfortunately I can't drill any new holes since the entire case is made out of metal(actual metal not the cheap crap that comes in most cases). I'm not sure how I would mount the HDD to the air flow holes but it's an idea worth exploring as long as I leave one of the sides open. As for the double-sided tape I don't have any actual double-sided tape but I can make a loop out of regular tape(not that it'll keep it from vibrating at all). I'm planning on not having any PCIe cards for two reasons: This is supposed to be a server The case prevents me from putting any "standard" PCIe cards in without modification I do want to keep it secure to the case because this will be running for long periods of time.
  14. So I decided to try to build the smallest computer possible using parts I already have. I've had success thus far, however I didn't think about the HDD until I tried to put it into the case. Since the motherboard(MicroATX) is bigger than the previous one(FlexATX), it doesn't have any room for the HDD bracket anymore. That's fine because I wasn't planning on having a full-sized desktop HDD, but I still don't have a place to put my laptop HDD. Does anybody have any ideas for mounting it? Thanks in advance, Breadpudding