home.social

#smb1 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #smb1, aggregated by home.social.

  1. I don't recall ever finishing #SMB1 lol, which is wack for a #retrogaming guy lol. Will try to get that done this weekend :mario_wave:

  2. I don't recall ever finishing #SMB1 lol, which is wack for a #retrogaming guy lol. Will try to get that done this weekend :mario_wave:

  3. I don't recall ever finishing #SMB1 lol, which is wack for a #retrogaming guy lol. Will try to get that done this weekend :mario_wave:

  4. I don't recall ever finishing #SMB1 lol, which is wack for a #retrogaming guy lol. Will try to get that done this weekend :mario_wave:

  5. I don't recall ever finishing #SMB1 lol, which is wack for a #retrogaming guy lol. Will try to get that done this weekend :mario_wave:

  6. TWIST: Meldaboi, SMB, Fatty M @ Twist Bar - 27 Mar feat. SMB (1), Meldaboi, Fatty M

    #SESH #SMB1 #Meldaboi #FattyM

    sesh.sx/e/1965038

  7. Over The Limit #3 @ Burza #4 - 13 Mar feat. SMB (1), Young Aesthete, Silverbo1 + more

    #SESH #SMB1 #YoungAesthete #Silverbo1

    sesh.sx/e/1919178

  8. Auf Windows 98 Netzwerkfreigaben (#SMB) von Windows 10 aus zugreifen

    Unter Windows 10/11 sind im heimischen Netzwerk plötzlich bisher funktionierende Netzwerkfreigeben / SMB-Shares auf Windows 98 oder einer FritzBox nicht mehr sichtbar und es kann auch nicht mehr darauf zugegriffen werden?

    Das liegt daran, dass ab Windows 10 die Unterstützung für das alte #SMB1 Protokoll für die Kommunikation im Netzwerk aus Sicherheitsgründen nicht mehr automatisch aktiviert ist.

    creopard.de/2020/01/Auf-Window

  9. Speedrunner averge11 has set a new world record in Super Mario Bros. 1, completing the game in 4:54.415! Their time is only 0.15 seconds, or 9 frames, away from a perfect run. This improves on the previous record by 2 frames, which was a tie between Niftski and averge11 themself.

    They didn't realize their run was a world record until a bit later, so watch to the end of the video for their reaction.

    youtu.be/R1Tlqfl3CxM

    #speedrunning #smb1 #worldrecord

  10. Speedrunner averge11 has set a new world record in Super Mario Bros. 1, completing the game in 4:54.415! Their time is only 0.15 seconds, or 9 frames, away from a perfect run. This improves on the previous record by 2 frames, which was a tie between Niftski and averge11 themself.

    They didn't realize their run was a world record until a bit later, so watch to the end of the video for their reaction.

    youtu.be/R1Tlqfl3CxM

    #speedrunning #smb1 #worldrecord

  11. And ten days after that record was set, the second-placed person (who had the then-WR only a couple of months backs) has achieved an identical time (recall: this is timed to the frame). So it's not just some fluke occurrence. Two people have gotten to the level of just *11 frames* slower than the best tool-assisted speedrun.

    #smb1 #speedrun

  12. And ten days after that record was set, the second-placed person (who had the then-WR only a couple of months backs) has achieved an identical time (recall: this is timed to the frame). So it's not just some fluke occurrence. Two people have gotten to the level of just *11 frames* slower than the best tool-assisted speedrun.

    #smb1 #speedrun

  13. And ten days after that record was set, the second-placed person (who had the then-WR only a couple of months backs) has achieved an identical time (recall: this is timed to the frame). So it's not just some fluke occurrence. Two people have gotten to the level of just *11 frames* slower than the best tool-assisted speedrun.

    #smb1 #speedrun

  14. And ten days after that record was set, the second-placed person (who had the then-WR only a couple of months backs) has achieved an identical time (recall: this is timed to the frame). So it's not just some fluke occurrence. Two people have gotten to the level of just *11 frames* slower than the best tool-assisted speedrun.

    #smb1 #speedrun

  15. And ten days after that record was set, the second-placed person (who had the then-WR only a couple of months backs) has achieved an identical time (recall: this is timed to the frame). So it's not just some fluke occurrence. Two people have gotten to the level of just *11 frames* slower than the best tool-assisted speedrun.

    #smb1 #speedrun

  16. I've commented before how these two #Microsoft #Win11 machines can see everything on my lan ... except each other 🤦‍♂️

    #CoPilot tells me this is a known issue and I can either activate #smb1 protocol 😱 or perform a simple 7-step work around, 🤔 basically enabling #netbios over #TCP

    Wrapping a non-error-correcting protocol inside an error-correcting protocol, for you non-nerds 🤓 instead of using an error-correcting protocol alone, b/c someone just can't say goodbye to #novel #netware🦕💩🧟‍♂️

    #1995

  17. I've commented before how these two #Microsoft #Win11 machines can see everything on my lan ... except each other 🤦‍♂️

    #CoPilot tells me this is a known issue and I can either activate #smb1 protocol 😱 or perform a simple 7-step work around, 🤔 basically enabling #netbios over #TCP

    Wrapping a non-error-correcting protocol inside an error-correcting protocol, for you non-nerds 🤓 instead of using an error-correcting protocol alone, b/c someone just can't say goodbye to #novel #netware🦕💩🧟‍♂️

    #1995

  18. I've commented before how these two #Microsoft #Win11 machines can see everything on my lan ... except each other 🤦‍♂️

    #CoPilot tells me this is a known issue and I can either activate #smb1 protocol 😱 or perform a simple 7-step work around, 🤔 basically enabling #netbios over #TCP

    Wrapping a non-error-correcting protocol inside an error-correcting protocol, for you non-nerds 🤓 instead of using an error-correcting protocol alone, b/c someone just can't say goodbye to #novel #netware🦕💩🧟‍♂️

    #1995

  19. Ебучие бляди, захуй вы убили в #ksmbd поддержку #smb1 (#cifs)?

    История: раньше работало всё через самбу, обновил #openwrt, они там отказались от «устаревших» протоколов. Маки отвалились, виндовоз (нахуй нужен) работает. Пришлось поставить кошерный #afp через #netatalk
    Аминь

  20. Ебучие бляди, захуй вы убили в #ksmbd поддержку #smb1 (#cifs)?

    История: раньше работало всё через самбу, обновил #openwrt, они там отказались от «устаревших» протоколов. Маки отвалились, виндовоз (нахуй нужен) работает. Пришлось поставить кошерный #afp через #netatalk
    Аминь

  21. Ебучие бляди, захуй вы убили в #ksmbd поддержку #smb1 (#cifs)?

    История: раньше работало всё через самбу, обновил #openwrt, они там отказались от «устаревших» протоколов. Маки отвалились, виндовоз (нахуй нужен) работает. Пришлось поставить кошерный #afp через #netatalk
    Аминь

  22. @CyDeFect @FiLiS all of these are missing too many details to tell anything about them. Except for #CIFS (although you probably don't even want that but #SMB3 instead, #Linux just kept tthe "CIFS" name although supporting SMB3), all #FreeBSD offers is indeed #SMB1. Whether this is an issue or not depends on your scenario and environment. I just offer my shares via #NFS as well, problem solved for me.

    BTW, #seamonkey was removed mainly because of a #python2 (EOL for a long time) build dependency. IIRC this is meanwhile solved, so the port *could* be readded, it's just someone would have to do it and maintain it. There's an inofficial port available, you'll find it on the forums.

  23. @CyDeFect @FiLiS all of these are missing too many details to tell anything about them. Except for #CIFS (although you probably don't even want that but #SMB3 instead, #Linux just kept tthe "CIFS" name although supporting SMB3), all #FreeBSD offers is indeed #SMB1. Whether this is an issue or not depends on your scenario and environment. I just offer my shares via #NFS as well, problem solved for me.

    BTW, #seamonkey was removed mainly because of a #python2 (EOL for a long time) build dependency. IIRC this is meanwhile solved, so the port *could* be readded, it's just someone would have to do it and maintain it. There's an inofficial port available, you'll find it on the forums.

  24. @CyDeFect @FiLiS all of these are missing too many details to tell anything about them. Except for #CIFS (although you probably don't even want that but #SMB3 instead, #Linux just kept tthe "CIFS" name although supporting SMB3), all #FreeBSD offers is indeed #SMB1. Whether this is an issue or not depends on your scenario and environment. I just offer my shares via #NFS as well, problem solved for me.

    BTW, #seamonkey was removed mainly because of a #python2 (EOL for a long time) build dependency. IIRC this is meanwhile solved, so the port *could* be readded, it's just someone would have to do it and maintain it. There's an inofficial port available, you'll find it on the forums.

  25. @CyDeFect @FiLiS all of these are missing too many details to tell anything about them. Except for #CIFS (although you probably don't even want that but #SMB3 instead, #Linux just kept tthe "CIFS" name although supporting SMB3), all #FreeBSD offers is indeed #SMB1. Whether this is an issue or not depends on your scenario and environment. I just offer my shares via #NFS as well, problem solved for me.

    BTW, #seamonkey was removed mainly because of a #python2 (EOL for a long time) build dependency. IIRC this is meanwhile solved, so the port *could* be readded, it's just someone would have to do it and maintain it. There's an inofficial port available, you'll find it on the forums.

  26. @CyDeFect @FiLiS all of these are missing too many details to tell anything about them. Except for (although you probably don't even want that but instead, just kept tthe "CIFS" name although supporting SMB3), all offers is indeed . Whether this is an issue or not depends on your scenario and environment. I just offer my shares via as well, problem solved for me.

    BTW, was removed mainly because of a (EOL for a long time) build dependency. IIRC this is meanwhile solved, so the port *could* be readded, it's just someone would have to do it and maintain it. There's an inofficial port available, you'll find it on the forums.

  27. just played the Super Mario Bros co-op #romhack with @nordern. it's pretty fun and works surprisingly well, even though we both suck at #SMB1 😅.

    romhacking.net/hacks/4180/

    #SuperMario #gaming

  28. just played the Super Mario Bros co-op #romhack with @nordern. it's pretty fun and works surprisingly well, even though we both suck at #SMB1 😅.

    romhacking.net/hacks/4180/

    #SuperMario #gaming

  29. just played the Super Mario Bros co-op #romhack with @nordern. it's pretty fun and works surprisingly well, even though we both suck at #SMB1 😅.

    romhacking.net/hacks/4180/

    #SuperMario #gaming

  30. just played the Super Mario Bros co-op #romhack with @nordern. it's pretty fun and works surprisingly well, even though we both suck at #SMB1 😅.

    romhacking.net/hacks/4180/

    #SuperMario #gaming

  31. P.S. If you made it this far and are wondering what wsdd2/WS-Discovery is all about: #Microsoft broke discovery of LAN devices when deprecating #SMB1.

    WS-Discovery is their attempt to "fix" this, and is basically a competitor to #Bonjour / #Avahi / #Zeroconf (why couldn't MS have just used that?).

    Unfortunately it means only devices implementing WS-Discovery are visible in Windows 10/11's network browser.

    Fortunately there's a #FOSS utility named #wsdd2 that implements WS-Discovery on Linux.

  32. P.S. If you made it this far and are wondering what wsdd2/WS-Discovery is all about: #Microsoft broke discovery of LAN devices when deprecating #SMB1.

    WS-Discovery is their attempt to "fix" this, and is basically a competitor to #Bonjour / #Avahi / #Zeroconf (why couldn't MS have just used that?).

    Unfortunately it means only devices implementing WS-Discovery are visible in Windows 10/11's network browser.

    Fortunately there's a #FOSS utility named #wsdd2 that implements WS-Discovery on Linux.

  33. P.S. If you made it this far and are wondering what wsdd2/WS-Discovery is all about: #Microsoft broke discovery of LAN devices when deprecating #SMB1.

    WS-Discovery is their attempt to "fix" this, and is basically a competitor to #Bonjour / #Avahi / #Zeroconf (why couldn't MS have just used that?).

    Unfortunately it means only devices implementing WS-Discovery are visible in Windows 10/11's network browser.

    Fortunately there's a #FOSS utility named #wsdd2 that implements WS-Discovery on Linux.

  34. #Microsoft disables #SMB1 file-sharing protocol by default in #Windows 11 Home

    While some argue this is bad because old servers depend on it argue it is security wise absolute a correct decision. Besides it is possible to upgrade to SMBv3.

    zdnet.com/article/microsoft-di

  35. ⚠️ Samba 4.11 schaltet SMB1 ab

    📌 Die Samba-Entwickler haben ihre Windows-Interoperabilitäts-Suite in der Version 4.11 veröffentlicht. Die Neuerungen seit der letzten Version sind umfangreich und umfassen viele Bereiche des Softwarepakets. Unter anderem wurde in der neuen Version das veraltete SMB1-Protokoll standardmäßig abgeschaltet.

    #Samba #Samba411 #SMB1 #Netzwerk

    pro-linux.de/news/1/27456/samb