dontasciime Posted March 3, 2006 Posted March 3, 2006 can you just drop the elby dll files straight into imgburn folder, like i have done with wnaspi32. or do you need to install clone etc, as it comes up with error when i just drop em in the imgburn folder. this may be down to it being an old version, not sure what latest version is, as i found a version of clone on my hard drive I 21:41:21 ImgBurn Version 1.1.0.0 started! I 21:41:21 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 21:41:21 Initialising ElbyCDIO... I 21:41:21 ELBYCDIO.DLL - Elaborate Bytes CDRTools - ElbyCDIO DLL - Version 3.3.4.1 E 21:41:21 Unable to initialise ElbyCDIO! - ELBYCDIO.DLL E 21:41:21 GetProcAddress Failed! - Function Name: ElbyCDIO_GetScsiAddress E 21:41:21 Reason: The specified procedure could not be found. E 21:41:21 It might be worth changing the 'I/O Interface' in the Settings to a different one.
???? Posted March 3, 2006 Posted March 3, 2006 I don't know if it is related to the old version, but the most recent version of elbycdio.dll is 5.1.1.2 and works just fine. You may try to update the dll.
dontasciime Posted March 3, 2006 Author Posted March 3, 2006 I don't know if it is related to the old version, but the most recent version of elbycdio.dll is 5.1.1.2 and works just fine. You may try to update the dll. is that on their site for download, just the I/O i thought it used to be but cannot seem to find it now.
???? Posted March 3, 2006 Posted March 3, 2006 No, AFAIK the dll is not available as a seperate download. But you can install the latest CloneDVD and use the dll provided by it. AFAIK its usage is not affected by the trial-period limitation. But why do you prefer this I/O over the default SPTI when you have no recent Elby/Slysoft software installed? LUK! told me once that SPTI passes most of his and his teams tests and should work without a problem. I wouldn't worry too much about it, although I can understand that you want to use it, as I am using it as well.
Shamus_McFartfinger Posted March 4, 2006 Posted March 4, 2006 ElbyCDIO needs to be installed (adding it to the registry) before it can be used. There is no expiration on the ElbyCDIO device, just the trial software that installs it. Most problems people seem to have using SPTI is that they aren?t using an account with admin privileges. SPTI needs admin access to function. ElbyCDIO does not.
dontasciime Posted March 4, 2006 Author Posted March 4, 2006 (edited) I like to experiment. I have to use wnaspi32 with my external dvd writer, as spti and the chipset in my external writer (ali chipset revision 1 no flash) do not get on IE you get Semaphore time out. I got imgburn using wnaspi32 and the older program using spti for internal writing on 108 just wanted to try the elby one instead of aheads. Edited March 4, 2006 by dontasciime
???? Posted March 4, 2006 Posted March 4, 2006 (edited) SPTI needs admin access to function. Ok, didn't knew that. Thanks! ... That's a good reason. The easiest way to get this dll working would be just to install the trial of CloneDVD as Shamus_McSmartfinger has also confirmed that it won't expire. I hope you get it working. Edited March 4, 2006 by ????
dontasciime Posted March 4, 2006 Author Posted March 4, 2006 i know i can get it working by installing, just wanted to see if i could use it without installing, i could but it requires quite a bit of messing on with the kernel, dll, registry control sets etc, SO i think i will just install the trial. my external 109 seems to hate everything now since my msi board blew up and i replced it wth the dfi, gets lots of write retries even when using wnaspi32, so im gonna now have to test it inside machine to rule out usb2, or put another brand new drive in enclosure and see what happens.
dontasciime Posted March 4, 2006 Author Posted March 4, 2006 (edited) i have now changed the drive in the enclosure for a brand new pioneer 110d and still doing it, i suspect a hardware error in the enclosure or is the error in log file an indication of something else, could it be the version of wnaspi32 from latest version of nero 6. I 15:17:18 ImgBurn Version 1.2.0.0 started! I 15:17:18 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 15:17:18 Initialising ASPI... I 15:17:18 WNASPI32.DLL - Nero WnAspi32 - Win32 Nero Aspi Library - Version 2.0.1.74 I 15:17:18 Searching for SCSI / ATAPI devices... I 15:17:18 Found 2 DVD-ROMs and 2 DVD?RWs! I 15:17:56 Operation Started! I 15:17:56 Source File: H:\more shrink\the net 2\THE_NET_2.ISO I 15:17:56 Source File Sectors: 1,561,790 (MODE1/2048) I 15:17:56 Source File Size: 3,198,545,920 bytes I 15:17:56 Source File Implementation Identifier: DVD Shrink I 15:17:56 Destination Device: [6:0:0] PIONEER DVD-RW DVR-110D 1.17 I 15:17:56 Destination Media Type: DVD-R (Disc ID: TTG02) (Speeds: 4x, 6x, 8x) I 15:17:56 Destination Media Sectors: 2,297,888 I 15:17:56 Write Mode: DVD I 15:17:56 Write Type: DAO I 15:17:56 Write Speed: 8x I 15:17:56 Link Size: Auto I 15:17:56 Test Mode: No I 15:17:56 BURN-Proof: Enabled I 15:17:56 Filling Buffer... I 15:17:56 Writing LeadIn... I 15:18:31 Writing Image... W 15:23:33 Failed to Write Sectors 1485248 - 1485279 - Parameter Value Invalid W 15:23:33 Retrying (1 of 20)... W 15:23:33 Retry Failed - Power On, Reset, or Bus Device Reset Occurred W 15:23:33 Retrying (2 of 20)... I 15:23:33 Writing Image... I 15:23:48 Synchronising Cache... I 15:24:04 Operation Successfully Completed! - Duration: 00:06:07 I 15:24:04 Average Write Rate: 9,884 KB/s (7.1x) - Maximum Write Rate: 11,141 KB/s (8.0x) Edit i have 2 of the icy external case one houses a pioneer dvdrom 120, which reads @14x-15.8X. the other has a pioneer 109, so i decided swap them over to test to see if i still got the same. Not quite, now the 109 will only burn @1.8x so swapped em back to test to see what the pioneer 120 ripped at and it was 14X then tried to write on 109 again and got I 17:50:05 ***********************************other program I 17:50:05 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 17:50:05 Initialising SPTI... I 17:50:05 Searching for SCSI / ATAPI devices... I 17:50:05 Found 2 DVD-ROMs and 2 DVD?RWs! W 17:50:14 I/O Interface has been changed! I 17:50:14 Shutting down SPTI... I 17:50:14 Initialising ASPI... I 17:50:14 WNASPI32.DLL - Nero WnAspi32 - Win32 Nero Aspi Library - Version 2.0.1.74 I 17:50:14 Searching for SCSI / ATAPI devices... I 17:50:15 Found 2 DVD-ROMs and 2 DVD?RWs! I 17:50:33 Operation Started! I 17:50:34 Source File: G:\SHRINK\WALLACE AND GROMIT CURSE OF THE WERE-RABBIT\WALLACE_AND_GROMIT.ISO I 17:50:34 Source File Sectors: 1,632,688 (MODE1/2048) I 17:50:34 Source File Size: 3,343,745,024 bytes I 17:50:34 Source File Implementation Identifier: DVD Shrink I 17:50:34 Destination Device: [6:0:0] PIONEER DVD-RW DVR-109 1.58 I 17:50:34 Destination Media Type: DVD-R (Disc ID: TTG02) (Speeds: 4x, 6x, 8x) I 17:50:34 Destination Media Sectors: 2,297,888 I 17:50:34 Write Mode: DVD I 17:50:34 Write Type: SAO I 17:50:34 Write Speed: MAX I 17:50:34 Link Size: Auto I 17:50:34 Test Mode: No I 17:50:34 BURN-Proof: Enabled I 17:50:34 Filling Buffer... I 17:50:34 Writing LeadIn... I 17:50:57 Writing Image... W 17:51:54 Failed to Write Sectors 197408 - 197439 - Parameter Value Invalid W 17:51:54 Retrying (1 of 20)... I 17:51:58 Writing Image... I 17:56:30 Synchronising Cache... I 17:56:46 Operation Successfully Completed! - Duration: 00:06:12 I 17:56:46 Average Write Rate: 9,835 KB/s (7.1x) - Maximum Write Rate: 11,110 KB/s (8.0x) who else on here uses external writers, can you recommend a particular brand, one that is not using ALi rev 1a m5621 , and something nice looking, as i like the look of my ICY BOXES with blue LED etc, i think akasa make a nice blue lit one may be a similar sounding company, just need to know chipset in em, thanks Edited March 4, 2006 by dontasciime
dontasciime Posted March 4, 2006 Author Posted March 4, 2006 anyone using this chipset for external drive and spti Cypress (USB 2.0) ATA-6 chipsets
LIGHTNING UK! Posted March 4, 2006 Posted March 4, 2006 I just got the ?18 usb2/firewire one from SVP! Maybe you could bodge swapping the little board in them over into your nice blue lit case? They use the prolific chipset. Oh and Nero ASPI is just a wrapper for SPTI under NT based OS's. You'd need Adaptecs one to have any hope of getting around that timeout issue. Your Pioneer 110 needs a firmware update btw
dontasciime Posted March 4, 2006 Author Posted March 4, 2006 (edited) just been looking at the usb2 only version of that on svp, just asked em what chipset it has as well. and i have never had timeout using wnaspi32, can you still get the adaptec one though, is that the aspi v4.70 etc, been a while since i used them, and am i remembering correctly that 4.60 is a better choice than the newer one or was it 4.71 sucked .. it my be my new dfi lanpary ut has issues with usb2 ext boxes, there is only one bios update avail, and the bios thats in now indicates in read me that it,s supposed to fix usb2 hangs etc. And yeah i looked at how outdated 110d firmware was, but decided to just download em at the minute until i build my new computer up and install it to case /ide not gonna take chance and update firmware whilst in external. i pressume you can update them in external anyways, but not gonna even if i could. i tried also to download 1.17 from rpc seems file they link to is corrupt, as i always like to have the firmware that comes installed into any of my drives, just to put back if i have to. wonder what cypress chipset is like i will check ata-6 specs again. thanks edit, decided to buy the combo from svp as well as my 3rd philips writer, known my luck they be crap , if they are might just see how fast i can get discs to spin in them. elby i/o also gives semaphore timeout expired.. also did someone delete a post i made in this topic, or did i somehow manage to post it in a different topic, or i might have forgotten to press add reply Edited March 4, 2006 by dontasciime
dontasciime Posted March 7, 2006 Author Posted March 7, 2006 well i bought the same combo from svp usb2/firewire prolific chipset and its worse I 16:23:14 ImgBurn Version 1.2.0.0 started! I 16:23:14 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 16:23:14 Initialising SPTI... I 16:23:14 Searching for SCSI / ATAPI devices... I 16:23:15 Found 2 DVD-ROMs and 2 DVD?RWs! I 16:25:28 Operation Started! I 16:25:28 Source File: I:\NEW.MDS I 16:25:28 Source File Sectors: 1,534,320 (MODE1/2048) I 16:25:28 Source File Size: 3,142,287,360 bytes I 16:25:28 Source File Application Identifier: NERO BURNING ROM I 16:25:28 Destination Device: [0:0:0] PIONEER DVD-RW DVR-109 1.58 (Q:) (USB) I 16:25:28 Destination Media Type: DVD-R (Disc ID: TTG02) (Speeds: 4x, 6x, 8x) I 16:25:28 Destination Media Sectors: 2,297,888 I 16:25:28 Write Mode: DVD I 16:25:28 Write Type: DAO I 16:25:28 Write Speed: MAX I 16:25:28 Link Size: Auto I 16:25:28 Test Mode: No I 16:25:28 BURN-Proof: Enabled I 16:25:28 Filling Buffer... I 16:25:29 Writing LeadIn... I 16:25:52 Writing Image... W 16:25:53 Failed to Write Sectors 4256 - 4287 - The semaphore timeout period has expired. W 16:25:53 Retrying (1 of 20)... I 16:25:54 Writing Image... W 16:25:55 Failed to Write Sectors 8192 - 8223 - The semaphore timeout period has expired. W 16:25:55 Retrying (1 of 20)... I 16:25:55 Writing Image... W 16:26:00 Failed to Write Sectors 26240 - 26271 - The semaphore timeout period has expired. W 16:26:00 Retrying (1 of 20)... I 16:26:00 Writing Image... W 16:26:07 Failed to Write Sectors 52704 - 52735 - The semaphore timeout period has expired. W 16:26:07 Retrying (1 of 20)... I 16:26:07 Writing Image... W 16:26:10 Failed to Write Sectors 63296 - 63327 - The semaphore timeout period has expired. W 16:26:10 Retrying (1 of 20)... I 16:26:10 Writing Image... W 16:26:11 Failed to Write Sectors 67776 - 67807 - The semaphore timeout period has expired. W 16:26:11 Retrying (1 of 20)... I 16:26:12 Writing Image... W 16:26:13 Failed to Write Sectors 71744 - 71775 - The semaphore timeout period has expired. W 16:26:13 Retrying (1 of 20)... I 16:26:13 Writing Image... W 16:26:15 Failed to Write Sectors 79520 - 79551 - The semaphore timeout period has expired. W 16:26:15 Retrying (1 of 20)... I 16:26:15 Writing Image... W 16:26:16 Failed to Write Sectors 83936 - 83967 - The semaphore timeout period has expired. W 16:26:16 Retrying (1 of 20)... I 16:26:17 Writing Image... W 16:26:21 Failed to Write Sectors 100352 - 100383 - The semaphore timeout period has expired. W 16:26:21 Retrying (1 of 20)... I 16:26:21 Writing Image... W 16:26:21 Failed to Write Sectors 101248 - 101279 - The semaphore timeout period has expired. W 16:26:21 Retrying (1 of 20)... I 16:26:22 Writing Image... W 16:26:27 Failed to Write Sectors 122720 - 122751 - The semaphore timeout period has expired. W 16:26:27 Retrying (1 of 20)... I 16:26:27 Writing Image... W 16:26:29 Failed to Write Sectors 127840 - 127871 - The semaphore timeout period has expired. W 16:26:29 Retrying (1 of 20)... I 16:26:29 Writing Image... W 16:26:30 Failed to Write Sectors 130912 - 130943 - The semaphore timeout period has expired. W 16:26:30 Retrying (1 of 20)... I 16:26:30 Writing Image... W 16:26:31 Failed to Write Sectors 133024 - 133055 - The semaphore timeout period has expired. W 16:26:31 Retrying (1 of 20)... I 16:26:31 Writing Image... W 16:26:32 Failed to Write Sectors 135936 - 135967 - The semaphore timeout period has expired. W 16:26:32 Retrying (1 of 20)... I 16:26:32 Writing Image... W 16:26:35 Failed to Write Sectors 145856 - 145887 - The semaphore timeout period has expired. W 16:26:35 Retrying (1 of 20)... I 16:26:35 Writing Image... W 16:26:35 Failed to Write Sectors 147040 - 147071 - The semaphore timeout period has expired. W 16:26:35 Retrying (1 of 20)... I 16:26:36 Writing Image... W 16:26:41 Failed to Write Sectors 168896 - 168927 - The semaphore timeout period has expired. W 16:26:41 Retrying (1 of 20)... I 16:26:41 Writing Image... W 16:26:43 Failed to Write Sectors 175520 - 175551 - The semaphore timeout period has expired. W 16:26:43 Retrying (1 of 20)... I 16:26:43 Writing Image... W 16:26:45 Failed to Write Sectors 181568 - 181599 - The semaphore timeout period has expired. W 16:26:45 Retrying (1 of 20)... I 16:26:45 Writing Image... W 16:26:48 Failed to Write Sectors 190752 - 190783 - The semaphore timeout period has expired. W 16:26:48 Retrying (1 of 20)... I 16:26:48 Writing Image... W 16:26:48 Failed to Write Sectors 191520 - 191551 - The semaphore timeout period has expired. W 16:26:48 Retrying (1 of 20)... I 16:26:48 Writing Image... W 16:26:54 Failed to Write Sectors 197408 - 197439 - The semaphore timeout period has expired. W 16:26:54 Retrying (1 of 20)... W 16:27:00 Retry Failed - The semaphore timeout period has expired. W 16:27:00 Retrying (2 of 20)... I 16:27:01 Writing Image... W 16:27:06 Failed to Write Sectors 216000 - 216031 - The semaphore timeout period has expired. W 16:27:06 Retrying (1 of 20)... I 16:27:06 Writing Image... W 16:27:07 Failed to Write Sectors 224384 - 224415 - The semaphore timeout period has expired. W 16:27:07 Retrying (1 of 20)... I 16:27:08 Writing Image... W 16:27:10 Failed to Write Sectors 234496 - 234527 - The semaphore timeout period has expired. W 16:27:10 Retrying (1 of 20)... I 16:27:10 Writing Image... W 16:27:10 Failed to Write Sectors 236160 - 236191 - The semaphore timeout period has expired. W 16:27:10 Retrying (1 of 20)... I 16:27:11 Writing Image... W 16:27:17 Failed to Write Sectors 268512 - 268543 - The semaphore timeout period has expired. W 16:27:17 Retrying (1 of 20)... I 16:27:17 Writing Image... W 16:27:18 Failed to Write Sectors 270144 - 270175 - The semaphore timeout period has expired. W 16:27:18 Retrying (1 of 20)... I 16:27:18 Writing Image... W 16:27:21 Failed to Write Sectors 284576 - 284607 - The semaphore timeout period has expired. W 16:27:21 Retrying (1 of 20)... I 16:27:21 Writing Image... W 16:27:21 Failed to Write Sectors 285344 - 285375 - The semaphore timeout period has expired. W 16:27:21 Retrying (1 of 20)... I 16:27:21 Writing Image... W 16:27:24 Failed to Write Sectors 300608 - 300639 - The semaphore timeout period has expired. W 16:27:24 Retrying (1 of 20)... I 16:27:25 Writing Image... W 16:27:25 Failed to Write Sectors 303296 - 303327 - The semaphore timeout period has expired. W 16:27:25 Retrying (1 of 20)... I 16:27:26 Writing Image... W 16:27:27 Failed to Write Sectors 307712 - 307743 - The semaphore timeout period has expired. W 16:27:27 Retrying (1 of 20)... I 16:27:27 Writing Image... W 16:27:28 Failed to Write Sectors 312352 - 312383 - The semaphore timeout period has expired. W 16:27:28 Retrying (1 of 20)... I 16:27:28 Writing Image... W 16:27:28 Failed to Write Sectors 313120 - 313151 - The semaphore timeout period has expired. W 16:27:28 Retrying (1 of 20)... I 16:27:29 Writing Image... W 16:27:36 Failed to Write Sectors 351360 - 351391 - The semaphore timeout period has expired. W 16:27:36 Retrying (1 of 20)... I 16:27:36 Writing Image... W 16:27:41 Failed to Write Sectors 379040 - 379071 - The semaphore timeout period has expired. W 16:27:41 Retrying (1 of 20)... I 16:27:42 Writing Image... W 16:27:45 Failed to Write Sectors 395936 - 395967 - The semaphore timeout period has expired. W 16:27:45 Retrying (1 of 20)... I 16:27:45 Writing Image... W 16:27:46 Failed to Write Sectors 397440 - 397471 - The semaphore timeout period has expired. W 16:27:46 Retrying (1 of 20)... I 16:27:46 Writing Image... W 16:27:49 Failed to Write Sectors 408480 - 408511 - The semaphore timeout period has expired. W 16:27:49 Retrying (1 of 20)... I 16:27:49 Writing Image... W 16:27:50 Failed to Write Sectors 411328 - 411359 - The semaphore timeout period has expired. W 16:27:50 Retrying (1 of 20)... I 16:27:50 Writing Image... W 16:27:51 Failed to Write Sectors 416224 - 416255 - The semaphore timeout period has expired. W 16:27:51 Retrying (1 of 20)... I 16:27:51 Writing Image... W 16:27:51 Failed to Write Sectors 416992 - 417023 - The semaphore timeout period has expired. W 16:27:51 Retrying (1 of 20)... I 16:27:52 Writing Image... W 16:27:58 Failed to Write Sectors 448384 - 448415 - The semaphore timeout period has expired. W 16:27:58 Retrying (1 of 20)... I 16:27:58 Writing Image... W 16:28:00 Failed to Write Sectors 461888 - 461919 - The semaphore timeout period has expired. W 16:28:00 Retrying (1 of 20)... I 16:28:01 Writing Image... W 16:28:04 Failed to Write Sectors 476960 - 476991 - The semaphore timeout period has expired. W 16:28:04 Retrying (1 of 20)... I 16:28:04 Writing Image... W 16:28:08 Failed to Write Sectors 497568 - 497599 - The semaphore timeout period has expired. W 16:28:08 Retrying (1 of 20)... I 16:28:08 Writing Image... W 16:28:09 Failed to Write Sectors 502976 - 503007 - The semaphore timeout period has expired. W 16:28:09 Retrying (1 of 20)... I 16:28:10 Writing Image... W 16:28:15 Failed to Write Sectors 531008 - 531039 - The semaphore timeout period has expired. W 16:28:15 Retrying (1 of 20)... I 16:28:15 Writing Image... W 16:28:19 Failed to Write Sectors 548544 - 548575 - The semaphore timeout period has expired. W 16:28:19 Retrying (1 of 20)... I 16:28:19 Writing Image... W 16:28:20 Failed to Write Sectors 552224 - 552255 - The semaphore timeout period has expired. W 16:28:20 Retrying (1 of 20)... I 16:28:20 Writing Image... W 16:28:23 Failed to Write Sectors 569408 - 569439 - The semaphore timeout period has expired. W 16:28:23 Retrying (1 of 20)... I 16:28:24 Writing Image... W 16:28:26 Failed to Write Sectors 581824 - 581855 - The semaphore timeout period has expired. W 16:28:26 Retrying (1 of 20)... I 16:28:26 Writing Image... W 16:28:35 Failed to Write Sectors 628384 - 628415 - The semaphore timeout period has expired. W 16:28:35 Retrying (1 of 20)... I 16:28:36 Writing Image... W 16:28:37 Failed to Write Sectors 635456 - 635487 - The semaphore timeout period has expired. W 16:28:37 Retrying (1 of 20)... I 16:28:37 Writing Image... W 16:28:39 Failed to Write Sectors 644256 - 644287 - The semaphore timeout period has expired. W 16:28:39 Retrying (1 of 20)... I 16:28:39 Writing Image... W 16:28:42 Failed to Write Sectors 661248 - 661279 - The semaphore timeout period has expired. W 16:28:42 Retrying (1 of 20)... I 16:28:43 Writing Image... W 16:28:43 Failed to Write Sectors 662720 - 662751 - The semaphore timeout period has expired. W 16:28:43 Retrying (1 of 20)... I 16:28:43 Writing Image... W 16:28:44 Failed to Write Sectors 665280 - 665311 - The semaphore timeout period has expired. W 16:28:44 Retrying (1 of 20)... I 16:28:44 Writing Image... W 16:28:48 Failed to Write Sectors 683744 - 683775 - The semaphore timeout period has expired. W 16:28:48 Retrying (1 of 20)... I 16:28:48 Writing Image... W 16:28:49 Failed to Write Sectors 687328 - 687359 - The semaphore timeout period has expired. W 16:28:49 Retrying (1 of 20)... I 16:28:49 Writing Image... W 16:28:49 Failed to Write Sectors 688096 - 688127 - The semaphore timeout period has expired. W 16:28:49 Retrying (1 of 20)... I 16:28:50 Writing Image... W 16:28:57 Failed to Write Sectors 727232 - 727263 - The semaphore timeout period has expired. W 16:28:57 Retrying (1 of 20)... I 16:28:57 Writing Image... W 16:29:01 Failed to Write Sectors 746880 - 746911 - The semaphore timeout period has expired. W 16:29:01 Retrying (1 of 20)... I 16:29:01 Writing Image... W 16:29:02 Failed to Write Sectors 749184 - 749215 - The semaphore timeout period has expired. W 16:29:02 Retrying (1 of 20)... I 16:29:02 Writing Image... W 16:29:03 Failed to Write Sectors 751648 - 751679 - The semaphore timeout period has expired. W 16:29:03 Retrying (1 of 20)... I 16:29:03 Writing Image... W 16:29:08 Failed to Write Sectors 777472 - 777503 - The semaphore timeout period has expired. W 16:29:08 Retrying (1 of 20)... I 16:29:08 Writing Image... W 16:29:11 Failed to Write Sectors 790272 - 790303 - The semaphore timeout period has expired. W 16:29:11 Retrying (1 of 20)... I 16:29:11 Writing Image... W 16:29:13 Failed to Write Sectors 799872 - 799903 - The semaphore timeout period has expired. W 16:29:13 Retrying (1 of 20)... I 16:29:14 Writing Image... W 16:29:14 Failed to Write Sectors 801024 - 801055 - The semaphore timeout period has expired. W 16:29:14 Retrying (1 of 20)... I 16:29:14 Writing Image... W 16:29:15 Failed to Write Sectors 803456 - 803487 - The semaphore timeout period has expired. W 16:29:15 Retrying (1 of 20)... I 16:29:15 Writing Image... W 16:29:16 Failed to Write Sectors 811136 - 811167 - The semaphore timeout period has expired. W 16:29:16 Retrying (1 of 20)... I 16:29:17 Writing Image... W 16:29:18 Failed to Write Sectors 815104 - 815135 - The semaphore timeout period has expired. W 16:29:18 Retrying (1 of 20)... I 16:29:18 Writing Image... W 16:29:23 Failed to Write Sectors 842656 - 842687 - The semaphore timeout period has expired. W 16:29:23 Retrying (1 of 20)... I 16:29:23 Writing Image... W 16:29:27 Failed to Write Sectors 859424 - 859455 - The semaphore timeout period has expired. W 16:29:27 Retrying (1 of 20)... I 16:29:27 Writing Image... W 16:29:29 Failed to Write Sectors 868352 - 868383 - The semaphore timeout period has expired. W 16:29:29 Retrying (1 of 20)... I 16:29:29 Writing Image... W 16:29:29 Failed to Write Sectors 869280 - 869311 - The semaphore timeout period has expired. W 16:29:29 Retrying (1 of 20)... I 16:29:30 Writing Image... W 16:29:32 Failed to Write Sectors 880192 - 880223 - The semaphore timeout period has expired. W 16:29:32 Retrying (1 of 20)... I 16:29:32 Writing Image... W 16:29:33 Failed to Write Sectors 885888 - 885919 - The semaphore timeout period has expired. W 16:29:33 Retrying (1 of 20)... I 16:29:34 Writing Image... W 16:29:35 Failed to Write Sectors 890944 - 890975 - The semaphore timeout period has expired. W 16:29:35 Retrying (1 of 20)... I 16:29:35 Writing Image... W 16:29:39 Failed to Write Sectors 913856 - 913887 - The semaphore timeout period has expired. W 16:29:39 Retrying (1 of 20)... I 16:29:39 Writing Image... W 16:29:42 Failed to Write Sectors 928064 - 928095 - The semaphore timeout period has expired. W 16:29:42 Retrying (1 of 20)... I 16:29:43 Writing Image... W 16:29:48 Failed to Write Sectors 955680 - 955711 - The semaphore timeout period has expired. W 16:29:48 Retrying (1 of 20)... I 16:29:48 Writing Image... W 16:29:49 Failed to Write Sectors 961024 - 961055 - The semaphore timeout period has expired. W 16:29:49 Retrying (1 of 20)... I 16:29:49 Writing Image... W 16:29:50 Failed to Write Sectors 962528 - 962559 - The semaphore timeout period has expired. W 16:29:50 Retrying (1 of 20)... I 16:29:50 Writing Image... W 16:29:53 Failed to Write Sectors 978656 - 978687 - The semaphore timeout period has expired. W 16:29:53 Retrying (1 of 20)... I 16:29:54 Writing Image... W 16:30:01 Failed to Write Sectors 1013280 - 1013311 - The semaphore timeout period has expired. W 16:30:01 Retrying (1 of 20)... I 16:30:01 Writing Image... W 16:30:02 Failed to Write Sectors 1016032 - 1016063 - The semaphore timeout period has expired. W 16:30:02 Retrying (1 of 20)... I 16:30:02 Writing Image... W 16:30:03 Failed to Write Sectors 1018656 - 1018687 - The semaphore timeout period has expired. W 16:30:03 Retrying (1 of 20)... I 16:30:03 Writing Image... W 16:30:06 Failed to Write Sectors 1032992 - 1033023 - The semaphore timeout period has expired. W 16:30:06 Retrying (1 of 20)... I 16:30:06 Writing Image... W 16:30:09 Failed to Write Sectors 1047392 - 1047423 - The semaphore timeout period has expired. W 16:30:09 Retrying (1 of 20)... I 16:30:09 Writing Image... W 16:30:14 Failed to Write Sectors 1074112 - 1074143 - The semaphore timeout period has expired. W 16:30:14 Retrying (1 of 20)... I 16:30:15 Writing Image... W 16:30:15 Failed to Write Sectors 1076096 - 1076127 - The semaphore timeout period has expired. W 16:30:15 Retrying (1 of 20)... I 16:30:15 Writing Image... W 16:30:16 Failed to Write Sectors 1078464 - 1078495 - The semaphore timeout period has expired. W 16:30:16 Retrying (1 of 20)... I 16:30:16 Writing Image... W 16:30:16 Failed to Write Sectors 1079552 - 1079583 - The semaphore timeout period has expired. W 16:30:16 Retrying (1 of 20)... I 16:30:17 Writing Image... W 16:30:17 Failed to Write Sectors 1080320 - 1080351 - The semaphore timeout period has expired. W 16:30:17 Retrying (1 of 20)... I 16:30:17 Writing Image... W 16:30:27 Failed to Write Sectors 1131840 - 1131871 - The semaphore timeout period has expired. W 16:30:27 Retrying (1 of 20)... I 16:30:27 Writing Image... W 16:30:28 Failed to Write Sectors 1134656 - 1134687 - The semaphore timeout period has expired. W 16:30:28 Retrying (1 of 20)... I 16:30:28 Writing Image... W 16:30:29 Failed to Write Sectors 1141248 - 1141279 - The semaphore timeout period has expired. W 16:30:29 Retrying (1 of 20)... I 16:30:30 Writing Image... W 16:30:32 Failed to Write Sectors 1153376 - 1153407 - The semaphore timeout period has expired. W 16:30:32 Retrying (1 of 20)... I 16:30:32 Writing Image... W 16:30:34 Failed to Write Sectors 1159296 - 1159327 - The semaphore timeout period has expired. W 16:30:34 Retrying (1 of 20)... I 16:30:34 Writing Image... W 16:30:35 Failed to Write Sectors 1163552 - 1163583 - The semaphore timeout period has expired. W 16:30:35 Retrying (1 of 20)... I 16:30:35 Writing Image... W 16:30:40 Failed to Write Sectors 1192224 - 1192255 - The semaphore timeout period has expired. W 16:30:40 Retrying (1 of 20)... I 16:30:41 Writing Image... W 16:30:43 Failed to Write Sectors 1200448 - 1200479 - The semaphore timeout period has expired. W 16:30:43 Retrying (1 of 20)... I 16:30:43 Writing Image... W 16:30:45 Failed to Write Sectors 1212256 - 1212287 - The semaphore timeout period has expired. W 16:30:45 Retrying (1 of 20)... I 16:30:46 Writing Image... W 16:30:52 Failed to Write Sectors 1245696 - 1245727 - The semaphore timeout period has expired. W 16:30:52 Retrying (1 of 20)... I 16:30:52 Writing Image... W 16:30:54 Failed to Write Sectors 1252096 - 1252127 - The semaphore timeout period has expired. W 16:30:54 Retrying (1 of 20)... I 16:30:54 Writing Image... W 16:30:55 Failed to Write Sectors 1256416 - 1256447 - The semaphore timeout period has expired. W 16:30:55 Retrying (1 of 20)... I 16:30:55 Writing Image... W 16:30:58 Failed to Write Sectors 1269728 - 1269759 - The semaphore timeout period has expired. W 16:30:58 Retrying (1 of 20)... I 16:30:58 Writing Image... W 16:31:04 Failed to Write Sectors 1297728 - 1297759 - The semaphore timeout period has expired. W 16:31:04 Retrying (1 of 20)... I 16:31:04 Writing Image... W 16:31:08 Failed to Write Sectors 1321088 - 1321119 - The semaphore timeout period has expired. W 16:31:08 Retrying (1 of 20)... I 16:31:09 Writing Image... W 16:31:09 Failed to Write Sectors 1321856 - 1321887 - The semaphore timeout period has expired. W 16:31:09 Retrying (1 of 20)... I 16:31:09 Writing Image... W 16:31:11 Failed to Write Sectors 1328448 - 1328479 - The semaphore timeout period has expired. W 16:31:11 Retrying (1 of 20)... I 16:31:11 Writing Image... W 16:31:15 Failed to Write Sectors 1348768 - 1348799 - The semaphore timeout period has expired. W 16:31:15 Retrying (1 of 20)... I 16:31:15 Writing Image... W 16:31:16 Failed to Write Sectors 1352352 - 1352383 - The semaphore timeout period has expired. W 16:31:16 Retrying (1 of 20)... I 16:31:16 Writing Image... W 16:31:17 Failed to Write Sectors 1355296 - 1355327 - The semaphore timeout period has expired. W 16:31:17 Retrying (1 of 20)... I 16:31:17 Writing Image... W 16:31:19 Failed to Write Sectors 1367648 - 1367679 - The semaphore timeout period has expired. W 16:31:19 Retrying (1 of 20)... I 16:31:20 Writing Image... W 16:31:24 Failed to Write Sectors 1391776 - 1391807 - The semaphore timeout period has expired. W 16:31:24 Retrying (1 of 20)... I 16:31:25 Writing Image... W 16:31:25 Failed to Write Sectors 1392832 - 1392863 - The semaphore timeout period has expired. W 16:31:25 Retrying (1 of 20)... I 16:31:25 Writing Image... W 16:31:28 Failed to Write Sectors 1409856 - 1409887 - The semaphore timeout period has expired. W 16:31:28 Retrying (1 of 20)... I 16:31:29 Writing Image... W 16:31:33 Failed to Write Sectors 1430080 - 1430111 - The semaphore timeout period has expired. W 16:31:33 Retrying (1 of 20)... I 16:31:33 Writing Image... W 16:31:41 Failed to Write Sectors 1472192 - 1472223 - The semaphore timeout period has expired. W 16:31:41 Retrying (1 of 20)... I 16:31:41 Writing Image... W 16:31:43 Failed to Write Sectors 1480320 - 1480351 - The semaphore timeout period has expired. W 16:31:43 Retrying (1 of 20)... I 16:31:43 Writing Image... W 16:31:45 Failed to Write Sectors 1491520 - 1491551 - The semaphore timeout period has expired. W 16:31:45 Retrying (1 of 20)... I 16:31:46 Writing Image... W 16:31:47 Failed to Write Sectors 1495072 - 1495103 - The semaphore timeout period has expired. W 16:31:47 Retrying (1 of 20)... I 16:31:47 Writing Image... W 16:31:48 Failed to Write Sectors 1498208 - 1498239 - The semaphore timeout period has expired. W 16:31:48 Retrying (1 of 20)... I 16:31:48 Writing Image... W 16:31:48 Failed to Write Sectors 1499520 - 1499551 - The semaphore timeout period has expired. W 16:31:48 Retrying (1 of 20)... I 16:31:48 Writing Image... W 16:31:49 Failed to Write Sectors 1500640 - 1500671 - The semaphore timeout period has expired. W 16:31:49 Retrying (1 of 20)... I 16:31:49 Writing Image... W 16:31:52 Failed to Write Sectors 1514912 - 1514943 - The semaphore timeout period has expired. W 16:31:52 Retrying (1 of 20)... I 16:31:52 Writing Image... W 16:31:53 Failed to Write Sectors 1518336 - 1518367 - The semaphore timeout period has expired. W 16:31:53 Retrying (1 of 20)... I 16:31:53 Writing Image... W 16:31:53 Failed to Write Sectors 1519904 - 1519935 - The semaphore timeout period has expired. W 16:31:53 Retrying (1 of 20)... I 16:31:54 Writing Image... W 16:31:55 Failed to Write Sectors 1524000 - 1524031 - The semaphore timeout period has expired. W 16:31:55 Retrying (1 of 20)... I 16:31:55 Writing Image... W 16:31:56 Failed to Write Sectors 1526528 - 1526559 - The semaphore timeout period has expired. W 16:31:56 Retrying (1 of 20)... I 16:31:56 Writing Image... W 16:31:56 Failed to Write Sectors 1527296 - 1527327 - The semaphore timeout period has expired. W 16:31:56 Retrying (1 of 20)... I 16:31:57 Writing Image... I 16:31:58 Synchronising Cache... I 16:32:14 Operation Successfully Completed! - Duration: 00:06:46 I 16:32:14 Average Write Rate: 8,384 KB/s (6.1x) - Maximum Write Rate: 11,141 KB/s (8.0x)
LIGHTNING UK! Posted March 7, 2006 Posted March 7, 2006 Did you update the firmware on the enclosure? That's the only thing I've done. If that doesn't work for you, it must be something else in your pc that's causing it.
dontasciime Posted March 7, 2006 Author Posted March 7, 2006 (edited) is the firmware for the enclosure on the supplied disc, can you also jump backward and forward between firmwares for the enclosure ? I stuck one of the 3 philips drives i got from svp and its fine for 5 burns so far. so it would appear that either my 109 is responsible(it has latest firmware 1.58) unless there is a 1.59, strange that my brand new 110 (1.17) seemed to do same thing as the 109 in the ICY box though if i can be bothered might try the 110 in the new enclosure from svp... I 17:43:45 ImgBurn Version 1.2.0.0 started! I 17:43:45 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 17:43:45 Initialising SPTI... I 17:43:45 Searching for SCSI / ATAPI devices... I 17:43:46 Found 2 DVD-ROMs and 2 DVD?RWs! I 17:44:14 Operation Started! I 17:44:14 Source File: H:\more shrink\goal\GOAL.ISO I 17:44:14 Source File Sectors: 2,145,467 (MODE1/2048) I 17:44:14 Source File Size: 4,393,916,416 bytes I 17:44:14 Source File Implementation Identifier: DVD Shrink I 17:44:14 Destination Device: [0:0:0] PHILIPS SPD2400L1 Y5H3 (Q:) (USB) I 17:44:14 Destination Media Type: DVD-R (Disc ID: TTG02) (Speeds: 4x, 6x, 8x) I 17:44:14 Destination Media Sectors: 2,297,888 I 17:44:14 Write Mode: DVD I 17:44:14 Write Type: DAO I 17:44:14 Write Speed: 8x I 17:44:14 Link Size: Auto I 17:44:14 Test Mode: No I 17:44:14 BURN-Proof: Enabled I 17:44:14 Filling Buffer... I 17:44:14 Writing LeadIn... I 17:45:02 Writing Image... I 17:52:00 Synchronising Cache... I 17:52:19 Operation Successfully Completed! - Duration: 00:08:05 I 17:52:19 Average Write Rate: 10,290 KB/s (7.4x) - Maximum Write Rate: 11,148 KB/s (8.0x) brand new computer as well, clean install, no conflicts at all, irq's all fine so i cannot see it being the computer, unless it hates pioneers hardware whilst using usb2. Edited March 7, 2006 by dontasciime
LIGHTNING UK! Posted March 7, 2006 Posted March 7, 2006 Nah, you have to download the firmware from prolific. http://www.prolific.com.tw/eng/downloads.asp?ID=44 You need the flasher and the firmware itself. Both are on that page. The enclosure firmware isn't like burner ones... there should be no benefit from going backwards - i.e. if write strategies got mucked up! Do just double check it's using the PL3507 chipset though yeah
dontasciime Posted March 7, 2006 Author Posted March 7, 2006 (edited) i searched on google just checked back in here to ask if there is a way to find out the firmware already on the enclosure, i have not finished reading about it yet, so that info may be on their site, or maybe it show you when you run the program. i have downloaded all the firmwares, i have to have the firmware i am using, just a rule i like to keep to, as i have no probs with the firmware in enclosure using the philips drive. def 3507 as looked at chip on pcb as soon as i got it. that def the romwriter i need to run yeah ? Edited March 7, 2006 by dontasciime
LIGHTNING UK! Posted March 7, 2006 Posted March 7, 2006 looks good to me. Flash with it connected to usb rather than firewire. Mine didn't work on firewire when I first tried it.
dontasciime Posted March 7, 2006 Author Posted March 7, 2006 (edited) ta, was planning to use usb to flash, if i decide to do it, will run it with the philips drive for now, then if i suspect after getting my pioneer 111 in a few days time i may try the 111 in enclosure, if i get any issues with it i will update firmware in enclosure... Did you get one of the philips drives ?19.99 from svp ? I quite like the burn from what i have seen of it, i like the way the write rate steadily goes up and the buffer only slightly fluctuates Edited March 7, 2006 by dontasciime
LIGHTNING UK! Posted March 7, 2006 Posted March 7, 2006 You shouldn't wait for a problem to manifest itself, just flash the enclosure and be done with it! Yeah I ordered one of those philips drives today - for no reason at all - I already have a liteon 1635! Just good to have a wide range so I can help people with problems.
dontasciime Posted March 7, 2006 Author Posted March 7, 2006 LOL. Can only fit one drive in enclosure at a time. just pleased it works with the philips, gonna start builing up one of my new 939 boards msi k8n neo plat2, well it aint new i had it 17months sat in cupboard, will try 109 in there and see if its fooked, only burnt about 30 discs on it, got no idea when or where i bought it. Might order another one of these enclosures and another philips drive, then test the 109 in that enclosure and then update firmware in enclosure to see if it fixes it etc, though i suspect the 109 has had it, will put one of the other philips i got back in ICY box and try that also. The other enclosure that svp sell the usb only uses genesys GL811 chipset you ever used anything with that in or anyone else reading this ever used an enclosure that uses that chipset ?
LIGHTNING UK! Posted March 7, 2006 Posted March 7, 2006 I don't bother screwing my drives into the usb case, I use that as my quick swap method of testing out all the drives! I put a proper ide cable on it and a power extension to ease swapping drives in and out. Interesting about the USB enclosure, I'd have expected it to be prolific like the usb/firewire one. Not seen that chipset, no, sorry.
dbminter Posted March 9, 2006 Posted March 9, 2006 My enclosure doesn't even have a top anymore. It's just the bottom tray and the board at the back with the IDE to USB bridge chip, power in, etc. That way, I can easily slip in drives as needed for testing, temporary HD storage, etc.
dbminter Posted March 9, 2006 Posted March 9, 2006 I have to use wnaspi32 with my external dvd writer, as spti and the chipset in my external writer (ali chipset revision 1 no flash) do not get on IE you get Semaphore time out.I got imgburn using wnaspi32 and the older program using spti for internal writing on 108 You say you didn't get a semaphore time out with ALi Rev. 1a m5621 on wnaspi32 with ImgBurn? I have not tested my drive with ImgBurn yet. I was getting semaphore time out with another certain app most unfortunately lost forever to the history of time with ALi M5621 A1 0348 TH05 XHG2QK00000I to be precise.
dontasciime Posted March 9, 2006 Author Posted March 9, 2006 (edited) i wasnt using my k8n neo plat, but that blew up, replaced it with dfi lanparty ut, then it started whilst using wnaspi32, but i suspect my 109 is broken as using the new enclosure i got from svp which uses prolific chipset , i got 97 semaphore errors after disc finished burning using spti though, but the new philips drive is OK, so gonna do some further testing today as i got another enclosure that uses prolific and anotehr one of those philips drives from svp to test, though the test will involve my pioneer 109 and 110, on dfi, then on msi k8n neo plat 2 i just built up. [edit] when using the elby io and the icy box which uses ali m5621 1a was getting loads of semaphore time out errors as well on the suspected faulty 109 Edited March 9, 2006 by dontasciime
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now