LIGHTNING UK!

The physical position (LBA) of the file on the disc shouldn't have anything to do with the playing order. Why not just burn a disc and try it?!

Optical drives don't really like anything other than ATA/IDE mode - and on top of that they're quite fussy about drivers (especially on nvidia chipset boards) You could always get yourself a Silicon Image 3512 PCI card and run the drive off that. You can pick them up for about

You should at least try a couple of Verbatims. They're about

File systems tend to store files in alphabetical order - some insist upon it. If you want to play then in a different order, change the name and put a number at the start (this is typically the track number). Of course it's only going to be like how they are on your hdd. They don't play in any set order off there, except how you import them into your playing software. MP3 players will typically parse the ID3 tags of the files and build a listing based on the artist, album name etc - so the order within the file system doesn't mean anything.

I have no personal experience of that drive so obviously I can't make you any promises. They are THE most likely to work of all the DL's made though. Just make sure you get the 2.4x ones, MKM-001-00 dye, made in Singapore.

If Sony don't have an update on the support page for your laptop model then you're probably out of luck. Of course you could always try emailing / contacting their support team to actually ask for one. Just mention the problem with it burning 'RICOHJPN-D01-02' media.

Yup, fair point. Consider it removed.

Yup, it's a simple CD burner, DVD reader. If you want to burn DVD's you'll need to buy a DVD burner.

I'd hoped the 'smashing chair' emoticon would have been a big enough clue

CD-TEXT only applies to a CD Audio (CD-DA) disc. If you're burning an MP3 data disc then whatever ID3 tags are in the files will still be there once they've been burnt to the disc. You burn an MP3 data disc using Build mode.

Please read the pink bit at the top of the forum.

Could you please answer the questions I posted above. If the files you're adding to the 'Source' box aren't correct then the little boot image isn't going to do anything. It's not a case of '1 boot image for all'.

Is that actually supposed to work anyway? The 2k boot image will be expecting a certain file in the i386 folder. Which options did you use for the bootable bit within ImgBurn? ImgBurn can extract boot images from CD/DVD discs too and it tells you everything you need to know about how to re-use them in the log.

ISO is a container format. Like a jar / box / tin. The contents of the ISO are what's important. So what files do you see on the disc once you've burnt it? Open it up via explorer / my computer and take a look.

Normally if the drive has 'CDRW' in the identifier it means it's a CD burner and a DVD *reader*. As such you won't be able to burn DVDs. Look in the ImgBurn log window, it'll tell you what type of drives are found. Copy + paste the line here if you like so we can see it too.

Ok I've added the 2 profiles / sizes you mentioned.

The ImgBurn.com one.

I did try docking mine but it wouldn't budge! Maybe it's only possible with 'Themes' disabled or something. Hopefully the changes I've made will work in both cases anyway.

Do you mean the taskbar? i.e. start button, quick launch, task buttons, system icons, clock etc? Even if it gets it wrong the first time it should still remember where you dragged it to the next time it starts. EDIT: Tested with taskbar at the top, the problem has now been fixed. Thanks

Update your drives firmware and try again. http://wwwbsc.pioneer.co.jp/cgi-bin/www1/d...109_FW158EU.EXE

Please post the log.

Happy Birthday! ...and thanks for the pic Altercuno

If a given ISO works when burnt to BD-RE but not BD-R then I guess the payers are either blocking playback on that type of media or they just can't read it at all (unsupported disc/dye).

That model is so old that it might not even support returning the media id of the current disc. I'd go for a new drive.

If the drive reports that the source disc contains 290,445 sectors, that's how many ImgBurn will read. The image being larger certainly isn't going to be causing corrupt files, after all, you've got more data, not less. The files will still be at the same LBA within the image no matter what size it is. If in doubt, make an image of the disc in ImgBurn and mount it in daemon tools. Then compare the files on the original cd to the virtual cd using whatever tool you prefer to use for that kind of thing (I like Beyond Compare).