Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,457
  • Joined

  • Last visited

Posts posted by LIGHTNING UK!

  1. Couple of things to try here..

    From what I can tell, there's an updated version of your AHCI driver available. I've seen 18.36.4.1022 mentioned around when Googling. Perhaps give that a go?

    Failing that, try going back to the Windows AHCI driver, which calls itself 'Standard SATA AHCI Controller'. To do that, locate your AHCI controller in Device Manager, right click it and select 'Update Driver'. Select 'Browse my computer for drivers' and then select 'Let me pick...'. You should then see the standard driver listed in the options. Select it and click Next etc. 

    I'm running the standard driver without any issues... but I'm on a 300 series board, not a 500.

     

  2. 2 hours ago, dbminter said:

    If another drive doesn't work, try using Alcohol to read it.  Some of the discs in my collection would not read with certain hardware and ImgBurn, but Alcohol did.  If another drive AND another software don't work, then the culprit is probably the disc has gone bad with age and simply can't be read fully anymore.  It is almost 20 years since the retirement of the original Playstation hardware.

     

    That would need to have been because of a different issue (like analysing gaps between tracks or something). An unreadable disc is an unreadable disc - they only have access to the same commands (to 'read' a sector) as I do.

  3. Does your bin/cue image consist of 20 bin files?

    I take back what I said last night, the image I have here for the christmas version of Nights doesn't specify PREGAP in the CUE, it's making use of INDEX 0 and taking data from the corresponding BIN file. The non-christmas version used PREGAP.

    Looking at the 2nd bin file (which is the bin for track 2), I can see that byte 15 is set to 01 (in each of the first 150 sectors (of 2352 bytes) of the file), when it should be 02 if it's a mode 2 track - as specified in the CUE file.

    So in my case at least, the BIN/CUE are wrong.

  4. The speed of the connection can and will limit the speed of the drive. A fast bd drive won’t work properly over a usb 2 connection.

    I doubt you could buy a recent model that doesn’t have the correct connection type required to achieve what the drive is capable of. Therefore, you probably don’t need to worry too much.

  5. Are you mounting the ISO as a virtual drive and then playing from the virtual drive, or are you simply loading the ISO in whatever playback tool you've chosen to use? The two methods could cause the playback software to behave differently.

    If the ISO is really ok, there's no reason for it to behave differently when burnt to disc - subject to the device being able to read the disc nicely / quickly enough.

    Whilst there are probably people on the forum that could offer some advice, your issue doesn't sound like it's related to ImgBurn... or even burning in general. You might be better off asking for help at somewhere like videohelp.com

     

  6. When you say you've checked the CD-R, what exactly have you done?

    Once the disc has burnt and you get that error.... if you 'ok' the box and then switch to Read mode, can you copy and paste everything from the box on the right of the main window please?

    It seems as if your drive is reporting that the disc is still empty - hence the session count coming back as 0 on the burnt disc.

  7. Ok, maybe it was the load segment value was throwing it off before.

    Most other bits get noticed and corrected by the program when it detects you want to build an OS installation disc.

    As you're using etfsboot.com, it doesn't look like you're building a UEFI bootable disc, it looks like a legacy bios one.

    This is the same issue covered a couple of days ago in this thread... 

    But if it boots for you, I guess it's all good and your VM has handled it.

     

×
×
  • Create New...

Important Information

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