Jump to content

Dolt

Members
  • Content Count

    35
  • Joined

  • Last visited

About Dolt

  • Rank
    ISF Newbie
  1. Dolt

    Burner Buffer 0%

    It a crappy NEC 3550A which came with nothing. Oddly the BIOS recognizes over 900 media signatures instead of the usual puny 50 - 100 of most drives. I was able to get a patched version so now it's region free and more importantly I can set the Book Type via the NEC tool in ImgBurn so I can now burn playable DVD+R media but still no WOPC utility that I know of. It's excellent with CDs and burns at 16X and 48X with perfection but it's junky when burning DVDs and can only handle 2X due to the crappy WOPC always slowing it down. Do you know of such a utility for a Lite-On Drive. Those things are useless. It's calibrating every billionth of a second and runs as slow as heck. My pioneer 110D is crap too. I miss burning at 4X since 2X take eons by comparison. Even 2.4X DVD+R disks are much nicer than s sluggish 2X burn.
  2. He might as well remove the damned option since it's so useless. Nobody can safely use it. Everyone here says they the besy thing is to NOT use the damned delete option since it's too dangerous. I thought only Microsoft was dumb enough to leave in defective code that can cause the user to unwittingly damage their data.
  3. Dolt

    Blue Screen @ Sata burner

    It crashed but there's NO DUMP! It hits the system so hard that it fails to dump ANYTHING. No memory dumps! NOTHING but a BSOD !!! It justs says something useless like "The previous systen shutdown was unexpected." I have some old error claiming "an error was detected on \Devide\CdRom0 during a pagging operation" and it says it about 100 times over a 1-2 second period back on the 5th of February.
  4. Dolt

    cannot set the layer break

    well i just ordered + r verbatim , ok guys this forum is great : in france nobody wanted to answer me : i hate frenchies.. I've had good results with Memorex media which is made by Ritek "RITEK-D01-01" but better quality then their own RiData line, "RITEKG04" & RITEKG05". They have a dark purple unlike the Ritek's I've had problems with. RiData's are at about 10% failure for any media type, I forget the disk ID fro their DL ones. The Maxell's I have say RITEKG04 for their descriptor ID. I had 8 of 10 Verbatim DL's fail "MKM-001-00" but only 4 of 50 SL ones "MCC 02RG20" fail. I've had similar results with PlayO, only more extreme, 20 for 20 DL failures "RICOH00-?00-01" and maybe 4-5 out of 50 for their SL ones "MCC 03RG20" and half of those were from a BSOD during a burn.
  5. Dolt

    Burner Buffer 0%

    Is there any way to turn off WOPC so I stop getting errors on my DVDs. 99% of the time it results in damaged PGC data. That's often the case but sometimes there's a small amount in the cache which is confusing but I usually only do very low damnding operations during burning and I do moderate activities, like going here or checking e-mail during verification since it doesn't risk damaging data stored on the DVD. At 2X the WOPC only drops the internal device buffer to 60-70% but at 4X it drops to 7% and then the drive stops burning for about a second then the light goes on again. With the Lit-On drives it happens ALL the time so the drive slow to a crawl. They are crap. My NEC will only do it half a dozen times not zillions like the crappy Lite-On drive. At this point I'd pay triple for a Plextor if I was convinced they didn't have the same crappy design or if they simply used a 8 or 16MB buffer and not a microscopic 2 MB one. I suspect it would solve everything since it works fine at 2X. A 2 MB buffer simply doesn't hold enough data to allow it to not empty at 5.54 MB/sec., an 8MB, or ideally a 16MB, buffer should hold enough data just like 2MB does for a 2X burn. As you may guess by now I find may products to be designed by idiots. ImgBurn is an exception. DVD ReMake Pro is an even better product. It's almost magical. DVD burners are mostly junk but then Windows is crap itself. Every week there's another zillion bugs.
  6. Dolt

    Blue Screen @ Sata burner

    Yeah, I just reactivated all that. I'm sure now that it's set up it will take a week to crash again, which is a mixed blessing, I guess. Then again, it may crash tomorrow. Also, I do not do 4X burns anymore so I'm having problems locating an OLD .IBG. I do know that usually when Windows 2003 starts again I often get messages about PowerDVD having crashed but I'm not sure it that old stuff from weeks ago I never sent or what. I've turned those but turn on the dumps. I know that having ImgBurn eject a DVD when it finishes helps because sometimes a DVD would finish and the it would be read by the system and PowerDVD would then try and play it via Windows F'g annoying autoplay. S#!+ I F'g hate that Damn annoying "feature" every time I stick a disk in it statrs pestering me!!! I check the always box and select DO NOTHING EVRY TIME but the retarded function NEVER remembers. Anyhow, that usually leads to a BSOD. I have NOTHING cause BSODs on 2003 but F'g DVDs.
  7. "It doesn't take into account failed burns within a multi copy burn that you may or may not want to retry." "The image deletion code is in a different part of the program (and it's run first) to the bit that asks if you want to retry failed burns." That's a bad design. You should swap the order of execution. It seems that the problem is you do not redo the first disk so the count is wrong. You have only 1 successful image of 2 then you simple should NOT advance the count when a verification fails. You should wait until a verification passes and returns a passing value when that condition is set on before advancing to the next image. Instead you apparently do so when the burn finishes. It's bad logic. I do programming myself and bad logic is the cause of most serious bugs. I suppose if you were designing a washing machine you'd start filling it with water once the first quarter is placed in the machine expecting the others will go in as well. What we have here is someone only put two quarters in for a $1 washing machine and you went ahead and said that was "close enough" and ran the wash anyway. It's bad code, period. Actually SAO mean Session At Once. It does NOT finalize a CD like a DAO would. A DAO burn burns one session and then finalizes the CD. A SAO burn burns one sseesion and does NOT finalize the CD so more sessions can be added to the media. This also means once can actually remove data from the index for the next session and then finalize the CD with the data in the CD but not accessible when loaded into windows. Believe me, I've done dozens of multi-session CDs at this point. You can even do Multi-Session CD-DA CDs where a CD player will only see the first session but a CD-ROM drive will see more tracks that a CD player will not. I've done it. You need either an older version of Win-On-CD to do it.
  8. Dolt

    Buffer Recovery

    I click on the Upload button but all I get is the swirling pattern and no activity.
  9. Dolt

    Queue Options

    1. It does, it's under Verify. He can also just manually check the boxes if he wants, after it starts, and walk away. I usually leave them off just like DELETE IMAGE and then manually turn them on, during a burn, if desired. 6. Agreed 7. Personally, I'm suspicious of anyone who needs to burn 10 copies of the same DVD.
  10. Dolt

    Buffer Recovery

    I wish I had a 3540A, everything I can read shows they didn't have the buffer problems of the 3550A. The best drive I ever had was a DRW-3S163 which burned 6X perfectly, the buffer never got empty, but the Lite-On drives I tried that they market under their own name are crap. The buffer empties and it slows down to 1.2X or some junk. Utter garbage! I've tried the SHM-160P6S, SHM-160H6S AND SHM-165H6S and they're all junk. Interestingly, the DRW-3S163 weighs 4 pounds instead of the 2 pounds of the other drives. I suspect it uses metal parts instead of cheap plastic. Also, the Pioneer DVR-110D fails to keep it's buffer full as well. Only the DRW-3S163 seems to respond and fill it's buffer before it gets too empty at anything above 2X. So, I'm stuck using an NEC 3550A at only 2X which can manage to keep it buffer full. This seems to happen under Windows 2000 Pro., 2000 Adv. Server, XP and 2003. I currently don't have XP/2003 x64 installed but I expect it to be a similar problem.
  11. Dolt

    Buffer Recovery

    Upper Device Filter: redbook Device Object: NERO IMAGEDRIVE2 SCSI CdRom Device Lower Class Filter: PxHelp20 Driver Name: redbook.sys File Location: l:\win2003\system32\drivers File Description: Redbook Audio Filter Driver File Version: 5.2.3790.1830 Product Name: Microsoft? Windows? Operating System Product Version: 5.2.3790.1830 [5.2.3790.1830] Company Name: Microsoft Corporation Driver Name: pxhelp20.sys File Location: l:\win2003\system32\drivers File Description: Px Engine Device Driver for Windows 2000/XP File Version: 2.03.28a [2.3.28.0] Product Name: PxHelp20 Product Version: [2.0.0.0] Company Name: Sonic Solutions Should I remove pxhelp20.sys and what they heck does it do? Also, HOW do I disable if that's appropriate. I'm sick of my buffer getting empty when I use 4X or faster. OOPS! Wrong device but same question ... Upper Device Filter: redbook Device Object: _NEC DVD_RW ND-3550A Lower Class Filter: PxHelp20 Lower Device Filter: imapi Driver Name: redbook.sys File Location: l:\win2003\system32\drivers File Description: Redbook Audio Filter Driver File Version: 5.2.3790.1830 Product Name: Microsoft? Windows? Operating System Product Version: 5.2.3790.1830 [5.2.3790.1830] Company Name: Microsoft Corporation Driver Name: pxhelp20.sys File Location: l:\win2003\system32\drivers File Description: Px Engine Device Driver for Windows 2000/XP File Version: 2.03.28a [2.3.28.0] Product Name: PxHelp20 Product Version: [2.0.0.0] Company Name: Sonic Solutions Driver Name: imapi.sys File Location: l:\win2003\system32\drivers File Description: IMAPI Kernel Driver File Version: 5.2.3790.1830 Product Name: Microsoft? Windows? Operating System Product Version: 5.2.3790.1830 [5.2.3790.1830] Company Name: Microsoft Corporation
  12. Dolt

    Buffer Recovery

    Upper Device Filter: redbook Device Object: NERO IMAGEDRIVE2 SCSI CdRom Device Lower Class Filter: PxHelp20 Driver Name: redbook.sys File Location: l:\win2003\system32\drivers File Description: Redbook Audio Filter Driver File Version: 5.2.3790.1830 Product Name: Microsoft? Windows? Operating System Product Version: 5.2.3790.1830 [5.2.3790.1830] Company Name: Microsoft Corporation Driver Name: pxhelp20.sys File Location: l:\win2003\system32\drivers File Description: Px Engine Device Driver for Windows 2000/XP File Version: 2.03.28a [2.3.28.0] Product Name: PxHelp20 Product Version: [2.0.0.0] Company Name: Sonic Solutions Should I remove pxhelp20.sys and what they heck does it do? Also, HOW do I disable if that's appropriate. I'm sick of my buffer getting empty when I use 4X or faster.
  13. Dolt

    Buffer Recovery

    bustrace sucks!!! You need to be a F'g corporation with a web site to even download their damned demo !!!
  14. Dolt

    Burner Buffer 0%

    I've seem similar odd behavior using an NEC-3550A under Windows 2003. I haven't bothered keeping too many details. Also, sometimes it will sit at some odd value like 30% and then later on it will shoot up BUT this odd behavior seems to occur during the verification stage NOT during burning stage, as I recall.
  15. Dolt

    Blue Screen @ Sata burner

    I've never had an issue with any SATA drive but but NEC-3550A is always the source of BSOD's which seems to occur every few days in the middle of making a DVD (using ImgBurn or Nero), never on CDs (usually Nero) and usually during verification, especially when late in the process if the drive is spinning over 10X while verifying (in Nero or ImgBurn). Using the limited speed option of ImgBurn has cut way down on BSODs but they STILL occur but ONLY with DVD disks. My SATA HD's run and 40-120 MB/sec. depending on the fragmentation (obviously from my performance speeds I do defrag fairly often), and whether the other HD is on the other SATA sets, I have two (4 SATA-I and 4 SATA-II) on the MB (only 2 SATA-II HDs in use) plus a Promise Tech. RAID-5 card, or if the other HD an older PATA drive, etc. I also use a 1.87 GHz Athlon 64 so I doubt it's the CPU being too slow either.
×

Important Information

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