Jump to content

FelixCold

Members
  • Content Count

    18
  • Joined

  • Last visited

About FelixCold

  • Rank
    ISF Newbie
  • Birthday 11/08/1971

Contact Methods

  • Website URL
    http://www.radiolocman.com
  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    Vilnius, LTU
  • Interests
    I'm a deep-digger!<br />That means - I'm a perfectionist.<br />That means - some people consider me as troll!<br />(I'm becoming famous in it!)<br />But I just want to make things clear ...<br />Cos "pink glasses" is the most dangerous disease in the world!
  1. FelixCold

    So you say to use Verbatims ...

    My first impression was somehow similar after all I've read at this forum, but I'm confused because of quantity numbers shown there - they're talking about millions! The case isn't about to stick with cheap media, but rather about not being able to stick with such called "high quality" one, as I originally wanted & was ready to advice the same to others. Accidentally my Verbatim DVDs ended in the middle of the night (somehow I was sure I still have more of them) & I used remaining cheap brand which suddenly performed better! Now as I still see little difference between these media I'll use both of them for further investigations & I'll be very careful with spreading advices I've read at this forum.
  2. FelixCold

    So you say to use Verbatims ...

    Regrettably, I can't find any info about this on my DVDs & their boxes - all I have with state of origin posted on are several Verbatim CD stacks - two are made in China & two in India. I guess there's no any sense for traders to import better media to our lands ... #39;( Later I'll try to look on DVD packages at more local stores, but it already seems like until now I've been paying extra for something that isn't really present? And "MCC-004-00" is just another two-faced Janus ... I can try to accept them until they're denied by my own experience. I can't already state this for sure as I have too little statistics but some obvious things in it are very suspicious.
  3. FelixCold

    So you say to use Verbatims ...

    I hoped I came here for the first one, but sometimes it tends to turn into the second depending on the quality of the first! I didn't state anything here without a proof, differently to you guys. These things are slightly different for those who don't need to burn thousands of discs. If I need to burn in average about 1 disc in a week, I can't consider a drive that is still on warranty as old, I doubt that there's much sense in trying which is the best of many available firmware "updates" one by one (most of them not original) otherwise than from pure interest if the existing one still works good enough & as I prefer to have several more simple & less powerful computers instead of one "super-machine" for the same price (cos sudden problem which can end in losing workability of this one & only & the last working computer can make me much more trouble than the lack of GHz & etc. on those several less powerful), I can't have a most modern DVD writer in every of my computers - instead I have more simple ones there (usually combo-s, except one) & one common portable USB DVD writer for all, especially, when I use DVDs less than CDs & mostly for backups cos I don't care so much if my movies are in some compressed format instead of "true DVD". I see we have slightly different views to solving problems cos I'm more concentrated on the exact trouble I have instead of many general things as you trying to point me to - maybe for those who are constantly burning a big amount of discs this "general" way works, but for the ones like me trying to improve everything in general usually leads to waste of time & money & health for things that rarely give a direct result. I don't understand why are you still pointing me to that USB speed aspect when as I can see it isn't directly or maybe even anyhow related to the problems I have. I don't have problems with limited long-term USB transfer speed from computer to external drive, cos all the main burning process goes fine, I'm having problems at "writing lead in" moment - how they can be caused by USB? How can USB make ACME crap work better than Verbatims? When I came to local computer store yesterday & asked for Verbatim blank DVDs I was presented just with a coloured 5 piece pack instead of ordinary colourless ones & they didn't have a DVDRW of that brand at all (I had to buy ACME), so I asked then why there's so little choice. The answer was: "you know, most of our customers don't care much about brand, they care just about general type (CD or DVD, R or RW) & price, so there's no much sense for us to keep here a wide choice of different products, especially higher-priced". If other "crappy" brands would be the same unreliable as they're cheap (about 1.5 to 1), this should be already well known even for ordinary users as I'm sure in that case they would prefer though more expensive, but more reliable media - as I see, the former statement about higher reliability is at least doubtable. One good thing is that at manufacturers site the previous-to-last original firmware version that my drive still has doesn't already exist for download - that means the last one is now the only that is available there & so I think I can use it without troubles regarding warranty. I'll see if there'll be noticeable changes in my drive behaviour. To be continued later ... (as I'll burn more DVDs I'll post more logs when they'll be available)
  4. FelixCold

    So you say to use Verbatims ...

    Thank you for your replies, great experts, but! Sorry, what on this statement is based? USB2.0 port has max speed 480 mbit/sec=60MB/sec, lets take a half of it because of system reserve (though as I know it can use just under 30% of bandwidth, not a half) - now we've got 30MB/sec & let's split it further into 2 parts cos some of the files in the build are on the USB flash drives - we'll get 15MB/sec, we can even lower it some more - it's still enough to reach 8x speed when I need just 6x, which is actually slightly exceeded in some of my logs. I wanted to do a test write at max speed to see what is the real limit, but regrettably this mode somehow isn't supported for DVDs. This "lowest speed" is the same for ACMEs crap too & as you can see the actual speed is kept by drive close enough to this level rather than to what I've set it! From readings at this forum I already know it will behave like this so I set 4x speed exactly to force the drive to use the lowest possible & it's actually 6x. Regrettably, I can't do this, cos there's no physical place for anything else like this inside computer I'm working with now, which is Dell Optiplex GX50. Yes, I've already downloaded the next update from that site, just didn't install it earlier cos I had no problems with existing firmware. Maybe now it's almost a right time to try it - drive warranty will end soon, so I'll be free from danger of loosing it. I don't think so. It was purchased 2006.03.23 with 24 months warranty, so I still have some time of it. I use it about 4 months after I got it from previous owner & I didn't have such problems with it until now - rather even not with it, but with Verbatim DVDs! In that time I've burned almost 20 CDs & made just one real coaster because of my own mistake to hit "cancel" button at the wrong time + one time there was a fail with CD-RW which I just rewrote. I've almost already forgotten about such things as burning problems with that drive until this recent case. Thanks for your links chewy, but they just confused me now! I thought the only one firmware update that can be useful to me is the one presented in the link from blutach & now there's so many different options that I just don't know what & why should I use. OK, I'll try to study that info. Anyway, the main question still remains open - why I'm getting some similar problems with Verbatim DVDs from different sources when this isn't the case with cheap ACME DVDs!? As I can remember, somewhere at this forum I've seen a statement that Verbatim or TY DVDs have 99% reliability, when other crap is almost 50 to 50%. It's strange to me again, but what I must think then seeing this: http://www.burnworld.com/dvd/media/burner-media4.htm
  5. FelixCold

    So you say to use Verbatims ...

    Yesterday I tried to burn second of my backup DVDs on this computer & this drive (previously some of my friends had helped me with that as I had just a combodrive, not DVDRW), using the same media as for the first successful burn, but regrettably things didn't happen as expected & were rather strange, keeping in mind all media related advices that can be read at this forum. So, here's the log : I 02:44:29 Operation Started! I 02:44:29 Source File: -==/\/[bUILD IMAGE]\/\==- I 02:44:29 Source File Sectors: 2.024.352 (MODE1/2048) I 02:44:29 Source File Size: 4.145.872.896 bytes I 02:44:29 Source File Volume Identifier: OpenSUSE_ALTLinux_DesktopBSD_HirensBootCD-9.3 I 02:44:29 Source File Application Identifier: ImgBurn v2.3.2.0 - The Ultimate Image Burner! I 02:44:29 Source File Implementation Identifier: ImgBurn I 02:44:29 Source File File System(s): ISO9660; Joliet; UDF (1.02) I 02:44:29 Destination Device: [0:0:0] LITE-ON DVDRW SOHW-1673S JS0C (G:) (USB) I 02:44:29 Destination Media Type: DVD+R (Disc ID: MCC-004-00) (Speeds: 6x; 8x; 12x; 16x) I 02:44:29 Destination Media Sectors: 2.295.104 I 02:44:29 Write Mode: DVD I 02:44:29 Write Type: DAO I 02:44:29 Write Speed: 4x I 02:44:29 Link Size: Auto I 02:44:29 Test Mode: No I 02:44:29 BURN-Proof: Enabled I 02:44:30 Filling Buffer... (20 MB) I 02:44:33 Writing LeadIn... W 02:45:59 Failed to Write Sectors 0 - 31 - Write Error (my comment - time interval is 1 min 26 sec + 10 sec) W 02:45:59 Retrying (1 of 20)... I 02:46:08 Writing LeadIn... I 02:46:09 Writing Image... (LBA: 0 - 2024351) I 02:57:11 Synchronising Cache... I 02:57:12 Closing Track... I 02:57:20 Finalising Disc... I 02:57:47 Image MD5: ad63049771261f3ebda07acc86dc7e0b I 02:57:48 Operation Successfully Completed! - Duration: 00:13:18 I 02:57:48 Average Write Rate: 6.115 KB/s (4.4x) - Maximum Write Rate: 8.780 KB/s (6.3x) I 02:57:48 Cycling Tray before Verify... W 02:57:56 Waiting for device to become ready... I 02:58:09 Device Ready! I 02:58:10 Operation Started! I 02:58:10 Source Device: [0:0:0] LITE-ON DVDRW SOHW-1673S JS0C (G:) (USB) I 02:58:10 Source Media Type: DVD+RW (Book Type: DVD-ROM) (Disc ID: MCC-004-00) (Speeds: 4x) I 02:58:10 Image File: -==/\/[bUILD IMAGE]\/\==- I 02:58:10 Image File Sectors: 2.024.352 (MODE1/2048) I 02:58:10 Image File Size: 4.145.872.896 bytes I 02:58:10 Image File Volume Identifier: OpenSUSE_ALTLinux_DesktopBSD_HirensBootCD-9.3 I 02:58:10 Image File Application Identifier: ImgBurn v2.3.2.0 - The Ultimate Image Burner! I 02:58:10 Image File Implementation Identifier: ImgBurn I 02:58:10 Image File File System(s): ISO9660; Joliet; UDF (1.02) I 02:58:10 Verifying Sectors... (LBA: 0 - 2024351) W 03:00:35 Failed to Read Sector 0 - L-EC Uncorrectable Error W 03:00:45 Failed to Read Sector 1 - L-EC Uncorrectable Error W 03:00:47 Failed to Read Sector 2 - L-EC Uncorrectable Error W 03:00:49 Failed to Read Sector 3 - L-EC Uncorrectable Error E 03:00:53 Failed to Read Sector 4 - L-EC Uncorrectable Error E 03:00:53 Failed to Verify Sectors! E 03:00:54 Operation Failed! - Duration: 00:02:43 I 03:00:54 Average Verify Rate: 0 KB/s (0.0x) - Maximum Verify Rate: 0 KB/s (0.0x) Disc isn't accessible at least from windoze OS - when inserted in any drive (ext. USB DVDRW or int. combo) no any label appears & I get an error trying to open it. Besides, that's what ImgBurn displays under "device" about this disc now, after that "burn", & more than this - it thinks it's "ready" to write to it again instead of showing "disc not empty"! LITE-ON DVDRW SOHW-1673S JS0C (USB) Current Profile: DVD+RW Disc Information: Status: Complete Erasable: Yes Formatted: Yes Supported Write Speeds: 4x TOC Information: Session 1... -> Track 01 (Mode 1, LBA: 0 - 2295103) -> LeadOut (LBA: 2295104) Physical Format Information (ADIP): Disc ID: MCC-004-00 Book Type: DVD+RW Part Version: 2 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.491.711 Last Physical Sector in Layer 0: 0 Physical Format Information (Last Recorded): Disc ID: MCC-004-00 Book Type: DVD-ROM Part Version: 1 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.220.959 Last Physical Sector in Layer 0: 0 Current Format Capacity: Sectors: 2.295.104 Size: 4.700.372.992 bytes Time: 510:03:29 (MM:SS:FF) Preferred Format Capacity: Sectors: 2.295.104 Size: 4.700.372.992 bytes Time: 510:03:29 (MM:SS:FF) Maximum Format Capacity: Sectors: 2.295.104 Size: 4.700.372.992 bytes Time: 510:03:29 (MM:SS:FF) OK, I thought, maybe that was the one & only bad disc amongst all these so good & reliable Verbatims, so I'll just burn another one. But, after I've looked around in all corners I realized that it was the last one blank DVD of this brand I had at that moment & as you can see that was not the best time (about 3 a.m.) to go out & get some more of them. The only ones which were still present were cheap ACMEs blank DVDs. As I wanted to be sure the problem wasn't caused by my drive I decided to test one of these too, to see if it will fail & if yes, then in what exact place. Here's what I got: I 05:26:39 Operation Started! I 05:26:39 Source File: -==/\/[bUILD IMAGE]\/\==- I 05:26:39 Source File Sectors: 2.024.352 (MODE1/2048) I 05:26:39 Source File Size: 4.145.872.896 bytes I 05:26:39 Source File Volume Identifier: OpenSUSE_ALTLinux_DesktopBSD_HirensBootCD-9.3 I 05:26:39 Source File Application Identifier: ImgBurn v2.3.2.0 - The Ultimate Image Burner! I 05:26:39 Source File Implementation Identifier: ImgBurn I 05:26:39 Source File File System(s): ISO9660; Joliet; UDF (1.02) I 05:26:39 Destination Device: [0:0:0] LITE-ON DVDRW SOHW-1673S JS0C (G:) (USB) I 05:26:39 Destination Media Type: DVD+R (Disc ID: MBIPG101-R05-01) (Speeds: 6x; 8x; 12x; 16x) I 05:26:39 Destination Media Sectors: 2.295.104 I 05:26:39 Write Mode: DVD I 05:26:39 Write Type: DAO I 05:26:39 Write Speed: 4x I 05:26:39 Link Size: Auto I 05:26:39 Test Mode: No I 05:26:39 BURN-Proof: Enabled I 05:26:40 Filling Buffer... (20 MB) I 05:26:43 Writing LeadIn... I 05:28:03 Writing Image... (LBA: 0 - 2024351) (my comment - time interval is 1 min 20 sec) I 05:38:24 Synchronising Cache... I 05:38:25 Closing Track... I 05:38:33 Finalising Disc... I 05:39:00 Image MD5: ff9b8735a8c6fb20153f007d74d930ff I 05:39:01 Operation Successfully Completed! - Duration: 00:12:21 I 05:39:01 Average Write Rate: 6.519 KB/s (4.7x) - Maximum Write Rate: 8.687 KB/s (6.3x) I 05:39:01 Cycling Tray before Verify... W 05:39:09 Waiting for device to become ready... I 05:39:22 Device Ready! I 05:39:23 Operation Started! I 05:39:23 Source Device: [0:0:0] LITE-ON DVDRW SOHW-1673S JS0C (G:) (USB) I 05:39:23 Source Media Type: DVD+R (Book Type: DVD-ROM) (Disc ID: MBIPG101-R05-01) (Speeds: 6x; 8x; 12x; 16x) I 05:39:23 Image File: -==/\/[bUILD IMAGE]\/\==- I 05:39:23 Image File Sectors: 2.024.352 (MODE1/2048) I 05:39:23 Image File Size: 4.145.872.896 bytes I 05:39:23 Image File Volume Identifier: OpenSUSE_ALTLinux_DesktopBSD_HirensBootCD-9.3 I 05:39:23 Image File Application Identifier: ImgBurn v2.3.2.0 - The Ultimate Image Burner! I 05:39:23 Image File Implementation Identifier: ImgBurn I 05:39:23 Image File File System(s): ISO9660; Joliet; UDF (1.02) I 05:39:23 Verifying Sectors... (LBA: 0 - 2024351) I 05:53:33 Device MD5: ff9b8735a8c6fb20153f007d74d930ff I 05:53:33 Image MD5: ff9b8735a8c6fb20153f007d74d930ff I 05:53:33 Operation Successfully Completed! - Duration: 00:14:10 I 05:53:33 Average Verify Rate: 4.763 KB/s (3.4x) - Maximum Verify Rate: 7.857 KB/s (5.7x) Well, the chance that previously this was just an accident still was possible, so another day I got some new blank Verbatim DVDs which were slightly different externally, so they couldn't "accidentally" have the same problem, but look what I got when I tried to burn one of these DVDs (I added one more small file to previous build for better recognizing which DVD is which when they're inside the drives) : I 16:09:55 Operation Started! I 16:09:55 Source File: -==/\/[bUILD IMAGE]\/\==- I 16:09:55 Source File Sectors: 2.050.592 (MODE1/2048) I 16:09:55 Source File Size: 4.199.612.416 bytes I 16:09:55 Source File Volume Identifier: OpenSUSE_ALTLinux_DesktopBSD_HirensBootCD-9.3 I 16:09:55 Source File Application Identifier: ImgBurn v2.3.2.0 - The Ultimate Image Burner! I 16:09:55 Source File Implementation Identifier: ImgBurn I 16:09:55 Source File File System(s): ISO9660; Joliet; UDF (1.02) I 16:09:55 Destination Device: [0:0:0] LITE-ON DVDRW SOHW-1673S JS0C (G:) (USB) I 16:09:55 Destination Media Type: DVD+R (Disc ID: MCC-004-00) (Speeds: 6x; 8x; 12x; 16x) I 16:09:55 Destination Media Sectors: 2.295.104 I 16:09:56 Write Mode: DVD I 16:09:56 Write Type: DAO I 16:09:56 Write Speed: 4x I 16:09:56 Link Size: Auto I 16:09:56 Test Mode: No I 16:09:56 BURN-Proof: Enabled I 16:09:57 Filling Buffer... (20 MB) I 16:09:59 Writing LeadIn... W 16:11:14 Failed to Write Sectors 0 - 31 - Power Calibration Area Error (my comment - time interval is 1 min 15 sec + 9 sec) W 16:11:14 Retrying (1 of 20)... I 16:11:22 Writing LeadIn... I 16:11:23 Writing Image... (LBA: 0 - 2050591) I 16:19:41 Synchronising Cache... I 16:19:42 Closing Track... I 16:19:48 Finalising Disc... I 16:20:21 Image MD5: 7a1160418be8bfa49e30ad797d029ae3 I 16:20:22 Operation Successfully Completed! - Duration: 00:10:25 I 16:20:22 Average Write Rate: 8.251 KB/s (6.0x) - Maximum Write Rate: 8.664 KB/s (6.3x) I 16:20:22 Cycling Tray before Verify... I 16:20:51 Device Ready! I 16:20:55 Operation Started! I 16:20:55 Source Device: [0:0:0] LITE-ON DVDRW SOHW-1673S JS0C (G:) (USB) I 16:20:55 Source Media Type: DVD+R (Book Type: DVD-ROM) (Disc ID: MCC-004-00) (Speeds: 6x; 8x; 12x; 16x) I 16:20:55 Image File: -==/\/[bUILD IMAGE]\/\==- I 16:20:55 Image File Sectors: 2.050.592 (MODE1/2048) I 16:20:55 Image File Size: 4.199.612.416 bytes I 16:20:55 Image File Volume Identifier: OpenSUSE_ALTLinux_DesktopBSD_HirensBootCD-9.3 I 16:20:55 Image File Application Identifier: ImgBurn v2.3.2.0 - The Ultimate Image Burner! I 16:20:55 Image File Implementation Identifier: ImgBurn I 16:20:55 Image File File System(s): ISO9660; Joliet; UDF (1.02) I 16:20:56 Verifying Sectors... (LBA: 0 - 2050591) I 16:35:30 Device MD5: 7a1160418be8bfa49e30ad797d029ae3 I 16:35:30 Image MD5: 7a1160418be8bfa49e30ad797d029ae3 I 16:35:30 Operation Successfully Completed! - Duration: 00:14:35 I 16:35:30 Average Verify Rate: 4.697 KB/s (3.4x) - Maximum Verify Rate: 7.798 KB/s (5.6x) As I was directly monitoring all the process, I can say that the most suspected in all cases, & especially when Verbatims were used, was "writing lead in" moment - at that time drive was performing several loud "burn-outs" (not in CD-DVD terms, but rather in drag racing ones!) & in the last case even a strong enough burnt taste came out of the drive (yes, this wasn't the same as usual!) - I was almost ready to see a smoke getting out of it. More than this, there were the least these "writing lead in" (or "burnout" if you prefer) hi-speed turning attempts exactly with this ACME crap as well as this media didn't get ANY error messages. As I can remember, the very first successful Verbatim DVD burn almost a week ago also suffered from this "burnout" problem: I 01:43:56 Operation Started! I 01:43:56 Source File: -==/\/[bUILD IMAGE]\/\==- I 01:43:56 Source File Sectors: 2.253.808 (MODE1/2048) I 01:43:56 Source File Size: 4.615.798.784 bytes I 01:43:56 Source File Volume Identifier: Mandriva+PClinuxOS I 01:43:56 Source File Application Identifier: ImgBurn v2.3.2.0 - The Ultimate Image Burner! I 01:43:56 Source File Implementation Identifier: ImgBurn I 01:43:56 Source File File System(s): ISO9660; Joliet; UDF (1.02) I 01:43:56 Destination Device: [0:0:0] LITE-ON DVDRW SOHW-1673S JS0C (G:) (USB) I 01:43:56 Destination Media Type: DVD+R (Disc ID: MCC-004-00) (Speeds: 6x; 8x; 12x; 16x) I 01:43:56 Destination Media Sectors: 2.295.104 I 01:43:56 Write Mode: DVD I 01:43:56 Write Type: DAO I 01:43:56 Write Speed: 8x I 01:43:56 Link Size: Auto I 01:43:56 Test Mode: No I 01:43:56 BURN-Proof: Enabled I 01:43:57 Filling Buffer... (20 MB) I 01:43:59 Writing LeadIn... I 01:45:24 Writing Image... (LBA: 0 - 2253807) (my comment - time interval is not less than 1 min 25 sec) W 01:51:20 Waiting for buffers to recover... I 01:51:47 Writing Image... I 01:56:54 Synchronising Cache... I 01:56:55 Closing Track... I 01:57:03 Finalising Disc... I 01:57:28 Image MD5: b51ae8a5f0ef07575e0fc2a058ad1d39 I 01:57:28 Operation Successfully Completed! - Duration: 00:13:32 I 01:57:28 Average Write Rate: 6.532 KB/s (4.7x) - Maximum Write Rate: 8.769 KB/s (6.3x) I 01:57:28 Cycling Tray before Verify... W 01:57:37 Waiting for device to become ready... I 01:57:50 Device Ready! I 01:57:50 Operation Started! I 01:57:50 Source Device: [0:0:0] LITE-ON DVDRW SOHW-1673S JS0C (G:) (USB) I 01:57:50 Source Media Type: DVD+R (Book Type: DVD-ROM) (Disc ID: MCC-004-00) (Speeds: 6x; 8x; 12x; 16x) I 01:57:50 Image File: -==/\/[bUILD IMAGE]\/\==- I 01:57:50 Image File Sectors: 2.253.808 (MODE1/2048) I 01:57:50 Image File Size: 4.615.798.784 bytes I 01:57:50 Image File Volume Identifier: Mandriva+PClinuxOS I 01:57:50 Image File Application Identifier: ImgBurn v2.3.2.0 - The Ultimate Image Burner! I 01:57:50 Image File Implementation Identifier: ImgBurn I 01:57:50 Image File File System(s): ISO9660; Joliet; UDF (1.02) I 01:57:51 Verifying Sectors... (LBA: 0 - 2253807) I 02:11:29 Device MD5: b51ae8a5f0ef07575e0fc2a058ad1d39 I 02:11:29 Image MD5: b51ae8a5f0ef07575e0fc2a058ad1d39 I 02:11:29 Operation Successfully Completed! - Duration: 00:13:38 I 02:11:29 Average Verify Rate: 5.510 KB/s (4.0x) - Maximum Verify Rate: 8.739 KB/s (6.3x) I 02:32:08 Operation Started! I 02:32:08 Source Device: [0:0:0] LITE-ON DVDRW SOHW-1673S JS0C (G:) (USB) I 02:32:08 Source Media Type: DVD+R (Book Type: DVD-ROM) (Disc ID: MCC-004-00) (Speeds: 6x; 8x; 12x; 16x) I 02:32:08 Source Media Sectors: 2.253.808 I 02:32:08 Source Media Size: 4.615.798.784 bytes I 02:32:08 Verify Against Image File: No I 02:32:08 Verifying Sectors... (LBA: 0 - 2253807) I 02:41:45 Device MD5: b51ae8a5f0ef07575e0fc2a058ad1d39 I 02:41:45 Operation Successfully Completed! - Duration: 00:09:37 I 02:41:45 Average Verify Rate: 7.812 KB/s (5.6x) - Maximum Verify Rate: 10.975 KB/s (7.9x) This last part of the log file is another joke (can someone explain me what it was & what could be the sense of it?) but let's go back to the main topic, cos it's time for some interesting questions to arrive: 1. Why ACMEs crap media gave the best result competing with famous Verbatim DVDs from different batches? 2. If this isn't enough statistical data to make some certain conclusions - how many blank DVDs of both brands & from how much different batches I must try to see as obvious that the Verbatim media is worth it's more than 50% higher price? (for examle - I've burned about >50 CD-Rs last year, about >20 of which are from ACME & about >30 are Verbatim ones, but I don't see any worth mentioning difference in % of coasters made in both cases) 3. What is the cause of such a long "writing lead in" process, especially when writing to DVD discs (compared to CDs) & why it's followed by such a loud hi-speed "burnouts"? 4. If some errors appeared during "writing lead in", but then all the written to disc data was verified as correct - does this mean an increased chance of fail in the future, cos the other disc, which gave similar error at the same operation, failed to verify right after burn & exactly in the beginning of the disc, what directly corresponds with an operation which gave the error? Thank you for your attention!
  6. FelixCold

    PACKET WRIGHTING MODE

    They will ??? http://search.netscape.com/search/search?i...player+with+usb
  7. FelixCold

    Strange search results!

    You're of course right spinningwheel regarding more basic & fundamental research on given term, but in this case I was just searching for some minor details in an area that is generally already known for me & I was surprised that indirect "Google search" way is more efficient than direct "Imgburn forum search" one. Recently a similar situation occured again, when I tried to find some data regarding quality of Verbatim's DVD+R dye "MCC-004-00" using local forum "search": MCC-004-00 - no results, *MCC-004-00* - 13 pages (limited to 1000) of results, *MCC-004-00 - no results again, MCC-004-00* - 13 pages of results again. By switching to Google I found what I searched for very quickly (the third result was exactly the topic at this forum about testing this media on different drives), but this left me again with a doubtable feeling about local search feature ...
  8. FelixCold

    About improving "cancel" feature

    OK Boss, as you say. Sorry for wasting your time, but by doing this I just wanted to remind that minor problems are much more noticeable when there are no big ones around. We don't expect much comfort & are ready somewhat for many "surprises" when driving on the potholed road, but just one such "surprise" on the even road can make so annoying that one & only broken wheel. (it seems to me that I've alredy seen one like this somewhere here? ) Anyway, thank you for your great program, it's still the best & the fact that we're discussing such a minor problems here just proves this one more time.
  9. FelixCold

    About improving "cancel" feature

    I thought what I suggest could be done without pausing "everything" - so I was wrong? OK, so how it is different if "Cancel" & "Pause" buttons are pressed one after another quick enough? Sorry Boss, but I still don't understand what makes such a significant difference between: 1. User clicks "Cancel", then "Pause". 2. User clicks "Cancel", then the same "Pause" is switched on automatically by a program. ??? - ??? Yes, but I don't see anything strange in it, cos I never needed to use this function before! Yes, cos I don't see any reasons to expect that most of the other users will try to push that "Cancel" button before they actually need it, just to learn how ImgBurn works in details - to be aware for the future. That's why I think most of their experience will be the same as my own one! Well, I based my opinion on the things I've read at this forum (when I searched for the term "cancel" before starting this topic) - the ones like this: http://forum.imgburn.com/index.php?showtop...4&hl=cancel There you explain that there's no any danger in using "pause" function, in "manual" combination with previous "cancel" - the latter, as you've explained here, just brings up a cancel window. You're of course right, but I dont want your program to meet any of my "personal" needs which could be out of logic or "mainstream" - instead of it I suggest something I consider as objectively right & useful & I've explained why!
  10. FelixCold

    About improving "cancel" feature

    Watch this attachment, from my collection of ImgBurn screenshots! Wait, but ImgBurn still can't warn me if I didn't set correct burning speed or even if I forgot to put all of the files for writing! What a crap then! (ha-ha-ha!)
  11. FelixCold

    About improving "cancel" feature

    Just checked again that log - I don't know why I didn't a test write first as I usually do - now I can't remember the exact details. But if I've forgotten to check the right drive that time, there will be some cases when check "test mode" will be forgotten too. Nobody is free from accidental mistakes & it could be great if ImgBurn could help avoid bad results of some of them. This is clear & the most of my disappointment was caused by the fact that I gave the first "cancel" comand BEFORE the laser actually started to work!
  12. FelixCold

    About improving "cancel" feature

    But as you can understand, from an average user point of view the suggested thing of auto-switching into a pause state after "cancel" window is launched is rather simplifying than overcomplicating. (no need to double-click!) Well, if this is the only or the easiest way of achieving that goal (of course you can better see possible methods) - then why not, generally it solves this part of the "coaster-making danger" problem! Thank you, Big Boss!
  13. FelixCold

    About improving "cancel" feature

    Thank you for your reply, Big Boss! It could be avoided if just 1 of the 2 sides wouldn't fail - me or ImgBurn. This time both of us failed & I'm not avoiding my fault, I just think that ImgBurn side could be improved too. Well, it's a very nice advice, but ... what "Cancel" button is for then? As I've said, in that case I had time just until buffer is filled - just a few seconds. Now when looking to this from aside almost anyone can see as obvious what you're talking about, but then from inside this wasn't so easy. The exact time when "I quit the burn" was determined not just by me, but by ImgBurn too. I've hit the "Cancel" button BEFORE actual burn (irreversible action to disc surface) began & I was just expecting ImgBurn will react in the most "safe" way, but it didn't. To be more precise, I'll quote some of my previous post as importance of these words could be missed in that long story: Thank you.
  14. FelixCold

    3 Ideas

    Rather the log has to be attached first to the main window leaving no space between them, then it will follow when dragging, otherwise both windows can be moved just as separate? About erase progress bar - that came to my mind too, but I thought I could somehow live without it, cos after a few times average erase duration becomes clear & as this is some kind of "destroying" action there will be probably no need to know more details, cos this action can be easily repeated in case of fail (what exactly?). (pressing "L" works!)
  15. FelixCold

    Strange search results!

    Thank you for your advice! I really found what I searched for in "more results from forum.imgburn.com" I'll try this method regarding other forums too! (Google still rocks!)
×

Important Information

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