LIGHTNING UK!

Joliet is unicode - meaning it uses 2 bytes per character instead of 1. So if the field in the filesystem structure allows for 32 bytes, ISO9660 can have 32 characters, Joliet gets halved to 16.

The 3 brands might have all been the same media ID, hence not really any different at all. If you load the program AND THEN insert the disc, does the message in the status bar change to 'Logical Unit in process of becoming ready', before then going back to 'medium not present' ? It would certainly appear as though the drive just doesn't like those discs.

Make sure you visit the site for your own laptop manufacturer! There's a good chance the xx3x series is for a different one to the xx0x series - and we don't want to be responsible for you bricking your drive!

Perhaps I should just change it to say: 'Are you trying to build a DVD Video image / disc?' [Yes] / [No]

Whatever you've done, it's not right. You've burnt a disc with IFO/BUP/VOB files I assume (?) and yet according to the logs, you've no folders in the compilation - which of course means you don't have those files in a VIDEO_TS folder - which is a basic requirement for a DVD Video disc.

Do you just want to burn the ISO file? You do that in 'Write' mode, not 'Build' mode.

If you've done a full format on the disc (using the default program settings) and in the info window on the right it still doesn't say 'Formatted: Yes', your drive isn't formatting the discs properly. The only fix for that is different media and / or new firmware.

Happy Birthday Kirk!

www.svp.co.uk Oh and i think there's an AX03 firmware for that drive available somewhere - someone just caught me on email saying the drive doesn't burn anything - seems this is common and dell (who happen to use these drives) just swap them out for a decent NEC one.

Oh good, that saves me messing around

If that's supposed to be a DVD Video disc, no wonder it won't work. You appear to have all the files in the root of the disc rather than in a VIDEO_TS folder. The program normally detects DVD Video files in the wrong place and prompts you to see if you actually meant to burn a DVD Video disc. Do you remember seeing any such prompts when building the image?

You're not really giving us much to go on! What type of files are you burning? How are you burning them? Where's the log of the burn? What does the disc look like once burnt if you browse it in explorer?

Yeah you do! It means the program scans the subdirectories of any folder you add to the list (and the subdirectories of those subdirectories etc etc) - otherwise you'd only have files from within THAT folder.

Maybe you haven't burnt one in a while, but could you?! We're not exactly getting anywhere by just looking at your machine failing to produce a steady stream of data in build mode.

Did you burn using 2.3.2.0, or were you using 2.3.1.0? 2.3.1.0 misread some of the file formats and so you'd get a bad burn. In case you were already using 2.3.2.0, is there any chance you can tell me exactly how to reproduce this problem using the software you mentioned? Some screenshots showing what to do etc - otherwise I won't be able to do anything about it. Oh and no you can't change that they burn in alphabetical order.

Try some different discs, your drive doesn't appear to like those and can't initialise them (the drive has to do that before it lets software see them). Check for firmware updates too.

They make it sound so scary... believe me, it's not! You run the exe, select your drive (if you happen to have more than 1) and then click go. (ensure the drive is empty first) When it's done, just reboot. It's not going to touch your computers hard drive or the software on it, so don't worry.

You can't actually count the 6 seconds as the parsing time, that's just the time it took to loop through the file list and display everything in the listbox! Any chance you could time how long the actual 'read ahead' process takes? i.e. by watching the status bar and using a stopwatch! The read ahead should be the quick bit because that's a single api call to read the data from the file in one long stream. That actual parsing is lots of individual file accesses, reading 1 sector at a time - and potentially from all over the place within the file. At the moment that also involves a lot of opening / closing of files, but I've removed that overhead in the latest (unreleased) beta.

Sorry, I meant whereby the % isn't changing. It's these 2 bytes that contain the % complete status. 100% being FF FF As you can see, AB 89 is only just past half way As to why it's not finishing, I dunno, you'll have to ask the drive Try some discs with a different dye. Verbatim ones or something. Perhaps get some DVD-RW's too while you're at it so you have a few to play around with.

I know. And I said No. Then when I logged in as a non-admin user, it went ahead and checked for updates anyway. I know you understand why it works like this though, don't make it out to be something it's not. It went ahead and checked for updates because THAT user hadn't told it not to (and ok, there's no way to do that without first loading the program or manually editing the registry). The bottom line is, the program is not aware of other users and their chosen settings. The options selected at any given time ONLY apply to the user they're selected under. It's like me having SKY TV fitted and my neighbour complaing that they can't get it. Why should they? It's on my house, not theirs. In any case, I've done what I mentioned in a previous post about the 'Install for All Users' thing. If you want your personal 'check for updates' setting to apply to all users (on first run at least), just tick that box in the installer. If you don't, you'll have the same problem again if you wipe out the 'normal users' settings.

Ok, the last bit of the debug log may have been more helpful But if it's at 98% and still accepting commands, it's just the drive not finishing what it's told to do.

The booktype stuff is done automatically on samsung drives - since v2.2.0.0 or so I believe.

It's functioning in the only way it can. As a per user tool, it doesn't know about other users on the pc or care what settings they're using. If you install via 'Run As' whilst logged on as your normal user, does it still not put the registry stuff in the key for the currently logged on user? In any case, even as a security aware user, you were given perfectly decent explainations at the start of this thread as to why it does what it does. There was no reason at all to then say it 'smells like spyware'. Saying stuff like that just makes you come across as a bit of a twat - and I've no time for twats. EDIT: Oh and it's not ignoring what the admin user said, it doesn't know what they said! A user is just a user. Be it an admin one or anyone else. It works both ways. I could default to 'Never' for update checking and the 'Admin' user could say 'Yes, I want to check for updates' - which then makes it check weekly. Other users on the system would still use the program default of 'Never' and then I'd have them moaning. The only way I could change it is to rename the 'Create shortcuts for all users' to 'Install for all users' and then create an ImgBurn key under HKLM\Software which then contains an overriding setting for the update checking which 'new' people will use rather than the default program value.

5 minutes?! Damn, what are you using.... 18x DVD+RW media?! My 8x ones take about 9 minutes - as can be seen here http://forum.imgburn.com/index.php?showtopic=3282 When it seems like it's stuck on 98%, press F8 and see if the drive is still responding to commands. You should see them scrolling up in the log window. There's nothing I can really do if the drive just doesn't want to finish the task. Perhaps a lens cleaner might help? I assume the firmware is up-to-date and that the 'different' discs you tried were using different dyes?

On a clean install (or where you choose to reset the settings), you'll get a prompt to check for updates. Otherwise, it'll use your existing setting. The whole update checking routine ONLY runs if a certain variable is set - obviously it was for you or it wouldn't have run. if(Settings.EVENTS_CheckForProgramUpdate) { SetStatusBarText("Checking For Program Update", 0); CheckForProgramUpdate(true); } Settings.EVENTS_CheckForProgramUpdate is only ever a value between 0 and 4 Where 0 = Never, 1 = Daily, 2 = Weekly, 3 = Fortnightly, 4 = Month. It's probably worth mentioning that the program defaults to checking for updates every week and the settings are on a per user basis - so if you install as one person and then run as another, the updates will be disabled for the person that installed it, but will be on (weekly) for the other user. If you can honestly tell me (hand on your heart) that the program connects to the net when you start it up and yet on the events tab in the settings it says 'Never' for checking for updates, I'll eat my words.