home.social

#linc — Public Fediverse posts

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

  1. Imagine sipping your morning coffee on a sunlit patio in Woodthorpe, the gentle buzz of nature surrounding you. Local tradespeople know just how to enhance that bliss with tailored landscaping, from sturdy driveways to tranquil garden nooks. Their expertise in our Lincolnshire soil makes all the difference, turning your outdoor vision into a reality while boosting your home's value. Support local and watch your space flourish!

    ukpavingtalkgroup.com/towns/wo

    #Woodthorpe #Linc

  2. Another amazing find by @larsbrinkhoff is this #LAP6 source code printout: bitsavers.org/pdf/washingtonUn

    It was good to see probably the most hardcore #LINC program out there in its original source form. But looking into this we found an oddity that uncovered some ingenious #RealProgrammer tricks that Mary Allen Wilkes used in her code.

    Take a look at the attached screenshot here. This is a section from the `MSDISPLY.M` "manuscript" (text/source code) file for the main LAP6 editor. The first column is the memory location (in octal), second column is the octal value for the instruction line, and to the right of that is the source code in LINC assembly.

    The code is full of subroutines, which make use of the fact that the first 16 memory locations are treated as a sort of register file, and the `JMP` instruction stores a return pointer in "register" 0 so that a `JMP 0` is basically `RET`. The only mnemonics that are in this code are `JMP`, `LDA`, `SAE`, and `XSK`.

    `LDA i` loads the next word in the code into the accumulator, `SAE i` skips an instruction if the accumulator is equal to the next word in the code, and `XSK i 0` checks to see if the address in register 0 has overflowed somehow. The details of this subroutine are less interesting than all of the other lines.

    Some of the lines have text like `BIGGEST BLOCK USED IN WA` and `MAXIMUM LN`, which the assembler has assigned the value `0000`, presumably because they are invalid instructions in LAP6 assembly. I guess that's a neat trick: bad memonics can make a handy self-documenting null value!

    But take a look at line `524`:

    ```
    524 0011 CURRENT LN
    ```

    That's a bit of a novelty. How did `CURRENT LN` assemble to the value `0011` (9, decimal)?

    Well remember that Mary Allen Wilkes had a strong hand on the LINC ISA: she wrote the emulator that could run LINC code before the hardware was anywhere near functional. She also wrote the assembler for this ISA on that emulator. She had direct control of both parts of this chain, and so she made it so that the LINC Assembly Program only checked two letters to see if it was a valid mnemonic: the middle letter was ignored for uniqueness!

    So the word `CURRENT` basically matched the regex `^C.R`, and the assembler put the instruction for the `CLR` mnemonic, which is `0011`! (Incidentally this clears the accumulator when run as an opcode rather than an operand).

    I'm still not sure how it picked the values. Somehow at one point she uses the text `TAPE INSTR` to match the `SCR` instruction (`0340` if you're curious). So my regex above wasn't the only way it could match mnemonics.

    But now that I know that only the first and third letters are unique in combination, the whole instruction set begins to make more sense to me.

    #RetroComputing #MaryAllenWilkes

  3. Another amazing find by @larsbrinkhoff is this #LAP6 source code printout: bitsavers.org/pdf/washingtonUn

    It was good to see probably the most hardcore #LINC program out there in its original source form. But looking into this we found an oddity that uncovered some ingenious #RealProgrammer tricks that Mary Allen Wilkes used in her code.

    Take a look at the attached screenshot here. This is a section from the `MSDISPLY.M` "manuscript" (text/source code) file for the main LAP6 editor. The first column is the memory location (in octal), second column is the octal value for the instruction line, and to the right of that is the source code in LINC assembly.

    The code is full of subroutines, which make use of the fact that the first 16 memory locations are treated as a sort of register file, and the `JMP` instruction stores a return pointer in "register" 0 so that a `JMP 0` is basically `RET`. The only mnemonics that are in this code are `JMP`, `LDA`, `SAE`, and `XSK`.

    `LDA i` loads the next word in the code into the accumulator, `SAE i` skips an instruction if the accumulator is equal to the next word in the code, and `XSK i 0` checks to see if the address in register 0 has overflowed somehow. The details of this subroutine are less interesting than all of the other lines.

    Some of the lines have text like `BIGGEST BLOCK USED IN WA` and `MAXIMUM LN`, which the assembler has assigned the value `0000`, presumably because they are invalid instructions in LAP6 assembly. I guess that's a neat trick: bad memonics can make a handy self-documenting null value!

    But take a look at line `524`:

    ```
    524 0011 CURRENT LN
    ```

    That's a bit of a novelty. How did `CURRENT LN` assemble to the value `0011` (9, decimal)?

    Well remember that Mary Allen Wilkes had a strong hand on the LINC ISA: she wrote the emulator that could run LINC code before the hardware was anywhere near functional. She also wrote the assembler for this ISA on that emulator. She had direct control of both parts of this chain, and so she made it so that the LINC Assembly Program only checked two letters to see if it was a valid mnemonic: the middle letter was ignored for uniqueness!

    So the word `CURRENT` basically matched the regex `^C.R`, and the assembler put the instruction for the `CLR` mnemonic, which is `0011`! (Incidentally this clears the accumulator when run as an opcode rather than an operand).

    I'm still not sure how it picked the values. Somehow at one point she uses the text `TAPE INSTR` to match the `SCR` instruction (`0340` if you're curious). So my regex above wasn't the only way it could match mnemonics.

    But now that I know that only the first and third letters are unique in combination, the whole instruction set begins to make more sense to me.

    #RetroComputing #MaryAllenWilkes

  4. Another amazing find by @larsbrinkhoff is this #LAP6 source code printout: bitsavers.org/pdf/washingtonUn

    It was good to see probably the most hardcore #LINC program out there in its original source form. But looking into this we found an oddity that uncovered some ingenious #RealProgrammer tricks that Mary Allen Wilkes used in her code.

    Take a look at the attached screenshot here. This is a section from the `MSDISPLY.M` "manuscript" (text/source code) file for the main LAP6 editor. The first column is the memory location (in octal), second column is the octal value for the instruction line, and to the right of that is the source code in LINC assembly.

    The code is full of subroutines, which make use of the fact that the first 16 memory locations are treated as a sort of register file, and the `JMP` instruction stores a return pointer in "register" 0 so that a `JMP 0` is basically `RET`. The only mnemonics that are in this code are `JMP`, `LDA`, `SAE`, and `XSK`.

    `LDA i` loads the next word in the code into the accumulator, `SAE i` skips an instruction if the accumulator is equal to the next word in the code, and `XSK i 0` checks to see if the address in register 0 has overflowed somehow. The details of this subroutine are less interesting than all of the other lines.

    Some of the lines have text like `BIGGEST BLOCK USED IN WA` and `MAXIMUM LN`, which the assembler has assigned the value `0000`, presumably because they are invalid instructions in LAP6 assembly. I guess that's a neat trick: bad memonics can make a handy self-documenting null value!

    But take a look at line `524`:

    ```
    524 0011 CURRENT LN
    ```

    That's a bit of a novelty. How did `CURRENT LN` assemble to the value `0011` (9, decimal)?

    Well remember that Mary Allen Wilkes had a strong hand on the LINC ISA: she wrote the emulator that could run LINC code before the hardware was anywhere near functional. She also wrote the assembler for this ISA on that emulator. She had direct control of both parts of this chain, and so she made it so that the LINC Assembly Program only checked two letters to see if it was a valid mnemonic: the middle letter was ignored for uniqueness!

    So the word `CURRENT` basically matched the regex `^C.R`, and the assembler put the instruction for the `CLR` mnemonic, which is `0011`! (Incidentally this clears the accumulator when run as an opcode rather than an operand).

    I'm still not sure how it picked the values. Somehow at one point she uses the text `TAPE INSTR` to match the `SCR` instruction (`0340` if you're curious). So my regex above wasn't the only way it could match mnemonics.

    But now that I know that only the first and third letters are unique in combination, the whole instruction set begins to make more sense to me.

    #RetroComputing #MaryAllenWilkes

  5. Another amazing find by @larsbrinkhoff is this #LAP6 source code printout: bitsavers.org/pdf/washingtonUn

    It was good to see probably the most hardcore #LINC program out there in its original source form. But looking into this we found an oddity that uncovered some ingenious #RealProgrammer tricks that Mary Allen Wilkes used in her code.

    Take a look at the attached screenshot here. This is a section from the `MSDISPLY.M` "manuscript" (text/source code) file for the main LAP6 editor. The first column is the memory location (in octal), second column is the octal value for the instruction line, and to the right of that is the source code in LINC assembly.

    The code is full of subroutines, which make use of the fact that the first 16 memory locations are treated as a sort of register file, and the `JMP` instruction stores a return pointer in "register" 0 so that a `JMP 0` is basically `RET`. The only mnemonics that are in this code are `JMP`, `LDA`, `SAE`, and `XSK`.

    `LDA i` loads the next word in the code into the accumulator, `SAE i` skips an instruction if the accumulator is equal to the next word in the code, and `XSK i 0` checks to see if the address in register 0 has overflowed somehow. The details of this subroutine are less interesting than all of the other lines.

    Some of the lines have text like `BIGGEST BLOCK USED IN WA` and `MAXIMUM LN`, which the assembler has assigned the value `0000`, presumably because they are invalid instructions in LAP6 assembly. I guess that's a neat trick: bad memonics can make a handy self-documenting null value!

    But take a look at line `524`:

    ```
    524 0011 CURRENT LN
    ```

    That's a bit of a novelty. How did `CURRENT LN` assemble to the value `0011` (9, decimal)?

    Well remember that Mary Allen Wilkes had a strong hand on the LINC ISA: she wrote the emulator that could run LINC code before the hardware was anywhere near functional. She also wrote the assembler for this ISA on that emulator. She had direct control of both parts of this chain, and so she made it so that the LINC Assembly Program only checked two letters to see if it was a valid mnemonic: the middle letter was ignored for uniqueness!

    So the word `CURRENT` basically matched the regex `^C.R`, and the assembler put the instruction for the `CLR` mnemonic, which is `0011`! (Incidentally this clears the accumulator when run as an opcode rather than an operand).

    I'm still not sure how it picked the values. Somehow at one point she uses the text `TAPE INSTR` to match the `SCR` instruction (`0340` if you're curious). So my regex above wasn't the only way it could match mnemonics.

    But now that I know that only the first and third letters are unique in combination, the whole instruction set begins to make more sense to me.

    #RetroComputing #MaryAllenWilkes

  6. Another amazing find by @larsbrinkhoff is this #LAP6 source code printout: bitsavers.org/pdf/washingtonUn

    It was good to see probably the most hardcore #LINC program out there in its original source form. But looking into this we found an oddity that uncovered some ingenious #RealProgrammer tricks that Mary Allen Wilkes used in her code.

    Take a look at the attached screenshot here. This is a section from the `MSDISPLY.M` "manuscript" (text/source code) file for the main LAP6 editor. The first column is the memory location (in octal), second column is the octal value for the instruction line, and to the right of that is the source code in LINC assembly.

    The code is full of subroutines, which make use of the fact that the first 16 memory locations are treated as a sort of register file, and the `JMP` instruction stores a return pointer in "register" 0 so that a `JMP 0` is basically `RET`. The only mnemonics that are in this code are `JMP`, `LDA`, `SAE`, and `XSK`.

    `LDA i` loads the next word in the code into the accumulator, `SAE i` skips an instruction if the accumulator is equal to the next word in the code, and `XSK i 0` checks to see if the address in register 0 has overflowed somehow. The details of this subroutine are less interesting than all of the other lines.

    Some of the lines have text like `BIGGEST BLOCK USED IN WA` and `MAXIMUM LN`, which the assembler has assigned the value `0000`, presumably because they are invalid instructions in LAP6 assembly. I guess that's a neat trick: bad memonics can make a handy self-documenting null value!

    But take a look at line `524`:

    ```
    524 0011 CURRENT LN
    ```

    That's a bit of a novelty. How did `CURRENT LN` assemble to the value `0011` (9, decimal)?

    Well remember that Mary Allen Wilkes had a strong hand on the LINC ISA: she wrote the emulator that could run LINC code before the hardware was anywhere near functional. She also wrote the assembler for this ISA on that emulator. She had direct control of both parts of this chain, and so she made it so that the LINC Assembly Program only checked two letters to see if it was a valid mnemonic: the middle letter was ignored for uniqueness!

    So the word `CURRENT` basically matched the regex `^C.R`, and the assembler put the instruction for the `CLR` mnemonic, which is `0011`! (Incidentally this clears the accumulator when run as an opcode rather than an operand).

    I'm still not sure how it picked the values. Somehow at one point she uses the text `TAPE INSTR` to match the `SCR` instruction (`0340` if you're curious). So my regex above wasn't the only way it could match mnemonics.

    But now that I know that only the first and third letters are unique in combination, the whole instruction set begins to make more sense to me.

    #RetroComputing #MaryAllenWilkes

  7. github.com/open-simh/simh/pull ← There's a new emulator in open #SIMH for the #LINC, by @larsbrinkhoff. I will absolutely be running this on the hardware from my exhibit once the current exhibition finishes, and I'll work on getting the knobs and switches working accurately. I'll need to drive way more neopixels for that to work! #retrocomputing #vintagecomputing

  8. github.com/open-simh/simh/pull ← There's a new emulator in open #SIMH for the #LINC, by @larsbrinkhoff. I will absolutely be running this on the hardware from my exhibit once the current exhibition finishes, and I'll work on getting the knobs and switches working accurately. I'll need to drive way more neopixels for that to work! #retrocomputing #vintagecomputing

  9. github.com/open-simh/simh/pull ← There's a new emulator in open #SIMH for the #LINC, by @larsbrinkhoff. I will absolutely be running this on the hardware from my exhibit once the current exhibition finishes, and I'll work on getting the knobs and switches working accurately. I'll need to drive way more neopixels for that to work! #retrocomputing #vintagecomputing

  10. github.com/open-simh/simh/pull ← There's a new emulator in open #SIMH for the #LINC, by @larsbrinkhoff. I will absolutely be running this on the hardware from my exhibit once the current exhibition finishes, and I'll work on getting the knobs and switches working accurately. I'll need to drive way more neopixels for that to work! #retrocomputing #vintagecomputing

  11. github.com/open-simh/simh/pull ← There's a new emulator in open #SIMH for the #LINC, by @larsbrinkhoff. I will absolutely be running this on the hardware from my exhibit once the current exhibition finishes, and I'll work on getting the knobs and switches working accurately. I'll need to drive way more neopixels for that to work! #retrocomputing #vintagecomputing

  12. My #RetroComputing exhibit on the #LINC and Mary Allen Wilkes is open for free to the public in #Stratford #London through the end of October 2025. Please drop by and interact with it!

    ucl.ac.uk/bartlett/events/2025

  13. My #RetroComputing exhibit on the #LINC and Mary Allen Wilkes is open for free to the public in #Stratford #London through the end of October 2025. Please drop by and interact with it!

    ucl.ac.uk/bartlett/events/2025

  14. My #RetroComputing exhibit on the #LINC and Mary Allen Wilkes is open for free to the public in #Stratford #London through the end of October 2025. Please drop by and interact with it!

    ucl.ac.uk/bartlett/events/2025

  15. My #RetroComputing exhibit on the #LINC and Mary Allen Wilkes is open for free to the public in #Stratford #London through the end of October 2025. Please drop by and interact with it!

    ucl.ac.uk/bartlett/events/2025

  16. My #RetroComputing exhibit on the #LINC and Mary Allen Wilkes is open for free to the public in #Stratford #London through the end of October 2025. Please drop by and interact with it!

    ucl.ac.uk/bartlett/events/2025

  17. @neale Here's a closeup of the exhibit as I left it after showing it to @anmeisel the other day. #LINC #RetroComputing #UCL #PublicHistory

  18. @neale Here's a closeup of the exhibit as I left it after showing it to @anmeisel the other day. #LINC #RetroComputing #UCL #PublicHistory

  19. @neale Here's a closeup of the exhibit as I left it after showing it to @anmeisel the other day. #LINC #RetroComputing #UCL #PublicHistory

  20. @neale Here's a closeup of the exhibit as I left it after showing it to @anmeisel the other day. #LINC #RetroComputing #UCL #PublicHistory

  21. @neale Here's a closeup of the exhibit as I left it after showing it to @anmeisel the other day. #LINC #RetroComputing #UCL #PublicHistory

  22. My #RetroComputing exhibit about the #LINC is about to open at the #UCL Urban Room for the next two months.
    ucl.ac.uk/bartlett/events/2025

    Edit: It's now open! You have until Friday, 31 Oct 2025 to come and see it!

  23. My #RetroComputing exhibit about the #LINC is about to open at the #UCL Urban Room for the next two months.
    ucl.ac.uk/bartlett/events/2025

    Edit: It's now open! You have until Friday, 31 Oct 2025 to come and see it!

  24. My #RetroComputing exhibit about the #LINC is about to open at the #UCL Urban Room for the next two months.
    ucl.ac.uk/bartlett/events/2025

    Edit: It's now open! You have until Friday, 31 Oct 2025 to come and see it!

  25. My #RetroComputing exhibit about the #LINC is about to open at the #UCL Urban Room for the next two months.
    ucl.ac.uk/bartlett/events/2025

    Edit: It's now open! You have until Friday, 31 Oct 2025 to come and see it!

  26. My #RetroComputing exhibit about the #LINC is about to open at the #UCL Urban Room for the next two months.
    ucl.ac.uk/bartlett/events/2025

    Edit: It's now open! You have until Friday, 31 Oct 2025 to come and see it!

  27. Bağcılar'da kız arkadaşını bıçaklayan şüpheli linç edildi: Olay saat 20.00 sıralarında Güneşli Mahallesi'nde meydana geldi. Aynı iş yerinde çalışan Z.S. isimli kadın ile E.Y. isimli erkek arasında gönül ilişkisi başladı. Çiftin iş yerinde tartışma yaşaması üzerine, iş yeri sahibi E.Y.'yi işten çıkardı.

    SALDIRGAN MAHALLELİ TARAFINDAN LİNÇ EDİLDİ

    Duruma sinirlenen E.Y., takip ettiği Z.S.'yi… eshahaber.com.tr/haber/bagcila EshaHaber.com.tr #Bağcılar #KadınaŞiddet #Linç #Güvenlik #Özgürlük

  28. Bağcılar'da kız arkadaşını bıçaklayan şüpheli linç edildi: Olay saat 20.00 sıralarında Güneşli Mahallesi'nde meydana geldi. Aynı iş yerinde çalışan Z.S. isimli kadın ile E.Y. isimli erkek arasında gönül ilişkisi başladı. Çiftin iş yerinde tartışma yaşaması üzerine, iş yeri sahibi E.Y.'yi işten çıkardı.

    SALDIRGAN MAHALLELİ TARAFINDAN LİNÇ EDİLDİ

    Duruma sinirlenen E.Y., takip ettiği Z.S.'yi… eshahaber.com.tr/haber/bagcila EshaHaber.com.tr #Bağcılar #KadınaŞiddet #Linç #Güvenlik #Özgürlük

  29. Bağcılar'da kız arkadaşını bıçaklayan şüpheli linç edildi: Olay saat 20.00 sıralarında Güneşli Mahallesi'nde meydana geldi. Aynı iş yerinde çalışan Z.S. isimli kadın ile E.Y. isimli erkek arasında gönül ilişkisi başladı. Çiftin iş yerinde tartışma yaşaması üzerine, iş yeri sahibi E.Y.'yi işten çıkardı.

    SALDIRGAN MAHALLELİ TARAFINDAN LİNÇ EDİLDİ

    Duruma sinirlenen E.Y., takip ettiği Z.S.'yi… eshahaber.com.tr/haber/bagcila EshaHaber.com.tr #Bağcılar #KadınaŞiddet #Linç #Güvenlik #Özgürlük

  30. Yol ortasında öldüresiye darbedildi! Linç girişimi kamerada: Olay, Kuşadası İkiçemelik Mahallesi Aydın Bulvarı üzerinde yaşandı. Amatör kameraya yansıyan görüntülerde, kimlikleri henüz belirlenemeyen bir grup ile bir şahsı saldırdı.

    "KÜFÜR" YÜZÜNDEN ÖLDÜRESİYE DARBEDİLDİ

    Sebebinin küfür ve hakaret olduğu iddia edilen olayda, yumruk ve sopalarla öldüresiye dövülen şahıs, bir motosikletin üzerine yığılarak… eshahaber.com.tr/haber/yol-ort EshaHaber.com.tr #Kuşadası #linç #şiddet #haber #olay

  31. Yol ortasında öldüresiye darbedildi! Linç girişimi kamerada: Olay, Kuşadası İkiçemelik Mahallesi Aydın Bulvarı üzerinde yaşandı. Amatör kameraya yansıyan görüntülerde, kimlikleri henüz belirlenemeyen bir grup ile bir şahsı saldırdı.

    "KÜFÜR" YÜZÜNDEN ÖLDÜRESİYE DARBEDİLDİ

    Sebebinin küfür ve hakaret olduğu iddia edilen olayda, yumruk ve sopalarla öldüresiye dövülen şahıs, bir motosikletin üzerine yığılarak… eshahaber.com.tr/haber/yol-ort EshaHaber.com.tr #Kuşadası #linç #şiddet #haber #olay

  32. Yol ortasında öldüresiye darbedildi! Linç girişimi kamerada: Olay, Kuşadası İkiçemelik Mahallesi Aydın Bulvarı üzerinde yaşandı. Amatör kameraya yansıyan görüntülerde, kimlikleri henüz belirlenemeyen bir grup ile bir şahsı saldırdı.

    "KÜFÜR" YÜZÜNDEN ÖLDÜRESİYE DARBEDİLDİ

    Sebebinin küfür ve hakaret olduğu iddia edilen olayda, yumruk ve sopalarla öldüresiye dövülen şahıs, bir motosikletin üzerine yığılarak… eshahaber.com.tr/haber/yol-ort EshaHaber.com.tr #Kuşadası #linç #şiddet #haber #olay

  33. Atatürk sorusuna cevap veremedi! Linç edildi: 24 yaşındaki kadın girişimce Kamile Bağcı, ATV'de yayınlanan Sunucu Oktay Kaynarca’nın yönettiği "Kim Milyoner Olmak İster" adlı yarışmaya katıldı.

    Yarışmada 5. soruya kadar başarıyla ilerleyen yarışmacı, Atatürk’ün matematik öğretmeninin ismini soran soruda yanlış cevap verince olanlar oldu.

    ATATÜRK SORUSUNA CEVAP VEREMEDİ

    "Mustafa… eshahaber.com.tr/haber/ataturk EshaHaber.com.tr #Atatürk #linç #KimMilyonerOlmakİster #KamileBağcı #yarışma

  34. Atatürk sorusuna cevap veremedi! Linç edildi: 24 yaşındaki kadın girişimce Kamile Bağcı, ATV'de yayınlanan Sunucu Oktay Kaynarca’nın yönettiği "Kim Milyoner Olmak İster" adlı yarışmaya katıldı.

    Yarışmada 5. soruya kadar başarıyla ilerleyen yarışmacı, Atatürk’ün matematik öğretmeninin ismini soran soruda yanlış cevap verince olanlar oldu.

    ATATÜRK SORUSUNA CEVAP VEREMEDİ

    "Mustafa… eshahaber.com.tr/haber/ataturk EshaHaber.com.tr #Atatürk #linç #KimMilyonerOlmakİster #KamileBağcı #yarışma

  35. Atatürk sorusuna cevap veremedi! Linç edildi: 24 yaşındaki kadın girişimce Kamile Bağcı, ATV'de yayınlanan Sunucu Oktay Kaynarca’nın yönettiği "Kim Milyoner Olmak İster" adlı yarışmaya katıldı.

    Yarışmada 5. soruya kadar başarıyla ilerleyen yarışmacı, Atatürk’ün matematik öğretmeninin ismini soran soruda yanlış cevap verince olanlar oldu.

    ATATÜRK SORUSUNA CEVAP VEREMEDİ

    "Mustafa… eshahaber.com.tr/haber/ataturk EshaHaber.com.tr #Atatürk #linç #KimMilyonerOlmakİster #KamileBağcı #yarışma

  36. Cartographie des entrepôts de données de santé en France, proposée par le Laboratoire d’innovation numérique de la CNIL #LINC : cnil.fr/fr/explorez-la-cartogr

  37. Mottok et spennende byggesett på døra i går, komplett med grønn overledning #MT32-Pi #linc #midi #norsktut

  38. Mottok et spennende byggesett på døra i går, komplett med grønn overledning #MT32-Pi #linc #midi #norsktut

  39. Mottok et spennende byggesett på døra i går, komplett med grønn overledning #MT32-Pi #linc #midi #norsktut