All USB interrupts are disabled at the moment.  As for the ModelID, I can look into fixing that.

Glad it works! All i have is an 84+

For the record, this part of the code doesn't make sense:

Code: [Select]

ld a, (ModelID)
cp 2 ; Models 2 and up have USB.
jp c, ResumeInterrupt ; Leave if we don't have the hardware (also tested with NC)
This code doesn't make sense in my brain. Say the ModelID is 4. cp 2 would set the carry flag, right? So jp c would jump back for all the models with USB and try and run on those without it.

For that protocol interrupt, if it wants to send you some data over the control pipe, it might not like you ignoring it.  For now, I think you might be able to just stall the ports and that will prevent it from connecting at all, but it should keep the driver working.

No, 4 minus 2 does not carry. (Technically the highest model number is 3 though, I think)

I double checked this.  C is set on greater than or equal to for a CP instruction.  And the model IDs are set at boot time, and are as follows:
0: TI-83+
1: TI-83+ SE
2: TI-84+
3: TI-84+ SE

This doesn't really matter though, because I will eventually change the way the interrupt detects the model.  It's way too unsecure when a program can simply change a single number and completely screw up a TI-83+ (SE) or disable USB access on a TI-84+ (SE).

Yeah, the compatability was fixed, as I mentioned in an earlier post.  My Ti-84+ BE is currently running KnightOS.

I double checked this.  C is set on greater than or equal to for a CP instruction.  And the model IDs are set at boot time, and are as follows:
0: TI-83+
1: TI-83+ SE
2: TI-84+
3: TI-84+ SE

This doesn't really matter though, because I will eventually change the way the interrupt detects the model.  It's way too unsecure when a program can simply change a single number and completely screw up a TI-83+ (SE) or disable USB access on a TI-84+ (SE).

yeah, but how are you going to make it more secure? Maybe have a section that only KOS can edit.

Speaking of which, will KOS mess with the certificate at all? I'm not doubting your coding skills, I'm just really afraid that my calculator would be bricked.

KOS will never have the certificate page swapped in, ever.
Also, I'll make it more secure by just running the same hardware test I use to set that byte at boot-time from in the interrupt.

sweet.  I was thinking cryptography next. j/k  Also, with wikiTI down, I can't test all this stuff, but I have a pretty good idea how USB works atm.

Yay!
Really glad you figured it out I think it was something like what you did that solved it last time.

graphmastur, what do you mean WikiTI is down? It's been up for me.

It was down for a while, but is now back up.