LIGHTNING UK!

Your drivers for whatever controller that drive is connected to are blocking the command. Update/get rid of them.

The dye is different between the 2.4x ones and the 8x ones. You might find that drives prefer the 2.4x ones - after all, they've been around a lot longer! As for buying ones from Singapore on the internet, I would suggest you contact the company and ask them directly.

Try using the eject button in ImgBurn.

Yup, it sure does.

Ok, you got a totally different error that time. It's looking more and more like a disc issue. Try the decent Verbs/Taiyo Yudens and get back to me if it still happens.

I'll need an 'I/O Debug' enabled log of you attempting the same thing please. All you have to do is press F8 before you click the 'Write' button. Probably best to save the log as a file and upload/attach it to your post rather than doing copy+paste (it'll be a lot longer!)

See now if you'd actually mentioned the error in your first post you could have avoided getting the reponse you did from me. We can't guess what the problem is, you have to tell us. In this case, yes your VIDETO_TS.IFO is corrupt and that's nothing to do with ImgBurn.

RegKill.sys is causing it and it's actually wmplayer.exe that's initiating it. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0012e705, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 88be03f5, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 81d275a0 Unable to read MiSystemVaType memory at 81d086a0 0012e705 CURRENT_IRQL: 2 FAULTING_IP: RegKill+3f5 88be03f5 ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: wmplayer.exe TRAP_FRAME: 87403d9c -- (.trap 0xffffffff87403d9c) ErrCode = 00000000 eax=0012e700 ebx=854bf4b0 ecx=83d0fe88 edx=0861000a esi=83a57788 edi=83a578af eip=88be03f5 esp=87403e10 ebp=87403e4c iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 RegKill+0x3f5: 88be03f5 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from 88be03f5 to 81c493d4 STACK_TEXT: 87403d9c 88be03f5 badb0d00 0861000a c026928c nt!KiTrap0E+0x2ac WARNING: Stack unwind information not available. Following frames may be wrong. 87403e0c 88be0493 854bf4b0 0012e700 81c34ae0 RegKill+0x3f5 87403e4c 877980fb 83a57788 87403e6c 87798148 RegKill+0x493 87403e58 87798148 83a57788 00000000 83c67a68 ataport!IdeCompleteIoctl+0x17 87403e6c 8779c76f 83a57788 84229970 83cbd1eb ataport!ASyncScsiPassThroughCompletion+0x12 87403e8c 8779c806 83a57788 83c67a68 83cbd178 ataport!PortpCompleteRequestIrp+0x57 87403ea0 81c34ae0 00000000 83cbd178 83c67a68 ataport!PortpAsyncCompletion+0x1e 87403ed4 877952c9 83d0fe30 83a3b2e8 87403f04 nt!IopfCompleteRequest+0x12d 87403ee4 87795cac 84229970 83cbd178 83d0fe30 ataport!IdeCompleteScsiIrp+0x31 87403f04 87792fdc 84229970 00000000 87403f34 ataport!IdeCommonCrbCompletion+0x44 87403f14 87797e39 841e20e0 83a3b2e8 83a3b2e8 ataport!IdeTranslateCompletedRequest+0x3e 87403f34 8779806f 841e20e0 83a3b2e8 81cec820 ataport!IdeProcessCompletedRequests+0x121 87403f88 81c6b07e 841e209c 841e2028 00000000 ataport!IdePortCompletionDpc+0xab 87403ff4 81c3751d a04c145c 00000000 00000000 nt!KiRetireDpcList+0x147 87403ff8 a04c145c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x3d 81c3751d 00000000 0000001a 00c1850f bb830000 0xa04c145c STACK_COMMAND: kb FOLLOWUP_IP: RegKill+3f5 88be03f5 ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: RegKill+3f5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: RegKill IMAGE_NAME: RegKill.sys DEBUG_FLR_IMAGE_TIMESTAMP: 3c8ad50e FAILURE_BUCKET_ID: 0xD1_RegKill+3f5 BUCKET_ID: OLD_IMAGE_RegKill.sys Followup: MachineOwner ---------

http://forum.imgburn.com/index.php?showtopic=4632 If you'd read the pink bit at the top of the forum you could have found that out for yourself.

It's the same code, take other things into account. The program is only ever waiting on the drive so just press F8 to enable I/O debug mode and you can see what the program/drive are saying to eachother via the messages in the log window.

That box is nothing to do with being seamless or not, it's purpose is to make you select a layer break position - so I have to ask, are you intentionally burning a double layer disc or have you got DVD Flick configured incorrectly? That box has been in ImgBurn for ages now, probably since day 1 (well, when Build mode was introduced anyway), so you'd have seen it before now if everything else was the same.

I can't locate such a message in my code. Can you provide a screenshot or the EXACT wording?

It'll be in 2.4.1.0 when that's released. Hopefully that won't be long! lol (Been saying that for 3 weeks )

Ditch the jmicron and install a Silicon Image 680 PCI card (

Ah yes, this is what happens when you burn to discs that have no concept of tracks or the amount of data burnt to them. (That's what DVD+RW are like) You have to rely on info from the file system - which may or may not be accurate. Anyway, the problem here is that I've obviously not tested this fallback method enough with discs not using UDF files systems (UDF discs are ok) and it turns out that I'm subtracting 1 from the size (to get the last sector number rather than the actual size) twice. My bad! It's fixed now, thanks.

What controller is it actually connected to? My jmicron one gave me the same problem, hence why I don't use it. It probably only likes short cables and mine have to be quite long because i have a huge case. Look in your motherboard manual and find out which IDE socket is which if you have a few of them.

You can mount your ISO in daemon tools (as a virtual drive) and play it from there. It might save you some time when checking / testing things.

Sorry, yes it's the 'Perform OPC Before Write' one.

Maybe it's a new feature in Showtime, I wasn't aware that it could read ISO's like that properly.... then again, maybe it's not. Maybe it's just playing the first bit of data it comes across without really knowing what it is. Can't say as I've ever tried though to be honest and I don't generally have Nero installed. Building an ISO and burning is the same as Building directly to disc. There must be some other issue here. Are you not even able to select the audio stream via the context (right click) menu in showtime?

Since when does ShowTime play from an ISO file? Aren't these the same thing?

That's ok, I really have no idea what you're doing/talking about either! I thought I did but then you post something else and I just think.... why?! Do you actually want the systemrescuecd-x86-1.0.0.iso image on the disc which then becomes an option in your boot menu? If not, what is it's purpose? Yeah that's right. The bootable bit of that image is not a floppy disc image, it's a custom one. It probably invokes some other file within that image that then does all the hard work. That C:\BootImage.ima is what should go into the 'Boot Image' field on that tab. 'Emulation Type' should be set to None (Custom). Leave 'Developer ID' blank Leave 'Load Segment' on 07C0 Sectors to load should be 4. As you can see, all that info is in the log for you to just copy out. I tried to make this stuff easier! lol

As I mentioned in my above post, when you extract the boot image via the 'Extract Boot Image' option, the program logs everything you need to know in order to fill out the boxes and create a new bootable image with new 'Source' content. If you've only got a 2k file it's obviously not emulating a FDD, it's a custom boot image with 4 sectors that need to be loaded. (each being 512 bytes) I'd expect the menu program to parse the image properly and read the El Torito file descriptor for all the info it needs.

The drive might pad the end of the disc so both layers are equal (you wouldn't know it's doing it apart from noticing it's taking a long time to close the disc) but ImgBurn does it's own padding at the start of the disc so the cells can be aligned in nice places for a layer break. I'm pretty sure DVD+R DL came before DVD-R DL so if anything, DVD+R DL would be more compatible as that's what the manufacturers would have implemented support for first.

I know el torito, that's what ImgBurn has to write the descriptors for in the file system! It was the booting of other bootable images within the bootable images that interested me! Normally your bios handles the bootable bit but it would only do that for the physical disc, not the images inside it. They must have made some funky program stored within the boot image of the physical disc to do that bit - and that's what I thought was cool.

You should be adding the normal disc content in the 'Source' box on the left and then adding the *.ima file to the bootable disc tab. i.e. the remaining (as you call it) 178MB goes into the source box. Get the files out of the non booting 178MB iso using something like daemon tools, winrar, 7zip, isobuster etc. Add those to the source box, put the ima in the bootable tab with the correct settings (they go into the log when you extract it) and then build your new iso. Add that new iso to the disc with the boot menu.