Jump to content

dontasciime

Beta Team Members
  • Posts

    5,151
  • Joined

  • Last visited

Posts posted by dontasciime

  1. Nothing you can do but clean drive, Use Verbatim MKM-001-00 Made in Singapore (MIS ones are not that good) The A-One disc's are terrible so you cannot compare them.

     

    Your using the latest firmware from Liteon .

     

    If the IDE controller on your motherboard is third party like Jmicron make sure driver is most recent or make sure that options in Bios for this controller are set to IDE/ATA .

     

    If using NForce Chipset (just use standard ms drivers for SATA/IDE) not the nvidia storage driver

     

    Maybe drive is faulty, try another writer in a friends computer etc.

     

    Try one Verbatim @4X instead of 2.4x

  2. LOL

     

    Look I have 15 actually make that 16 computers running in my house with various hardware with over 70 dvd writers, Actually don't matter your right I am wrong.

     

     

    Edit 24/07/08

     

    Meant to add this last night but had something else to do.

     

    Carl take this whichever way you want.. You joined this forum to ? well, to post a response add weight to dann23's argument

     

    So I guess that confirms that the problem is with ImagBurn's driver and not the cable, drive etc.... I have a similar problem with a relatively new LG Blu-Ray / HD reader/ DVD burner. Anytime I record an image and then put a blank disc in and try to switch imageburn from reading to writing it locks up trying to look at the disc. I can't even end task on it. (The program closes but the process does not) the only way to unlock the system is to reboot the computer (Usually twice).

     

    I think it is a problem with ImageBurn's interaction with SATA DVD-Rom drives. but whatever it is it is definately an ImageBurn problem and not the hardware's fault.

     

    Hopefully it will get fixed in a future update.

     

    Carl. ]

     

     

    I instantly thought dann23 had joined again with different user name to add weight to their so called argument.

     

    Anyway back to your statement "I guess that confirms that the problem is with ImagBurn's driver and not the cable, drive etc"

     

    As pointed out there are no drivers for ImgBurn, I/O is provided by operating system and third party drivers (dll etc)

     

    How they interact with operating system and hardware is a very very long chain whereby something can go wrong and to find out what it is (usually hardware/driver) can make you believe one thing is to blame because of logic.

     

    If you format your computer and install vista clean and not an upgrade and you cannot get the drive to work with ImgBurn then using so called logic ImgBurn is the culprit in your eyes, well how if I am to accept your logic can you not accept my logic when I say umm my LG drive (which is the same make model as your) works fine on vista cleanly installed with ImgBurn. My logic says your drive is broken, then cable is broken (or the set of drivers vista installs at default for your hardware is not playing nicely and you then have to try a few different chipset drivers or sata controller drivers), bearing in mind a cable does not need to be broken 100% to be broken I mean that a cable might look OK, seem to be working OK, but in fact is not working as it should as in odd behaviour (drive not working as it should as in maybe 1 pin slightly pushed in ) .

     

     

    I think it is a problem with ImageBurn's interaction with SATA DVD-Rom drives. but whatever it is it is definately an ImageBurn problem and not the hardware's fault.

     

    Hopefully it will get fixed in a future update

     

     

    The above is the bit I have the biggest problem with . It is drivers/hardware/chipsets/controllers/Bios/Firmware/USER/ that have the interaction problem.

     

    You can tell me all day that nero works, isobuster/ magiciso/ burn/ nti dvd / Sorry but I have seen a lot of people use that argument when they know fine well that they are exaggerating the truth and they mean 1 other program works or they are getting the same issue in other programs and find 1 program they know has support that gets answered and use the other programs work argument whilst making out "X" program is at fault to facilitate a fix.

     

     

    It may turn out that your particular drive is not broken and that on your hardware there turns out to be a bug in the code of ImgBurn whereby it only shows on your drive with your hardware.

     

    But then you should have started your own thread / reported it as a bug instead of taking over someone else's post for support with a HTTA.

  3. Maybe ditch vista for xp and when your using different drivers see if it works then, When it does you can then blame vista drivers.

     

    And you can report about the program as many times as you like but when your report is wrong (and is blaming the wrong thing in this case your blaming the program when it clearly is not actually the program but something on your system that is not quite right) no one is gonna take it seriously.

     

    Your hardware/drivers are at fault.

     

    Wipe your install and get as many drivers as you can dated from early to latest and keep reinstalling your operating system until you get a stable system (which should be possible but bad drivers can cause untold mysteries) or return it to PC world or wherever you bought it from and get something that works as it should.

     

    You can vote with your feet and just use all the other programs you mentioned, no one is forcing you to use ImgBurn.

     

     

    My LG BR is fine On ICH7 set to IDE mode in BIOS (using same firmware as yours I bet)

  4. I want to apologise me for the trouble caused.

    I hope the discussion will be over now!

     

     

    Not having a clue what you typed In your native language, Im easy either way :)

  5. You have the problem. You also have the choice of using whatever software you want but when it bites you on the backside and makes you look like a knob do not ask for help until you admit your a knob.

     

    You can have your opinion and your entitled to it but your wrong.

  6. Well since virtually everyone who is reporting this error (Including me I have at least 5 other programs that I use to write various types of data to my single SATA DVD burner) reports that their drives work just fine with several other CD / DVD writing programs I think it is obvious that it is ImageBurn that is not playing nice with these drives. How many of your 6 drives are SATA writers? since it seems to be with these (Or other interfaces that report themselves as being SCSI), that ImageBurn seems to be having problems with.
    Carl.

     

     

    Stop talking sh*** and if you must then at least get the name of the program your whining about right. It is "ImgBurn"

     

     

    Edit ...

     

    Carl have you posted a log of a failed burn, have you also posted what motherboard your using with which driver and which sata port/ controller you have your optical connected to.

     

    You see I only have 15 SATA writers So what do I know. Only The Samsung SATA ones I have do not play nice with writing onto DVD+R whilst trying to set book type to DVD-ROM

     

    The Chipset/s I am using in MOBO[iCH7] and VIA addon card 6421L and GL chipset in SATA 2 usb adapter (This includes all burning programs) and only with DVD+R >DVD-ROM (My optiarc's/ Pioneers/ are fine though.

  7. So I guess that confirms that the problem is with ImagBurn's driver and not the cable, drive etc

     

     

    :sleeping::sleeping::sleeping:

     

     

     

    If your system behaves itself there's never any reason for anything to get stuck. Mine never does and I have 6 drives in my pc - and I bet I use ImgBurn a lot more than you do!

    How you can stay cool is beyond me :icecream:

  8. Change your SATA cable

     

    Change which SATA port you have it plugged into.

     

    Set your Bios to use Emulated IDE for SATA ports.

     

    Change the driver your using In windows to handle IDE/SATA

     

    And It's not ImgBurn problem but yours as in your system / hardware/ drivers if Nero works for you keep paying for it and use it.

     

    Please also start your own thread about a problem as you have different drive to the original thread poster.

×
×
  • Create New...

Important Information

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