Dacta Control Lab Software

[evank]

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?

[AJB2K3]

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.

 

[maehw]

Hacker voice: "I'm in."

(I got a response from my Interface B via serial.)

[Toastie]

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 Thursday at 09:54 PM by Toastie

[AJB2K3]

8 hours ago, maehw said:

Hacker voice: "I'm in."

(I got a response from my Interface B via serial.)

Nice work.

[evank]

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.

[Toastie]

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

[evank]

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.

[Toastie]

2 hours ago, evank said:

I could swear I saw it in an A manual once

The RCX needed that string as well, as far as I remember, without the ### and $$$ ...

Best
Thorsten   

[maehw]

4 hours ago, Toastie said:

The RCX needed that string as well, as far as I remember, without the ### and $$$ ...

Best
Thorsten   

You're right. 

It's in the ROM code. 

Seems to be used for checking the firmware image – which resides in RAM after having been successfully transferred via the infrared serial interface.

So it also needs to be contained in every firmware image as this check is executed during the "unlock firmware" command.  

[Toastie]

1 hour ago, maehw said:

So it also needs to be contained in every firmware image as this check is executed during the "unlock firmware" command.

Yes, that was it. Back in my days, using QBASIC (I am still using and will "never" stop using it, owing to DOSBox-X), that was the way to get "in". With NQC and foremost BricxCC, things got relatively "easy" ;)

When folks want to go from scratch today, well, then use the "from scratch" information, which is all out there. AI so far does know that much about it, it will learn though, of course.

All the best
Thorsten