DreamShell v4.0.0 Release

[yo4yo4]

(09.02.2024 16:57)SWAT писал(а):  

(08.02.2024 07:09)VeraBecker писал(а):  Hi SWAT!

What Quake version, do you use? I use NTSC but when the I use virtual VMU does not start game .

CDI games can be play it?, ssf2 and space channel part does not work.

The games with WINCE have problems, sega rally stuck when i star race.
Bust a move 4, random stuck.

Regards!

Q3 works only with CDDA or with VMU, but can't works with both of them. Memory is not enough.

CDI should work, but not everything may. I didn't do anything to them, everything remained the same. I don't recommend using this format.

For WinCE and 2k2 games need defragmented images. Sega Rally try another region.

Hello swat and team!
I have tried everything since then, but still "sega rally 2 jp ver." does not play correctly, PAL and NTSC-US are fine, but only JP ver. does not play CDDA correctly. It is just like when the clock is out of sync. It plays "da-da-da-da-da..." as if a construction site drill is being used. Is this the limit at this point?
Please let me know if there is any way to improve it.

0x8c000100 DMA TRUE CDDA non IRQ
0x8c001100
PAL and NTSC JAP EUR

[SWAT]

(20.02.2024 01:00)yo4yo4 писал(а):  

(09.02.2024 16:57)SWAT писал(а):  

(08.02.2024 07:09)VeraBecker писал(а):  Hi SWAT!

What Quake version, do you use? I use NTSC but when the I use virtual VMU does not start game .

CDI games can be play it?, ssf2 and space channel part does not work.

The games with WINCE have problems, sega rally stuck when i star race.
Bust a move 4, random stuck.

Regards!

Q3 works only with CDDA or with VMU, but can't works with both of them. Memory is not enough.

CDI should work, but not everything may. I didn't do anything to them, everything remained the same. I don't recommend using this format.

For WinCE and 2k2 games need defragmented images. Sega Rally try another region.

Hello swat and team!
I have tried everything since then, but still "sega rally 2 jp ver." does not play correctly, PAL and NTSC-US are fine, but only JP ver. does not play CDDA correctly. It is just like when the clock is out of sync. It plays "da-da-da-da-da..." as if a construction site drill is being used. Is this the limit at this point?
Please let me know if there is any way to improve it.

0x8c000100 DMA TRUE CDDA non IRQ
0x8c001100
PAL and NTSC JAP EUR

You should enable IRQ hooking.
CDDA in WinCE games doesn't works correctly without it.

[yo4yo4]

(20.02.2024 06:19)SWAT писал(а):  

(20.02.2024 01:00)yo4yo4 писал(а):  

(09.02.2024 16:57)SWAT писал(а):  

(08.02.2024 07:09)VeraBecker писал(а):  Hi SWAT!

What Quake version, do you use? I use NTSC but when the I use virtual VMU does not start game .

CDI games can be play it?, ssf2 and space channel part does not work.

The games with WINCE have problems, sega rally stuck when i star race.
Bust a move 4, random stuck.

Regards!

Q3 works only with CDDA or with VMU, but can't works with both of them. Memory is not enough.

CDI should work, but not everything may. I didn't do anything to them, everything remained the same. I don't recommend using this format.

For WinCE and 2k2 games need defragmented images. Sega Rally try another region.

Hello swat and team!
I have tried everything since then, but still "sega rally 2 jp ver." does not play correctly, PAL and NTSC-US are fine, but only JP ver. does not play CDDA correctly. It is just like when the clock is out of sync. It plays "da-da-da-da-da..." as if a construction site drill is being used. Is this the limit at this point?
Please let me know if there is any way to improve it.

0x8c000100 DMA TRUE CDDA non IRQ
0x8c001100
PAL and NTSC JAP EUR

You should enable IRQ hooking.
CDDA in WinCE games doesn't works correctly without it.

Thank you for your reply comment.

I enabled "IRQ hooking" and it did not start. If I disable it, it does start, but the construction sound starts on the demo and menu screens. If I enable it, it stops on execute.
It is the same when I change each region. I have tried all addresses. I can find a low level startup with background music off, but I could not find a JP ver. setting with background music." The result is the same whether I use cf or "IDE", the bios is the same as the one that was included in the released version.
I have no idea what is wrong.
My several DC and several rally2 are all in the same situation.
If I could find a preset that could play the BGM on the jp ver. demo and menu screens, I could choose to adjust or give up, but I'll look into it some more.

Thank you very much.

[SWAT]

(20.02.2024 08:09)yo4yo4 писал(а):  I enabled "IRQ hooking" and it did not start. If I disable it, it does start, but the construction sound starts on the demo and menu screens. If I enable it, it stops on execute.
It is the same when I change each region. I have tried all addresses. I can find a low level startup with background music off, but I could not find a JP ver. setting with background music." The result is the same whether I use cf or "IDE", the bios is the same as the one that was included in the released version.
I have no idea what is wrong.
My several DC and several rally2 are all in the same situation.
If I could find a preset that could play the BGM on the jp ver. demo and menu screens, I could choose to adjust or give up, but I'll look into it some more.

Thank you very much.

Maybe just copy CDDA tracks from JP to USA version? What the difference?

[yo4yo4]

(20.02.2024 11:46)SWAT писал(а):  

(20.02.2024 08:09)yo4yo4 писал(а):  I enabled "IRQ hooking" and it did not start. If I disable it, it does start, but the construction sound starts on the demo and menu screens. If I enable it, it stops on execute.
It is the same when I change each region. I have tried all addresses. I can find a low level startup with background music off, but I could not find a JP ver. setting with background music." The result is the same whether I use cf or "IDE", the bios is the same as the one that was included in the released version.
I have no idea what is wrong.
My several DC and several rally2 are all in the same situation.
If I could find a preset that could play the BGM on the jp ver. demo and menu screens, I could choose to adjust or give up, but I'll look into it some more.

Thank you very much.

Maybe just copy CDDA tracks from JP to USA version? What the difference?

We apologise for all the trouble we have caused you.
As far as I have been able to find out, the following versions exist depending on the time of sale.

PAL 1.000 - 1.003
NTSC-US

The last track above is 21. Each has a different file size. Furthermore, the final track is the programme placement.

NTSC-JP has a final track of 23 and the programme itself is larger than the above, with different file sizes etc.
If you copy and place the programme in consideration of the file size, etc., it will only reboot. There is currently no other way left but to modify the data with a binary editor while applying patches to the data.
The hardware and software emulators start without any problems, but until now the only information I could find on the internet was on a Japanese forum that existed in the past.

It is good to start and play with a separate disk, but the process of trying various things and making things is interesting and I got absorbed in it after a long time, so I try various things.

It reminds me of what other developers related to playback used to say, that if Sega Rally 2 (Japanese version), the final release, could be started normally, it would be the end of it.

I wish for further development.
Thank you very much.

[yo4yo4]

Hello all.

The settings for Rally 2 in the past list were completely different on my Dreamcast, so I'm posting this in case it helps with the release version.
For those of you who don't have a problem, please ignore this.

Thank you to the development team and supporters.
Thank you very much.

Hardware configuration

Japanese Dreamcast VA1 + PD9439 (SATA converter) + 80-core IDE cable + GD-IDE + 1pf bypass capacitor for GD-ROM 5V and GND + Pull VCC and GND like a lens unit from the front side and connect DATA wires from the back side.
A connector is attached to the intermediate board and the bypass capacitor and LEDs are attached. 3.3V LEDs are taken from the back side and the configuration is 12V + GND (2 wires) 5V on the surface.
The reason why it is not 5V only is simply because there were times when the voltage drops in the measured values.
The SSD is a Samsung 840 EVO 120GB.
The hard disk with a buffer was relatively stable. (Only the release disc works) Toshiba is unstable WD is good
Defragmentation is of course optimised by megavolt85.
I have checked that I have done it well because if you do the optimisation twice in the same folder, you will get a problem.
The above is the result of the current situation after trying to find a setting that does not stop on the way as much as possible.
The Japanese version that cannot be started unless IRQ is switched off is a mystery. (A sound under construction sounds:-))
Is it the start sector or the memory capacity... haha

I don't know if this is helpful, but...

Bios boot_loader_retail.bios

Country Europe Broadcast PAL Language French
AND
USA NTSC English
Japan NTSC Japan

Use DMA transfer ON
Emulate async true
Emulate CDDA ON
IRQ hooking ON
Binary OS Auto
BOOT Direct

Loader memory 0x8c001100

Sega Rally 2 v1.000 (1999)(Sega)(PAL)[!]
Sega Rally 2 v1.001 (1999)(Sega)(PAL)[!]

Loader memory 0x8c000100

Sega Rally 2 v1.003 (1999)(Sega)(US)[!]
[GDI] Sega Rally 2 [truncated]

IRQ hooking OFF

Sega Rally 2 v1.04 (1999)(Sega)(JP)(en)[!][HJ120D, HJ121A, HJ121E, HJ122C]
Sega Rally 2 v1.04 (1999)(Sega)(JP)[!][10M3, 10MM1]
Sega Rally 2 v1.04 (1999)(Sega)(JP)[!][11MB1, 11MM1]
Sega Rally 2 v1.04 (1999)(Sega)(JP)[!][13M1]
Sega Rally 2 v1.04 (1999)(Sega)(JP)[!][MT B02, MT B04]
Sega Rally 2 v1.04 (1999)(Sega)(JP)[!][MT B02]

SEGA_RALLY2 JPNDisk Master Ripping

[luizroz]

1.
In RC4, i made scripts LUA like this:

Dead_or_Alive_2.lua
-------------------
local path = os.getenv("PATH");
OpenModule(path .. "/modules/minilzo.klf");
OpenModule(path .. "/modules/isofs.klf");
OpenModule(path .. "/modules/isoldr.klf");
os.execute("isoldr -o 0 -x 0x8c004000 -e 8 -j 0 -f /ide/Games/Retail/Games_D/Dead_or_Alive_2/disc.gdi" );
------------------
in this version dont work.

2.
In ISOLOADER, In presets, after saving:
the last field for memory (customized), these content dont save with same text (strange characters in place).

[SWAT]

(26.02.2024 15:11)luizroz писал(а):  1.
In RC4, i made scripts LUA like this:

Dead_or_Alive_2.lua
-------------------
local path = os.getenv("PATH");
OpenModule(path .. "/modules/minilzo.klf");
OpenModule(path .. "/modules/isofs.klf");
OpenModule(path .. "/modules/isoldr.klf");
os.execute("isoldr -o 0 -x 0x8c004000 -e 8 -j 0 -f /ide/Games/Retail/Games_D/Dead_or_Alive_2/disc.gdi" );
------------------
in this version dont work.

2.
In ISOLOADER, In presets, after saving:
the last field for memory (customized), these content dont save with same text (strange characters in place).

Thanks for report!

1. Works fine for me:

PHP код:

-- DOA2.lua
local path = os.getenv("PATH");
OpenModule(path .. "/modules/minilzo.klf");
OpenModule(path .. "/modules/isofs.klf");
OpenModule(path .. "/modules/isoldr.klf");
os.execute("isoldr -x 0x8c004000 -a -f /ide/games/0_Widescreen/Dead_or_Alive_2/disk.gdi"); 


2. Yes, this is already known, I received a similar report and checked it myself, there are some issues with this.
You can fix it manually yet in text editor on PC. It's good that this option is not often used.

[luizroz]

(27.02.2024 06:12)SWAT писал(а):  

(26.02.2024 15:11)luizroz писал(а):  1.
In RC4, i made scripts LUA like this:

Dead_or_Alive_2.lua
-------------------
local path = os.getenv("PATH");
OpenModule(path .. "/modules/minilzo.klf");
OpenModule(path .. "/modules/isofs.klf");
OpenModule(path .. "/modules/isoldr.klf");
os.execute("isoldr -o 0 -x 0x8c004000 -e 8 -j 0 -f /ide/Games/Retail/Games_D/Dead_or_Alive_2/disc.gdi" );
------------------
in this version dont work.

2.
In ISOLOADER, In presets, after saving:
the last field for memory (customized), these content dont save with same text (strange characters in place).

Thanks for report!

1. Works fine for me:

PHP код:

-- DOA2.lua
local path = os.getenv("PATH");
OpenModule(path .. "/modules/minilzo.klf");
OpenModule(path .. "/modules/isofs.klf");
OpenModule(path .. "/modules/isoldr.klf");
os.execute("isoldr -x 0x8c004000 -a -f /ide/games/0_Widescreen/Dead_or_Alive_2/disk.gdi"); 


2. Yes, this is already known, I received a similar report and checked it myself, there are some issues with this.
You can fix it manually yet in text editor on PC. It's good that this option is not often used.

Thanks for checking. I will edit files .cfg in PC in theses cases.

[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.

[svk77]

(22.02.2024 11:56)yo4yo4 писал(а):  Country Europe Broadcast PAL Language French
AND
USA NTSC English
Japan NTSC Japan

Use DMA transfer ON
Emulate async true
Emulate CDDA ON
IRQ hooking ON
Binary OS Auto
BOOT Direct

Loader memory 0x8c001100

Sega Rally 2 v1.000 (1999)(Sega)(PAL)[!]
Sega Rally 2 v1.001 (1999)(Sega)(PAL)[!]

Loader memory 0x8c000100

Sega Rally 2 v1.003 (1999)(Sega)(US)[!]
[GDI] Sega Rally 2 [truncated]

IRQ hooking OFF

Sega Rally 2 v1.04 (1999)(Sega)(JP)(en)[!][HJ120D, HJ121A, HJ121E, HJ122C]
Sega Rally 2 v1.04 (1999)(Sega)(JP)[!][10M3, 10MM1]
Sega Rally 2 v1.04 (1999)(Sega)(JP)[!][11MB1, 11MM1]
Sega Rally 2 v1.04 (1999)(Sega)(JP)[!][13M1]
Sega Rally 2 v1.04 (1999)(Sega)(JP)[!][MT B02, MT B04]
Sega Rally 2 v1.04 (1999)(Sega)(JP)[!][MT B02]

SEGA_RALLY2 JPNDisk Master Ripping

HKT-3030 (VA1 maybe), USA NTSC English, ide hdd.

https://mega.nz/file/PJ5HARTC#w3P2OF0MML...Zkr-i2tuoo
It works normally only in low level mode.
Accordingly, without CDDA. Otherwise ingame hangs.
I tried everything loader memory address from the settings.

https://ia801503.us.archive.org/35/items...003%29.zip
Doesn't start at all.

Could you share the pal/ntsc images that work fine for you?

[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...

[pcwzrd13]

(03.03.2024 09:21)SWAT писал(а):  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...

That's what I was thinking but why would 0.7 and 0.8 low-level get a different ID if that's the case?

[SWAT]

(03.03.2024 17:13)pcwzrd13 писал(а):  

(03.03.2024 09:21)SWAT писал(а):  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...

That's what I was thinking but why would 0.7 and 0.8 low-level get a different ID if that's the case?

Need to figure it out, maybe this will help understand the reason.
Obviously something is wrong here in all cases of emulation of this syscall.

[megavolt85]

(03.03.2024 17:13)pcwzrd13 писал(а):  That's what I was thinking but why would 0.7 and 0.8 low-level get a different ID if that's the case?

unpack with replace to DS/firmware/bios/
test ChuChu Rocket with low-level

[pcwzrd13]

(03.03.2024 21:53)megavolt85 писал(а):  

(03.03.2024 17:13)pcwzrd13 писал(а):  That's what I was thinking but why would 0.7 and 0.8 low-level get a different ID if that's the case?

unpack with replace to DS/firmware/bios/
test ChuChu Rocket with low-level

Doesn't seem to be a difference. Looks like I'm getting the same (incorrect) ID.

[megavolt85]

(03.03.2024 23:11)pcwzrd13 писал(а):  Doesn't seem to be a difference. Looks like I'm getting the same (incorrect) ID.

I found two more errors, check

[fafadou]

I just check my DS folder and there are 3 syscalls.bin, and they don't have the have size.

Should I replace all of them by this new one ?

[pcwzrd13]

(04.03.2024 00:20)megavolt85 писал(а):  

(03.03.2024 23:11)pcwzrd13 писал(а):  Doesn't seem to be a difference. Looks like I'm getting the same (incorrect) ID.

I found two more errors, check

Nope, still the same. If you can see what ID the loader is getting, you can compare it to your correct ID using Flash Uploader Tool.

[megavolt85]

(04.03.2024 02:11)pcwzrd13 писал(а):  Nope, still the same.

shit, need replace another file syscalls.bin, thank @fafadou
/DS/firmware/isoldr/syscalls.bin