Could have just researched what character was being inserted by the ctrl backspace and then used the keyboard to insert the character from its ascii or unicode code to login and then changed your password before nuking your computer
But with what computer?!
Your phone maybe?
Oh, you're young
Oh yeah I forgot that your problem was on an old version of windows.
Your what? Like those things with the dial that are attached to the wall? How are you meant to do it with that?
Easy. You whistle in binary and say modem noises. The operator will patch you through to the internet.
I'm in.
I genuinely can't tell if you and the person you responded to are doing a bit and committing to it, or are genuinely referring to:
Making weird modem noises to hack phones will always be the funniest 90's hacker thing I've ever heard.
Hey, it worked, okay lol? And we were in the 70’s.
I was a 90's kid. Making weird noises in the phone was magic to me.
I know a lot of people get weird about it, but the Anarchist's Cookbook had TONS of info on phreaking and exploiting telephone systems. It wasn't just about how to make napalm and tennis ball bombs (but that shit was hella fun, too).
Ohhhh so like Terminator 3
I'm sure this version of windows was before phones had screens attached, and likely before the internet was ubiquitous. They likely had one computer and would have had to go somewhere else to look it up if that was even an option.
And a time when if you had a phone capable of theinternet it would probably cost 5€ per minute.
Yup, I tried doing the keystrokes I found online that promised to put the ASCII character in, but it wasn't working for me and gave up eventually.
Or just cleared the SAM password altogether. Windows is trivially easy to break into if you have physical access and the volume isn't encrypted.
My go-to solution is to simply replace some kind of accessibility feature executable, such as onscreen keyboard, with cmd.exe. It runs under SYSTEM.
Does SYSTEM have enough permission to write to the SAM file?
I actually did do that! I found the ASCII code but couldn't get it inputted correctly to the password. The nuking came after I gave up and decided it wasn't worth it. What's life without restarting every now and then?
Could have just researched what character was being inserted by the ctrl backspace and then used the keyboard to insert the character from its ascii or unicode code to login and then changed your password before nuking your computer
But with what computer?!
Your phone maybe?
Oh, you're young
Oh yeah I forgot that your problem was on an old version of windows.
Your what? Like those things with the dial that are attached to the wall? How are you meant to do it with that?
Easy. You whistle in binary and say modem noises. The operator will patch you through to the internet.
I'm in.
I genuinely can't tell if you and the person you responded to are doing a bit and committing to it, or are genuinely referring to:
Phreakers
Making weird modem noises to hack phones will always be the funniest 90's hacker thing I've ever heard.
Hey, it worked, okay lol? And we were in the 70’s.
I was a 90's kid. Making weird noises in the phone was magic to me.
I know a lot of people get weird about it, but the Anarchist's Cookbook had TONS of info on phreaking and exploiting telephone systems. It wasn't just about how to make napalm and tennis ball bombs (but that shit was hella fun, too).
Ohhhh so like Terminator 3
I'm sure this version of windows was before phones had screens attached, and likely before the internet was ubiquitous. They likely had one computer and would have had to go somewhere else to look it up if that was even an option.
And a time when if you had a phone capable of the internet it would probably cost 5€ per minute.
It looks like it was the ASCII char 127 (delete char). https://superuser.com/questions/33142/ctrlbackspace-inserts-a-small-box-instead-of-erasing
Yup, I tried doing the keystrokes I found online that promised to put the ASCII character in, but it wasn't working for me and gave up eventually.
Or just cleared the SAM password altogether. Windows is trivially easy to break into if you have physical access and the volume isn't encrypted.
My go-to solution is to simply replace some kind of accessibility feature executable, such as onscreen keyboard, with cmd.exe. It runs under SYSTEM.
Does SYSTEM have enough permission to write to the SAM file?
I actually did do that! I found the ASCII code but couldn't get it inputted correctly to the password. The nuking came after I gave up and decided it wasn't worth it. What's life without restarting every now and then?