• QuazarOmega@lemy.lol
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      Even funnier when it’s their own platform and it has been missing the feature to disable them for so long afaik

    • zarenki@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      In 2014, MS-DOS 1.25 and 2.0 were released under a Microsoft shared-source license (Microsoft Research License) which forbids redistribution

      In 2018, both versions were published to GitHub and relicensed as MIT, making them properly open-source

      Today, MS-DOS 4.00 was added to that repo, also under MIT.

  • viking@infosec.pub
    link
    fedilink
    arrow-up
    2
    ·
    7 months ago

    LOL, some of the comments in the source are gold.

    https://github.com/microsoft/MS-DOS/blob/main/v4.0/src/DOS/ABORT.ASM

    Note:  We do need to explicitly close FCBs.  Reasons are as follows:  If we
    ; are running in the no-sharing no-network environment, we are simulating the
    ; 2.0 world and thus if the user doesn't close the file, that is his problem
    ; BUT...  the cache remains in a state with garbage that may be reused by the
    ; next process.  We scan the set and blast the ref counts of the FCBs we own.
    ;
    ; If sharing is loaded, then the following call to close process will
    ; correctly close all FCBs.  We will then need to walk the list AFTER here.
    ;
    ; Finally, the following call to NET_Abort will cause an EOP to be sent to all
    ; known network resources.  These resources are then responsible for cleaning
    ; up after this process.
    ;
    ; Sleazy, eh?~
    
  • katy ✨@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

    i remember writing .bat files and pretending they were really fancy update scripts when i was like ten they did nothing but it was still fun :)

    • Ms. ArmoredThirteen@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      7 months ago

      Like half of my job is writing .bat files to automate stuff locally and not tell my boss that all I do anymore is double click the right things in the right order…

      • viking@infosec.pub
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        You can put in a timeout command at the end, and then call the next .bat file.

        For example “TIMEOUT /T 60” waits for 60 seconds before resuming, or you can override it by pressing any key.

        So if you know how long the wait time between scripts is, just write a master.bat and call them in order, with adequate waiting time in between.