| View previous topic :: View next topic |
| Author |
Message |
denzilla
Regular
Joined: 03 Jan 2003
Posts: 141
|
 Posted: Tue Mar 21, 2006 4:14 pm Post subject: |
 |
|
| Alright so in a nutshell you're saying the bin/cues I made are correct? |
|
| Back to top |
|
 |
2X4
Member
Joined: 20 Jan 2005
Posts: 39
|
| Posted: Tue Mar 21, 2006 4:22 pm Post subject: |
|
|
Hey Nightwolve, thanks. Didn't mean to waste your time, especially when youre working on important stuff, like turborip, and thay OiF patch, which, when released I will send you my first born and maybe a fruit basket. Can't wait for that. Keep up the good work! 
| denzilla wrote: | | I have a 1:1 copy of Dracula X that i wanted to preserve before it became a victom of "CD Rot" that all copied CDs will fall fate to at some point. Following Squaresoft74's intructions I created the image and checked it with CDmage and it had no errors. ME also reports it as good during boot. |
I am one of those types that when I cant get something to work, I will labor at it until I do, regardless of how unimportant it might be. I took that archive and renamed all of the files to correspond with Square's TOC, then DLd the cue from NECstasy, then DLd the last iso track from a crappy ISO mp3 rom sight, and renamed it to match Square's cue, loaded 'r up in Daemon Tools, and Presto Chango! It still gives a bad TOC when loaded in ME. The TOC looks good when I check it in cdrwin, so, if I understand Nightwolve correctly, this is because of an issue with cdrwin? (Don't worry NW, I have no intention of entertaining the dillusions of a Linux zealot  )
_________________
 |
|
| Back to top |
|
|
Squaresoft74
Elder
Joined: 19 Apr 2002
Posts: 366
Location: France
|
| Posted: Tue Mar 21, 2006 5:33 pm Post subject: |
|
|
| NightWolve wrote: |
On my machine, I can only read sectors 3890 to 14036.
|
Strange.
The only people i heard that had similar issue, had it when doing a sectors range dump only.
They didn't have any problem making a full bin/cue dump and the iso/wav set they got from that bin/cue image using Cdmage was flawless.
All they had to do to fix their reading issue when using the sector range dumping feature, was to either upgrade their Cdrwin version or their Aspi drivers to get it properly working.
| 2X4 wrote: | | It still gives a bad TOC when loaded in ME. The TOC looks good when I check it in cdrwin, |
Pay attention to the leadout value aswell.
If the data track you used for Track22 is shorter than it should be , then your leadout won't be correct , hence the bad TOC message.
_________________
 |
|
| Back to top |
|
|
2X4
Member
Joined: 20 Jan 2005
Posts: 39
|
| Posted: Tue Mar 21, 2006 6:12 pm Post subject: |
|
|
I was afraid of that, I don't know why cdrwin doesn't display the leadout on the TOC, its kind of important. I guess I thought it was impossible to wrongly dump the iso track for some reason, that's why I grabbed it from a crappy source. 
_________________
|
|
| Back to top |
|
|
Squaresoft74
Elder
Joined: 19 Apr 2002
Posts: 366
Location: France
|
| Posted: Tue Mar 21, 2006 6:27 pm Post subject: |
|
|
| 2X4 wrote: | | I don't know why cdrwin doesn't display the leadout on the TOC |
It does, just look at the "Total Disc Time" tab.
_________________
|
|
| Back to top |
|
|
NightWolve
Elder
Joined: 19 Apr 2002
Posts: 304
Location: Chicago, IL, USA
|
| Posted: Tue Mar 21, 2006 6:35 pm Post subject: |
|
|
| Squaresoft74 wrote: |
Strange.
The only people i heard that had similar issue, had it when doing a sectors range dump only.
They didn't have any problem making a full bin/cue dump and the iso/wav set they got from that bin/cue image using Cdmage was flawless.
All they had to do to fix their reading issue when using the sector range dumping feature, was to either upgrade their Cdrwin version or their Aspi drivers to get it properly working.
|
Yeah, that's not the problem here. I can dump a BIN/CUE no problem. That's just the difference in behavior when you're doing a whole raw dump start to finish for a BIN/CUE as opposed to one track with a specified range. CDRWIN doesn't stop when it encounters an unreadable sector and so it continues to the next track. If I do a sector range dump, it'll stop at the first unreadable sector.
Anyway, it's not CDRWIN (there is no newer version to get) and I've had the latest ASPI. This is just when the drive gets close to the PREGAP area and fails to read near it, like one or two sectors too early, etc.
Now, are you sure those who you're talking about knew about subtracting the correct amount of sectors to prevent reading near the PREGAP area (the 225 or 150 you have to subract from track 1+2)?? You were telling them how to use the sector range feature to extract a track with the PREGAP issue?
Anyway, even programs like pcerip don't work for me now. However, if I use my DVD reader, it is able to make it to the final sector before the PREGAP on the same setup. So, it's related to the drive itself if another drive on the same PC with the same ASPI works. Like my friend said, it can vary with the drive when dealing with the undefined PREGAP area.
| denzilla wrote: | | Alright so in a nutshell you're saying the bin/cues I made are correct? |
No, I never said anything about your dump. I mean, I was talking about in general having discovered a problem I hadn't previously known about that probably explains some wrongly sized ISO tracks floating around out there. I was saying in essence that CDRWIN isn't perfect. Well, it's not really the software's fault; it's the hardware that might cause this issue that I'm referring to.
| 2X4 wrote: | | The TOC looks good when I check it in cdrwin, so, if I understand Nightwolve correctly, this is because of an issue with cdrwin? (Don't worry NW, I have no intention of entertaining the dillusions of a Linux zealot ) |
Well, you've now got an ISO/WAV/CUE file set, right? Have you been made aware of my TocFixer program? Just run that and that will guarantee every file is correctly sized. If you still get bad TOC by MagicEngine, it means the CRC doesn't match for track 2. Get another data track 2 from somewhere else in that case. But yeah, first run TocFixer on your ISO/WAV files. It'll make you a reliable CUE file too. This tool btw is compiled with the Squaresoft's TOC database and uses that to do the fixing. That's its magic.
Here:
http://nick.serveblog.net/index.php?ind=downloads&op=entry_view&iden=4
http://nick.serveblog.net/index.php?ind=downloads&op=download_file&ide=4&file=TocFixer101.rar
This is what should happen if it succeeds (Look at this image):
http://nick.serveblog.net/images/TocFixer02.png
Oh, heck naw. Hey Square, do you see that image? That last data track was enlarged by 4096 as it turns out. This is the image I got from that old pcengine.xxx something site, if you remember (where he had the mp3 files as class files). Anyway, 4096 is 2048 + 2048. It's missing the two last sectors, so that guy had the same problem. And being the last data track in particular, it does not require sector subtraction so he didn't have to deal with that difficulty. It's with track 21, the audio track, you have to worry about subtracting 225 sectors to rip it using a sector range feature. Anyway, point is, he may not have been as much of an idiot as we thought he was in creating that ISO/MP3 archive.
_________________
Translation Projects: Xak 3, Ys 4, Ys 1&2 Complete
Boycott XSEED Games!
Last edited by NightWolve on Tue Mar 21, 2006 7:58 pm; edited 2 times in total |
|
| Back to top |
|
|
Squaresoft74
Elder
Joined: 19 Apr 2002
Posts: 366
Location: France
|
| Posted: Tue Mar 21, 2006 7:14 pm Post subject: |
|
|
| NightWolve wrote: |
Now, are you sure those who you're talking about knew about subtracting the correct amount of sectors to prevent reading near the PREGAP area (the 225 or 150 you have to subract from track 1+2)?? You were telling them how to use the sector range feature to extract a track with the PREGAP issue? |
I gave them the sector range value to use.
Remember when we talked about how i was calculating it differently from you but we ended with the same ripped data result. 
So basically your tool will allow people who got those dumping issues with Cdrwin to dump their data without anymore trouble ?
_________________
|
|
| Back to top |
|
|
NightWolve
Elder
Joined: 19 Apr 2002
Posts: 304
Location: Chicago, IL, USA
|
| Posted: Tue Mar 21, 2006 7:36 pm Post subject: |
|
|
| Squaresoft74 wrote: | | So basically your tool will allow people who got those dumping issues with Cdrwin to dump their data without anymore trouble ? |
Yeah, it'll correctly subtract the 150 or 225 for tracks dealing with a transition of course, and then right when it gets towards the end, it'll read as many sectors before the PREGAP and if it fails early, that's fine, the track file will be padded with nulls.
_________________
Translation Projects: Xak 3, Ys 4, Ys 1&2 Complete
Boycott XSEED Games! |
|
| Back to top |
|
|
denzilla
Regular
Joined: 03 Jan 2003
Posts: 141
|
| Posted: Tue Mar 21, 2006 8:27 pm Post subject: |
|
|
| How do I take a bin/cue and make a ISO/WAV/CUE set using CDMage? |
|
| Back to top |
|
|
Squaresoft74
Elder
Joined: 19 Apr 2002
Posts: 366
Location: France
|
| Posted: Tue Mar 21, 2006 8:35 pm Post subject: |
|
|
Check the tutorial on my homepage.
| NightWolve wrote: | | the track file will be padded with nulls. |
That will be fine if the original track ends with 0x00 but it won't be accurate if it's originaly padded with something else such as 0xFF.
How can you be sure every single PCE CD data track ends with 0x00?
_________________
|
|
| Back to top |
|
|
denzilla
Regular
Joined: 03 Jan 2003
Posts: 141
|
| Posted: Tue Mar 21, 2006 11:44 pm Post subject: |
|
|
| I extracted 4 bin/cues made with CDRWIN to ISO/WAV/CUE using CDMage and the TOC Fixer said they all were the correct size. |
|
| Back to top |
|
|
NightWolve
Elder
Joined: 19 Apr 2002
Posts: 304
Location: Chicago, IL, USA
|
| Posted: Wed Mar 22, 2006 12:56 am Post subject: |
|
|
| Squaresoft74 wrote: | | That will be fine if the original track ends with 0x00 but it won't be accurate if it's originaly padded with something else such as 0xFF. |
Well, code doesn't use data near that area, and if it did, that'd be asking for trouble which I believe developers knew enough to avoid. So what value those bytes at the end have shouldn't matter. I've only ever seen 0x00 near the PREGAP area (the end of the transitioning track) myself though. Have you seen other values?
| Quote: | | How can you be sure every single PCE CD data track ends with 0x00? |
I can't be sure, obviously, but I can be sure that I cannot read the unreadable sectors when the laser encounters them and fails in error, so there's no other option. I suppose you could take the last byte of the last sector you read and padd with that, but that's rather pointless and still no guarantee if we're gonna be picky. Or yeah, go the distance and just duplicate the last readable sector for every unreadable one.
| denzilla wrote: | | I extracted 4 bin/cues made with CDRWIN to ISO/WAV/CUE using CDMage and the TOC Fixer said they all were the correct size. |
That's a good test. You're fine.
_________________
Translation Projects: Xak 3, Ys 4, Ys 1&2 Complete
Boycott XSEED Games! |
|
| Back to top |
|
|
NightWolve
Elder
Joined: 19 Apr 2002
Posts: 304
Location: Chicago, IL, USA
|
|
| Back to top |
|
|
Squaresoft74
Elder
Joined: 19 Apr 2002
Posts: 366
Location: France
|
| Posted: Sun Mar 26, 2006 10:01 pm Post subject: |
|
|
Yes that's correct.
Been busy lately but i finaly checked and answered them both !
_________________
|
|
| Back to top |
|
|
denzilla
Regular
Joined: 03 Jan 2003
Posts: 141
|
| Posted: Wed Mar 29, 2006 12:50 pm Post subject: |
|
|
| Will the .ini file be history once ME goes final? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
