-
Posts
30,521 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by LIGHTNING UK!
-
I'm sorry I didn't take you saying 'TS file' to mean a complete set of DVD Video files, how stupid of me. Try actually saying what you mean, it'll help the people trying to help you. Maybe you can read all the stuff I wrote in the pink box up the top and save me wasting more time by actually posting a log like it says to do. If the disc burns and verifies without errors or retries, there was no issue. Playback issues are not really our concern as they typically stem from bad source files or a bad player. I've put in a request to have the min search limit put down to 3. I've already updated the forum config to allow for 3 letters. If you actually search for 'DVD', it'll return 0 results (until the server is sorted) but if you search for 'DVD*' it should work. I can't imagine any of the results will be of any use to you anyway. edit: 3 letter search has been sorted now.
-
Is the drive not still making noises? What controller have you attached the drive to? Make sure it's on the Intel controller. Right click the drive selection box and pick 'Family Tree'. Close the prompt and copy + paste from the log window.
-
Cannot burn DVD with SPTI, but can with ElbyCDIO
LIGHTNING UK! replied to jontyy's topic in ImgBurn Support
TDSS is a very sophisticated rootkit and will probably go totally unnoticed by most software running on the infected system. You'd have to scan the problem drive within Hiren's XP. As you know it works fine in Hiren's XP, I'd probably consider just zero filling the entire hdd (again, using Hiren's - there's a nuke program on the initial menu) and installing from scratch. -
If it burnt and verified ok, the disc is 100% readable in your burner. (That's ImgBurn's job out of the way) It's then down to your standalone to: 1. be able to read the disc 2. be able to play its contents So if you're having problem with some stuff you're burning but not other stuff, and assuming you're using the same discs all the time, it must be an issue with what's on the disc. Check for firmware updates for your player and software updates for whatever's making the source files you're then feeding into ImgBurn.
-
Cannot burn DVD with SPTI, but can with ElbyCDIO
LIGHTNING UK! replied to jontyy's topic in ImgBurn Support
1. You can delete Upper and Lower filters directly in ImgBurn via the Tools menu, no need to invoke RegEdit at all. 2. Windows 7 seems to provide all users (with and without UAC enabled) with SPTI access to optical drives. 3. - 4. DMA sill applies. You just remove whatever controller entries you have listed in device manager under the IDE ATA/ATAPI branch. It would have helped if you posted a log from ImgBurn. If you install Unlocker and/or LockHunter, does anything get listed as locking the device when you right click on a problem drive in 'Computer' and select 'What's locking this file?' or 'Unlocker' ? Does ImgBurn have access to the drive if you boot up in safemode? What if you boot into Windows XP from something like the Hiren's Boot CD? There are some viruses/rootkits that can cause these kinds of issues - TDSS (and variants?) for instance. -
http://forum.imgburn.com/index.php?showtopic=8000
-
Post a log please - as per the pink box up the top
-
You just install over the top of the old one.
-
SPLIP is a flag, it's 1 bit in a byte. You set *it* to 0 or 1, not the whole byte - which shouldn't ever be changed to a fixed value. You take the original value, modify the bit and then write back the new value. http://dvd.sourceforge.net/dvdinfo/pgc.html#play Just forget about cells on a DVD5 disc being marked as non seamless (or 'layer break'). You marking a non seamless cell as seamless is probably what's making the PS3 mess up. The flag is there for technical reasons - none of which are anything to do with a physical layer break on the media - which obviously never existed in the first place. Anyway, I feel like I'm hitting my head against a brick wall with this one so I'll leave it at that. You wanted to know why the PS3 is failing to play your modified files and I've said it's probably because you've modified them! Leave them alone
-
If you just export the whole of 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}' to a reg file using RegEdit, you should be able to remove the upper and lower filter drivers using ImgBurn (or just delete all the entries in 'UpperFilters' and 'LowerFilters' from within that reg key), then reboot and test to see what happens. Fingers crossed, your optical drives should also work in safe mode once you've done that. If not (and if you start safe mode with network support), try this 'Microsoft Fix It' tool here - http://support.microsoft.com/kb/982116/en-gb Restore the filters by reimporting the reg file you created earlier.
-
If ImgBurn is still listing the size as 12219392 then you have nothing to worry about - just ignore Explorer, it's talking rubbish.
-
I still don't understand why you're touching anything on a DVD-5 disc. If it has cells set with SPLIP = 0 (what Ifoedit calls a 'layer break') then it will have them set like that for a reason... and it's nothing to do with a physical layer break. You changing them to 1 could be what's causing the problem.
-
You just press F8 the second windows starts to load. Your optical drive(s) should be visible in safemode, mine certainly is. Once you've booted in to Linux Live, can't you just add the 'Wine' application as you would do any other application? Then download and install ImgBurn from imgburn.com.
-
It can create an image file from a disc using Read mode. If you just want to copy the contents of a disc onto your hdd, use Explorer!
-
Are you actually making an image or burning directly to disc? You should make an ISO first and then burn that to disc. If your compilation contains loads of little files, turning off antivirus might help - each one will be scanned by AV when ImgBurn tries to read it and that'll slow things down.
-
BD-R and BD-RE (formatted to max capacity - i.e. spare areas disabled) are exactly the same size. They both end up with 12219392 sectors available for use. 12219392 * 2048 = 25,025,314,816 bytes / 1024 = 24,438,784 KB / 1024 = 23,866 MB / 1024 = 23.306640625 GB So there's your 23.3 GB.
-
That doesn't mean anything. CDs aren't DVDs. You might be able to hit a 10m wide target from 100m, it doesn't mean you could hit a 1m wide target from the same distance.
-
It's impossible to say 100% Put it this way, if they aren't, you need a new drive - and you'll still have the new/better discs to use in the new drive so you haven't really wasted anything.
-
Well, I wouldn't use anything other than Verbatim or Taiyo Yuden personally. Their discs are always the most reliable and produce the best quality burns.
-
Try the lower supported write speeds. Try cleaning the drive with a cleaning discs. RITEKF1 aren't great discs to start with and slimline drives are all pretty rubbish.
-
Post the full log please.
-
Do you actually have 2 drives in your machine? If you do, the 2nd drive must have an issue - check it in Device Manager. You might also like to check it in the BIOS at bootup and the cabling etc. If you don't, the drive you do have is just a DVD-ROM drive, it can't burn anything.
-
Remove ImgBurn from right-click context menu on dvds
LIGHTNING UK! replied to panacea's topic in ImgBurn Support
Your hidden post doesn't list 'HKCR\DVD\shell\Read using ImgBurn', only the current 'HKCR\DVD\shell\open.ImgBurn' version In any case, I've just checked the 2.5.6.0 uninstaller and it wipes that one out too (well, the 'HKCU\Software\Classes\DVD\shell\Read using ImgBurn' and 'HKLM\SOFTWARE\Classes\DVD\shell\Read using ImgBurn' ones anyway) - so it can't be that - assuming the OP did actually try installing + uninstalling 2.5.6.0. -
That's all fine and perfectly normal. The disc has been formatted to the maximum capacity. As for the speed, it's not an exact science. Different drives use different values to mean the same thing and so it makes using a single calculation to go from KB -> Speed a bit hit and miss. The speed descriptors reported by the drive are also only accurate to +- 10%. Going by the figures your drive returns and taking 1x BD speed to equal 4495 kB/s (1kB = 1000 bytes)... 35903 / 4495 = 7.9873192436040044493882091212458 10338 / 4495 = 2.2998887652947719688542825361513 35903 / 8 = 4487.875 10338 / 2.3 = 4494.7826086956521739130434782609 So where ImgBurn calls it 2.4x in the current version is probably wrong, it should say 2.3x instead. It's caused by the program using a 2nd calculation (based on a slightly different 1x speed) if the first doesn't end up at a whole number (i.e. 2x, 3x, 4x etc, because speeds typically are). I've now made the program only use the result of the 2nd calculation if its result is a whole number, otherwise it just sticks with the result of the 1st one. Compare those speed values/calculations to what something like an iHBS112 returns... 35960 / 4495 = 8 8990 / 4495 = 2 35960 / 8 = 4495 8990 / 2 = 4495 Clearly those are much nicer to work with! And then back to an LG drive (BH12LS38) for a BD-RE DL disc... 21668 / 4495 = 4.8204671857619577308120133481646 8991 / 4495 = 2.0002224694104560622914349276974 21668 / 4.8 = 4514.1666666666666666666666666667 8991 / 2 = 4495.5