RightThere
-
Posts
21 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by RightThere
-
-
ImgBurn sets its own timeout as part of the I/O request, but it's being ignored by the driver I expect - if that timeout in EV was directly related to a command sent by ImgBurn.
I can't explain why the thing that's happening is happening, I just know it is
it takes a lot more messing around and I/O snooping with various discs to work out what's going wrong.Sorry for necroposting, but since it's my thread question, I just want to make sure I understand this correctly;
As far as installing the files from 10.8.0.1003_f6flpy-x64.zip go:
1) Go to Device Manager
2) Select IDE /ATAPI Controllers, Then right click Intel ICH10R SATA AHCI Controller
3) Select Properties
4) Select "Update Driver"
5) Select the iastor.inf file from the extracted files in that zip file?
I'm going to attempt to see if this fixes the strange bin/cue issue I'm having, so I at least want to make sure I will be installing it correctly.
-
FILE "Quake2.bin" BINARY
TRACK 01 MODE1/2352
INDEX 01 00:00:00
TRACK 02 AUDIO
PREGAP 00:02:00
INDEX 01 40:34:18
TRACK 03 AUDIO
INDEX 00 44:03:08
INDEX 01 44:05:05
TRACK 04 AUDIO
INDEX 00 46:22:60
INDEX 01 46:24:57
TRACK 05 AUDIO
INDEX 00 48:56:69
INDEX 01 48:58:66
TRACK 06 AUDIO
INDEX 00 51:50:30
INDEX 01 51:52:27
TRACK 07 AUDIO
INDEX 00 54:27:22
INDEX 01 54:29:19
TRACK 08 AUDIO
INDEX 00 58:04:34
INDEX 01 58:06:31
TRACK 09 AUDIO
INDEX 00 61:10:50
INDEX 01 61:12:47
TRACK 10 AUDIO
INDEX 00 63:48:43
INDEX 01 63:50:40
TRACK 11 AUDIO
INDEX 00 65:50:46
INDEX 01 65:52:43
FILE "Quake2.bin" BINARY
TRACK 01 MODE1/2352
INDEX 01 00:00:00
TRACK 02 AUDIO
INDEX 01 40:36:18
TRACK 03 AUDIO
INDEX 01 44:07:05
TRACK 04 AUDIO
INDEX 01 46:26:57
TRACK 05 AUDIO
INDEX 01 49:00:66
TRACK 06 AUDIO
INDEX 01 51:54:27
TRACK 07 AUDIO
INDEX 01 54:31:19
TRACK 08 AUDIO
INDEX 01 58:08:31
TRACK 09 AUDIO
INDEX 01 61:14:47
TRACK 10 AUDIO
INDEX 01 63:52:40
TRACK 11 AUDIO
INDEX 01 65:54:43
The first one was created via Imgburn 2.5.7.0 (not via the PC I'm having the driver issue on) and the second was created via AnyBurn 3.5, 64-bit portable (on the PC with my driver issue).
Is there any functional difference between the two bin/cue file pairs? Is this kind of difference normal for bin/cue files between Imgburn and other similar applications? If so, does that mean the two file pairs are, for all intents and purposes, the same?
-
https://en.wikipedia.org/wiki/Compact_Disc_subcode
Sometimes they'd make use of the subchannel area as part of copy protection. I expect Quake predates that though.
ImgBurn reads and writes ISRC, MCN and CD-TEXT, so you aren't really missing anything - unless it's something 'unusual' that's stored in the R-W channels. With the exception of CD+G Karaoke discs, that's not going to be anything you'd ever see or use.
Quake 1 has Pre-emphasis on the audio, so Imgburn would not write that to a newly burned CD, then?
-
Yes, they check you have the required hardware before installing. If you don't have any hardware matching the device identifiers in the INF file, it won't install. The processor isn't an issue here.
It means what it says
A device didn't respond to a command within the timeout period. I don't know what that timeout period is though or what command it failed to respond to.Another thing that I found after further testing:
If I attempt to create a bin/cue or bin/wav file of a regular Audio CD using Imgburn, it works and I do not get any error messages regarding the Subchannel Data or I/O errors. Why would it only fail/hang on Mixed Mode CDs, like Quake 2?
There's no way to adjust that time out period either, right?
-
When it comes to 1990s Mixed-Mode CD PC games, such as Quake or Descent, what would actually be contained in the Sub-Channel data? That's solely for audio, right?
Since ImgBurn does not burn Sub-Channel data when you burn a CD, what would be missing from the newly burned CD, then?
Can someone clarify that?
-
10.8 should install just fine on an x58 chipset motherboard - which is what I believe yours is.
It's worth just giving that a go first to see if it makes a difference.
You could also install the latest chipset device inf drivers while you're at it.
https://downloadcenter.intel.com/download/20775/Intel-Chipset-Device-Software-INF-Update-Utility-
Never rely on that driver update feature built into Windows, it's useless.
According to CPU-z, I have:
Name Intel Core i7 920
Codename Bloomfield
Specification Intel® Core i7 CPU 920 @ 2.67GHz
Northbridge Intel X58 rev. 13
Southbridge Intel 82801JR (ICH10R) rev. 00
The problem with your first link, though, is that it says I needed one of the following processors:
Intel® vPro
Intel® Celeron
Intel® Pentium
These tools do check to make sure they're compatible before they install themselves, right?
Edit 2/4/2017: I think I've found the source of the problem.
In Event Viewer, I found the following error message:
The device, \Device\Ide\iaStor0, did not respond within the timeout period.
Lightning, what on earth does that error message mean? I know that iaStor0 is the Blu Ray drive's device name.
-
Lightning UK, can I assume that it burned correctly, despite the Verify function hanging at that L-EC Uncorrectable error?
(See attached log).
Before burning this CD and when this CD was still blank, I ran the CD in Verify's Test Mode (laser turned off) to see if Windows 7 was communicating with the drive properly. It did not return any i/o or other errors.
That Test Mode wouldn't cause those L-EC Uncorrectable errors when burning, right? (I know the media I'm using is crappy, btw.)
-
I should mention that, if ImgBurn imports this file and is able to read additional sectors, it should then remove those sectors from the bad sector list file or create a new, smaller bad sector list file.
http://dvdisaster.com/en/misc.html#windows
http://dvdisaster.com/downloads/manual.pdf
A very, a very powerful tool.
-
When I asked why version 9, I did so because v9 is ancient.I run v10.8 and even that's ancient.
The PC itself is a Dell Studio XPS 9000 from the year 2010. It originally came with RST 8, but v9 is the latest supported version for that PC model. I'm not entirely sure I can upgrade RST further than that. Thanks for your help so far.
-
I had no choice but to upgrade the intel driver, because Windows Update ended up broken on the newly cloned drive and would not even check for updates. I read online that upgrading RST resolved that issue, which it did for me. Moreover, the PC still got stuck but now checking for updates. I had to install an additional offline Windows Update patch to get WU working roperly again.Which chipset does your motherboard use? Is there any reason you've gone for v9 of the IRST driver? Have you tried booting into safe mode to see if it does the same thing? It looks like the OS/drive is blocking one command as the error being returned is not from the drive itself.
'FF FF' means it came from the OS/driver rather than the drive itself. So IRST could be blocking the command or swallowing the actual error and returning its own - which isn't helpful!There's also something weird going on with the subchannel requests/responses.I 17:40:46 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:40:46 CDB: BE 00 00 00 00 00 00 00 1A F8 02 00I 17:40:46 CDB Interpretation: Read CD - Sectors: 0 - 25E 17:43:49 SENSE: 00 00 04 5D 00 00 00 00 00 00 00 00 FF FFE 17:43:50 SENSE SK Interpretation: No SenseE 17:43:50 SENSE ASC/ASCQ Interpretation: The request could not be performed because of an I/O device error.
Notice how the first 5 'Buffer' lines have values in them, then they're basically just full of zeroes.The program is asking for info but never receiving it.I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 26 16 00 00 00 04I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 26 2F 00 00 00 1DI 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 26 44 00 00 00 32I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 27 0F 00 00 00 48I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 27 26 00 00 01 14I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00
Also, to clarify, I also tried creating Quake 2 bin cue files in Alcohol 120% trial and it did work for me there. That's a workaround for me at least. I will check on chipset drivers if available. So basically what you're saying is that RST created a knock on effect with respect to the OS driver and imgburn.
I had no choice but to upgrade the intel driver, because Windows Update ended up broken on the newly cloned drive and would not even check for updates. I read online that upgrading RST resolved that issue, which it did for me. Moreover, the PC still got stuck but now checking for updates. I had to install an additional offline Windows Update patch to get WU working roperly again.Which chipset does your motherboard use? Is there any reason you've gone for v9 of the IRST driver? Have you tried booting into safe mode to see if it does the same thing? It looks like the OS/drive is blocking one command as the error being returned is not from the drive itself.
'FF FF' means it came from the OS/driver rather than the drive itself. So IRST could be blocking the command or swallowing the actual error and returning its own - which isn't helpful!There's also something weird going on with the subchannel requests/responses.I 17:40:46 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:40:46 CDB: BE 00 00 00 00 00 00 00 1A F8 02 00I 17:40:46 CDB Interpretation: Read CD - Sectors: 0 - 25E 17:43:49 SENSE: 00 00 04 5D 00 00 00 00 00 00 00 00 FF FFE 17:43:50 SENSE SK Interpretation: No SenseE 17:43:50 SENSE ASC/ASCQ Interpretation: The request could not be performed because of an I/O device error.
Notice how the first 5 'Buffer' lines have values in them, then they're basically just full of zeroes.The program is asking for info but never receiving it.I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 26 16 00 00 00 04I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 26 2F 00 00 00 1DI 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 26 44 00 00 00 32I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 27 0F 00 00 00 48I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 27 26 00 00 01 14I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00I 17:43:55 [0:0:0] PLDS DVDRWBD DH-6E2S 7D12 (D:) (ATAPI)I 17:43:55 CDB: 42 02 40 01 00 00 00 00 10 00I 17:43:55 CDB Interpretation: Read Sub-ChannelI 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00
Also, to clarify, I also tried creating Quake 2 bin cue files in Alcohol 120% trial and it did work for me there. That's a workaround for me at least. I will check on chipset drivers if available. So basically what you're saying is that RST created a knock on effect with respect to the OS driver and imgburn?
-
The actual problem is Imgburn gets stuck at Analysing Disc and goes no further than that, thus not creating a bin cue file pair. Could my problem stem from the blue ray drive having old firmware not compatible with that Intel Rapid Storage Technology driver?Some commands are expected to fail, don't worry about it.
What's the actual problem? Are you getting an actual error message?
I also don't get any error messages from imgburn.
-
Windows 7, 64-bit
Intel Rapid Storage Technology 9.6.0.1014
ImageBurn 2.5.8.0
Quake 2 Mixed-Mode CD
Back in September 2016, my previous hard drive was failing, so I cloned it to a new WD Black 1 TB Hard Drive using Macrium Reflect. As a result, I wasn't able to use Windows Updates, so I had to also upgrade Intel Rapid Storage Technology 9.6.0.1014, which resolved that issue (along with an additional manually installed update from Windows on top of that).
What does this have to do with Imgburn, then?
I can no longer create bin/cue files using Imgburn, but can still read .isos without any issues.
In the attached log, you'll notice:
E 17:43:50 SENSE: 70 00 05 00 00 00 00 0A 00 00 00 00 20 00 00 00 00 00
E 17:43:50 SENSE SK Interpretation: Illegal Request
E 17:43:50 SENSE ASC/ASCQ Interpretation: Invalid Command Operation Codeand
E 17:43:51 SENSE: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00 00 00
E 17:43:51 SENSE SK Interpretation: Illegal Request
E 17:43:51 SENSE ASC/ASCQ Interpretation: Invalid Field in CDBLUK, what on earth do those mean and how can this be fixed, so I can create bin/cue files again?
-
What's in the ini file exactly? Attach one or copy + paste its contents please.
It appears that at least in DVDFAB HD Decrypter 9.1.5.9, the program does not create an .ini file when making a dual-layer DVD Iso. As a result, I cannot provide that to you, otherwise I would do so.
You're right, then. With this program, it's better to rip the disc as a folder and then build the image in ImgBurn to get the proper layer break. Thanks for your assistance regardless.
-
That's correct, it's not suitable.
An MDS with no original layerbreak position specified within it is no different to a plain old ISO.
One other question I forgot to ask:
When creating a dual-layer DVD Iso with DVD Fab HD Decrypter, that program also creates an accompanying .ini file for the layer break. Can Imgburn's "Create MDS File" feature use the layer break info from the .ini file to create an .mds file?
-
Some things are so idiotic in Windows 8!
For instance, if you select multiple files, you CANNOT use CTRL plus a mouse to deselect individual files from the list! It slightly unhighlights the item but doesn't complete deselect it. So whatever action you perform on the other files gets performed on the file you don't want included. This also happens if you select the Select all button. Idiots!
Notifications don't always appear on top! Idiots! They appear minimized and you're only warned by a flashing window in the task bar from File Explorer. For instance, a Permanently delete dialog might do this. The AnyDVD window that appeared whenever a new DVD was inserted on Windows 7 doesn't open on Windows 8.
It's Microsoft. What did you expect? They don't give a damn about the end user experience.
-
You'd be better off having DVDFab output a VIDEO_TS folder and burn that in Build mode so you can pick the layer break position properly.
Meaning that the Create an MDS option would not be suitable for what I'm asking?
-
I don't know why DVD Fab would create an .INI file. .INI files have nothing to do with ISO's unless DVD Fab creates .INI files for its own use to burn them.
I'd think there would be no need to create an MDS or DVD file with burning an ISO in ImgBurn, even if it's a dual layer DVD. Just load the ISO in ImgBurn and burn it.
But if the .iso is from a Dual Layer DVD, it needs to have its layer-break set properly or the disc won't play. That's why I'm asking about the Create an MDS File option. Would Create an MDS File solve that issue?
-
If I backup a Dual Layer DVD using DVDFab HD Decrypter as an .iso to my hard drive, can I instead burn it with ImgBurn using the .ini file that DVDFab creates, since there's no initial .mds file?
Or, do I have to go into Imgburn and select "Create MDS File" and then select the .iso file in question?
-
Yes
Thanks for clearing that up. Until now, I hadn't been able to get any answers over at CDFreaks/MyCE regarding whether or not my drive supported bitsetting of Single and Double Layer DVDs.
Now, all I have to is use Taiyou Yudens and Verbatims, instead of Raitek's!
-
Do the bolded parts in this output mean my drive booktypes DVD R+ DLs as DVD-Roms?
PLDS DVDRWBD DH-6E2S 7D12 (ATAPI)
Current Profile: DVD+R DL
Disc Information:
Status: Complete
State of Last Session: Complete
Erasable: No
Sessions: 1
Sectors: 3,870,560
Size: 7,926,906,880 bytes
Time: 860:09:35 (MM:SS:FF)
MID: RITEK-S04-66
Supported Read Speeds: 2.4x, 4x, 6x, 8x
Current Read Speed: 2.4x - 6x
File System Information:
Sectors: 3,870,560
Size: 7,926,906,880 bytes
Time: 860:09:35 (MM:SS:FF)
TOC Information:
Session 1... (LBA: 0)
-> Track 01 (Mode 1, LBA: 0 - 3870559)
-> LeadOut (LBA: 3870560)
Track Information:
Session 1...
-> Track 01 (LTSA: 0, LTS: 3870560, LRA: 0)
Disc Control Blocks Information:
PLDS
Physical Format Information (ADIP - L0):
Disc ID: RITEK-S04-66
Book Type: DVD+R DL
Part Version: 1
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 2
Track Path: Opposite Track Path (OTP)
Linear Density: 0.293 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 16,580,607
Last Physical Sector in Layer 0: 2,283,519
Physical Format Information (ADIP - L1):
Disc ID: RITEK-S04-66
Book Type: DVD+R DL
Part Version: 1
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 2
Track Path: Opposite Track Path (OTP)
Linear Density: 0.293 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 16,580,607
Last Physical Sector in Layer 0: 2,283,519
Physical Format Information (Last Recorded - L0):
Disc ID: RITEK-S04-66
Book Type: DVD-ROM
Part Version: 1
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 2
Track Path: Opposite Track Path (OTP)
Linear Density: 0.293 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 16,561,375
Last Physical Sector in Layer 0: 2,141,503
Physical Format Information (Last Recorded - L1):
Disc ID: RITEK-S04-66
Book Type: DVD-ROM
Part Version: 1
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 2
Track Path: Opposite Track Path (OTP)
Linear Density: 0.293 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 16,561,375
Last Physical Sector in Layer 0: 2,141,503
Layer Information:
Layer 0 Sectors: 1,944,896 (50.25%)
Layer 1 Sectors: 1,925,664 (49.75%)
Analysing Disc Error
in ImgBurn Support
Posted · Edited by RightThere
Lightning UK, I installed RST 10 like you suggested.
https://downloadcenter.intel.com/download/20768/AHCI-Intel-R...river-for-Intel-Desktop-Boards
Still won't rip bin/cue files for mixed-mode CDs.
The https://downloadcenter.intel.com/download/20775/Intel-Chipse...e-Software-INF-Update-Utility- link won't install, erroring out with an "unknown error" message.
This is so frustrating.
Log file is attached.
Edit: Another oddity I've discovered is in the filter driver section:
rst10.log