LIGHTNING UK!

Sorry, what I meant was that svrapi.dll shouldn't be present on a Windows NT based OS - or at least not XP onwards (not sure about NT4). Just delete it. Cynthia, yeah I noticed that earlier too That's Microsoft's stupid max width/word wrapping on MessageBoxes (from Vista onwards).

Yes, you're out of luck. I've never seen any booktype commands for Matshita drives so I doubt they're capable of doing it - unless the drive does it automatically anyway (like Pioneer drives).

http://forum.imgburn.com/index.php?showtopic=18825 You've got a rogue copy of svrapi.dll on your system that shouldn't be there. Thanks for the report on the email link not working, I've fixed that now.

I'd say your drive doesn't like the media you're using. Buy some better discs - Verbatim or Taiyo Yuden. You could try the remaining supported speeds first though - you've already tried 'MAX' (i.e. 8x)

If you want to keep them in avi format you just add both files in Build mode. If you don't want to keep them as avi files, you don't want ImgBurn! Convert them to DVD Video format using other tools - such as DVD Flick, ConvertXtoDVD etc. Then burn the DVD Video folder/files (VIDEO_TS folder with IFO/BUP/VOB files) using ImgBurn in build mode - there are loads of guides for that in the guides section.

http://forum.imgburn.com/index.php?showtopic=8000

You can't, ImgBurn doesn't support multisession in Build mode. Do as your friend did and use the drag+drop burning built into Windows. (unless you're still running Windows XP which can only burn to CD) Failing that, use another app. That doesn't of course mean you have to remove ImgBurn. There's no law (that I know of) preventing you from having more than 1 tool for the job!

What's this device? Vodafone something. Unplug it. or disable the device's CDROM emulation by issuing the following AT command (via a serial program like hyperterminal) AT^U2DIAG=0

Read some xbox related news sites (one that actually deals with this stuff) and I'm sure you'll find the reason.

If PaintShopPro associated itself with and made itself the default app for a file extension supported by ImgBurn, that would explain it. The problem with using something generic like 'PSP7.image' is that a change made under 'PSP7.image' will apply to ALL the file extensions that redirect to it. so where you've got .jpg -> PSP7.image, there could also be .img -> PSP7.image. If ImgBurn then (quite harmlessly) adds an option in PSP7.image that technically allows for a 'Write using ImgBurn' option on the context menu of IMG files, that option is then available for both .jpg and .img. If PSP had used 'PSP7.image.jpg' and 'PSP7.image.img' instead (no longer generic), ImgBurn would have only added itself under 'PSP7.image.img' and your .jpg file extensions wouldn't have been touched. You could just search for psp7.image in regedit and delete everything you find. It should just be in those '(Default)' values and then perhaps an actual 'HKCR\PSP7.image' key.

It sounds like your file associations have got messed up. There are quick ways of fixing it and proper ways. The quick way would be to right click the file, select 'open with', pick windows picture and fax viewer' from the list of app and tell windows to always use that app for that file type by ticking the checkbox. Another quick way would be to click Tools -> Folder Options in an Explorer window, then switch to the 'File Types' tab, find the file extension in question and change the app that opens it. The proper way (and way you'd find out WHY it happened) would be to open RegEdit (via the Run command - Windows key + R), expand HKEY_CLASSES_ROOT and find the file extension (e.g. .jpg) Read the value of '(Default)' from the right pane and then navigate to that in the left pane (e.g. jpegfile) - if it's empty, stay where you are. The stuff under the 'shell' branch is what you see when you right click the file. If you let me know what it says, I'll tell you what happened and why - plus find the app that caused the problem in the first place.

Varbatim's BD-RE DL discs are quite new to the market. The GGW-H20L is quite old now and would have only gained support for the MID in the most recent firmware - as such, it probably hasn't had a chance to mature yet. Hopefully a new disc will solve the problem, but you shouldn't be totally surprised if it doesn't.

If you actually scroll down to the fix-it util you'll see that Windows 7 is listed. Ideally, you should have all the autorun settings configured as below in the registry. HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer -> NoAutorun = [REG_DWORD] 0x00000000 (0) HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer -> NoDriveAutoRun = [REG_DWORD] 0x00000000 (0) HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer -> NoDriveTypeAutoRun = [REG_DWORD] 0x00000091 (145) HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer -> NoAutorun = [REG_DWORD] 0x00000000 (0) HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer -> NoDriveAutoRun = [REG_DWORD] 0x00000000 (0) HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer -> NoDriveTypeAutoRun = [REG_DWORD] 0x00000091 (145) HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon -> allocatecdroms = [REG_SZ] 0 HKLM\SYSTEM\CurrentControlSet\services\cdrom -> AutoRun = [REG_DWORD] 0x00000001 (1) Please try something out for me... Once you've burnt a disc, close ImgBurn. Now load it again and make sure it's just in the 'Ez-Mode Picker' mode (with the 6 big buttons on the screen) and also load a program called DebugView ( http://technet.microsoft.com/en-us/sysinternals/bb896647 ). When you eject/insert a disc in the drive you should see 'Media in drive x: just arrive/removed' entries in the DebugView window. Just check you're actually getting those please.

If the drive reported an error when attempting to do a full erase on the disc, there's something it doesn't like about it. At that point you could try a 2nd and 3rd time. If they all fail, write the disc off and get yourself another one.

lol sure, just delete the image yourself when you're finished with it. The hand is a feature of a program called SnagIt. Yes, Audio CDs will use bin+cue.

Your machine should have created a dump file when it BSOD'd. It's usually stored in the Windows directory as memory.dmp or similar. I typically view them in WinDgb (from Microsoft) but you could use this - http://www.nirsoft.net/utils/blue_screen_view.html

It's not for me to tell you how you use my program. Use it however you like. For your sake, just make sure you're legally allowed to make copies of the disc. All you do is make an image using Read mode (saving it on your hdd) and then write it as many times as required. In the end you'll have a bunch of images on the computer's hdd that will enable you to burn extra copies later down the line without having to dig out a source disc.

What error messages? There's already an option to follow junctions - Tools -> Settings -> Build -> Page 1 -> 'Advanced' box -> Include Reparse Point Files

Those options aren't ImgBurn options, they represent how your OS is currently configured. What happens if you burn a disc, close ImgBurn, press F5 to refresh the 'My Computer' window, eject the disc, F5 again, insert the disc, F5 again? The drive icon should be changing during those different states/stages. There's a Microsoft Fix It for Autorun stuff too - http://go.microsoft.com/?linkid=9743275 (found here http://support.microsoft.com/kb/967715 )

The chipset driver won't have done any harm. It's an Intel one and will only install what's compatible with your machine. You should look into the cause of the BSOD. The (mini)dump logs usually provide enough info about what driver crashed. Filter drivers will always show up (they're values in the registry), they just shouldn't really get loaded - that's the whole idea of safemode (so as to get around issues).

Believe me, what you posted cannot ever be the only thing written in that box. It's the last thing written in that box (last section anyway).

We need to see the burn+verify log from ImgBurn.

Most autorun settings can be manipulated by ImgBurn itself. Go into Tools -> Settings and look on the Device tab.

http://forum.imgburn.com/index.php?showtopic=8000

Nope, and it wouldn't work anyway. You'd need a firmware update from Acer.