LIGHTNING UK!

I've just downloaded SMS v2.3 and I'll have a play around with it when I get a chance.

So you're in Build mode and 'Output' is set to 'Device' yeah? When you've got a blank DVD+R DL in the drive, please copy + paste all the text from the 'Device' tab within the main window. Then once you've added your VIDEO_TS folder to the source box and hit calculate, please tell me exactly what it say in whatever box pops up. A screenshot could be useful.

Can you please just confirm the 'Lock Volume - Exclusive Access' option is still checked in the settings on the 'Write' tab. You should also update DT and install the 1.50 SPTD interface.

Does it also look like that under windows?! If not, it would appear there's some weird issue with sms - or it's done on purpose to save you drilling down loads of folders?

It means the drive doesn't like the media you're using. See if there are any firmware updates available for the drive, they help fix these kinds of issues. If you're not already doing so, start using decent media. Verbatim / Taiyo Yuden discs are the ones we recommend.

Click the 'Advanced' tab and you'll see one called 'Restrictions'. Sorry, I don't really know what you mean by: 'Inside the directories i can see the contents of the next folder as well!Y?' Any chance of a screenshot?

That's just how the specs were defined. As I say, just relax the restrictions and you'll be able to use longer ones.

Considering the drive is supposed to be locked for exclusive usage (unless you disabled / ignored that feature?), opening 'My Computer' shouldn't do anything at all. In any case, the drive should be able to recover from interruptions due to burnproof type technology. It's therefore most odd that you're having problems.

I don't do anything with DVD Audio discs/files and it's very unlikely that I ever will. I've no interest in them myself, and the demand is very low. It's just not worth the hassle, sorry.

ImgBurn is just a burning tool. What goes in is what comes out. You cannot manipulate anything.

If you add the 2 files into ConvertXtoDVD (divxtodvd is the old name for the program - perhaps you need to update), it makes a menu for them anyway.

All parts of the image (i.e. all 3 files) MUST be burnt at the same time (and to the same disc). They are part of 1 larger 'disc image' file. If any one of them is missing, the disc would be useless / incomplete.

Nice one lfc Hoorah to UKTV G2 for showing all the old Top Gear eps! Although I'd already heard it, the one about Hammond's crash did make me chuckle.

If you're building on-the-fly (i.e. the 'output' is set to 'Device'), it should know you're not using a DL disc and not prompt. If you're creating an image file first, it'll go by the settings.

That's life though isn't it?! If you mess up driving (by going on the wrong side of the road for instance), you crash your car So long as you're not trying to force flash your drive with the wrong firmware, there's no reason for things to mess up. Sites have to issue warnings about such things to cover their own backs. I update my drives all the time and I never really bat an eyelid. It might be scary the first time you do it, but after that it's like 2nd nature.

Are you using discs that your drive supports? Have you tried checking for firmware updates for the drive? As it appears to only be a DVD+ (plus) format burner, now might be a good time to buy yourself a decent up-to-date drive. That thing you're running must be a good few years old now.

Make is smaller with something like Nero Recode.

LITE-ON DVDRW LH-20A1H LL0B (SCSI) Media Information: LITE-ON DVDRW LH-20A1H LL0B (SCSI) Current Profile: DVD-RAM Disc Information: Status: Others Erasable: Yes Supported Write Speeds: 6x, 8x, 12x TOC Information: Session 1... -> Track 01 (Mode 1, LBA: 0 - 2236703) -> LeadOut (LBA: 2236704) Physical Format Information (Last Recorded): Disc ID: MXL22 Book Type: DVD-RAM Part Version: 7 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 1 Track Path: Parallel Track Path (PTP) Linear Density: 0.280 to 0.291 um/bit Track Density: 0.615 um/track First Physical Sector of Data Area: 200,704 Last Physical Sector of Data Area: 2,514,783 Last Physical Sector in Layer 0: 0 Current Format Capacity: Sectors: 2,236,704 Size: 4,580,769,792 bytes Time: 497:04:54 (MM:SS:FF) Preferred Format Capacity: Sectors: 2,236,704 Size: 4,580,769,792 bytes Time: 497:04:54 (MM:SS:FF) Maximum Format Capacity: Sectors: 2,295,072 Size: 4,700,307,456 bytes Time: 510:02:72 (MM:SS:FF) Erase: I 19:02:32 ImgBurn Version 2.3.2.5 Beta started! I 19:02:32 Microsoft Windows Server 2003, Standard Edition (5.2, Build 3790 : Service Pack 2) I 19:02:32 Total Physical Memory: 3,406,220 KB - Available: 2,127,296 KB I 19:02:32 Initialising SPTI... I 19:02:32 Searching for SCSI / ATAPI devices... I 19:02:33 Found 3 DVD-ROMs, 2 DVD?RWs and 4 DVD?RW/RAMs! I 19:03:31 Operation Started! I 19:03:31 Device: [5:0:0] LITE-ON DVDRW LH-20A1H LL0B (O:) (SCSI) I 19:03:31 Media Type: DVD-RAM (Disc ID: MXL22) (Speeds: 6x, 8x, 12x) I 19:03:31 Quick Erase: No I 19:03:31 Erasing Disc... I 19:15:29 Operation Successfully Completed! - Duration: 00:11:58 Results: I 19:18:46 ImgBurn Version 2.3.2.5 Beta started! I 19:18:46 Microsoft Windows Server 2003, Standard Edition (5.2, Build 3790 : Service Pack 2) I 19:18:46 Total Physical Memory: 3,406,220 KB - Available: 2,149,304 KB I 19:18:46 Initialising SPTI... I 19:18:46 Searching for SCSI / ATAPI devices... I 19:18:51 Found 3 DVD-ROMs, 2 DVD

Media: Maxell 12x DVD-RAM [MXL22] Burnt With: LITE-ON DVDRW LH-20A1H LL0B (SCSI)

For DVDs, yes. For CDs that would required 'RAW' mode, no. When burning CD's the program uses SAO and works with the user data areas, not the subchannel / leadin / leadout ones. So it all depends on what you're really asking about! For normal data discs, yeah it's pretty much 1:1. If you've got anything with protection on it, no it's not 1:1.

It's the size of one of the files inside the image that's important, not the size of the image itself (i.e. the total size). Where you'd normally be limited to a file Apologies if you already meant one of the files was > 4GB in size

I think they mean file size donta, not file name length Yes it supports large files if you just use UDF.

This is a recent Wine problem. They did a patch for another unicode issue a few days (weeks) ago, and now it's broken other stuff. Take a look at the bugs page at winehq and you can see their progress with the issues. http://bugs.winehq.org/show_bug.cgi?id=7512 http://bugs.winehq.org/show_bug.cgi?id=8963 http://bugs.winehq.org/show_bug.cgi?id=8624 So going by those, they've pretty much all been resolved now. Update to the latest version of Wine perhaps?

Build mode was designed to work form an existing folder layout / hdd structure. If I ever change that, it will of course become much more flexible.

Try Nero Recode, it's basically an updated version of DVDShrink anyway.