Resolved: [Bug Report] Tom & Jerry's War of the Wiskers [PAL]
#21
Ok.. so, I tried on my sister's laptop
And it worked Ohmy

.... Could have been different since this was the first SATA drive I used?


Attached Files
.txt   emuLog Tom&Jerry.txt (Size: 56,93 KB / Downloads: 403)
.txt   emuLog donalduck.txt (Size: 57,41 KB / Downloads: 304)

Sponsored links

#22
This is even worse. It fails to read in the proper XA2 mode but succeeds with the wrong YellowMode2.
I've really no idea at this point. We need someone with better experience with IOCTLs Tongue2
#23
(05-16-2014, 10:52 PM)rama Wrote: Should be fixed in the latest git build of cdvdgigaherz Smile

Is that fix this one? Git commit

Form the code it looks like it tries YellowMode2 before trying XAForm2, but the logs seem to suggest that the plugin tries XAForm2 first.

Am I just looking at the wrong commit/code? Is there a reason for the difference?
#24
According to Gigaherz YellowMode2 is fine. If the game boots for you, the read mode is correct.
We've determined that some drives apparently don't work with PS2 CD-ROM games.
#25
Well, both my drive are quite old indeed (even though original PS2 dvd drives are even older)

But.. if windows can.. why couldn't pcsx2?
#26
Windows is probably not using IOCTL raw reads Smile
I guess it's more like a bug though. We're following examples and there could be something wrong or missing
that some drives require and some don't. I didn't find it though ><
#27
So, I did some other -noob- researching
First, I found this. I think it would really deserve a look

Back to the topic what can I say? All I have are just empirical tests
First, I can successfully read raw cd both with HxD and with devdump (part of cdrtools suite)

If the latter is open, pcsx2 will refuse to load the drive though, claiming there are no available CDs. Windows still opens the drive pretty fine

Then, I noticed that for some weird reason.. in the correct reading (that on my sister's computer) you have Sector 16, then 18 and 22 and so on..
here (where it fails) 16, 48 then 32 and again 16

Last but not least, I logged pcsx2 with process monitor.. don't know if this could help
Hats off Laugh

[I found some confused chatter even here]
other Microsoft. documentation


Attached Files
.7z   Logs.7z (Size: 30,22 KB / Downloads: 233)
#28
Ok I have now retrieved a much newer SATA dvd drive...
And it still fail miserably.. so that doesn't seem the problem
#29
So, I could finally compare a properly working drive and a malfunctioning one on the same computer.

I attached console outputs here.
Would devel logs help more?

Had I better to open an issue on github?


Attached Files
.txt   working.txt (Size: 21,12 KB / Downloads: 225)
.txt   notworking.txt (Size: 87,99 KB / Downloads: 208)
#30
Thank you for your report.
This bug report has now been marked as Pushed and has been posted as an issue in our Github repository HERE

Issue link: https://github.com/PCSX2/pcsx2/issues/64...-120722523

This thread will now be moved in the Pushed bug reports subforum.
We're supposed to be working as a team, if we aren't helping and suggesting things to each other, we aren't working as a team.
- Refraction




Users browsing this thread: 1 Guest(s)