evank Posted 20 hours ago Posted 20 hours ago 9 hours ago, AJB2K3 said: When you put faith in AI, always be disappointed. Now I know the core foundations I have to start from scratch because Gemini keeps hitting what I call the Admiral Ackbar crash What does this have to do with the discussion topic? Quote
AJB2K3 Posted 19 hours ago Posted 19 hours ago 42 minutes ago, evank said: What does this have to do with the discussion topic? I used AI to create the ULI blockly front end for my Interface B code but it got to a stage where the AI kept getting confused blocking the port and causing the "Its A Trap" error when running the code which instantly crashes code and programs. Quote
maehw Posted 17 hours ago Posted 17 hours ago Hacker voice: "I'm in." (I got a response from my Interface B via serial.) Quote
Toastie Posted 16 hours ago Posted 16 hours ago (edited) 23 minutes ago, maehw said: Hacker voice: "I'm in." Heehee, oh yes. Just read these 31 bytes, and the byte bombarding begins ... Here it is, in QBASIC PRINT #1, "p" + CHR$(0) + "###Do you byte, when I knock?$$$"; 'Programm stalls here, when USB2Ser adapter was unplugged during run 'time and then plugged back in; CTRL NumLock = break into program. R$ = INPUT$(31, #1) '"###Just a bit off the block!$$$"=31 byte 'If it is 31 byte, just throw it away; if not throw an error. Fun time. Best Thorsten Edited 16 hours ago by Toastie Quote
AJB2K3 Posted 8 hours ago Posted 8 hours ago 8 hours ago, maehw said: Hacker voice: "I'm in." (I got a response from my Interface B via serial.) Nice work. Quote
evank Posted 1 hour ago Posted 1 hour ago 15 hours ago, Toastie said: Heehee, oh yes. Just read these 31 bytes, and the byte bombarding begins ... Here it is, in QBASIC PRINT #1, "p" + CHR$(0) + "###Do you byte, when I knock?$$$"; 'Programm stalls here, when USB2Ser adapter was unplugged during run 'time and then plugged back in; CTRL NumLock = break into program. R$ = INPUT$(31, #1) '"###Just a bit off the block!$$$"=31 byte 'If it is 31 byte, just throw it away; if not throw an error. Fun time. Best Thorsten I always LOL'd at that communication string, but what baffles me is why it's mentioned in an Interface A manual! I can't recall which one right now. Quote
Toastie Posted 48 minutes ago Posted 48 minutes ago 6 minutes ago, evank said: but what baffles me is why it's mentioned in an Interface A manual! I guess it isn't? This is only relevant for getting "access" to Interface B = starting its serial data spit-out frenzy, isn't it? You even need the 5 chars in front of the "phrase", I forgot how many of these chars it actually reads, maybe all. Interface A requires no initialization at all, just the I/O chips in the computer driving it may need port direction initialization. Best Thorsten Quote
evank Posted 40 minutes ago Posted 40 minutes ago I could swear I saw it in an A manual once, which made no sense at all. I don't have time to go look right now. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.