Jump to content

ilitws

Members
  • Posts

    42
  • Joined

  • Last visited

Everything posted by ilitws

  1. I did that. I've tried my best. This is how I understand when to use which mode while writing CD in ImgBurn 2.5.1. Have I understood it correctly? 1) The user needs to decide which of the 4 modes is best suited to the task. Fundamentally it is the drive i.e. firmware which supports or not supports the 4 various CD writing modes. If you have the appropriate firmware (not merely the latest update of the given firmware) it would allow you to choose any one of these 4 modes. If you do not have the appropriate firmware then you would not be allowed to use some of these modes. The 4 CD writing modes are :- 1) CDDA 2) Mode 1 2) Mode 2 Form 1 3) Mode 2 Form 2 XA 2) CDDA - can be used for digital audio CD's. It is specially made for that purpose 3) Mode 1 - Can be used for any data (multimedia file or non multimedia file) only if you do not want to write multimedia files & non-multimedia files to the same CD. Can be used only if the media is not VCD or SVCD. VCD & SVCD standards do not allow Mode 1 form of CD writing. Since Mode 1 allows error correction (there is less chance of data getting corrupted). It has set aside certain number of bytes of code for error correction. As a result of this you can save less data than would have been the case had a portion of code not been set aside for error correction. So as a user you need to decide whether it is worthwhile to gain the benefit of error correction by foregoing being able to save more data. You may need to sacrifice upto 12% space in order to gain the benefit of error correction. 4) Mode 2 Form 1 - Can be used for any data (multimedia file or non multimedia file) if you do not mind writing multimedia files & non-multimedia files to the same CD. Can be used even if the media is a VCD or SVCD. VCD & SVCD standards allow Mode 2 Form 1 method of CD writing. Since it allows error correction (there is less chance of data getting corrupted) it has set aside certain number of bytes of code for this purpose. As a result of this you can save less data than would have been the case had a portion of code not been set aside for error correction. So as a user you need to decide whether it is worthwhile to gain the benefit of error correction by foregoing being able to save more data. You may need to sacrifice upto 12% space in order to gain the benefit of error correction. Your drive i.e. firmware if it allows Mode 2 Form 1 operates upon what is called XA (Extended Architecture). One need not bother understanding what XA means. 5) Mode 2 Form 2 XA - Can be used for any data (multimedia file or non multimedia file) if you do not mind writing multimedia files & non-multimedia files to the same CD. Can be used even if the media is a VCD or SVCD. VCD & SVCD standards allow Mode 2 form 2 XA method of CD writing. Since it does not allow error correction you can save more data than would have been the case had a portion of code been set aside for error correction. So as a user you need to decide whether it is worthwhile to forego the benefit of error correction for the sake of being able to save more data. You may be able to save 12% more data in terms of file size. Your drive i.e. firmware if it allows Mode 2 Form 2 XA operates upon what is called XA (Extended Architecture). One need not bother understanding what XA means. So as a user one has to choose the CD writing mode which suits the task best. I have only one request. Have I understood the matter correctly? I'd be grateful if you could let me know.
  2. Background Happy, grateful, loyal user of ImgBurn 2.5.1 Concept Understood So Far DVD/HD DVD/BD only supports one track mode - Mode 1. This is regardless of whether you burn via Build mode (mp3 files, avi files, doc files, xls files, jpg file etc) all end up in a data track. Clarification Kindly Required CD supports Mode 1, Mode 2 and CD-DA How does CD Mode 1 differ from CD Mode 2 differ from CD-DA i.e. when does each one of them get used?
  3. Thanks for clarifying both my doubts i.e. It is not video file or audio file. Audio track in this context means CD - so this setting is relevant only to CD. Understood. There is no such thing as correct verify speed - it should be left on default values. Understood. Query A kind clarification regarding - "it's for data or audio TRACKS. (You can only have audio tracks on a CD)" please A data CD or a data DVD means if your output CD or output DVD will contain .xls, .doc, .ppt files etc isn't it? Have I understood correctly? "audio TRACKS" means you have a CD or DVD with a "song or speech on it but without any video" isn't it? Have I understood correctly? Therefore I am unable to understand why audio tracks can be had as an output only on a CD but not on DVD! I understand the point relating to verify speed setting i.e. the right dropbox relates only to CD. So I have no doubts on that point any longer. I'd like to understand whether (using ImgBurn 2.5.1) I can burn an audio only on a CD file but not on a DVD whereas (using ImgBurn 2.5.1) I can burn a video file both on CD & DVD I would be grateful for your guidance
  4. Gratitude Thanks to ImgBurn 2.5.1 & great forum advices I've continually got great ISO's, great burns & understand my logs - all of which I save.......The logs along with the above inputs has helped to greatly reduce my learning curve. I've set my write speed correctly at 6x for my firmware Sony-DWQ30A & I have the latest exe update of the firmware i.e. YYS7. In fact I've set a fixed write speed at 6x for the combination of "Sony-DWQ30A" & "DVD-R 120min/4.7GB AccuCORE 16x/1x" So my last log said - Average Write Rate: 8,159 KB/s (5.9x) - Maximum Write Rate: 8,402 KB/s (6.1x) My Assumption Just like one can set the correct write speed one can also the correct verification speed for:- video file - by going inside "Mode-Verify-Settings" for your video file. Do the needful on dropbox on the left if it is a video file or audio file - by going inside "Mode-Verify-Settings" for your audio file. Do the needful on dropbox on the right if it is not a video file but an audio file Queries:- How do I set the correct verify speed the very first time? Is the first time just trial & error? For the second time onwards can I just note down my last log & set the "verify speed" exactly equal to or slightly below (in case an exact match is not possible).After setting "write speed" at 6x my last log said - Average Verify Rate: 15,098 KB/s (10.9x) - Maximum Verify Rate: 21,679 KB/s (15.7x) Therefore shall I for this combination of firmware+media set "verify speed" at 10x since there is no option like 10.9x? Kindly guide
  5. Thanks a ton. So storing an ISO seems to be a smart thing to do for 2 reasons. Creating an ISO from a DVD folder takes very few minutes Writing a DVD from ISO also is possible Thanks again.
  6. I went through that forum as advised by you. It is mainly focused on comparison of software. So I could not find an answer to whether ISO also can get infected by virus. Therefore grateful if you could kindly therefore let me know if virus can infect ISO too? Please
  7. ilitws

    AWS

    @mmalves Thanks to you, updating firmware took up my write speed from 1x to 6x. A huge time saver!
  8. @paul11 yes .WMA, .MP3, .AVI can be affected by virus I don't know about .iso and so I too would like to know
  9. Background WinXp Professional 32 bit; ImgBurn 2.5.1; DVD Flick 1.3.0.7 build 738; VLC MediaPlayer 1.0.5; The KMPlayer 2.9.4.1435; Sony DW-Q30A DVD on which I have to update firmware driver from YYS3 to YYS7_WIN.EXE Query By referring to the ImgBurn 2.5.1 logs (which I will save one after another) can I proactively determine that after a certain number of hours of writing I must do maintenance on my writer - Sony DW-Q30A? I have a time calculator app (called Minute By Minute) which will tell me as to how many hours I've "written" or "read" using Sony DW-Q30A over a period of time
  10. ilitws

    AWS

    @mmalves & @LIGHTNING UK! Admirable guidance. Heartfelt thanks! @LIGHTNING UK! What I have now done My Device Manager was already DMA enabled. I'll check to see that BIOS setting is on auto rather than DMA or PIO. Will do it upon my next logon. I'll keep my fingers (& toes) crossed as I am entering BIOS for the first time. But then I've never ever been squeamish & am careful Will download the latest firmware for Sony DW-Q30A After I finish using my blank DVD's in the future I'll go for MCC, TY and YUDEN for single layer DVD-R discs Query Regarding 1 Thing I Now Need To Do I will download the latest firmware for my burner for Sony DW-Q30A YYS7_WIN.EXE , Date 26th July 2006, File Size 650KB. Which is the correct folder to install this firmware? I do not have a seperate DVD player. I always play things on my PC
  11. ilitws

    AWS

    I am terribly sorry if I have done that. I never meant to do so. I asked in that thread itself only for sake of continuity. I now understand the meaning of hijack & will try to ask in separate threads only. Grateful for your kind reply
  12. ilitws

    AWS

    @mmalves Thanks for your kind reply. I had read your enclosure earlier & again re-read it now Background My earlier understanding of what AWS means was wrong I earlier took AWS to mean that if you leave it on AWS ImgBurn would automatically decide the correct speed. My understanding was totally wrong My interpretation of what AWS means has now been corrected Automatic Writing Speed never meant ImgBurn 2.5.1 decides which speed is most appropriate. Rather the user has to decide that. Once the user decides that & sets it there onwards ImgBurn 2.5.1 would use only that same speed to write Query How should a user choose the correct write speed? How does one get it right the first time? The second time onwards can one choose the speed by referring to the prior log if one is using the same type of DVD? I am providing 2 bits of information to you One bit of information - Upon inserting my DVD - "DVD-R 120min/4.7GB AccuCORE 16x/1x" my screen says SONY DVD RW DW-Q30A YYS3 (ATA) Current Profile: DVD-R Disc Information: Status: Empty State of Last Session: Empty Erasable: No Free Sectors: 2,297,888 Free Space: 4,706,074,624 bytes Free Time: 510:40:38 (MM:SS:FF) Next Writable Address: 0 Supported Write Speeds: 6x, 8x, 12x, 16x Pre-recorded Information: Manufacturer ID: SONY16D1 Physical Format Information (Last Recorded): Disc ID: 0@P-!-00 Book Type: DVD-R Part Version: 5 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 1 Track Path: Parallel Track Path (PTP) Linear Density: 0.267 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196,608 Last Physical Sector of Data Area: 2,495,103 Last Physical Sector in Layer 0: 0 Performance (Write Speed): Descriptor 1... -> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 0 (0x00000000) -> RS: 8,864 KB/s (6.6x) - WS: 8,310 KB/s (6x) Descriptor 2... -> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 0 (0x00000000) -> RS: 8,864 KB/s (6.6x) - WS: 11,080 KB/s (8x) Descriptor 3... -> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 0 (0x00000000) -> RS: 8,864 KB/s (6.6x) - WS: 16,620 KB/s (12x) Descriptor 4... -> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 0 (0x00000000) -> RS: 8,864 KB/s (6.6x) - WS: 22,160 KB/s (16x) Another bit of information is based upon a log (I saved) of a successful write I had done using the same DVD but when I did not understand the correct meaning of AWS. So my setting was AWS which obviously meant (Max) I 20:48:08 ImgBurn Version 2.5.1.0 started! I 20:48:08 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 20:48:08 Total Physical Memory: 514,792 KB - Available: 200,660 KB W 20:48:08 Drive D:\ (FAT32) does not support single files > 4 GB in size. W 20:48:08 Drive E:\ (FAT32) does not support single files > 4 GB in size. I 20:48:08 Initialising SPTI... I 20:48:08 Searching for SCSI / ATAPI devices... I 20:48:08 -> Drive 1 - Info: SONY DVD RW DW-Q30A YYS3 (F:) (ATA) I 20:48:08 Found 1 DVD±RW! I 20:49:29 Operation Started! I 20:49:29 Building Image Tree... I 20:49:29 Checking Directory Depth... I 20:49:29 Calculating Totals... I 20:49:29 Preparing Image... I 20:49:29 Checking Path Length... I 20:49:30 Contents: 8 Files, 2 Folders I 20:49:30 Content Type: DVD Video I 20:49:30 Data Type: MODE1/2048 I 20:49:30 File System(s): ISO9660, UDF (1.02) I 20:49:30 Volume Label: [Not Configured] I 20:49:30 IFO/BUP 32K Padding: Enabled I 20:49:30 Region Code: 1, 2, 3, 4, 5, 6, 7, 8 I 20:49:30 TV System: PAL I 20:49:30 Size: 4,125,515,776 bytes I 20:49:30 Sectors: 2,014,412 I 20:49:30 Image Size: 4,126,146,560 bytes I 20:49:30 Image Sectors: 2,014,720 I 20:49:30 Operation Successfully Completed! - Duration: 00:00:00 I 20:55:40 Operation Started! I 20:55:40 Building Image Tree... I 20:55:40 Checking Directory Depth... I 20:55:40 Calculating Totals... I 20:55:40 Preparing Image... I 20:55:41 Checking Path Length... I 20:55:41 Contents: 8 Files, 2 Folders I 20:55:41 Content Type: DVD Video I 20:55:41 Data Type: MODE1/2048 I 20:55:41 File System(s): ISO9660, UDF (1.02) I 20:55:41 Volume Label: JAMES_BOND__LICENSE_TO_KILL_1989 I 20:55:41 IFO/BUP 32K Padding: Enabled I 20:55:41 Region Code: 1, 2, 3, 4, 5, 6, 7, 8 I 20:55:41 TV System: PAL I 20:55:41 Size: 4,125,515,776 bytes I 20:55:41 Sectors: 2,014,412 I 20:55:41 Image Size: 4,126,146,560 bytes I 20:55:41 Image Sectors: 2,014,720 I 20:56:02 Operation Successfully Completed! - Duration: 00:00:21 I 20:56:02 Operation Started! I 20:56:02 Image Contents: 8 Files, 2 Folders I 20:56:02 Image Sectors: 2,014,720 (MODE1/2048) I 20:56:02 Image Size: 4,126,146,560 bytes I 20:56:02 Image Single Layer Profile: DVD-R/RW (Media Capacity: 2,297,888) I 20:56:02 Image Volume Identifier: JAMES_BOND__LICENSE_TO_KILL_1989 I 20:56:02 Image Volume Set Identifier: 3CAEA6F4001EBDF2 I 20:56:02 Image Application Identifier: IMGBURN V2.5.1.0 - THE ULTIMATE IMAGE BURNER! I 20:56:02 Image Implementation Identifier: ImgBurn I 20:56:02 Image File System(s): ISO9660, UDF (1.02) I 20:56:02 Destination File: E:\James Bond - Licence To Kill [1989].iso I 20:56:02 Destination Free Space: 10,086,219,776 Bytes (9,849,824 KB) (9,618 MB) (9 GB) I 20:56:02 Destination File System: FAT32 I 20:56:02 File Splitting: Auto I 20:56:02 Writing Image... I 21:01:28 Operation Successfully Completed! - Duration: 00:05:26 I 21:01:28 Average Write Rate: 12,360 KB/s (8.9x) - Maximum Write Rate: 23,463 KB/s (16.9x) I 21:37:43 Operation Started! I 21:37:43 Source File: E:\James Bond - Licence To Kill [1989].iso I 21:37:43 Source File Sectors: 2,014,720 (MODE1/2048) I 21:37:43 Source File Size: 4,126,146,560 bytes I 21:37:43 Source File Volume Identifier: JAMES_BOND__LICENSE_TO_KILL_1989 I 21:37:43 Source File Volume Set Identifier: 3CAEA6F4001EBDF2 I 21:37:43 Source File Application Identifier: IMGBURN V2.5.1.0 - THE ULTIMATE IMAGE BURNER! I 21:37:43 Source File Implementation Identifier: ImgBurn I 21:37:44 Source File File System(s): ISO9660, UDF (1.02) I 21:37:44 Destination Device: [0:0:0] SONY DVD RW DW-Q30A YYS3 (F:) (ATA) I 21:37:44 Destination Media Type: DVD-R (Disc ID: SONY16D1) (Speeds: 6x, 8x, 12x, 16x) I 21:37:44 Destination Media Sectors: 2,297,888 I 21:37:44 Write Mode: DVD I 21:37:44 Write Type: DAO I 21:37:44 Write Speed: MAX I 21:37:44 Link Size: Auto I 21:37:44 Lock Volume: Yes I 21:37:44 Test Mode: No I 21:37:44 OPC: No I 21:37:44 BURN-Proof: Disabled W 21:37:44 Write Speed Miscompare! - MODE SENSE: 22,160 KB/s (16x), GET PERFORMANCE: 8,864 KB/s (6.6x) I 21:37:44 Write Speed Successfully Set! - Effective: 8,864 KB/s (6.6x) I 21:37:44 Filling Buffer... (20 MB) I 21:37:45 Writing LeadIn... I 21:38:22 Writing Session 1 of 1... (1 Track, LBA: 0 - 2014719) I 21:38:22 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2014719) I 22:28:29 Synchronising Cache... I 22:28:48 Exporting Graph Data... I 22:28:49 Graph Data File: C:\Documents and Settings\Ramesh\Application Data\ImgBurn\Graph Data Files\SONY_DVD_RW_DW-Q30A_YYS3_FRIDAY-MAY-14-2010_9-37_PM_SONY16D1_MAX.ibg I 22:28:49 Export Successfully Completed! I 22:28:49 Operation Successfully Completed! - Duration: 00:51:04 I 22:28:49 Average Write Rate: 1,340 KB/s (1.0x) - Maximum Write Rate: 2,231 KB/s (1.6x) I 22:28:49 Cycling Tray before Verify... W 22:28:59 Waiting for device to become ready... I 22:29:08 Device Ready! I 22:29:12 Operation Started! I 22:29:12 Source Device: [0:0:0] SONY DVD RW DW-Q30A YYS3 (F:) (ATA) I 22:29:12 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: SONY16D1) (Speeds: 6x, 8x, 12x, 16x) I 22:29:12 Image File: E:\James Bond - Licence To Kill [1989].iso I 22:29:12 Image File Sectors: 2,014,720 (MODE1/2048) I 22:29:12 Image File Size: 4,126,146,560 bytes I 22:29:12 Image File Volume Identifier: JAMES_BOND__LICENSE_TO_KILL_1989 I 22:29:12 Image File Volume Set Identifier: 3CAEA6F4001EBDF2 I 22:29:12 Image File Application Identifier: IMGBURN V2.5.1.0 - THE ULTIMATE IMAGE BURNER! I 22:29:12 Image File Implementation Identifier: ImgBurn I 22:29:12 Image File File System(s): ISO9660, UDF (1.02) I 22:29:12 Read Speed (Data/Audio): MAX / MAX I 22:29:12 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2014719) I 22:29:12 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2014719) I 22:57:11 Exporting Graph Data... I 22:57:11 Graph Data File: C:\Documents and Settings\Ramesh\Application Data\ImgBurn\Graph Data Files\SONY_DVD_RW_DW-Q30A_YYS3_FRIDAY-MAY-14-2010_9-37_PM_SONY16D1_MAX.ibg I 22:57:11 Export Successfully Completed! I 22:57:11 Operation Successfully Completed! - Duration: 00:27:58 I 22:57:11 Average Verify Rate: 2,401 KB/s (1.7x) - Maximum Verify Rate: 2,747 KB/s (2.0x) Based upon the log of a successfully written dvd & the ImgBurn write screen is this okay? Now onwards I can build ISO at 8.9x 8x Now onwards I can write DVD at 6x, 8x, 12x, 16x 1x
  13. @mmalves - I am always diligently following your excellent advice & benefit from it & so my ImgBurn 2.5.1 settings are always on default setting only. I only wanted to know in that context which parameter to enhance. Even this doubt of mine you've clarified nicely since his operating system is Win7 Home 64bit whereas mine is WinXp Professional 32 bit - as indicated in the log. As you rightly say one cannot generalize one's understanding. It varies as per operating system & situation. This wonderful software continues to amaze me as it adjusts its settings so intelligently! Thanks for your kind reply
  14. Thanks for your kind reply. Understood the difference between Test & Verify You've mentioned - "Notice, though, that a successful test doesn't mean the real burn will be successful since a lot of things can change while doing a real burn". What sort of things can change? I ask this because even while doing Test I would be inserting the same DVD disc into my F drive which would be the same one to which I would do the burn if the Test proved to be a success.
  15. Background In ImgBurn 2.5.1 I gather:- Test - It is a kind of "pretend burn" (it does everything but the laser does not get turned on). Doing it will tell you if your burn will be okay even before you actually start the burn Verify - After you have burnt it tells you if the burn happened properly So Test is "Before Burn" & Verify is "After Burn" Query In ImgBurn 2.5.1 under what situations is it appropriate to use Test & under what other situations is it appropriate to use Verify?
  16. I read this thread & kindly wish to understand this Which settings should be increased and/or modified? 1)Transfer length Automatic - default. Should it be made Manual? Slider 32KB - default. Should it be increased? 2)Buffer Size - default is 20MB.Should it be increased? Enable buffer recovery is TICKED by default 3)Buffer Recovery Thresholds Main 20% - default.Should it be increased? Device 40% - default.Should it be increased? Average Disc Queue Length 1.0 - default.Should it be increased?
  17. Thanks for your kind reply. I'll keep both unticked so that I never run the risk of exceeding 5000 lines. So in my case I'll prefer the option to append a number to the end of the log an that just gets incremented each time a new log is created Kindly tell me this. If & when I delete some prior logs will that pose a problem in log numbering? For instance if I have Log1, Log2, Log3 then the next log which is self created would be Log4. Now were I to delete Log2 would I just be left with Log1, Log3 & Log4?
  18. Background I'd like to preserve all my ImgBurn 2.5.1 logs since:- project specifics vary from project to project e.g. PAL, NTFS, specifications of media used, File System used e.g. ISO9660, UDF (1.02), Output Size e.g. Image Size, Data Type e.g. MODE1/2048, Write Rate, Time Taken to Write hours, minutes & seconds, Verify Rate, Time Taken To Verify hours, minutes & seconds etc I can learn from my logs & use those learnings for future tasks so that I avoid mistakes, estimate how much time each task would take & do not needlessly have to reinvent the wheel Gratitude It is great that in ImgBurn 2.5.1 by clicking on Help-ImgBurn Logs it directly/quickly takes me to the Log folder which happens to be in "Application Folder" which happens to be a hidden folder & hidden file. This "quick click gui method" saves me a lot of time as otherwise I would have had to click on a folder & change 2 settings in WinXP Professional to get to the ImgBurn 2.5.1 Log file Query As I will continue to use ImgBurn 2.5.1 time after time I'd like to save all my logs rather than my latest log getting replaced with the latest one Does the latest log of the session:- overwrite the earlier log of previous session/sessions or increment it in the earlier session log itself ----- this would be great as I won't end up with >1 log file or gets created as a fresh session log -------- this too would be fine since I do not mind if number of log files >1 So what type of log file is it? - overwrite, increment or fresh? Can log file name be configured by me for automatic file naming e.g. "Label Name + Read", "Label Name + Build", "Label Name + Write", "Label Name + Verify", "Label Name + Write + Verify"
  19. ilitws

    AWS

    Background I ask this question only because everyone tries to avoid wasting a disc. Also as a newbie ImgBurn 2.5.1 user I've read the forum guides as well & also the excellent pdf - ImgBurn Functions.pdf. Query Is setting write speed to AWS a solution which would ensure this type of incident never happens. Is choosing AWS rather than setting a speed a perfect solution which would work every time. I also ask this because I understand Automatic Write Speed (AWS)automatically sets write speed to Max if everything is fine otherwise AWS itself chooses the perfect write speed for that given situation. Is my understanding correct? Does AWS take the burden of guesswork out of the situation?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.