On 11/1/24 13:33, Johan Helsingius via cctalk wrote:
> UNIX might have been unobtainium in your home, but a lot of BBS's
> used UUCP to get email and USENET connectivity, and a huge amount
> of students had modem access to an UNIX computer at their university.
Back in the day, I used a package cal
And before that, TENEX/TOPS-20 on the DECSYSTEM-20. But that's slightly
before my time. (By the time I entered the CMU Ph.D. program, very few
DECSYSTEMs were left, being replaced by 11/780s and then a plethora of
microvaxen. Running VMS, but also BSD 4.1 with lots of 4.2 patches.)
VMS certainly w
For a few year VMS was the OS of the "internet". I remember wondering in
1991 or 1992 if UNIX would still be around by 2000
On Fri, Nov 1, 2024, 4:42 PM Johan Helsingius via cctalk <
cctalk@classiccmp.org> wrote:
> UNIX might have been unobtainium in your home, but a lot of BBS's
> used UUCP to
The IBM monochrome monitor could be damaged by putting it into an
unsupported mode.
The idea of a command that would brick the system is popular.
It may be possible, but it's very difficult to track down the details from
FOAFs.
--
Grumpy Ol' Fred ci...@xenosoft.com
There was a "Killer Poke" on the commodore PET that would alter the video
horizontal output frequency, which had the effect of physically damaging
the video hardware as the high voltage was generated by the flyback
transformer.l and there was no regulation.
It's mere existence made my father paran
Nope. If you believe this mythical instruction exists, you are the
person that gets to spend the time digging up the references to it.
I've been writing assembly on the 6502 since the early 1980s and I have
never managed to damage one when my programs went off the rails, which
they did on many
> I had remembered the HCF as being a z-80 thing, so I searched for it.
>
> All I can find says it was 6800, not 6502.
The NMOS 6502 has a number of undocumented lock-up opcodes. However, they arise
as a consequence of its instruction decoder PLA and weren't intended for
testing like the 6800 H
On Fri, Nov 01, 2024 at 09:33:31PM +0100, Johan Helsingius via cctalk wrote:
> UNIX might have been unobtainium in your home, but a lot of BBS's
> used UUCP to get email and USENET connectivity, and a huge amount
> of students had modem access to an UNIX computer at their university.
Sure. I ran a
UNIX might have been unobtainium in your home, but a lot of BBS's
used UUCP to get email and USENET connectivity, and a huge amount
of students had modem access to an UNIX computer at their university.
Julf
On 10/24/24 04:36, Doug Jackson via cctalk wrote:
Yes, UUCP was literally a thi
On 11/1/24 14:55, CAREY SCHUG via cctalk wrote:
Wikipedia lists models 60, 62, 64, and 66 (never shipped)
and 65 and 67 as shipped, but no 63.
since I don't remember 65s, I assume not many of them made it out the door?
Uh, no. The 360/65 was a very popular model, QUITE (4X) a
step up from the
Wikipedia lists models 60, 62, 64, and 66 (never shipped)
and 65 and 67 as shipped, but no 63.
since I don't remember 65s, I assume not many of them made it out the door?
https://en.wikipedia.org/wiki/IBM_System/360
--Carey
> On 11/01/2024 1:12 PM CDT Van Snyder via cctalk wrote:
>
>
> On
I had remembered the HCF as being a z-80 thing, so I searched for it.
All I can find says it was 6800, not 6502.
https://en.wikipedia.org/wiki/Halt_and_Catch_Fire_(computing)
http://www.ffd2.com/fridge/docs/6502-NMOS.extra.opcodes
http://www.z80.info/zip/z80-documented.pdf
New question: what do
On Fri, 2024-11-01 at 11:01 -0700, David Barto via cctalk wrote:
> > > The 6502 had a HCF (halt and catch fire) undocumented
> > > instruction.
> > > I forget the opcode and if you knew what you were doing you could
> > > get the instruction executed on the chip using any assembler.
Early in 196
Nope. Read the documentation for the chip. Turns out that the HCF instruction
basically sent the chip into an internal loop which would render parts of it
unusable after about 30-45 seconds.
Tried it once and the chip got hot. Very very hot and then just stopped working.
David
> On Nov
David Barto wrote:
>
> The 6502 had a HCF (halt and catch fire) undocumented instruction.
> I forget the opcode and if you knew what you were doing you could get the
> instruction executed on the chip using any assembler.
>
> Security through obscurity back in the 70s.
> The chip was advanced
Well, I learned that not all drives that look like ST-506, are... Turns out
the drive I was going to use is a Micropolis 1355, which is an ESDI drive.
So it won't work with the RQDX3.
I guess that drive goes back on the shelf until something else comes along.
Thanks for all the info on the formatt
Glad I never tried it. 😊
The 6502 had a HCF (halt and catch fire) undocumented instruction.
I forget the opcode and if you knew what you were doing you could get the
instruction executed on the chip using any assembler.
Security through obscurity back in the 70s.
The chip was advanced enough that the DOD wanted to avo
18 matches
Mail list logo
