Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,521
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. If the installation file is just vaninshing SOMETHING must be removing it. It's hard to assist with something like this, the problem is your problem and you'll have to invest some time in finding out what's causing it. You're the first person to mention anything like this so it's not even as if we've seen it before and have already gotten to the bottom of it.
  2. Unpredictably sorts them?! I think not! It sorts them by name - except in the case of DVD Video where other factors come into play. If you're worried about the reliability of files at the end of overburnt discs, don't overburn, pretty simple really. I'm usually (brutally) honest when it comes to suggestions and giving files a priority rating is not something that interests me at this time, sorry. If you require that functionality you should stick to using your existing tools.
  3. lol it's not a SCSI drive, nobody really makes them these days. Your drivers are just emulating it as a SCSI device - probably because they offer some kind of RAID functionality somewhere along the line. Make sure the drive is connected to the proper IDE channels that are part of the motherboards southbridge, NOT any 3rd party IDE controller you may or may not also have onboard. Most add in PCI cards do NOT support optical drives.
  4. You AV is probably detecting something it doesn't like in the installer and so just deleting it. It's bad that it's not telling you about it though and instead just deleting it. You must have configured it to do that.... very scary! Ensure your AV program + definitions are up to date as the file at ImgBurn.com is guaranteed virus free.
  5. If you're doing DL at all then you want to make sure Shrink doesn't make an ISO image as it doesn't do it properly (DL weren't really around when it was designed).
  6. The bit about DVD Video specs was aimed more at DoIt than you fordman. I already kinda guessed you were just going by what you'd read in the Doom9 forum - I too have read that thread. I'm not one of these people who likes to do things based on hunches. If someone can say to me - "if something is such and such, you must do this and that" - then I'll do it. If not, I wait until they can I don't recall hearing that layer breaks have been causing any problems for people over these past few years so (being honest) I'm really not all that worried about changing the current method used or the info displayed to the user. I was mainly talking about all the discs people have done themselves and burnt using all the various tools available - not original discs. Until its recent inclusion in PgcEdit, I hadn't ever really seen 'mux rate' mentioned anywhere - and especially not in software that just burns your VIDEO_TS folder. I was actually given a heads up about dvd video specs and layer breaks some time ago. Out of the 5 or so points made regarding what makes a good layer break and how/where to position it, mux rate was not one of them.
  7. Your drive has burnt the disc ok but it can't read it back (at tested by the 'verify' stage) - hence the 'read error'. This is basically because the drive made a naff burn. Update your drives firmware and use decent media. *Decent* being Verbatim (MCC dye) or Taiyo Yuden.
  8. Well you will keep trying to go at a tangent to the program!
  9. Yeah that's actually the one I was referring to (without naming names).
  10. Yes we know what the layerbreak is in physical terms, however for DVD Video there are lots of other things to consider. You can only really say either way if you've actually read the DVD Video specs - and unless you work for an authoring company that's paid for them, I doubt you have!
  11. Bitsetting is performed automatically by almost all burners now. It's not something you have to 'do/change' for every burn. It's a set once and forget about it type setting (on all but LG drives I believe - more fool them!). ImgBurn supports changing the booktype setting on most of the major manufacturers, just click the little 'Book' picture down the bottom right when in one of the write mode. (on the 'Device' tab in Build mode).
  12. Ah maybe that's it then. I figured it would be 2 years everwhere.
  13. Doesn't that just run it into UltraISO / PowerISO? That's not a direction I see ImgBurn heading. If you want to add files, mount the existing ISO in DAEMON Tools and point Build mode at the virtual drive. Then add your new stuff and make a new image. When complete, delete old image.
  14. Does anyone really know for sure that the mux rate is important?! It strikes me that programs have been setting layer breaks without any regard for mux rate for ages and it's never really been an issue!
  15. I could have sworn Plextor drives came with 2 years warranty
  16. If you're burning non DVD Video data too, there is an option for where you want the DVD Video data to be positioned. Either at the start, mixed in or at the end. It defaults to mixed in. So although your VIDEO_TS folder might be quite small (and fit on 1 layer), some of the other stuff is probably pushing it over the edge. When it does / can fit on 1 layer, ImgBurn IS clever enough to know that it doesn't need splitting across the layer break. So perhaps you just need to play around with the 'Folder Content Location' option on the 'Build' tab in the settings.
  17. Pretty much the first thing I do in code is put up the splash screen. If it's not even getting that far, it's out of my hands, sorry. Try loading it in safemode and see if it still gets stuck.
  18. You're lucky it plays at all really - VCD's are multitrack and ImgBurn doesn't do multitrack burning. If it stops earlier than it should do, maybe the drive just can't read that bit on the disc and so gives up. Your guess is as good as ours.
  19. No offence but that really is the users problem if they buy media the drive doesn't support. I'm not even sure it's possible to know if the media is high speed and the drive doesn't support it.
  20. I just meant that for all the writer cares, you could have burnt 4 million 'zero filled' sectors. What's being burn is neither here nor there. The drive just can't read the sector back. It's not that the data on the disc doesn't match that of the image file, it's that the data on the disc is 110% useless because the drive cannot read it, full stop. Just RMA the drive and save yourself from wasting more time and money trying to fix things and diagnose problems.
  21. Really Blu?! I've got quite a few that come up as PTP in the disc info. *Finding* the layerbreak is not really the issue here. I assume Bloodyroar would be loading from an MDS so the original LB would be preserved. The reason it's not being, and hence why ImgBurn is searching full stop, is that the LB in the MDS is not usable on OTP media. What comes after that is almost to be expected - i.e. where no cells just happen to be aligned on an ECC boundary and still let L0 >= L1.
  22. You're getting proper read errors back from the drive. This is not an issue with WHAT has been burnt, just that something has been burnt at all! If the burner burns ok (no errors) and then can't read back what it just wrote, it's clear the burn was no good. I would almost expect that on cheapo ritek / cmc DL media but not on Verbatim ones. So if it really is still giving you read errors when you've burn to decent Verbatim discs, I would say your drive is on its way out. When mine died it would cycle the tray after the burn (and before the verify) but get stuck and just return the 'Unable to recover TOC' error. So it has just that second finished burning and then it couldn't even initialise the disc to gather info about it etc - and that process is TOTALLY internal to the drive. I filled out an RMA on the plextor site and 4 days later I had a new drive.
  23. That doesn't really mean anything bloodyroar. Every disc is different, this one just happens to have L0 That is not permitted on OTP discs so therefore this one must have come from PTP.
  24. In build mode, yes. You just add it as you would do any other folder. Or better still, add the parent folder - the one that contains the AUDIO_TS / JACKET_P / VIDEO_TS folders.
  25. As Blu said, you want to burn them at 2.4x, not 4x. When you burn the verbatims, set it to 2.4x too. If you really do get write errors on both sets of media, the media has got to be duff or the drive is. My Plextor 716 lasted a year before it died, just RMA it, it's easy/quick/free!
×
×
  • Create New...

Important Information

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