LIGHTNING UK!

lol try running that by babelfish or google translate

I don't think the network is the problem here. Copying files over my lan gives me about 40 - 45mb/s. I think reading 4 different images off your raid set is just too much random accessing to give you anything higher than ~20mb/s

Glad to hear things are looking up

lol so that's 4x over a network! making about 22mb/s if you're doing 4 of them at once. I don't think that's too bad at all.

Seriously, get onto them and tell them that then! They can't be huge apps or the companies would have already taken care of this issue. And being small, the developers are more likely to listen to the end user. I've made 2 companies aware of this problem in their apps and they've since fixed it. But I guess we're not using the same programs

I dunno but you can't instantly blame the drivers. There's obviously no real speed issue or it would never have reached 12x in the first place. People blame Nvidia and Intel drivers way too much. Who do you think made the first ones that ship with XP or whatever?! Microsoft aren't going to have done it, it's not their place to. Yes ok, their first few releases may have not been so good but XP has been around for years now and I doubt the drivers still really have problems. Just because they were bad 3 years ago doesn't mean they'll still be bad today. I run Intels latest chipset + ide/sata drivers (have done forever!) and don't have any problems. Same goes for my AMD machine that's running the Nvidia NForce 4 drivers. That said, it doesn't seem to have installed the PATA side of the 'enhanced' drivers. Those are still registering as standard. The graph is handy because it can help show the pattern. It could be a perfect stepdown, maybe shamus's G05s aren't up to much, who knows. The WOPC on the pioneer is also pretty aggressive and checks discs more frequently than any other drive I've seen.

ctrl+alt+del, task manager -> File -> New Task (run) -> 'explorer.exe' -> ok. If tray icons don't come back, go moan to the people that make those apps and have them listen to the right messages to capture the fact that explorer has just started and the system tray has just been created. i.e. WM_TASKBARCREATED = RegisterWindowMessage("TaskbarCreated"); Then listen for WM_TASKBARCREATED being passed to the application. When it is, recreate the systemtray icon.

They just focus the beam onto the different layers. When burning the second one, it just passes through the first without really having any impact on it.

Windows makes that icon, not me. It just takes the main app icon and sticks it inside a document type image. I can't really think of a decent one for images so it'll probably stay as-is.

lol that's a very open ended question chewy! It's kinda hard to tell what you were asking for exactly! If you're on about the SCSI ID address (the [x:x:x] one), yeah, just add some more controllers into your machine! As for the speed thing, no, that doesn't indicate anything to do with drivers. You've got a max of 12 and average of 4. To me it looks like it stepped up and stepped down again. Without seeing the write speed graph, it's hard to say - but that's what the graph is there for. That time is about right for a 4x burn though.

Tell me what it says in the status bar when you put this disc in. (Also, if you can, copy + paste the info from the panel on the right if it contains more than 2 lines) If the status bar says 'media not present', the drive isn't initialising the disc properly. There is nothing I can do about that. Eject + relaod it. Your drive is really a LiteOn, so just use that tab instead for changing the booktype. You should only need to do it once if you use the EEPROM settings.

Well I'm the only one who'd know the answer Going back to your questions.... ImgBurn doesn't create ISO files. It can't read anything. If another program was used that creates proper MDS files, yes the layerbreak position will be retained. If you reauthor a disc and it's done by a program that's not layerbreak aware (i.e. DVDShrink), you'll be lucky if the ISO it creates will be compliant for DL burning. The odds of it just happening to start a new cell on a LBA that's a multiple of 16 are pretty slim. ImgBurn cannot move the files within the ISO so if they're not right in the first place, you're stuck. In such situations, you're better off writing a video_ts folder and using PgcEdit to create the image. PgcEdit will ensure the image DOES have a cell that can be flagged as the layerbreak one and it WILL start on a sector (LBA) that's a multiple of 16.

No you don't.

lol, how can you call my logs strange?! They're the most straight forward things in the world compared to all the shite Nero outputs!

As ImgBurn doesn't (yet) create images from files, it's not really its job to make/set/align the layerbreak position. The thing people generally assume to mean 'layerbreak' is just a flag in one (or more if their LBA is the same) of the cells mentioned in the IFO. There is nothing in the vob to signal where it is. ImgBurn will parse the filesystem and look for vob files that lay with the acceptable LBA range. ie. the middle LBA of the file (minimum) and the original layerbreak on the media (before it's changed - that's the maximum). If it finds a vob between these points, it will read its associated IFO file. It then looks through all the PGCs within those IFO files to see if any of the cells are already marked with the 'I'm a layerbreak' flag. If it finds one, it add it to the list of potential layerbreak positions. If it scans all the cells and none are marked with the flag, it checks them again to see if they start on an LBA thats a multiple of 16. These then become a potential position for the layerbreak and are added to the list. Once that's all done, the list will hopefully contain a few potential positions. If it doesn't, the user is warned of the dangers of burning the disc. If it's not empty, the list is displayed to the user in a dialog box (if there is more than 1 option). They can then choose which one they want to use. If the selected position didn't have the flag set, ImgBurn sets it. Burning then continues. Of course none of that needs to happen if the user is burning from an MDS file where the layerbreak info is already contained within it.

There are no settings you need to change. The defaults work the best, that's why they're default!

No idea how to do any of it, I've never looked at recode! lol You just need to check any pair of IFO/BUP files. If there is no VOB between them, so much the better. If a vob is ever > 32k in size, forget about looking at that set - they will always be > 32k apart. (That's because it goes _0.IFO, _0.VOB, _1.VOB, _2.VOB.... _0.BUP)

With the right drive, they're excellent. http://forum.imgburn.com/index.php?showtopic=551

You could probably experiment and find out for youself. To test, you need to make it so that any _0.VOB file it makes is Then look at the image within ISO buster and see if the (end of the) ifo and (start of the) bup has at least 1 LBA address between them that's divisible by 16. It's not a major thing and certainly nothing to do with ISO or UDF specs. It's probably just advisable for DVD-Video because if the IFO and BUP are in the same ECC block and that gets ruined, there is no chance of reading either of them - making the 'BUP' file pretty pointless as its purpose in life is to be a backup!

Yes maybe it was a one-off. I guess it does depend on how the drive handles the command though. Maybe when you move the layer break position your drive is actually filling the gap (burning) between the old one and the new one. It's totally down the the manufacturer and the firmware really. Leave the 'check for updates' enabled in the program and it'll tell you when a new one is released - assuming you actually run ImgBurn from time to time! Also, you can check the website. Version 1.2.0.0 is right around the corner.

SAO -> DAO was just a name change, nothing more. The correct term for DVD burning is DAO. Setting the L0 capacity is down to your drive. If it's taking a while, it probably doesn't like the discs much. ImgBurn just sends 1 command to the drive, that is all. Make sure you only use Verbatim DVD+R DL media.

You're still leaving yourself open to a 'lost update' type of event. Sorry but this won't be happening any time soon.

Data wise, there shouldn't be, no. The table of contents will probably be different because one would have burnt mode 1 sectors, the other would burn mode 2 sectors. You should just burn the bin file. The only time(s) you cant burn bin+cue with ImgBurn is when the CUE mentions audio/mp3 (i.e. you're burning an audio disc), or when it contains multiple sessions/tracks. When you're converting that file, you're stripping off the header sequence, the EDC and ECC regions. They're what make up the 2048 -> 2352 bytes per sector difference. It's a pretty pointless exercise to be honest!

Found this just now too... http://www.litepc.com/support/kb.cgi?view=74

Problem: I get an error message saying that the required 'shfolder.dll' file is missing. Answer: You must be running a VERY basic installation of 95/98 etc without an up-to-date version of Internet Explorer installed. Normally this file IS already on the pc. Visit this link and download a package (containing it) from the Microsoft website. http://www.microsoft.com/downloads/details...D6-DBFA18D37E0F Well, it's that or update your installation of Internet Explorer.... or better still, your operating system! Update - March 2020: shfinst.exe seems to have been removed from Microsoft's servers (and most of the internet!). I'll attach a copy here instead. shfinst.exe