-
Posts
30,521 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by LIGHTNING UK!
-
Do you have 'Show All Devices' enabled in the settings on the 'I/O' panel ? If not, it certainly is strange that a USB stick would identify itself as a CD/DVD writer! That aside, no matter which drive I have selelcted when I close the program, if I specify one via the CLI, it goes to it. What happens if you use drive letters instead?
-
For DVD+RW, by default it should read the size from the filesystem - assuming it can understand it! It's the 'DVD+RW Capacity' option in the settings on the 'Read' tab. As a formatted DVD+RW always returns its size as being the ENTIRE size of the disc, not just the data, you have to rely on the filesystem values - depending on the users settings of course. When you're in read mode, it should tell you the filesystem capacity info in the info panel on the right. i.e. PLEXTOR DVDR PX-760A 1.06 (ATA) Current Profile: DVD+RW Disc Information: Status: Complete Erasable: Yes Formatted: Yes Sessions: 1 Sectors: 2,295,104 Size: 4,700,372,992 bytes Time: 510:03:29 (MM:SS:FF) File System Information: Sectors: 2,271,266 Size: 4,651,552,768 bytes Time: 504:45:41 (MM:SS:FF) When you try to read the disc, it should only read 2271266 sectors, not 2295104 if the option is set to 'File System' rather than 'Disc'
-
Are you in 'Build' mode ? Is 'Output' set to 'Image File' ? If you answer 'No' to either of those, that's why you can't output to an ISO.
-
It doesn't really matter what YOUR laws are, mine state I cannot provide a program that circumvents copyright protection.
-
The screenshot you've got there should work fine. You've already filled in the destination. So long as the I: drive actually exists, I see no reason for it to fail.
-
Drag and drop bug in v2.2.0.0 and Vista 64-bit
LIGHTNING UK! replied to RiPPn's topic in ImgBurn Bugs
Ok, I tried a fresh install of Vista Ultimate x64 and it appeared to work fine to me. -
Drag and drop bug in v2.2.0.0 and Vista 64-bit
LIGHTNING UK! replied to RiPPn's topic in ImgBurn Bugs
Hmm works ok in 32 bit at least. I'll try 64 bit when I can. What exactly does it do / not do? Do you just get the 'stop' circle cursor thingy all the time? -
No No Sorry but you really need to take a look at a forum that deals with this kind of stuff. This isn't an ImgBurn issue and so it's not really the best one to ask such questions on.
-
Sorry, I totally misread your original post. I thought that error had popped up when you were just burning normally. I'd expect it to fail if you did it manually - as it's not one that should be called on a CD. As you seem to have found out, ImgBurn always closes / finalises everything.
-
Nope, I have no plans. I just implement what I feel like implementing.
-
Drag and drop bug in v2.2.0.0 and Vista 64-bit
LIGHTNING UK! replied to RiPPn's topic in ImgBurn Bugs
Hmm that's an odd thing to break! I'll look into it. -
You could also make a .dvd file (plain text file with .dvd file extension) containing the text: layer0.dat layer1.dat or use the 'create dvd mds file' feature, add the two files and make a .mds file. Then load the .mds file in Write mode. Then imgburn will treat the 2 files as a single large file.
-
Post the full log please. I'm guessing your drive doesn't support the command used to determine the current media type and so it's using a 'fall back' function that just tries all the different close methods.
-
Hmm interesting... I had this issue with 98 / NT4 after I started using the TntControls for Unicode stuff. I updated TntControls a few times during the beta cycle and the problem went away. I did test it on NT4 before releasing it but I guess my version already had that file installed from my playing around during early beta testing. Weird that it didn't error out on 98 at the time of release though, and I made sure the msimg32 file didn't exist too! I've attached the msimg32.dll file to this post. Just stick it in the ImgBurn forlder or in your system dir. MSIMG32.zip
-
I doubt it, there's very little call for such things. Not only that, I've no idea what they are
-
Write a batch file to do the job and then add it to the scheduled tasks list in windows.
-
Yeah this is nothing to do with the ImgBurn program. Please visit the appropriate site for whatever tool you're using - it's not this one.
-
But incd only causes problems due to the type of software that it is. It won't affect ImgBurn any more/less than it would do any other burning software. Packet writing software is just pretty awful in general.
-
How exactly are you 'ripping' it ? ImgBurn's 'Read' mode will do a 1:1 copy of the disc to an image file. If you load up the image in ImgBurn as if you were going to burn it, what's does it say on the main screen for sector size / mode / type etc? Does ImgBurn see the image as being bootable? Read it again and copy + paste the log. Maybe we'll spot something.
-
It's only useful in the sense that we can see there's a problem with your drive burning to media - even decent media! (and we already kinda knew that) Now's a good time to run to the shops and pick up that 112 I'll be doing the same thing later on today
-
ImgBurn isn't there to allow you to copy movies (it won't, end of story), it's a burning tool and is a complex as a burning tool needs to be.
-
cannot read from file xxx.dll. Reason: The parameter is incorrect.
LIGHTNING UK! replied to mike s's topic in ImgBurn Support
It might be locked or something. What's the exact file name / path? Maybe a Google search will bring up something about it. -
You can already turn those off in the settings.
-
It compares it sector by sector. The MD5 stuff is just an added bonus. It's calculated but isn't used anywhere, only displayed in the log.
-
I wouldn't worry too much, I often leave the door shut on one of my pc's too and the drives don't seem to care that the tray won't open, they just give up trying to eject it after a few seconds.