Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,514
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. Please post the log so I can see what it IS finding.
  2. LIGHTNING UK!

    +R DL's

    It just stopped burning everything. DVD-R burns came out with the discs still registering as being 'Empty' but you could see it had burnt the disc by looking at it - although it did just look like it was burning from about 1cm from the inner ring. DVD+R always returned an 'Unable to recover TOC' error once it had burnt the disc and then tried to verify them - as such, verify never actually happened. No other drive could read the burns either. Sorry, I don't have an explanation for your odd verify speeds.... I don't recall doing anything that would have sped up 1.1.0.0.
  3. This is probably a booktype problem as ImgBurn always finalises the discs it burns. Fingers crossed there is some way to make your HP drive perform bitsetting on the DVD+ media so that it looks like DVDROM. I guess your Toshiba just doesn't like the DVD+ booktype.
  4. Don't forget the new 0.0.0.5 version mate 30mb/s does kinda suck though mate... there must be something wrong there (as you rightly said!). Mine actually starts off at around 85mb/s and I'd have expected yours to be 65 - 75 if that drive is anything like my ide/sata ones.
  5. LIGHTNING UK!

    +R DL's

    Yup, the plex has a 2 year warranty so I just filled out the online RMA and 3 days later I had a new drive Really can't fault plextors return policy! Good point about the BenQ firmware... it probably wont even see these Ricoh as being 8x! Guess it'll just be the plex that gets tested then.
  6. LIGHTNING UK!

    +R DL's

    I haven't tried any yet but I did buy a couple of the Ricoh ones a while back. I'll test them this weekend in the Plextor (now I have a nice new one back from Plextor... mine died ) and in the BenQ 1655 too.
  7. LIGHTNING UK!

    TYG02's

    Probably exactly what you showed in your pic earlier - that the scan gets worse at the end. So if you cut the burn short, you don't get to see all tha bad bits. Pretty obvious stuff really!
  8. I'd imagine he means the entire disc - as in wiping everything (filesystem included) off it.
  9. LIGHTNING UK!

    TYG02's

    Now one could say that about some of your posts! I can't speak for corny, but lfc and I got ours from SVP. The spindles I've got certainly look official, they even have a nice bit of paper on top of the first disc giving warnings about only using them in drives that comply with the new dvd-r specs for burning 16x media. It then goes on to say that they're made in Japan.
  10. Ok cheers, I found the file format via google and have added support for it.
  11. You can email the first 5 meg of it and I'll see what I can do.
  12. So no chance of you just emailing me the 2kb .gi file then?!
  13. Did it the other day about 10 times to a hdd I need to RMA with Maxtor. Using my own little HDD Tools program of course Didn't take anywhere near as long as your one though - my transfer rate was about 70mb/s
  14. Yeah you can't ever really trust the brand name, you have to go by the dye type. Checkout our media & drives forum for some help.
  15. Please provide us with the log or something so we can actually see what's happening.
  16. It's cool, I realised English wasn't your first language, that's why I tried to explain it again You probably can find the layer break position using PgcEdit, yes. It is not something I've tried so I cannot say for sure either way. Assuming you want to know the title/chapter/cell of the layer break, I'd probably use IFOEdit. Just get it to open up the largest IFO file (this will probably be the main VTS set) and see where it marks the layer break flag. If you want to know it in terms of LBA, load up ImgBurn and switch to verify mode. Down the bottom of the info on the right side of the window you'll see some information about layers.
  17. I don't think you quite understood what I was saying... You posted 2 screenshots. One where you loaded the MDS file, the other, just the ISO. What I was trying to say was the loading/not loading the MDS file is irrelevant to the 'Display IFO Layer Break Information...' feature because it does not use the info in the MDS file, it uses the IFO data. If you want to manually set your own layerbreak, it will not be done through ImgBurn. You authoring program / image building program will do it. So far is ImgBurn is concerned, it simply displays a list of options already available to you. You select the one you want (often there IS only 1), click ok, and then it burns.
  18. Doesn't matter if the MDS is present or not... that window will always only show the IFO layerbreak. To view the MDS one, load the image as if you were going to burn it and then hover the mouse over the 'sectors' information. A yellow tooltip will appear with the layer data in it.
  19. You should have the original layerbreak. ImgBurn will read this info from the IFO files. If you're worried about something, get a screenshot of that 'Layer Break Information' window and post it here on the forum.
  20. Maybe the drive doesn't report that it can burn DL media. They're not FORCED to. Anyway, ImgBurn doesn't rely on that info. If it can burn them it'll still work.
  21. That's just the way DVD-R DL was designed. You can't do anything about it. The DVD- (minus) format doesn't support booktype setting, that's one of the major advantages of DVD+ (plus). Same goes for moving the layerbreak. You're much better off with DVD+R DL and changing the booktype to DVDROM.
  22. Noooo, just the small / tiny .gi file. It should be no larger / bigger than 2KB in size (2048 bytes).
  23. Click Tools -> ISO -> Display IFO Layer Break Information... Point it to your ISO file and see what it finds. No, that value cannot (and wouldn't need to be) put in as the layerbreak position.
  24. Can you please email me the *.gi file? Just the small one.
×
×
  • Create New...

Important Information

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