Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?

#1

Post by segfaultbuserr » Thu, Sep 28, 2023, 3:45 AM UTC

Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?
retrocomputing.stackexchange.com

Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?

#2

Post by threeio » Thu, Sep 28, 2023, 4:29 AM UTC

Is it bad that I knew that one without opening it? ... never mind I'll be over yelling at these young kids to get off my lawn :)

Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?

#3

Post by [deleted] » Thu, Sep 28, 2023, 5:07 AM UTC

threeio wrote: post #2

Is it bad that I knew that one without opening it? ... never mind I'll be over yelling at these young kids to get off my lawn :)

[deleted]

Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?

#4

Post by CodeWriter23 » Thu, Sep 28, 2023, 5:08 AM UTC

threeio wrote: post #2

Is it bad that I knew that one without opening it? ... never mind I'll be over yelling at these young kids to get off my lawn :)

Troubleshooting was different when we came up. Just your wits and maybe some gurus you could call on a landline as backup. No fancy internet with tons of answers of varying degrees of usefulness.

Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?

#5

Post by tzahifadida » Thu, Sep 28, 2023, 5:08 AM UTC

I build a port check way back to determine if services are up. It crashed half the company by simply opening a few tcp ports to the machines. Ridiculous days :)

Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?

#6

Post by b800h » Thu, Sep 28, 2023, 5:20 AM UTC

This is proper programming. None of this namby-pamby web scripting that passes for development these days.

Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?

#7

Post by smokel » Thu, Sep 28, 2023, 5:22 AM UTC

CodeWriter23 wrote: post #4

threeio wrote: post #2

Is it bad that I knew that one without opening it? ... never mind I'll be over yelling at these young kids to get off my lawn :)

Troubleshooting was different when we came up. Just your wits and maybe some gurus you could call on a landline as backup. No fancy internet with tons of answers of varying degrees of usefulness.

You might have forgotten them, but there were also books printed on paper.

Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?

#8

Post by fulafel » Thu, Sep 28, 2023, 5:38 AM UTC

"The fix is obvious" indeed.

Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?

#9

Post by theGeatZhopa » Thu, Sep 28, 2023, 5:45 AM UTC

smokel wrote: post #7

CodeWriter23 wrote: post #4

Earlier quoted context omitted.

Troubleshooting was different when we came up. Just your wits and maybe some gurus you could call on a landline as backup. No fancy internet with tons of answers of varying degrees of usefulness.

You might have forgotten them, but there were also books printed on paper.

H4x0r doesn't need book. H4x0r try 4nd err0r.

Books were just knowledge. Debugging was skill. At certain point in knowledge-gain, you develop a good skill and after that point, you don't need books anymore. Maybe from time to time. I still have a suse6 printed manual.. I can't see it in the cellar, but It've been HUUGE

Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?

#10

Post by deely3 » Thu, Sep 28, 2023, 5:47 AM UTC

tzahifadida wrote: post #5

I build a port check way back to determine if services are up. It crashed half the company by simply opening a few tcp ports to the machines. Ridiculous days :)

Whoa, thats prettt funny.