RightThere Posted January 19, 2017 Posted January 19, 2017 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 00E 17:43:50 SENSE SK Interpretation: Illegal RequestE 17:43:50 SENSE ASC/ASCQ Interpretation: Invalid Command Operation Code and E 17:43:51 SENSE: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00 00 00E 17:43:51 SENSE SK Interpretation: Illegal RequestE 17:43:51 SENSE ASC/ASCQ Interpretation: Invalid Field in CDB LUK, what on earth do those mean and how can this be fixed, so I can create bin/cue files again? Analyzing Disc Error.log
LIGHTNING UK! Posted January 20, 2017 Posted January 20, 2017 Some commands are expected to fail, don't worry about it. What's the actual problem? Are you getting an actual error message?
RightThere Posted January 20, 2017 Author Posted January 20, 2017 (edited) Some commands are expected to fail, don't worry about it. What's the actual problem? Are you getting an actual error message? 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? I also don't get any error messages from imgburn. Edited January 20, 2017 by RightThere
LIGHTNING UK! Posted January 20, 2017 Posted January 20, 2017 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. 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 00 I 17:40:46 CDB Interpretation: Read CD - Sectors: 0 - 25 E 17:43:49 SENSE: 00 00 04 5D 00 00 00 00 00 00 00 00 FF FF E 17:43:50 SENSE SK Interpretation: No Sense E 17:43:50 SENSE ASC/ASCQ Interpretation: The request could not be performed because of an I/O device error. '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: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 00 I 17:43:55 CDB Interpretation: Read Sub-Channel I 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 26 16 00 00 00 04 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 00 I 17:43:55 CDB Interpretation: Read Sub-Channel I 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 26 2F 00 00 00 1D 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 00 I 17:43:55 CDB Interpretation: Read Sub-Channel I 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 26 44 00 00 00 32 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 00 I 17:43:55 CDB Interpretation: Read Sub-Channel I 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 27 0F 00 00 00 48 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 00 I 17:43:55 CDB Interpretation: Read Sub-Channel I 17:43:55 BUFFER: 00 00 00 0C 01 10 02 01 00 28 27 26 00 00 01 14 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 00 I 17:43:55 CDB Interpretation: Read Sub-Channel I 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00 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 00 I 17:43:55 CDB Interpretation: Read Sub-Channel I 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00 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 00 I 17:43:55 CDB Interpretation: Read Sub-Channel I 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00 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 00 I 17:43:55 CDB Interpretation: Read Sub-Channel I 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00 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 00 I 17:43:55 CDB Interpretation: Read Sub-Channel I 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00 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 00 I 17:43:55 CDB Interpretation: Read Sub-Channel I 17:43:55 BUFFER: 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00 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.
RightThere Posted January 20, 2017 Author Posted January 20, 2017 (edited) 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. 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.'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: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 00Notice 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 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. 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. 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. 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.'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: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 00Notice 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 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. 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? Edited January 20, 2017 by RightThere
LIGHTNING UK! Posted January 20, 2017 Posted January 20, 2017 When I asked why version 9, I did so because v9 is ancient. I run v10.8 and even that's ancient.
RightThere Posted January 20, 2017 Author Posted January 20, 2017 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.
LIGHTNING UK! Posted January 30, 2017 Posted January 30, 2017 10.8 should install just fine on an x58 chipset motherboard - which is what I believe yours is. https://downloadcenter.intel.com/download/20768/AHCI-Intel-Rapid-Storage-Technology-Driver-for-Intel-Desktop-Boards 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.
dbminter Posted January 30, 2017 Posted January 30, 2017 Yeah, the only time I ever get that Windows Update driver update check to find anything, the updates fail to install. And it only ever found like 2 since I can remember going back to Windows 8.1 Update 1.
RightThere Posted February 2, 2017 Author Posted February 2, 2017 (edited) 10.8 should install just fine on an x58 chipset motherboard - which is what I believe yours is. https://downloadcenter.intel.com/download/20768/AHCI-Intel-Rapid-Storage-Technology-Driver-for-Intel-Desktop-Boards 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. Edited February 4, 2017 by RightThere
LIGHTNING UK! Posted February 9, 2017 Posted February 9, 2017 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.
RightThere Posted February 9, 2017 Author Posted February 9, 2017 (edited) 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? Edited February 9, 2017 by RightThere
LIGHTNING UK! Posted February 9, 2017 Posted February 9, 2017 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.
RightThere Posted June 30, 2017 Author Posted June 30, 2017 (edited) 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. Edited June 30, 2017 by RightThere
RightThere Posted July 1, 2017 Author Posted July 1, 2017 (edited) 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: =============================================== Filter Driver Load Order - ImgBurn v2.5.8.0 =============================================== Upper Device Filter: [None Found] Upper Class Filter: [None Found] Device: CD/DVD-ROM Device Lower Class Filter: PxHlpa64 Lower Class Filter: AnyDVD Lower Device Filter: [None Found] Filter Name: PxHlpa64 File Name: C:\Windows\system32\Drivers\PxHlpa64.sys File Version: 3.00.93.0 [3.0.93.0] File Description: Px Engine Device Driver for 64-bit Windows Product Name: PxHelp64 Product Version: [2.0.0.0] Company Name: Sonic Solutions Copyright: Copyright © Sonic Solutions Filter Name: AnyDVD File Name: C:\Windows\System32\Drivers\AnyDVD.sys File Version: 7.4.6.1 File Description: AnyDVD Filter Driver Product Name: AnyDVD Product Version: 7.4.6.1 Company Name: SlySoft, Inc. Copyright: Copyright 2014 SlySoft, Inc. Notice how IaStor isn't listed? Would that effect ImgBurn not being able to rip mixed-mode CDs as bin/cue files? If so, how would I be able to get ImgBurn to recognize the IaStore Driver? rst10.log Edited July 2, 2017 by RightThere
Recommended Posts