Jump to content

2.4.4 Buffer running empty


Zardoz

Recommended Posts

*** Could you please post a link so I can download and install 2.4.2 again. I had no problems with this version and would like to have it until this problem is resolved. Thank you - Imgburn is a great program...

 

PROBLEM: I wasted one disk on this ver before going to test mode and trying to resolve the problem. Maxing out the buffer size makes the buffer emptying problem less frequent but the scenario below occurs none the less. As you can see, there are plenty of resources and the CPU and disk are not taxed at all. I'm not saying this is a Imgburn program problem but it may be some settings issue. In any case, I have searched the message posts and tweaked everything I can think of and have not been able to resolve it. The log is attached below - I obviously terminated the attempt.

 

1. The buffers both fill.

2. The main buffer empties as the data is being written.

3. The Device buffer empties.

4. ERROR MESSAGES:

- "Waiting for buffers to recover... "

- "Waiting for hard disk activity to reach threshold level..."

5. Eventually, the buffers both fill and the process starts over.

 

 

I 21:40:49 ImgBurn Version 2.4.4.0 started!

I 21:40:49 Microsoft Windows Vista Home Premium x64 Edition (6.0, Build 6001 : Service Pack 1)

I 21:40:49 Total Physical Memory: 8,386,128 KB - Available: 6,837,824 KB

I 21:40:49 Initialising SPTI...

I 21:40:49 Searching for SCSI / ATAPI devices...

I 21:40:49 Found 2 DVD

Link to comment
Share on other sites

What's the source drive where the files are being read from? How is it connected to the computer?

 

If you believe it's due to some setting, please re-install the latest ImgBurn and, when asked about keeping your current settings, answer No.

 

Source dirve is a NTFS partition on a SATA RAID array (2 X 750 Gig), Local Drive - J.

 

DVDRW is an IDE drive.

 

I have already uninstalled Imgburn and reinstalled with the default settings to no avail.

 

As I said, this hardware worked flawlessly with 2.4.2. I'm just being nice suggesting it may be a settings or other config problem...

Link to comment
Share on other sites

Do you have the latest driver software for your RAID controller? Do you have Alcohol 120% or Daemon Tools installed? Also please post your Filter Driver Load Order (look in Tools menu).

Link to comment
Share on other sites

Do you have the latest driver software for your RAID controller? Do you have Alcohol 120% or Daemon Tools installed? Also please post your Filter Driver Load Order (look in Tools menu).

 

 

No Alcohol 120% or Daemon Tools.

 

I do have an Ext2 Driver loaded, could that be a problem???

AnyDVD is on the system but I terminate it before starting Imgburn as I did in 2.4.2.

 

Here's the Filter Driver Load Order:

 

===============================================

Filter Driver Load Order - ImgBurn v2.4.4.0

===============================================

 

Upper Device Filter: [None Found]

Upper Class Filter: [None Found]

Device: CD/DVD-ROM Device

Lower Class Filter: cdrbsdrv

Lower Class Filter: AnyDVD

Lower Device Filter: [None Found]

 

Filter Name: cdrbsdrv

File Name: C:\Windows\system32\Drivers\cdrbsdrv.sys

File Version: 8. 0. 0. 5 [8.0.0.5]

File Description: CD-ROM Filter Driver for Windows2000/xp

Product Name: B's Recorder GOLD

Product Version: 8. 0. 0. 5 [8.0.0.5]

Company Name: B.H.A Corporation

Copyright: Copyright © 2000-2006 B.H.A Corporation

 

Filter Name: AnyDVD

File Name: C:\Windows\System32\Drivers\AnyDVD.sys

File Version: 6.5.4.0

File Description: AnyDVD Filter Driver

Product Name: AnyDVD

Product Version: 6.5.4.0

Company Name: SlySoft, Inc.

Copyright: Copyright 2002 - 2009 SlySoft, Inc.

Link to comment
Share on other sites

If I recall correctly ImgBurn uses standard API calls for file reading, and this hasn't been changed from 2.4.2.0 :unsure:

 

If you build an ISO image from those files and save it to another HD, how fast does it go?

Link to comment
Share on other sites

If I recall correctly ImgBurn uses standard API calls for file reading, and this hasn't been changed from 2.4.2.0 :unsure:

 

If you build an ISO image from those files and save it to another HD, how fast does it go?

 

 

I really don't have another HD other than the RAID array. It's not a access speed ot throughput issue with the hardware. I rip and transcode very quickly on this system. The files are good and the drive is routinely defragmented. I transfer the DVD files over to another local system which I use as a media center / PVR. If you want to send 2.4.2 I will reload it and verify that it works as before. If so, there must be some issue with 2.4.4 or 2.4.2 and my hardware.

Link to comment
Share on other sites

If I recall correctly ImgBurn uses standard API calls for file reading, and this hasn't been changed from 2.4.2.0 :unsure:

 

If you build an ISO image from those files and save it to another HD, how fast does it go?

 

 

I really don't have another HD other than the RAID array. It's not a access speed ot throughput issue with the hardware. I rip and transcode very quickly on this system. The files are good and the drive is routinely defragmented. I transfer the DVD files over to another local system which I use as a media center / PVR. If you want to send 2.4.2 I will reload it and verify that it works as before. If so, there must be some issue with 2.4.4 or 2.4.2 and my hardware.

 

 

I just tried it with the diagnostic startup in MSConfig with the same results...

Link to comment
Share on other sites

Tools -> Settings -> I/O -> Reading - Always Use Buffered I/O.

 

 

That's the solution!

 

Tools -> Settings -> I/O -> Reading - Always Use Buffered I/O.

 

I would have thought this would be the default???

 

Thank you!

Link to comment
Share on other sites

Nope because that means Windows caches everything which would normally slow things down - that's why the flags are available in the API functions to start with. Not only that, there's no real point in the OS attempting to cache the kind of file reads/writes that ImgBurn has to do (one time only stuff and normally on huge files).

 

You're getting awful transfer rates considering that's a raid array. Is it software or hardware raid?

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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