Jump to content

RightThere

Members
  • Posts

    21
  • Joined

  • Last visited

RightThere's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. 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
  2. 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.
  3. 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?
  4. Quake 1 has Pre-emphasis on the audio, so Imgburn would not write that to a newly burned CD, then?
  5. 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?
  6. 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?
  7. 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: Lightning, what on earth does that error message mean? I know that iaStor0 is the Blu Ray drive's device name.
  8. 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.) QuakeBurn.log
  9. http://dvdisaster.com/en/misc.html#windows http://dvdisaster.com/downloads/manual.pdf A very, a very powerful tool.
  10. 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.
  11. '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. 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 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. '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. 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 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?
  12. 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.
  13. 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: and 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
  14. 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.
  15. 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?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.