px_d8 i 0
px_d8 i 0 2
px_d8 i 0 1
How about the result of px_d8 details in 1210S and other plextor?
Sector: ??
MSF: ??:??:??
Combined offset: ??? bytes / ??? samples
You are not logged in. Please login or register.
Redump Forum → Posts by sarami
px_d8 i 0
px_d8 i 0 2
px_d8 i 0 1
How about the result of px_d8 details in 1210S and other plextor?
Sector: ??
MSF: ??:??:??
Combined offset: ??? bytes / ??? samples
To: Admin
Using Quick search, I want to search a disc with protect (safedisc, securom etc). Is it difficult?
It may be this.
DiscImageCreator\Doc\KnownIssue.txt
. Reading with/without subcode, differ offset. (firmware bug?)
PLEXTOR PX-W2410TA: +686(with), +98(without)
PLEXTOR PX-320A : +686(with), +98(without)
fixed: reading a subcode on ReadCDForSearchingOffset().
If my thought is right, "Combined Offset (Byte)" of disclog.txt increases 2352(0x930) byte in your 1210S. If so, to get right "CD offset", it needs to fix driveOffset.txt manually for these drives .
EDIT:
fixed: doesn't work startstop command from 20150227
My apologies, but I wasn't clear before about the ReadBufferCapacity() problem on the 1210S. For some reason, the 1210S resets itself if a SCSIOP_READ_BUFFER_CAPACITY is issued to it. When it resets itself, it is unresponsive for some seconds and the following SCSI commands fail with either "UNIT_ATTENTION - POWER ON, RESET, OR BUS DEVICE RESET OCCURRED" or "LUN NOT READY - BECOMING READY".
I found this page.
https://msdn.microsoft.com/en-us/librar … s.85).aspx
And I understood that 1210S didn't support ReadBufferCapacity according to your drivelog.
FeatureRealTimeStreaming
StreamRecording: No
WriteSpeedInGetPerf: No
WriteSpeedInMP2A: Yes
SetCDSpeed: Yes
ReadBufferCapacityBlock: No
Uploaded. But I don't know why SetCDSpeed fails on 1210S...
EDIT: remove some declspec(align(4) in struct.h. changed message when it failed re-read.
EDIT: I had made a silly mistake regarding reread from 20150227. fixed it.
I did some preliminary tests with the PX-W1210S. This drive has some weird quirks too, just like the 40TS. For some reason it returns 0 for SCSI.wCurrentMedia. I added code to set the media type to ProfileCdrom to bypass that issue. The other issue is that the call to ReadBufferCapacity results in a drive reset, causing subsequent drive operations to error due to drive not ready. I solved this by bypassing the ReadBufferCapacity call and hard-coding the buffer size (4096 KB, according to Plextools).
Uploaded. Could you test and upload log.
I noticed the /c2 option wasn't working, though, since bC2ErrorData == FALSE.
Thanks. Uploaded.
LBA[201301, 0x31255], Audio, 2ch, Copy NG, Pre-emphasis No, Track[19], Idx[01], RMSF[01:26:00], AMSF[44:46:01], RtoW[0, 0, 0, 0]
LBA[201302, 0x31256], Audio, 2ch, Copy NG, Pre-emphasis No, MediaCatalogNumber [0000000000000], AMSF[ :02], RtoW[0, 0, 0, 0]
LBA[201303, 0x31257], Audio, 2ch, Copy NG, Pre-emphasis No, Track[19], Idx[01], RMSF[00:03:00], AMSF[44:46:03], RtoW[0, 0, 0, 0]
LBA[201304, 0x31258], Audio, 2ch, Copy NG, Pre-emphasis No, Track[19], Idx[01], RMSF[00:03:01], AMSF[44:46:04], RtoW[0, 0, 0, 0]
:
:
There is incorrect RMSF. Probably fixed.
I started doing tests on an old Nakamichi.
If you can, could you test other old plextor scsi drive too
It works with px_d8, but not when reading subcodes. I've posted a question elsewhere on the forum to hopefully determine exactly how px_d8 does subcode reading, so maybe I can troubleshoot it.
http://forum.redump.org/topic/2468/offs … d-command/
px_d8 is created by Truong Hi and Dremora. Dremora github: https://github.com/Dremora
But px_d8 code didn't exist in this github...
- fixed: IsValidSubQTrack()
The disc that failed when I tested it yesterday was a single track disc (US version of Ace Combat 3). However, I tried on a multi trakc disc (Japan version of Ace Combat 1), and the px_d8 works.
I'll update the document until next release.
Reading is much slower than in the last version. My guess is this is due to the additional read commands used for subcode reading (which weren't being run before, since the buffer was 0 < MINIMUM_DRIVE_BUF_SIZE).
- fixed: MINIMUM_DRIVE_BUF_SIZE is from 256 to 512.
I've got some other SCSI drives I'll try to get tested eventually (Some old Nakamichi, Toshiba, other Plextor models, Yamaha, etc) and report results.
Thank you in advance.:)
- fixed: If ModeSense failed, set drive buffer size manually. (Ultraplex is 512)
Could you test again and upload all log of Ultraplex.
pDisc->SCSI.pszTitle == 0, because pDevice->bCanCDText == FALSE, so the pszTitle array isn't initialized. Same problem exists with pszPerformer, etc. I bypassed it by checking first if pDisc->SCSI.pszTitle == 0, and similar for other psz* variables. I'm not sure if that's the best solution, though.
Uploaded.
One other problem which I haven't looked into yet is, after reading all the scrambled sectors for a PSX disc, an error is presented:
Please all log file.
Somehow Ultraplex seems to get the fulltoc data as "hexadecimal"
PX-716AL: LastTrack 21, Ultraplex: LastTrack 33(=0x21)
PX-716AL: Leadout, MSF 51:57:08, Ultraplex: Leadout, MSF 81:87:08(=0x51:0x57:0x08)
:
:
I coded to convert hexadecimal to decimal these value. Could you test again..
Unfortunately it looks like there are some other obstacles. I had to bypass "ReadDiscInformation" as the Ultraplex doesn't support those commands either.
- fixed: alway return TRUE
The call to ScsiPassThroughDirect seems to only read 2448 bytes into lpbuf (if I'm understanding the ioctl call correctly -- DataTransferLength is only 2448. But then lpbuf2 is lpbuf + combined offset, and combined offset on this disc is 9160 bytes. lpbuf2 then goes past the end of the lpbuf array.
sorry, fixed. Could you test again.
It's a strange drive. Here's a brief discussion about it on the dbpoweramp forums, where a user mentions that it supports only 0xD8, and not 0xBE.
Uploaded test exe (with src)
- changed: from READ_CD(0xbe) to READ_D8(0xd8) or READ12(0xa8)
- fixed: buffer overrun
I think the incompatibility is (partly) because the Ultraplex 40 doesn't support the SCSIOP_READ_CD read command used in ReadTOCFull. It only supports 0xd8 reads.
Really? please stdout log.
I also did some testing with my Creative RW121032E which is (I believe) a rebadged PX-W1210TA. You are correct, on PSX discs px_d8 fails with "ILLEGAL_REQUEST. ILLEGAL MODE FOR THIS TRACK". In contrast, the PX-W1210S and Ultraplex 40 seem to work with px_d8 on these discs.
However, I was able to get the RW121032E to dump a Saturn disc using 0xd8.
Are PSX discs single track? If so, could you test PSX multi track discs too.
btw, how do you connect the scsi drive? There isn't a scsi interface in my pc, and an adapter of scsi to usb is very expensive..
Thank you log.
Is the ring code of Your Steamgear Mash vs. ring code of database same?
SS disc includes "The first sector of the 2nd track's pregap is a scrambled data sector" occasionally.
Your disc is needed by subdump.exe ripping. Please report to F1ReB4LL.
On another note, why are some drives noted as only supporting scrambled reads on PCE discs?
PX-W8432Ti, PX-W1210TA, PX-W2410TA ? I tested in the past and "ILLEGAL_REQUEST. ILLEGAL MODE FOR THIS TRACK" occurred except PCE discs.
I don't have these drive any longer. If you have these, plz test..
Just dumped Steamgear Mash with DIC and noticed that the size of the data track and the first audio track do not match the size / hash in the database.
log plz.
Uploaded about SetCDSpeed. Still, there are very few supported scsi commands...
Thanks px_d8 results.
- added: plextor scsi drive (http://www.skcj.co.jp/discon/download/scsi.html) (But I don't know these drive can read in/out yet.)
Thank you test.
Upload test version in the 1st post. Could you test please.
And I want to know that your PX-40TS, PX-W1210S supports the reading in/out and d8 command. Could you exec px_d8.exe.
Uploaded 20150227 of DIC, 20141217 of EccEdc
Here's the stdout from when I ran the drive on the Ultraplex 40:
This problem had already fixed at latest test version. Could you test the latest release version.
Does anyone know the compatibility of the PX-716AL?
Could you exec px_d8.exe. I want to know this drive supports a read in/out.
Bug with http://redump.org/disc/34115/ -- https://www.sendspace.com/file/ofhrnr -- Track 22's pregap incorrectly detected (latest test version of DIC).
Plz subdump log.
Bug with http://redump.org/disc/7090/ -- https://www.sendspace.com/file/yju8rp -- Track 31's pregap incorrectly detected (latest test version of DIC).
Probably fixed.
EDIT
improved: detecting MCN sector.
fixed: log for pce disc
fixed: pce disc (audio sector of data track)
EDIT2
improved: log for directory record
Error logs are huge with the latest build. Like 1GB with a perfect disc.
*EDIT* Seems data only discs have this problem
*EDIT2* Seems to be the case with certain discs only
maybe is this?
http://forum.redump.org/post/48053/#p48053
I get an error dumping Toca 2 with the latest version:
Probably fixed.
I've said "There are many discs, where the whole R-W area is padded with 0xFF"
Oh sorry, I misunderstood. I have already whole R-W area is padded with 0xFF disc.
Maybe it's better to detect any padding, not only 0xff? If 10 or 11 bytes out of 12 for 1 subchannel are the same = padding. Like, channel T: 08 08 08 08 09 08 08 08 08 08 08 09 => 10 bytes are 08 and 2 bytes are 09 => padded with 0x08.
I haven't supposed these data at the moment. If possible, please give me all subfiles that you perceive these data "padding".
Thank's report.
Uploaded
- added: If any of R-W area is padded with 0xff, detect it.
- fixed: cue file for CDTEXT
(channel T is filled with 0xFF). There are many discs
Could you tell me these many discs? Because I don't have a channel T filled disc.
Redump Forum → Posts by sarami
Powered by PunBB 1.4.4, supported by Informer Technologies, Inc.
Currently installed 6 official extensions. Copyright © 2003–2009 PunBB.