• Re: PC/IX, Unix on x86, Hmmm ... Downloaded Xenix - But It's *41*Floppies Worth

    From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,alt.folklore.computers on Tue Sep 2 21:22:35 2025
    From Newsgroup: comp.os.linux.misc

    On 2025-08-30, rbowman <bowman@montana.com> wrote:

    On Sat, 30 Aug 2025 03:06:11 -0400, c186282 wrote:

    Tbe original 8088 had all the needed registers.
    Could minimum deliver at LEAST an easy 64k code space and at LEAST
    another 64k data area. A few tricks and .......

    They mostly followed the bank switching the Z80s were doing but
    incorporated the memory management into the processor. After all, the i432 was the REAL answer so why get fancy with the Band-Aid.

    "It's a good thing the iAPX432 never took off. Otherwise a totally
    horrid Intel architecture might have taken over the world."
    --
    /~\ Charlie Gibbs | Growth for the sake of
    \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology
    X I'm really at ac.dekanfrus | of the cancer cell.
    / \ if you read it the right way. | -- Edward Abbey
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,alt.folklore.computers on Tue Sep 2 21:22:36 2025
    From Newsgroup: comp.os.linux.misc

    On 2025-08-30, candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:

    Lawrence D’Oliveiro <ldo@nz.invalid> wrote at 03:27 this Saturday (GMT):

    On Fri, 29 Aug 2025 23:51:18 GMT, Charlie Gibbs wrote:

    But there definitely was a period before that where the button vanished
    (although there would have been motherboard pins if you wanted to dig
    into it).

    Apple included a little springy clip thing (the “Programmers’s Switch”) in
    the box with each of those original classic-form-factor Macintoshes. When >> installed, pressing one side triggered NMI (used for invoking the resident >> debugger), while the other side triggered the RESET line (hard reboot).

    I still have the muscle memory: seated in front of the machine, reach
    around with right hand, far side was NMI, near side was RESET.

    That's pretty cool, I always wished there was a physical switch to
    trigger a debugger since the system might be frozen...

    And that, ladies and gentlemen, is why you want a reset button
    rather than having to resort to the power switch.
    --
    /~\ Charlie Gibbs | Growth for the sake of
    \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology
    X I'm really at ac.dekanfrus | of the cancer cell.
    / \ if you read it the right way. | -- Edward Abbey
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,alt.folklore.computers on Tue Sep 2 21:22:39 2025
    From Newsgroup: comp.os.linux.misc

    On 2025-08-30, Peter Flass <Peter@Iron-Spring.com> wrote:

    On 8/30/25 08:54, Scott Lurndal wrote:

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:

    On 29 Aug 2025 20:52:10 GMT, Ted Nolan <tednolan> wrote:

    Using overlays was never straightforward, on any OS.

    Typical troll comment.

    There are existance proofs counter to your
    unsupported blanket statement.

    Burroughs medium systems for example, where using overlays was built
    into the compilation tools (including the COBOL compiler) and the
    operating system. Even the operating system used overlays for
    rarely used functionality.

    OS/360 and applications made extensive use of overlays.

    I remember a (PC)-Dos application called "Enable" that overlayed like crazy.

    Univac's OS/3 (sort of a 360/370 workalike) had several utilities
    that had as many as 45 overlays. This, combined with other
    memory-squeezing tricks like "transients" (routines that rolled
    in and out of special areas in memory) meant that the system drive
    was typically thrashing furiously.

    It was typical to low-ball memory requirements to get a sale, then
    sell the customer more memory afterwards when the system turned out
    to be painfully slow and it was too late to back out.
    --
    /~\ Charlie Gibbs | Growth for the sake of
    \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology
    X I'm really at ac.dekanfrus | of the cancer cell.
    / \ if you read it the right way. | -- Edward Abbey
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From John Ames@commodorejohn@gmail.com to comp.os.linux.misc,alt.folklore.computers on Tue Sep 2 14:45:05 2025
    From Newsgroup: comp.os.linux.misc

    On Tue, 02 Sep 2025 21:22:39 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    It was typical to low-ball memory requirements to get a sale, then
    sell the customer more memory afterwards when the system turned out
    to be painfully slow and it was too late to back out.

    ...whereas nowadays, we have to recommend our customers spec out twice
    the memory they'd actually need as between Win10/11, the nine million
    browser tabs everyone keeps open at all times, vendor bloatware, and
    special gold-medal memory hogs like QuickBooks, an entry-level system
    is full to bursting and swapping madly before they even load *our* application...

    ...and half the damn time they buy the entry-level system anyway, and
    then complain about *our* software being slow :/

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,alt.folklore.computers on Tue Sep 2 21:46:58 2025
    From Newsgroup: comp.os.linux.misc

    Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
    On 2025-08-30, candycanearter07 ><candycanearter07@candycanearter07.nomail.afraid> wrote:

    Lawrence D’Oliveiro <ldo@nz.invalid> wrote at 03:27 this Saturday (GMT): >>
    On Fri, 29 Aug 2025 23:51:18 GMT, Charlie Gibbs wrote:

    But there definitely was a period before that where the button vanished >>>> (although there would have been motherboard pins if you wanted to dig
    into it).

    Apple included a little springy clip thing (the “Programmers’s Switch”) in
    the box with each of those original classic-form-factor Macintoshes. When >>> installed, pressing one side triggered NMI (used for invoking the resident >>> debugger), while the other side triggered the RESET line (hard reboot).

    I still have the muscle memory: seated in front of the machine, reach
    around with right hand, far side was NMI, near side was RESET.

    That's pretty cool, I always wished there was a physical switch to
    trigger a debugger since the system might be frozen...

    And that, ladies and gentlemen, is why you want a reset button
    rather than having to resort to the power switch.

    Unfortunately, a reset button would destroy most state
    that would be helpful in debugging since it directly
    (after debouncing) asserts the CPU reset signal.

    An NMI button, on the other hand is quite useful for debugging,
    particularly for kernel debugging.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,alt.folklore.computers on Tue Sep 2 22:03:18 2025
    From Newsgroup: comp.os.linux.misc

    Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
    On 2025-08-30, Peter Flass <Peter@Iron-Spring.com> wrote:

    On 8/30/25 08:54, Scott Lurndal wrote:

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:

    On 29 Aug 2025 20:52:10 GMT, Ted Nolan <tednolan> wrote:

    Using overlays was never straightforward, on any OS.

    Typical troll comment.

    There are existance proofs counter to your
    unsupported blanket statement.

    Burroughs medium systems for example, where using overlays was built
    into the compilation tools (including the COBOL compiler) and the
    operating system. Even the operating system used overlays for
    rarely used functionality.

    OS/360 and applications made extensive use of overlays.

    I remember a (PC)-Dos application called "Enable" that overlayed like crazy.

    Univac's OS/3 (sort of a 360/370 workalike) had several utilities
    that had as many as 45 overlays. This, combined with other
    memory-squeezing tricks like "transients" (routines that rolled
    in and out of special areas in memory) meant that the system drive
    was typically thrashing furiously.

    Burroughs MCP/VS 1.0 (formerly MCP, MCPV, MCPIX) supported
    overlays in applications[*]. Since the MCP was involved
    in loading the overlay from storage, we were able to
    leverage the larger memory in the later generations
    of the original B3500 architecture to create a 'quickmem'
    region in the physical memory that would cache overlays -
    avoiding thrashing. MCP supported multivolume disk
    subsystems (up to 6 IIRC) and overlay storage
    could be isolated to a set of volumes across multiple
    spindles for performance. In the 70's and 80's,
    one of the disk subsystems could be assigned to very
    expensive solid state disk subsystems (mainly third-party)
    that had large amounts of RAM. The I/O subsystem
    transferred at 8MBytes/sec per I/O controller, up to
    two I/O controllers were supported.

    [*] Automatically generated by the compilers, which supported
    hints in the syntax to group functions into one or more
    overlays. COBOL was the primary user language. Important
    because the code region maxed out at 150,000 bytes[**] (total program
    size maxed out at 500,000 bytes, so there could be up to
    350,000 bytes of data).

    MCP/VS 2.0 plus updated HW firmware/uCode provided a new highly
    segmented hardware memory architecture which supported
    100,000 full 500,000 byte code regions per application, so
    overlays went the way of the dodo.

    Just in time for the architecture to not survive the acquisition
    of Sperry.

    [**] Extended addressing in the B4700 extended maximum code + data
    size to 500,000 bytes and code could be located anywhere in
    the one megadigit region.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,alt.folklore.computers on Tue Sep 2 22:44:01 2025
    From Newsgroup: comp.os.linux.misc

    On Tue, 02 Sep 2025 21:22:36 GMT, Charlie Gibbs wrote:

    On 2025-08-30, candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:

    Lawrence D’Oliveiro <ldo@nz.invalid> wrote at 03:27 this Saturday (GMT): >>
    On Fri, 29 Aug 2025 23:51:18 GMT, Charlie Gibbs wrote:

    But there definitely was a period before that where the button vanished >>>> (although there would have been motherboard pins if you wanted to dig
    into it).

    Apple included a little springy clip thing (the “Programmers’s Switch”) in
    the box with each of those original classic-form-factor Macintoshes. When >>> installed, pressing one side triggered NMI (used for invoking the resident >>> debugger), while the other side triggered the RESET line (hard reboot).

    That's pretty cool, I always wished there was a physical switch to
    trigger a debugger since the system might be frozen...

    And that, ladies and gentlemen, is why you want a reset button
    rather than having to resort to the power switch.

    Interrupt button, surely.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Johnny Billquist@bqt@softjar.se to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 01:22:44 2025
    From Newsgroup: comp.os.linux.misc

    On 2025-09-02 23:22, Charlie Gibbs wrote:
    On 2025-08-30, candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:

    Lawrence D’Oliveiro <ldo@nz.invalid> wrote at 03:27 this Saturday (GMT): >>
    On Fri, 29 Aug 2025 23:51:18 GMT, Charlie Gibbs wrote:

    But there definitely was a period before that where the button vanished >>>> (although there would have been motherboard pins if you wanted to dig
    into it).

    Apple included a little springy clip thing (the “Programmers’s Switch”) in
    the box with each of those original classic-form-factor Macintoshes. When >>> installed, pressing one side triggered NMI (used for invoking the resident >>> debugger), while the other side triggered the RESET line (hard reboot).

    I still have the muscle memory: seated in front of the machine, reach
    around with right hand, far side was NMI, near side was RESET.

    That's pretty cool, I always wished there was a physical switch to
    trigger a debugger since the system might be frozen...

    And that, ladies and gentlemen, is why you want a reset button
    rather than having to resort to the power switch.

    Nah. That's the reason you want a front panel so you can halt the
    processor and change the PC to the debugger or crash dump function.
    Because interrupt vectors, including NMI, would normally be in RAM, and
    could be changed to something else than your debugger or whatever.
    (We are in a.f.c after all.)

    Johnny

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,alt.folklore.computers on Tue Sep 2 23:55:27 2025
    From Newsgroup: comp.os.linux.misc

    On 2025-09-02, Lawrence D’Oliveiro <ldo@nz.invalid> wrote:

    On Tue, 02 Sep 2025 21:22:36 GMT, Charlie Gibbs wrote:

    On 2025-08-30, candycanearter07
    <candycanearter07@candycanearter07.nomail.afraid> wrote:

    Lawrence D’Oliveiro <ldo@nz.invalid> wrote at 03:27 this Saturday (GMT): >>>
    On Fri, 29 Aug 2025 23:51:18 GMT, Charlie Gibbs wrote:

    But there definitely was a period before that where the button vanished >>>>> (although there would have been motherboard pins if you wanted to dig >>>>> into it).

    Apple included a little springy clip thing (the “Programmers’s Switch”) in
    the box with each of those original classic-form-factor Macintoshes. When >>>> installed, pressing one side triggered NMI (used for invoking the resident
    debugger), while the other side triggered the RESET line (hard reboot). >>>
    That's pretty cool, I always wished there was a physical switch to
    trigger a debugger since the system might be frozen...

    And that, ladies and gentlemen, is why you want a reset button
    rather than having to resort to the power switch.

    Interrupt button, surely.

    Maybe we need a series of buttons in a row, e.g. NMI, reset, power...

    And don't call me Shirley.
    --
    /~\ Charlie Gibbs | Growth for the sake of
    \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology
    X I'm really at ac.dekanfrus | of the cancer cell.
    / \ if you read it the right way. | -- Edward Abbey
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 01:13:21 2025
    From Newsgroup: comp.os.linux.misc

    In alt.folklore.computers Johnny Billquist <bqt@softjar.se> wrote:
    On 2025-09-02 23:22, Charlie Gibbs wrote:
    On 2025-08-30, candycanearter07
    <candycanearter07@candycanearter07.nomail.afraid> wrote:

    Lawrence D’Oliveiro <ldo@nz.invalid> wrote at 03:27 this Saturday (GMT): >>>
    On Fri, 29 Aug 2025 23:51:18 GMT, Charlie Gibbs wrote:

    But there definitely was a period before that where the button vanished >>>>> (although there would have been motherboard pins if you wanted to dig >>>>> into it).

    Apple included a little springy clip thing (the “Programmers’s Switch”) in
    the box with each of those original classic-form-factor Macintoshes. When >>>> installed, pressing one side triggered NMI (used for invoking the resident >>>> debugger), while the other side triggered the RESET line (hard reboot). >>>>
    I still have the muscle memory: seated in front of the machine, reach
    around with right hand, far side was NMI, near side was RESET.

    That's pretty cool, I always wished there was a physical switch to
    trigger a debugger since the system might be frozen...

    And that, ladies and gentlemen, is why you want a reset button
    rather than having to resort to the power switch.

    Nah. That's the reason you want a front panel so you can halt the
    processor and change the PC to the debugger or crash dump function.
    Because interrupt vectors, including NMI, would normally be in RAM, and could be changed to something else than your debugger or whatever.
    (We are in a.f.c after all.)

    There were nice debugging modules form 8-bit micros. IIUC better
    ones would initiate an interrupt and substitute ROM instead of RAM.
    So for CPU-s with fixed location of interrupt vectors CPU would
    fetch address (or code) from ROM and in effect transfer control
    to ROM. Code from ROM would do whatever was needed to get data
    from RAM. I never used one myself, so can not say more.

    There were also "developement systems", with comparator on address
    bus, so that one cold transfer control to debugger when code
    (or data) were fetched from chosen address. Debug registers in
    modern processors make external hardware like this redundant (and
    since important data stays inside the chip such external hardware
    would be impossible to build).
    --
    Waldek Hebisch
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 03:10:44 2025
    From Newsgroup: comp.os.linux.misc

    On Tue, 02 Sep 2025 21:22:35 GMT, Charlie Gibbs wrote:

    On 2025-08-30, rbowman <bowman@montana.com> wrote:

    On Sat, 30 Aug 2025 03:06:11 -0400, c186282 wrote:

    Tbe original 8088 had all the needed registers.
    Could minimum deliver at LEAST an easy 64k code space and at LEAST
    another 64k data area. A few tricks and .......

    They mostly followed the bank switching the Z80s were doing but
    incorporated the memory management into the processor. After all, the
    i432 was the REAL answer so why get fancy with the Band-Aid.

    "It's a good thing the iAPX432 never took off. Otherwise a totally
    horrid Intel architecture might have taken over the world."

    There truly are worse things than the x86. I think one of the 432
    designers had a computer science degree. That's the kiss of death :)

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 11:10:55 2025
    From Newsgroup: comp.os.linux.misc

    In alt.folklore.computers The Natural Philosopher <tnp@invalid.invalid> wrote:
    On 28/08/2025 12:02, Carlos E.R. wrote:

    Could MS-DOS (or CP/M) really make use of DMA?? Particularly since it
    couldn’t even do multitasking or interrupt-driven I/O, so the OS driver >> would just sit there spinning its wheels until the I/O completed anyway.

    Yes, MsDOS could.

    I know for certain because I used (in the 90's) an analog data
    acquisition card which came with routines for direct poll, interrupt driven, or dma driven. I still have the documentation.

    However, it worked, IIRC, at the same frequency than the original IBM
    PC. I have forgotten the exact explanation, but perhaps I have it
    written somewhere. Probably related to the clock frequency of the bus on the ISA cards.

    Floppy disk drive used DMA

    That was more for latency purposes. The floppy controller had a very small FIFO, so when data arrived from the disc you had to do *something* with it
    in short order otherwise the byte coming next would have to be dropped.
    DMA was the solution - you didn't need the CPU to do anything, you could
    just stash it in RAM via DMA.

    That was important when you had a ~500Kbps data stream from the FDC and only
    a 4.77MHz CPU. But there was only so much memory bandwidth to go around and
    at that point the floppy was taking a big chunk, so not a lot of progress
    would be made on the CPU while DMA was busy hammering the memory.

    Since the IBM PC had a DMA controller on the motherboard for that reason
    (and also DRAM refresh), it was then reasonably easy to make ISA cards that streamed data via DMA - you could just put your data on the data bus and generate basic DMARQ / DMACK cycles to store it to RAM, without having to
    worry about generating addresses since the 8237 did that for you.

    Theo
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 10:40:39 2025
    From Newsgroup: comp.os.linux.misc

    In article <20250902144505.00006bd9@gmail.com>,
    John Ames <commodorejohn@gmail.com> wrote:
    On Tue, 02 Sep 2025 21:22:39 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    It was typical to low-ball memory requirements to get a sale, then
    sell the customer more memory afterwards when the system turned out
    to be painfully slow and it was too late to back out.

    ...whereas nowadays, we have to recommend our customers spec out twice
    the memory they'd actually need as between Win10/11, the nine million
    browser tabs everyone keeps open at all times, vendor bloatware, and
    special gold-medal memory hogs like QuickBooks, an entry-level system
    is full to bursting and swapping madly before they even load *our* >application...

    ...and half the damn time they buy the entry-level system anyway, and
    then complain about *our* software being slow :/

    "What would YOU do with 128 GiB of RAM, Dan?"
    "Run two electron apps at the same time...."

    - Dan C.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 11:55:03 2025
    From Newsgroup: comp.os.linux.misc

    On 03/09/2025 11:10, Theo wrote:
    In alt.folklore.computers The Natural Philosopher <tnp@invalid.invalid> wrote:
    On 28/08/2025 12:02, Carlos E.R. wrote:

    Could MS-DOS (or CP/M) really make use of DMA?? Particularly since it
    couldn’t even do multitasking or interrupt-driven I/O, so the OS driver >>>> would just sit there spinning its wheels until the I/O completed anyway. >>>
    Yes, MsDOS could.

    I know for certain because I used (in the 90's) an analog data
    acquisition card which came with routines for direct poll, interrupt
    driven, or dma driven. I still have the documentation.

    However, it worked, IIRC, at the same frequency than the original IBM
    PC. I have forgotten the exact explanation, but perhaps I have it
    written somewhere. Probably related to the clock frequency of the bus on >>> the ISA cards.

    Floppy disk drive used DMA

    That was more for latency purposes. The floppy controller had a very small FIFO, so when data arrived from the disc you had to do *something* with it
    in short order otherwise the byte coming next would have to be dropped.
    DMA was the solution - you didn't need the CPU to do anything, you could
    just stash it in RAM via DMA.

    I merely noted that it used it. Not why.

    That was important when you had a ~500Kbps data stream from the FDC and only a 4.77MHz CPU. But there was only so much memory bandwidth to go around and at that point the floppy was taking a big chunk, so not a lot of progress would be made on the CPU while DMA was busy hammering the memory.

    Since the IBM PC had a DMA controller on the motherboard for that reason
    (and also DRAM refresh), it was then reasonably easy to make ISA cards that streamed data via DMA - you could just put your data on the data bus and generate basic DMARQ / DMACK cycles to store it to RAM, without having to worry about generating addresses since the 8237 did that for you.

    Theo
    --
    “There are two ways to be fooled. One is to believe what isn’t true; the other is to refuse to believe what is true.”

    —Soren Kierkegaard

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Alexander Schreiber@als@usenet.thangorodrim.de to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 14:31:10 2025
    From Newsgroup: comp.os.linux.misc

    Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    On 2025-09-02, Lawrence D’Oliveiro <ldo@nz.invalid> wrote:

    On Tue, 02 Sep 2025 21:22:36 GMT, Charlie Gibbs wrote:

    On 2025-08-30, candycanearter07
    <candycanearter07@candycanearter07.nomail.afraid> wrote:

    Lawrence D’Oliveiro <ldo@nz.invalid> wrote at 03:27 this Saturday (GMT): >>>>
    On Fri, 29 Aug 2025 23:51:18 GMT, Charlie Gibbs wrote:

    But there definitely was a period before that where the button vanished >>>>>> (although there would have been motherboard pins if you wanted to dig >>>>>> into it).

    Apple included a little springy clip thing (the “Programmers’s Switch”) in
    the box with each of those original classic-form-factor Macintoshes. When
    installed, pressing one side triggered NMI (used for invoking the resident
    debugger), while the other side triggered the RESET line (hard reboot). >>>>
    That's pretty cool, I always wished there was a physical switch to
    trigger a debugger since the system might be frozen...

    And that, ladies and gentlemen, is why you want a reset button
    rather than having to resort to the power switch.

    Interrupt button, surely.

    Maybe we need a series of buttons in a row, e.g. NMI, reset, power...

    .. halt-and-catch-fire, ...

    And don't call me Shirley.

    Shirley, you jest?

    SCNR,
    Alex.
    --
    "Opportunity is missed by most people because it is dressed in overalls and
    looks like work." -- Thomas A. Edison
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 14:53:53 2025
    From Newsgroup: comp.os.linux.misc

    In alt.folklore.computers Kerr-Mudd, John <admin@127.0.0.1> wrote:
    On Wed, 27 Aug 2025 16:40:27 +0200
    Alexander Schreiber <als@usenet.thangorodrim.de> wrote:

    []

    I haven't tried Unix on 8086, but DOS on x86 essentially relied on applications
    being reasonably correct and not too buggy. Having the reset button conveniently
    accessible was effectively a requirement for any DOS PC ;-)


    Unix on an early IBM PC (8086, 10M hard drive) would have been quite a shoehorning job. 'Slow' would probably be a generous word to use.

    That reminds me to check on how:
    https://github.com/ghaerr/elks

    is doing. Still seems to be alive and kicking, most recent release in
    October.

    Fits in 512KB of RAM on an 8086 and uses a single floppy.

    Of course it's Linux(ish) and not Unix.

    Theo
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 14:13:02 2025
    From Newsgroup: comp.os.linux.misc

    In alt.folklore.computers Theo <theom+news@chiark.greenend.org.uk> wrote:
    In alt.folklore.computers The Natural Philosopher <tnp@invalid.invalid> wrote:
    On 28/08/2025 12:02, Carlos E.R. wrote:

    Could MS-DOS (or CP/M) really make use of DMA?? Particularly since it
    couldn’t even do multitasking or interrupt-driven I/O, so the OS driver >> >> would just sit there spinning its wheels until the I/O completed anyway. >> >
    Yes, MsDOS could.

    I know for certain because I used (in the 90's) an analog data
    acquisition card which came with routines for direct poll, interrupt
    driven, or dma driven. I still have the documentation.

    However, it worked, IIRC, at the same frequency than the original IBM
    PC. I have forgotten the exact explanation, but perhaps I have it
    written somewhere. Probably related to the clock frequency of the bus on >> > the ISA cards.

    Floppy disk drive used DMA

    That was more for latency purposes. The floppy controller had a very small FIFO, so when data arrived from the disc you had to do *something* with it
    in short order otherwise the byte coming next would have to be dropped.
    DMA was the solution - you didn't need the CPU to do anything, you could
    just stash it in RAM via DMA.

    That was important when you had a ~500Kbps data stream from the FDC and only a 4.77MHz CPU. But there was only so much memory bandwidth to go around and at that point the floppy was taking a big chunk, so not a lot of progress would be made on the CPU while DMA was busy hammering the memory.

    Floppy was taking about 5% of memory bandwidth, plenty of cycles
    remaing to do CPU work. Even hard disc left enough cycles to do
    some useful CPU work. Not doing computation during floppy DMA
    transfer was just unwilingness to do more complex implementation.
    PC was no more constained than 360/30, where simultaneous I/O
    and computation was common.
    --
    Waldek Hebisch
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From John Ames@commodorejohn@gmail.com to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 07:59:08 2025
    From Newsgroup: comp.os.linux.misc

    On Wed, 3 Sep 2025 10:40:39 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) wrote:

    "What would YOU do with 128 GiB of RAM, Dan?"
    "Run two electron apps at the same time...."

    *Painfully* accurate :/

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 17:38:57 2025
    From Newsgroup: comp.os.linux.misc

    On Wed, 3 Sep 2025 07:59:08 -0700, John Ames wrote:

    On Wed, 3 Sep 2025 10:40:39 -0000 (UTC) cross@spitfire.i.gajendra.net
    (Dan Cross) wrote:

    "What would YOU do with 128 GiB of RAM, Dan?"
    "Run two electron apps at the same time...."

    *Painfully* accurate :/

    VS Code is an electron app and is not using excessive memory. Who is the
    prime offender? Pan at 11.4%.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 17:51:10 2025
    From Newsgroup: comp.os.linux.misc

    rbowman <bowman@montana.com> writes:
    On Wed, 3 Sep 2025 07:59:08 -0700, John Ames wrote:

    On Wed, 3 Sep 2025 10:40:39 -0000 (UTC) cross@spitfire.i.gajendra.net
    (Dan Cross) wrote:

    "What would YOU do with 128 GiB of RAM, Dan?"
    "Run two electron apps at the same time...."

    *Painfully* accurate :/

    VS Code is an electron app and is not using excessive memory. Who is the >prime offender? Pan at 11.4%.

    Pan may have a good UI, but the underlying implementation is poor. All
    header data is stored in simple, relatively unstructured, text files.

    The per-group header databases consume significant memory if all
    headers are preserved. Take rec.woodworking for example:

    $ wc -l .pan2/groups/rec.woodworking
    6044869 .pan2/groups/rec.woodworking
    $ stat .pan2/groups/rec.woodworking
    File: '.pan2/groups/rec.woodworking'
    Size: 266433271 Blocks: 520392 IO Block: 4096 regular file

    That's 256+ megabytes, 6 million lines of ASCII text. Just under ten
    lines per article, and that's a relatively small group.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Kerr-Mudd, John@admin@127.0.0.1 to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 20:43:51 2025
    From Newsgroup: comp.os.linux.misc

    On 03 Sep 2025 14:53:53 +0100 (BST)
    Theo <theom+news@chiark.greenend.org.uk> wrote:

    In alt.folklore.computers Kerr-Mudd, John <admin@127.0.0.1> wrote:
    On Wed, 27 Aug 2025 16:40:27 +0200
    Alexander Schreiber <als@usenet.thangorodrim.de> wrote:

    []

    I haven't tried Unix on 8086, but DOS on x86 essentially relied on applications
    being reasonably correct and not too buggy. Having the reset button conveniently
    accessible was effectively a requirement for any DOS PC ;-)


    Unix on an early IBM PC (8086, 10M hard drive) would have been quite a shoehorning job. 'Slow' would probably be a generous word to use.

    That reminds me to check on how:
    https://github.com/ghaerr/elks

    is doing. Still seems to be alive and kicking, most recent release in October.

    Fits in 512KB of RAM on an 8086 and uses a single floppy.

    Of course it's Linux(ish) and not Unix.

    Thanks, I had no idea.
    --
    Bah, and indeed Humbug.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 23:09:49 2025
    From Newsgroup: comp.os.linux.misc

    On 03 Sep 2025 11:10:55 +0100 (BST), Theo wrote:

    In alt.folklore.computers The Natural Philosopher <tnp@invalid.invalid> wrote:

    Floppy disk drive used DMA

    That was more for latency purposes. The floppy controller had a very
    small FIFO, so when data arrived from the disc you had to do *something*
    with it in short order otherwise the byte coming next would have to be dropped.
    DMA was the solution - you didn't need the CPU to do anything, you could
    just stash it in RAM via DMA.

    Apple managed it without DMA. And remember their floppies had higher
    capacity than IBM’s.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,alt.folklore.computers on Wed Sep 3 23:11:03 2025
    From Newsgroup: comp.os.linux.misc

    On Wed, 3 Sep 2025 14:13:02 -0000 (UTC), Waldek Hebisch wrote:

    PC was no more constained than 360/30, where simultaneous I/O and
    computation was common.

    Yes, but remember, IBM wouldn’t have wanted one of its product lines to cannibalize sales of another ... especially when there was several orders
    of magnitude difference in pricing involved.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Alexander Schreiber@als@usenet.thangorodrim.de to comp.os.linux.misc,alt.folklore.computers on Thu Sep 4 10:10:51 2025
    From Newsgroup: comp.os.linux.misc

    Waldek Hebisch <antispam@fricas.org> wrote:
    In alt.folklore.computers Theo <theom+news@chiark.greenend.org.uk> wrote:
    In alt.folklore.computers The Natural Philosopher <tnp@invalid.invalid> wrote:
    On 28/08/2025 12:02, Carlos E.R. wrote:

    Could MS-DOS (or CP/M) really make use of DMA?? Particularly since it >>> >> couldn’t even do multitasking or interrupt-driven I/O, so the OS driver
    would just sit there spinning its wheels until the I/O completed anyway. >>> >
    Yes, MsDOS could.

    I know for certain because I used (in the 90's) an analog data
    acquisition card which came with routines for direct poll, interrupt
    driven, or dma driven. I still have the documentation.

    However, it worked, IIRC, at the same frequency than the original IBM >>> > PC. I have forgotten the exact explanation, but perhaps I have it
    written somewhere. Probably related to the clock frequency of the bus on >>> > the ISA cards.

    Floppy disk drive used DMA

    That was more for latency purposes. The floppy controller had a very small >> FIFO, so when data arrived from the disc you had to do *something* with it >> in short order otherwise the byte coming next would have to be dropped.
    DMA was the solution - you didn't need the CPU to do anything, you could
    just stash it in RAM via DMA.

    That was important when you had a ~500Kbps data stream from the FDC and only >> a 4.77MHz CPU. But there was only so much memory bandwidth to go around and >> at that point the floppy was taking a big chunk, so not a lot of progress
    would be made on the CPU while DMA was busy hammering the memory.

    Floppy was taking about 5% of memory bandwidth, plenty of cycles
    remaing to do CPU work. Even hard disc left enough cycles to do
    some useful CPU work. Not doing computation during floppy DMA
    transfer was just unwilingness to do more complex implementation.
    PC was no more constained than 360/30, where simultaneous I/O
    and computation was common.

    But the PC was marketed by IBM as a machine for single users, where wasting cycles was fine as long as _some_ kind of apparently useful activity was
    done (including just displaying the spreadsheet while the user ruminates
    about it), whereas the Big Iron S/360 was marketed as the "company workhorse" with the associated price tag where obviously wasting cycles would have
    made the customer not happy.

    Different places in the market, very different prices and I assume very different profit margins - with IBM always being mindful of getting
    every nickel from the customer they could.

    Kind regards,
    Alex.
    --
    "Opportunity is missed by most people because it is dressed in overalls and
    looks like work." -- Thomas A. Edison
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Rich@rich@example.invalid to comp.os.linux.misc,alt.folklore.computers on Thu Sep 4 10:41:52 2025
    From Newsgroup: comp.os.linux.misc

    In comp.os.linux.misc Waldek Hebisch <antispam@fricas.org> wrote:
    In alt.folklore.computers Rich <rich@example.invalid> wrote:
    In comp.os.linux.misc c186282 <c186282@nnada.net> wrote:
    ... REAL power switch, like a 3-sec
    delay before anything happens.

    Only for ATX PSU based machines. The old AT PSU spec had the power
    switch as an actual switch that interrupted mains power.

    Granted, few remember AT PSU based systems anymore, and even fewer of
    them are still in service.

    Many PC have real power switch. There is software controlled one at
    the front and real one built into the power supply.

    That is the ATX PSU layout. And not all ATX PSU's bothered with the
    physical switch built into the PSU (dropping the switch reduced the BOM
    cost of the PSU).

    For the pre ATX PSU's (AT PSU's), the physical power switch that
    interrupted mains power was the switch that was mounted in the front of
    the case that user's used to turn on/off the machine.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From John Ames@commodorejohn@gmail.com to comp.os.linux.misc,alt.folklore.computers on Thu Sep 4 07:48:25 2025
    From Newsgroup: comp.os.linux.misc

    On Wed, 3 Sep 2025 23:09:49 -0000 (UTC)
    Lawrence D’Oliveiro <ldo@nz.invalid> wrote:
    Apple managed it without DMA. And remember their floppies had higher capacity than IBM’s.
    True, but it's much harder to do precise timing on an 8088 than a 6502;
    the combination of prefetch queue obscurity (which *is* calculable, in
    a sufficiently tight loop) and DRAM refresh (which isn't) yields a lot
    of uncertainty wrt. real-world execution times.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,alt.folklore.computers on Thu Sep 4 18:38:23 2025
    From Newsgroup: comp.os.linux.misc

    On 2025-09-04, Rich <rich@example.invalid> wrote:

    For the pre ATX PSU's (AT PSU's), the physical power switch that
    interrupted mains power was the switch that was mounted in the front of
    the case that user's used to turn on/off the machine.

    I saw some machines where the actual switch was in the power supply
    at the back of the machine, but it was activated via a long rod that
    ended in a button on the front panel.
    --
    /~\ Charlie Gibbs | Growth for the sake of
    \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology
    X I'm really at ac.dekanfrus | of the cancer cell.
    / \ if you read it the right way. | -- Edward Abbey
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,alt.folklore.computers on Thu Sep 4 18:42:25 2025
    From Newsgroup: comp.os.linux.misc

    On Thu, 04 Sep 2025 18:38:23 GMT, Charlie Gibbs wrote:

    On 2025-09-04, Rich <rich@example.invalid> wrote:

    For the pre ATX PSU's (AT PSU's), the physical power switch that
    interrupted mains power was the switch that was mounted in the front of
    the case that user's used to turn on/off the machine.

    I saw some machines where the actual switch was in the power supply at
    the back of the machine, but it was activated via a long rod that ended
    in a button on the front panel.

    All I know is at some point the power button on front of the box would
    turn the machine on. Pushing it again was a mild suggestion that the
    machine shut down if it felt like it. The cord was usually easier to find
    when groping around than the toggle on the PS.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,alt.folklore.computers on Thu Sep 4 20:51:44 2025
    From Newsgroup: comp.os.linux.misc

    On Thu, 4 Sep 2025 07:48:25 -0700, John Ames wrote:

    On Wed, 3 Sep 2025 23:09:49 -0000 (UTC)
    Lawrence D’Oliveiro <ldo@nz.invalid> wrote:

    Apple managed it without DMA. And remember their floppies had higher
    capacity than IBM’s.

    True, but it's much harder to do precise timing on an 8088 than a 6502;
    the combination of prefetch queue obscurity (which *is* calculable, in a sufficiently tight loop) and DRAM refresh (which isn't) yields a lot of uncertainty wrt. real-world execution times.

    Apple also managed it on the 68000-based Macintosh.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,alt.folklore.computers on Thu Sep 4 20:58:03 2025
    From Newsgroup: comp.os.linux.misc

    rbowman <bowman@montana.com> writes:
    On Thu, 04 Sep 2025 18:38:23 GMT, Charlie Gibbs wrote:

    On 2025-09-04, Rich <rich@example.invalid> wrote:

    For the pre ATX PSU's (AT PSU's), the physical power switch that
    interrupted mains power was the switch that was mounted in the front of
    the case that user's used to turn on/off the machine.

    I saw some machines where the actual switch was in the power supply at
    the back of the machine, but it was activated via a long rod that ended
    in a button on the front panel.

    All I know is at some point the power button on front of the box would
    turn the machine on. Pushing it again was a mild suggestion that the
    machine shut down if it felt like it. The cord was usually easier to find >when groping around than the toggle on the PS.

    The firmware has managed the power switch for the last couple of
    decades. The OS can arrange with the SMM firmware (through ACPI) to
    manage the power button to ensure that on-disk state remains
    consistent by shutting down the applications and operating systems
    cleanly.

    Works pretty well with Linux. Some windows applications have not,
    in the past, played well with soft power switches, and some
    BIOS implementations have been sub-par, to put it kindly.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Kerr-Mudd, John@admin@127.0.0.1 to comp.os.linux.misc,alt.folklore.computers on Thu Sep 4 22:22:31 2025
    From Newsgroup: comp.os.linux.misc

    On Thu, 04 Sep 2025 18:38:23 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    On 2025-09-04, Rich <rich@example.invalid> wrote:

    For the pre ATX PSU's (AT PSU's), the physical power switch that interrupted mains power was the switch that was mounted in the front of the case that user's used to turn on/off the machine.

    I saw some machines where the actual switch was in the power supply
    at the back of the machine, but it was activated via a long rod that
    ended in a button on the front panel.


    PS2 ?


    https://en.wikipedia.org/wiki/IBM_PS/2_Model_30#/media/File:IBM_PS-2_Model_30_286_open_top.jpg
    --
    Bah, and indeed Humbug.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,alt.folklore.computers on Thu Sep 4 22:35:11 2025
    From Newsgroup: comp.os.linux.misc

    On 2025-09-04, Kerr-Mudd, John <admin@127.0.0.1> wrote:

    On Thu, 04 Sep 2025 18:38:23 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    On 2025-09-04, Rich <rich@example.invalid> wrote:

    For the pre ATX PSU's (AT PSU's), the physical power switch that
    interrupted mains power was the switch that was mounted in the front of >>> the case that user's used to turn on/off the machine.

    I saw some machines where the actual switch was in the power supply
    at the back of the machine, but it was activated via a long rod that
    ended in a button on the front panel.

    PS2 ?

    https://en.wikipedia.org/wiki/IBM_PS/2_Model_30#/media/File:IBM_PS-2_Model_30_286_open_top.jpg

    Not quite, although that one is interesting. But rather than
    a toggle switch, the machine I'm thinking of had a pushbutton.
    And rather than a wire that pushed or pulled the toggle switch,
    there was a plastic rod (molded in such a way that it wouldn't
    flex) that relayed a push on the front-panel button to the
    pushbutton on the power supply.
    --
    /~\ Charlie Gibbs | Growth for the sake of
    \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology
    X I'm really at ac.dekanfrus | of the cancer cell.
    / \ if you read it the right way. | -- Edward Abbey
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,alt.folklore.computers on Fri Sep 5 05:06:44 2025
    From Newsgroup: comp.os.linux.misc

    On 9/4/25 5:22 PM, Kerr-Mudd, John wrote:
    On Thu, 04 Sep 2025 18:38:23 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    On 2025-09-04, Rich <rich@example.invalid> wrote:

    For the pre ATX PSU's (AT PSU's), the physical power switch that
    interrupted mains power was the switch that was mounted in the front of
    the case that user's used to turn on/off the machine.

    I saw some machines where the actual switch was in the power supply
    at the back of the machine, but it was activated via a long rod that
    ended in a button on the front panel.


    PS2 ?


    https://en.wikipedia.org/wiki/IBM_PS/2_Model_30#/media/File:IBM_PS-2_Model_30_286_open_top.jpg

    USUALLY you can just hold the power button down
    for about five seconds. FAIR shutdown.

    Have to do it often with this unit ... SOMETHING hangs
    these days, can't find it. Logs reveal little, much
    less REASONS.


    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,alt.folklore.computers on Fri Sep 5 05:08:43 2025
    From Newsgroup: comp.os.linux.misc

    On 9/4/25 4:58 PM, Scott Lurndal wrote:
    rbowman <bowman@montana.com> writes:
    On Thu, 04 Sep 2025 18:38:23 GMT, Charlie Gibbs wrote:

    On 2025-09-04, Rich <rich@example.invalid> wrote:

    For the pre ATX PSU's (AT PSU's), the physical power switch that
    interrupted mains power was the switch that was mounted in the front of >>>> the case that user's used to turn on/off the machine.

    I saw some machines where the actual switch was in the power supply at
    the back of the machine, but it was activated via a long rod that ended
    in a button on the front panel.

    All I know is at some point the power button on front of the box would
    turn the machine on. Pushing it again was a mild suggestion that the
    machine shut down if it felt like it. The cord was usually easier to find
    when groping around than the toggle on the PS.

    The firmware has managed the power switch for the last couple of
    decades. The OS can arrange with the SMM firmware (through ACPI) to
    manage the power button to ensure that on-disk state remains
    consistent by shutting down the applications and operating systems
    cleanly.

    Works pretty well with Linux. Some windows applications have not,
    in the past, played well with soft power switches, and some
    BIOS implementations have been sub-par, to put it kindly.

    To put it kindly .........

    -IX has become better at dealing with soft-shutdown
    than Win.


    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.os.linux.misc,alt.folklore.computers on Fri Sep 5 12:02:56 2025
    From Newsgroup: comp.os.linux.misc

    In alt.folklore.computers Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    On 2025-09-04, Rich <rich@example.invalid> wrote:

    For the pre ATX PSU's (AT PSU's), the physical power switch that
    interrupted mains power was the switch that was mounted in the front of
    the case that user's used to turn on/off the machine.

    I saw some machines where the actual switch was in the power supply
    at the back of the machine, but it was activated via a long rod that
    ended in a button on the front panel.

    I still have Olivetti PC enclosure (but nothing beside power supply
    inside) that uses this method.
    --
    Waldek Hebisch
    --- Synchronet 3.21a-Linux NewsLink 1.2