LIGHTNING UK!

I get ~30mb/s from my hdds in an 'icy box' 3.5" enclosure. Optical drives never get anywhere near that when I try! lol I 23:55:31 Operation Started! I 23:55:31 Device: [0:0:0] Maxtor 7 B300S0 (G:) (USB) I 23:55:31 Device Sectors: 586,114,704 I 23:55:31 Device Size: 300,090,728,448 bytes I 23:55:31 Action: Verify I 23:55:31 Passes: 1 I 23:55:31 Verifying Sectors... I 23:57:47 Abort Request Acknowledged E 23:57:48 Failed to Verify Sectors! E 23:57:48 Verify Aborted! - Duration: 00:02:16 I 23:57:48 Average I/O Rate: 34,108 KB/s - Maximum I/O Rate: 37,582 KB/s E 23:57:48 Operation Aborted! - Duration: 00:02:16

ImgBurn is a burning tool, it won't copy your movies unless they're home made ones (i.e. unprotected).

Why have you told it not to verify against an image file? That's the whole point of a verify - to test that the data is correct. You've clearly got some issues with all the buffer recovery stuff in the log. What are you doing that's stopping ImgBurn from reading quickly enough from your hdd? Do you ever run defrag? You should also be on 2.3.2.0 now. Upgrade A.S.A.P.

Please do make sure you're using 2.3.2.0 for your burns now and not still 2.3.1.0. It is indeed odd that it wont read the burnt discs. Does it just keep saying 'Device Not Ready (Medium Not Present)' in the status bar when you insert a disc, or does it say something else?

Nope, there isn't such a thing. ImgBurn doesn't support multisession so there's no point in leaving it open so far as ImgBurn is concerned. If you require multisession stuff, stick with Nero for now.

We don't talk about DVD Decrypter here, we CERTAINLY don't talk about other (similar) tools.

Try the BYX5 firmware. http://sony.storagesupport.com/dvdrw/firmware.htm#710

You really shouldn't need a buffer that big. Even at only 20mb, I never see mine fall below the maximum! It could well be due to fragmentation, but then it could also be something with vista indexing your files or something. Basically, if the program can't read the data fast enough to burn, *something* else must be using the drive too. It just doesn't make much sense otherwise. There are various performance counters your could look at in perfmon but I don't know if you've seen that tool before / would be comfortable looking at it.

That wasn't aimed at you hunginator.

Handsome fellow. I like the side parting but he could do with having the back trimmed a little. But seriously, how the hell does he eat with that thing in the way?!

lol I honestly haven't a clue. It's not something I've looked into and certainly not anything I've seen in passing. I have to admit, going though the entire program and changing everything text related to say 'resourcestring' or whatever really doesn't put a smile on my face... quite the opposite in fact! I've the feeling I could start now and I still wouldn't be done in time for Christmas.

correct.

search for 'burn to the brim' on google, it might be useful.

It's on purpose. The feature is only available on XP and above.

Well the time is the playback time. An IFO doesn't have a playback time, it's not played! Only a cell (that's part of a chapter / pgc etc) gets played, and hence has a time associated with it. If you split at a file, there's no chance of you noticing it during playback - because nothing is being played. The same goes for if you select a cell that the first cell in any pgc (so long as it's not used in the middle of any other pgcs) - you'd typically spot this by looking at the LBA values. Multiple entries with the same LBA (before the -> arrow), means they're the same thing. If it's cell 1 in one pgc but cell 10 in another, keep looking for better alternatives.

Bwhahahahaa I would be but I just shaved it off this morning - shucks!

Oh hang on, I expect some other site added that line because they knew Tech Spot would just copy + paste it from them. Hence by adding the line 'Tech Spot: a bunch of copy&paste idiots' to the change log, they'd catch them fair and square. i.e. Added: this and that Added: some stuff Tech Spot: a bunch of copy&paste idiots Changed: some stuff Fixed: some stuff So in answer to your original question calweycn, I've no idea. It's not in MY changelog and I don't write any of the others, the sites do as they please.

It's NOD32's problem.

Are you perhaps changing the read buffer for build mode rather than the write buffer on the I/O tab?

(assuming 'thermal' = 'printable') Do you want to print onto them? If not, why pay the extra for thermal ones?

Thats not a log file, that's the stuff out of the disc info window.

VTS_05_0.IFO on both. (Oh and it's the first cell in the pgc, it can't start at anything other than 00:00:00 lol)

Personally, no, not a clue.

That or I'm missing something

Hey, yeah, that's not too bad! I could actually do with some decent icons so I can get the Vista 256 sizes in there. So to all the people that can do artwork out there, feel free to knock something up if you have time