Jump to content


  • Content Count

  • Joined

  • Last visited

About Sigma

  • Rank
    ISF Newbie
  1. Sigma

    imgBURN now classified as a virus by ESET antivirus

    All antivirus products should be blocking this stuff. Everyone knows that devs only make money from this through user carelessness. If the options to install bundled software were unchecked by default, virtually nobody would actually choose to install that stuff, but money is being made because people often don't pay close attention to each step of the installer. The makers of Open Candy know this. Lightning UK knows this. That's why you should find an alternate program to ImgBurn and boycott it until it's no longer being used as a malware distribution tool.
  2. Sigma

    Imageburn and Sony Optriac

    I have the same drive with the same firmware and the device buffer only goes up to 96% for me too. Burns are very good quality though, so I've never worried about it. It was the same on for me as well.
  3. Hmmm, I've never used iTunes. It definitely wasn't there in though because I used to remove a filter driver called pfc.sys, leaving no others remaining. According to the file's properties, it's been on my system since February 25th. It's no big deal anyway. I was just wondering why it suddenly showed up in ImgBurn. Thanks for the reply.
  4. Technically that is true, but then this kind of thing does relies on people being click-happy, because who would actually choose to change their search provider and home page unless they were unaware what those terms even meant? If that wasn't the case, the options would be unchecked by default, not checked, and then I don't think anyone would have a problem with it.
  5. When I was using and I want to Tools - Filter Driver Load Order... there were no filter drivers listed there. I upgraded to, but now when I look at the filter drivers, this one is showing up: - Looking at the date of the SYS file, it's been on my machine since February, which I think might coincide with me doing a clean install of Windows 8 Pro. Is this file part of a stock Windows 8 install? Is it just a case of not picking it up, even though it was there? The only burning software I've got installed aside from ImgBurn is Ashampoo Burning Studio 12, but I installed that months ago and it hasn't been updated in ages. In fact, I haven't installed any new software at all on this machine in quite a long time, aside from updating existing software. It doesn't seem to be causing any issues. I'm just wondering where that file came from and why it wasn't detected by even though the file has been on my machine since February.
  6. I found what the problem was a few weeks ago, so I thought I'd come back and post it in case anyone else has the same issues with one of these high end ASUS mATX boards. When I started this thread, I had a Maximus IV Gene-Z/Gen3 board. After convincing myself that that must be the cause of my woes, I got a Maximus V Gene board instead, but I had the same problems with that too. It turns out that in both cases, I hadn't installed a necessary driver. Device Manager didn't show any issues, so I assumed that all of the drivers for all of my hardware were installed already, particularly as I occasionally got a good burn. But the SATA ports on these boards are controlled by 2 different controllers - an Intel one and an ASMedia one. Both boards only have 2 Intel ports and I had an SSD and a HDD plugged into those. I had my optical drive plugged into one of the ASMedia ports, but I had not installed the ASMedia drivers. As soon as I installed the ASMedia drivers a new entry appeared in Device Manager under IDE ATA/ATAPI controllers and in ImgBurn's family tree and I have not had a single issue since.
  7. I built a new PC last year. It's built around an ASUS Maximus IV Gene-Z/Gen3 motherboard. It has 6 SATA ports, 2 red and 4 black. My SSD and hard drive are hooked up to the red ports and work just fine. I was using Windows 7 and am now using Windows 8. I just cannot get a consistently good burn with dual layer media with ImgBurn. Burns fail with a variety of errors in the log. Here's the latest failed attempt: - I always use Verbatim MKM-003-00 discs. I have tried different spindles of discs. I have tried 4 different burners: - iHAS 124B iHAS 224B Sony Optiarc AD-5280S-PLUS (2 of them with the latest firmware) I have tried all 4 unused SATA ports. I have tried different SATA cables. The BIOS is up to date. All of the drivers, including the chipset drivers, are up to date. There are no filter drivers or other software causing issues. I have tried different burn speeds. When I was using the iHAS drives I tried different combinations of drive settings. I have tried alternative burning software such as CloneCD. Nothing works. I am getting to the end of my tether with this, as I just cannot see what the problem is. If the SATA controller on my MOBO was faulty, surely that wouldn't just affect burning discs? Wouldn't it affect other SATA devices as well, including my SSD/HDD? Is getting an external enclosure and connecting a burner via USB worth a try? Thanks for any help you can give.
  8. Sigma

    1.Z8 firmware

    Both drives turned up today and both have 1.Z8 pre-flashed.
  9. Sigma

    1.Z8 firmware

    I'll ask this here as it doesn't seem worth starting another thread for..... I'm waiting on a couple of these drives to arrive from the US. Is 1.Z8 the firmware that's pre-installed on them and if not, where can I download a firmware update? I can't find firmware downloads for this drive anywhere. Thanks.
  10. It's already fairly easy to use, but it would be good if it was built into ImgBurn with a checkbox to enable/disable it, so that if it was enabled, you could overburn DVD+R DL discs without having to take any other action.
  11. I retried the burn that I attempted in post 10 and this time it worked, but I'm still getting a success rate of about 1 in 4 or 1 in 5, which means a lot of binned discs. I haven't used Disc Juggler for years and it's never been installed on this machine. The only other burning software I have is Ashampoo Burning Studio 10, although I've had that installed for months and it hasn't been updated in that time, so I don't think it's that that's causing the issue, even if it's what placed the pfc.sys file on my machine. I'll try your other suggestions next time I need to burn a dual layer disc. Thanks for your help so far.
  12. Sigma

    Firmware update

    I don't think your drive is fake. I think that Asus just didn't add it to their product range on their website until after it was commercially available. Unless you're having burning issues, I don't think you have anything to worry about as you have a decent drive with the latest firmware installed.
  13. Sigma

    XGD3 Burn Problems

    As you've only had 1 successful burn, it could just be a coincidence regarding the update, but you could try uninstalling the update/rolling it back to see if that has any effect. Unless you can get good burns consistently over and over again (or with just the occasional failure here and there), I wouldn't attribute the issue to any 1 particular cause just yet.
  14. Sigma

    XGD3 Burn Problems

    Have you tried another spindle of discs? Have you successfully burned games to Verbatim MKM-001 discs before with that drive? Have you looked to see if there's a firmware update for your burner? I had a quick look via Google, but I couldn't see one, but one may be available. It's also possible that the drive is on the way out. You could try a lens cleaning disc though. Also, that's a slimline burner isn't it? They're not the best.
  15. Sigma

    LiteOn can do disc quality scans

    [ All burned/pressed discs will have errors on them. The important thing is that the error rate is low enough so that it doesn't affect the disc's ability to be read. If the error rate is too high, the drive may struggle to read the disc, with a 360 game you may get a "dirty disc" error, or a disc may not be able to be read at all. Doing a scan with something such as KProbe will show you the error rates on your burned disc. This is useful for a couple of reasons: - 1. If a disc won't read, you can scan it to see if high error rates are the cause. If not, you can rule out a bad burn. 2. You can do burns with different settings and at different speeds and scan them to see which gives the best results. That's exactly what Lightning UK did with XGD3 Xbox 360 games in this thread: - http://forum.imgburn.com/index.php?showtopic=18871&st=0&p=136519entry136519 So he tries various combinations of settings and burn speeds, then scans the discs with DVDInfoPro and KProbe to check the quality of the burn. For example, this is not a good burn: - The PIF rate ideally shouldn't go above 4, yet you can see that around the 50% mark (where the layer break is), it shoots up to above 70. That game almost certainly would not work in your 360 and if you were trying to install it, you would probably get a dirty disc error just before the 50% mark. And here is an example of a decent burn: - PI doesn't go above 25. PIF doesn't go above 2. That's a solid result. There, I've saved you a bit of Googling time.

Important Information

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