LIGHTNING UK!

Nothing in Borland's development environment is unicode enabled, it's all ansi. You have to install a bunch of 3rd party tools to get unicode - and they of course have their own set of bugs and issues. Converting to unicode (properly) would take ages, I can assure you! If it was a simple click of a button I'd have done it already. The new 'Build' bit of ImgBurn is already kinda built around WideString rather than AnsiString but existing parts of the program are limiting its usefulness at the moment. I do hope to someday get started on making it unicode enabled but I certainly don't have a date set for it.

Just as a heads up, the back end code is right for the program update time periods but the visual side of things (in that combobox) is wrong. So basically if you select fortnightly it'll check weekly and if you select weekly it'll check fortnightly.

scsi raid will be the OS install drives + apps etc. The rest are where I put all my junk! The forum etc aren't on this box. With IE7, I can quite easily run out of RAM (current have 2gb in my pc) after opening 30 odd tabs (with other programs running too of course)! I've seen it a few times where context menus fail to function etc. That's when I know I have to close things down! I may have a little play around overclocking it, yes.

1. God knows how that happened, I must have been asleep. 2. The '/' is used when building the date, only it's actually replaced with whatever date seperator your OS is set to use. The thing is, it then replaces certain characters that aren't allowed in path / filenames. To do it properly I'd actually have to build that text up on the fly inserting the correct date seperator and then replacing with '_' if I needed to. All that is just a little bit overkill. All threads default to 'normal' priority but the app itself switches to 'high' when burning. To override them, use the following keys: OVERRIDE_ThreadPriority_Build OVERRIDE_ThreadPriority_BuildRead OVERRIDE_ThreadPriority_Burn OVERRIDE_ThreadPriority_DeviceBuffer OVERRIDE_ThreadPriority_GraphData OVERRIDE_ThreadPriority_Read OVERRIDE_ThreadPriority_Verify They're all DWORD type values. 0 = idle, 1 = lowest, 2 = lower, 3 = normal, 4 = higher, 5 = highest, 6 = time critical, everything else = normal.

yeah

6700 conroe Intel 975xbx board 4gb g.skill hz 6400 ddr2 ram ati 7900xt dell perc 4e/dc (320/2e) scsi card 4x 73gb atlas 10k rpm scsi drives (1x raid 0, then 2 individual drives) 4x 500gb wd 7.2k rpm RE2 sata drives (2x raid 0) It'll be my new main (server type) machine so I'll use it for everything I do.

Me. Well, as soon as my damn SCSI card finally turns up from the US I will! It's holding up my new PC build

wahoo, it's still tonight and I've managed to release it! I'll just go pat myself on the back

Details, downloads etc on the main website. http://www.imgburn.com

The stuff after the ? is just 'querystring' data that's passed to the index.php page. The main website also has an index.php page, that's why it loaded It wouldn't understand the querystring data so it's just ignored.

Sorry mate, it's not something I'd implement! (being brutally honest!)

ok, all added (for all of the options on that page).

Yeah was just thinking about doing that. Will leave the normal one for people who just want 1 name for all filesystems and then break it down for people who like different ones.

You'll have to burn another one then so we can see what's up. If you're using DVD-R, just enable test mode and then you won't waste any discs. Copy + paste the full log once you've done that.

It was released internally the other day but I've been away and saw no point in releasing it if I wasn't around to assist with anything. Will try and update the site tonight and upload the new version so you 'normal' folk can download it.

Most drives remember their bitsetting stuff once it has been configured. So you could do it with another program and then it'll automatically bitset to DVDROM without ImgBurn having to do anything.

It will only remove a flag if you select a cell that's not already marked as non seamless.

in v2.0.0.0, there's actually no checking done on CLI passed volume labels. It will limit the length where it needs to, but otherwise it'll just use exactly what you specify (even if it breaks ISO9660 specs etc). v2.1.0.0 will convert to uppercase and replace invalid characters with underscores.

Surely it would just be easier to have the 'other' burning programs create an ISO image in the first place? Anyway, virtual drives aren't my thing.

Nope, sorry.

Those MSF times are from the old CD days where 74mins = 640mb, 80 mins = 700mb etc. It's all detailed in the MMC specs you can get from www.t10.org It's nothing to do with the length of a bit of video.

You drive doesn't appear to support those discs. Maybe try the 2.4x speed ones rather than the 8x ones.

ImgBurn is not a unicode program.

You're burning an MPEG file as if it's a disc image!! This is NOT possible and it wouldn't work even if the media wasn't awful.

Does it really say copy protected or does it say write protected? It could just be that your drive doesn't like the discs you're using if it's the latter.