Jump to content

liam

Members
  • Posts

    14
  • Joined

  • Last visited

liam's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. For now I'm using DVDdecrypter to get finalised burns which works around the problem
  2. I've done a whole bunch of test burns and so far here's what I've found out - Where ImgBurn can't finalise a burn DVDdecrypter can. Microsoft AHCI drivers for Vista (32 & 64) aren't 100% functional, they block commands for manual booktyping, ImgBurn reports 'unknown function', Nvidia's drivers allows manual booktyping but they're still not 100% as ImgBurn can't finalise, going back to XP@SP2 with AHCI was the same. MS's generic Vista ATA driver (SATA in IDE mode in BIOS) doesn't work properly on the Nvidia chipset on my Abit AN-M2HD boards BUT ImgBurn finalises the burn and it's auto booktyped to ROM but it can't verify a burn as the drive seems to stop sending data during the verify, the disks work in other devices. All of the S203B/Ns I have behave exactly the same, the burns have low PIF/POF rates on TY media. Conclusion - Nvidia's MCP68 (630a/7050PV) chipset SUCKS!
  3. Earlier I finished installing Vista64 etc on another PC so I tried to use a brand new S203N with ImgBurn to burn a disk, same "Potential 'WaitImmediateIO' Deferred Error - (99%, 0/3) - Program Memory Area Update Failure" resulting in a disk which can't be read by other devices. After a little bit of thought I tried to remember when this problem first began and realising it was some time ago I installed DVD Decrypter 3.5.4.0 (the final release I think) and burnt a disk which finalised and can be read by other devices My next step will be to plug in another HDD and install Vista64 with only the motherboard drivers and no windows updates or other software and try ImgBurn again to try and track down the source of the problem PS have just replicated this on the original problem PC with the S203Bs they burn without error in DVD Devrypter but have finalise error with ImgBurn I 00:35:00 DVD Decrypter Version 3.5.4.0 started! I 00:35:00 Microsoft Windows Code Name "Longhorn" Media Center Edition (6.0, Build 6001 : Service Pack 1) I 00:35:00 Initialising SPTI... I 00:35:00 Searching for SCSI / ATAPI devices... I 00:35:20 Found 1 DVD-ROM and 2 DVD-RAM/
  4. I have several more new S203s, one B and 2 Ns, which I bought when I couldn't get anything to booktype or finalise, they were only
  5. I tried it out this morning and it burned without any errors being reported but sadly both burnt disks don't play in my standalones or PS3 and aren't recognised by PX716 or PX760, though they are fine the S203s. Here's the log ImgBurn.log
  6. Just checked the control panel for the forums and my email address is correct I'll try it out asap and let you know the result
  7. here's the copy+paste from the right hand panel TSSTcorp CDDVDW SH-S203B SB03 (Fibre) Current Profile: DVD+R Disc Information: Status: Complete Erasable: No Sessions: 1 Sectors: 2,040,320 Size: 4,178,575,360 bytes Time: 453:26:20 (MM:SS:FF) TOC Information: Session 1... -> Track 01 (Mode 1, LBA: 0 - 2040319) -> LeadOut (LBA: 2040320) Track Information: Session 1... -> Track 01 (LTSA: 0, TS: 2040320, LRA: 0) Disc Control Blocks Information: TSSTcorp SH-S183B Physical Format Information (ADIP): Disc ID: MCC-004-00 Book Type: DVD+R 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,491,711 Last Physical Sector in Layer 0: 0 Physical Format Information (Last Recorded): Disc ID: MCC-004-00 Book Type: DVD+R 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,236,927 Last Physical Sector in Layer 0: 0 the here's the log file from burning and verifying the disk in the Samsung ImgBurn.log I tried the disk in an old standalone it says 'disk cannot be played (may be faulty)', another newer Toshiba 'The disc is not DVD format. Cannot play this disc' and the PS3 little blue light comes on and it makes some seeking noises but then stops after a few seconds and doesn't recognise it enough to play.
  8. No the two disk I just burnt are scrap, no standalone I have tried will play them, usual error is something like 'insert a DVD', PS3 says something like 'not a playable disc', my Plextor PX716A and PX760A don't recognise the disks both drives sit there with the yellow light flashing, the Samsungs will happily verify the disk and if you open PowerDVD they will play them too. If it's helpful I will burn another with verify and post the log.
  9. If you mean where talked about how running set as SATA IDE in the BIOS causes a problem? It's MS's generic driver not working 100% with the motherboard BIOS or chipset which isn't ImgBurns fault and it can fixed by just putting the BIOS back to SATA AHCI and letting Vista use the MS AHCI driver or forcing Nvidia's in. If you think the info will be helpful I can recreate it by just reverting the settings in the BIOS and in Vista. ISOburner 1.1 will burn the same image files that ImgBurn can't seem to finalise with the S203Bs, just to be completely clear - ImgBurn will burn the files on other burners, its just the S203Bs and S203Ns that don't want to work. Linkage http://www.ntfs.com/iso-burning.htm
  10. It's been so long since I used to ImgBurn on this PC that I had to check if it was installed after the the last reinstall of Vista, I did a couple of burns, here is what I get, I tried two burns the first one is Write settings at defaults and the second is with Auto booktyping unticked, I did remember to quit and restart ImgBurn for the settings change to take effect. ImgBurn.log
  11. I have two S203Bs running in AHCI on an Abit AN-M2HD (Nvidia 630a/7050). ImgBurn's manual booktyping does not function with Vista's MS AHCI driver resulting in 'unknown function'. Setting to SATA IDE in the BIOS doesn't help as then strange things happen during burn verification, basically the data transfer just kinda stops and ImgBurn is left just sitting waiting for something from the drive/OS (I'm guessing) and rebooting is the only way to recover. Recently I persuaded Vista64 to accept the Nvidia SATA driver and that lets ImgBurn manual booktyping work but ImgBurn still can't finalise any DVD+R in the S203Bs, it fails with either burner, the resulting disks won't play on standalones, PS3 and my other PCs won't recognise them. For me the auto retry on finalise is a waste Annoyingly enough some other burning tools manage to finalise their burns and the disks play on standalones and are recognised by other PCs. I can even use ImgBurns manual booktyping to set DVD+R to DVD-ROM and then close ImgBurn and burn with another tool and the disks come out booktyped as DVD-ROM I'd rather use ImgBurn but just can't get the S203B or S203N burners to work with it So I use IsoBurner with my S203s. ImgBurn works beatifully on my other PCs with Plextor and BenQ burners. I don't have those PIF spikes at the end of burns, here's a 16x burn on Verbatim DVD+R 16x that I just did
  12. Hi, just discovered this possible bug - I used InstantCopy to prepare a crunched down disk, when I tried to burn the image ImgBurn 1.1.0.0 got the end of the first file (xxx.pdi) and instead of carrying on (with xxx.pdi01) it popped up a message about unexpected end of file. I fired up DVD Decrypter and it burned the files without any problems at all.
  13. ) don't you wish all software developed this way? excellent, cheers
  14. when imgburn puts itself into the quick launch bar it uses the exact same (well looks like it) as DVDdecrypter used to, please do a minature version of the new imgburn icon (the one with the little flame on it) for when its on the quick launch bar.
×
×
  • Create New...

Important Information

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