DreamShell v4.0.0 Release

[SWAT]

(01.03.2024 20:53)pcwzrd13 писал(а):  Did some testing with ChuChu Rocket online. The console ID seems to be different across, 0.7, 0.8, and 0.8 with low-level. For 0.7 and 0.8 with low-level, I have to use different username or I get a password error. For some reason if I use 0.8 without low-level, I just get a password error every time, no matter if I try to use an existing username or a new one. @SWAT, maybe you can compare 0.7 and 0.8 and see why they're getting different console IDs?

Edit: It seems none of the loaders are getting the right console ID. A valid ID should consist of 12 characters including at least 5 letters. Shuouma told me my IDs in his server database are 3030313330AE for 0.7 and 284669671846 for 0.8 (with low-level) and neither of these are correct. Maybe the ID is being retrieved from the wrong location?

Edit 2: I think I found the issue! The correct console ID is retrieved if you use loader memory 0x8c004000 in all loader versions. I tested this with Dee Dee Planet which uses the console ID as well. Unfortunately I can't use this loader memory with ChuChu Rocket and CDDA. It will only boot from 0x8c004000 if CDDA is disabled.

Hmm... Need research this issue, because if you use loaders with 0x8c004000 and higher then only GD-ROM syscalls are emulated, so you get normal ID. If you using lower 0x8c004000 address that rewrited original syscalls, then emulated all syscalls, also all ssycalls emulated in low-level mode and 0.7 loader. Seems this is general issue for sys_id syscall. But this is very simple syscall, it just return pointer to 0x8c000068 where is should be ID that copied by BIOS from flashrom. Maybe 0x8c000068 is wrong address...