boco
-
Posts
12 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by boco
-
-
Note if you have a tool with a bundled version of ImgBurn (like DVDFlick) the internal update mechanism of ImgBurn will do no good. It just directs you to the Homepage and lets you download the installer, which will only install or update the installed version. The bundled ones are pretty much standalone/portable and must be updated manually.
-
Use the force, Luke - just click the calculator icon on the main Build window. ImgBurn will then snoop through your project and tell you about problems and necessary adjustments in the log. Just check that in the settings (Build Page 1) you did not disable any "Logging" options.
-
Users with a regular Windows account (one that doesn't have Admin rights) usually do not have permissions to burn media/SPTI in general. That has to be allowed by the system administrator.
-
By true DVD I mean the video and audio data being in a format satisfying the DVD-Video specifications. That format will (read: should) be recognized and played by all players bearing the DVD logo.BOCO - your english is quite good. You mention "true" DVD...Please explain. -
1. Normally "Build" mode, but with these WMV files alone you'll probably get a data disc only which the player may reject.
2. If you want a true DVD you have to use a DVD authoring program to get them into the correct format. The end result should be a VIDEO_TS folder with IFO, BUP, and VOB files in it. That folder will be recognized by ImageBurn in Build mode as representing a DVD VIDEO disc.
3. and 4. Logically, you must use discs both your burner and the player support. Just be aware that disc types ending with "RW" or "RE" are rewritable/erasable and not meant for long-term storage. You should use high-quality discs of the "R" type which can be recorded only once.
A remark to quality: Optical media degrade over time, and cheap dyes degrade faster. To enjoy your DVDs a long time, don't use cheap brands.
Sorry for the awful English.
-
Is ImgBurn the origin of said filter?Filter Name: cdrbsdrv
File Name: C:\Windows\system32\Drivers\cdrbsdrv.sys
File Version: 8. 0. 0. 5 [8.0.0.5]
File Description: CD-ROM Filter Driver for WindowsXP x64Edition
Product Name: B's Recorder GOLD
Product Version: 8. 0. 0. 5 [8.0.0.5]
Company Name: B.H.A Corporation
Copyright: Copyright © 2000-2006 B.H.A Corporation
It clearly isn't.
-
No problem. Btw. you can change AutoSandbox settings from the "Additional Protection" tab in avast! My recommendation is setting AutoSandbox mode to "Ask", so it will request confirmation. And you should exclude Shrink and ImgBurn from Sandboxing, so you do not have to disable protection to run it.
-
Hi,
I just wanted to throw in an idea. Do you maybe use avast! as your anti-virus solution at home? Avast! in version 6 has a new feature called Auto-Sandboxing. So your problem may be just that you're running these programs sandboxed by accident, which gives them very limited access. If I remember correctly, programs running sandboxed by avast! have a thin red frame border around them.
-
Maybe you could state that in the option's tooltip (if there's no intent to change it)? Possibly even disable MD5 generation if a split image is to be created...
-
Another possible bug I encountered:
I have MD5 file creation for images enabled in the settings. That works great for normal images (one big file). However if that image is split...
Example:
One has read and stored an split image and created the MD5 digest.
DVDImage.i00
DVDImage.i01
DVDImage.i02
DVDImage.mds
DVDImage.md5
But when looking inside the .md5 file, there's something like that:
# MD5 checksum generated by ImgBurn v2.5.5.0 (http://www.imgburn.com) 0123456789abcdef0123456789abcdef *DVDImage.i00
ImageBurn basically slaps the name of the first part on the MD5 of the whole (unsplit) file. I would have expected multiple MD5 sums of the split parts for easy external verification.
(I don't think a log is really needed here).
-
Hi ImgBurn people. Long-time user, long-time lurker, only now my first post (ImgBurn is very reliable, so I didn't have to post, yet). But now there's a small problem I wanted to report.
I scanned the FAQ and did a search, but couldn't find anything like that.
If selecting .ccd in the Read settings, ImageBurn creates a .ccd image layout file and forces the main image extension to be .img, which is correct for a CloneCD compatible image. Now to the problem: A CloneCD image consists of three files - a .ccd file (layout), a .img file (main image) and a .sub file (subchannels). I certainly know that ImageBurn doesn't care about subchannel data, which is fine with me. However, the .sub file itself is mandatory. For example, trying to mount it in DTPro greets me with the following message: (file attached at the end)
Would it be possible to write a (dummy) .sub file at image creation? It would only need to contain empty subchannel data, but must be present. Or is there something I'm doing wrong?
Here's the log creating the image, for completeness (and not to be beaten, lol):
I 16:35:16 ImgBurn Version 2.5.5.0 started! I 16:35:16 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1) I 16:35:16 Total Physical Memory: 3.930.548 KB - Available: 2.393.896 KB W 16:35:16 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 16:35:16 Initialising SPTI... I 16:35:16 Searching for SCSI / ATAPI devices... I 16:35:16 -> Drive 1 - Info: FARA ATAPI001 YRS5 (B:) (ATA) I 16:35:16 -> Drive 2 - Info: HL-DT-ST DVDRAM GSA-T50N RP05 (F:) (ATA) I 16:35:16 -> Drive 3 - Info: AZERTY THASDFABFRT 1.00 (G:) (SCSI) I 16:35:16 -> Drive 4 - Info: QWERTY -DEAD-BEEF- CAFE (H:) (SCSI) I 16:35:16 -> Drive 5 - Info: VSN 9Y78XEV4 3.5Z (I:) (SCSI) I 16:35:16 Found 1 DVD±RW/RAM and 4 BD-ROMs! W 16:35:30 Destination File renamed to: WeakSectors_TEST__CD$.img I 16:35:30 Operation Started! I 16:35:30 Source Device: [5:1:0] QWERTY -DEAD-BEEF- CAFE (H:) (SCSI) I 16:35:30 Source Media Type: CD-ROM I 16:35:30 Source Media Sectors: 238.112 I 16:35:30 Source Media Size: 487.653.376 bytes I 16:35:30 Source Media Volume Identifier: WeakSectors_TEST__CD I 16:35:30 Source Media Volume Set Identifier: 4D3022200000003D I 16:35:30 Source Media Application Identifier: _ I 16:35:30 Source Media Implementation Identifier: mkisofs I 16:35:30 Source Media File System(s): ISO9660; Joliet; UDF (1.02) I 16:35:30 Read Speed (Data/Audio): MAX / 8x I 16:35:30 Hardware Read Error Retries: 1 I 16:35:30 Destination File: Q:\WeakSectors_TEST__CD$.img I 16:35:30 Destination Free Space: 665.704.792.064 Bytes (650.102.336 KB) (634.865 MB) (619 GB) I 16:35:30 Destination File System: NTFS I 16:35:30 File Splitting: 2 GB I 16:35:32 Reading Session 1 of 1... (1 Track, LBA: 0 - 238111) I 16:35:32 Reading Track 1 of 1... (MODE1/2048, LBA: 0 - 238111) I 16:36:11 Image MD5: 03d779ab67c45b832744512c8c4af501 I 16:36:11 Exporting Graph Data... I 16:36:11 Graph Data File: C:\Users\Boco\AppData\Roaming\ImgBurn\Graph Data Files\QWERTY_-DEAD-BEEF-_CAFE_2011-02-05_04-35_PM_N-A_WeakSectors_TEST__CD(1).ibg I 16:36:11 Export Successfully Completed! I 16:36:11 Operation Successfully Completed! - Duration: 00:00:41 I 16:36:11 Average Read Rate: 11.615 KB/s (77.4x) - Maximum Read Rate: 13.584 KB/s (90.6x)
2.5.8.0 Installer exits/crashes
in ImgBurn Support
Posted
Same issue with Vista 32bit. The installer crashes when it attempts to display the License agreement. Strangely, the faulting module is kernel32.dll.
Workaround: Run the installer from a console / command line window, using the /S (silent) parameter. The visible parts of the Setup are not called in this case and the program is installed successfully.
SetupImgBurn_2.5.8.0.exe /S