Please Notice: For fastest support from PowerArchiver team, contact us via our Support page

Burn Image (.iso) delay


  • Alpha Testers

    Has anyone else encountered a lengthy delay when using this option?
    when I use it I get a 15 - 20 second delay before the program appears…I assume the program is performing some task in the background such as analyzing the dvd drive?


  • conexware

    it starts quickly here… does it depend on anything such as type of CD/DVD inserted?


  • Alpha Testers

    hmmm….strange…made no difference no matter what I tried whether it be blank dvd or cd.
    I still get the lengthy wait…I can live with it I guess…it isn’t a life or death situation…just wondered if anyone else had encountered it.


  • conexware

    Do you have PAVD installed? and if so, check in Config> Misc if you are using SPTD drivers.


  • Alpha Testers

    it’s just set to ‘Autodetect’


  • conexware

    then move to SPTD and try now 😉


  • Alpha Testers

    no change I’m afraid…exactly same delay time to open program…maybe a reboot would be in order…:)


  • conexware

    try SPTI then…


  • Alpha Testers

    thanks for trying Boss !
    no change no matter which drivers I select…
    I can live with it…15-20 seconds isn’t a lifetime of waiting…:)
    sheesh I’m starting to wonder why I was worried in the first place…:D



  • 15-20 seconds until the “Select image filesname” dialog appears, right? Are (Were) there any network drives?


  • Alpha Testers

    no ‘infimum’…no network drives…and yes 15-20 seconds until the “Select image filesname” dialog appears.
    I do have 6 Hard Drives/Partitions for it to access so maybe this is a contributing factor you think?
    no amount of rebooting or changing drivers alters the startup time.

    once I select the option to ‘Burn Image’ my processor goes beserk for the 15 - 20 seconds before opening the
    "Select image filesname" dialog and from there all seems to run ok.
    it’s just that initial opening where it seems to have an issue.


  • Alpha Testers

    @moles42:

    once I select the option to ‘Burn Image’ my processor goes beserk for the 15 - 20 seconds before opening the
    "Select image filesname" dialog and from there all seems to run ok.

    Maybe this won’t help you, but you could check the taskmanager to see which process that takes most of the CPU time during these 15 - 20 seconds. From your description it sonds like the computer is doing some heavy CPU task and after finish it, display the dialog.

    Kind Regards
    Micke


  • Alpha Testers

    already checked that but nothing excessive in usage and the only task that kicks in is the ‘PABURNTOOLS.EXE’…I too wondered what was causing the processor indicator to stay on for those 20 seconds but I see no reason for it.
    once the program finally opens it all returns back to normal…strange because I have no other issues like this with any other program not even Photoshop CS4 and it loves to bleed your system dry.



  • have you tried process explorer?


  • Alpha Testers

    I haven’t ‘guido’ but I will do thanks.

    I ran the program but still saw nothing to sound alarm bells unless of course I’m not looking for the right process.
    all I see is the ‘PABURNTOOLS.EXE’ start up and then I’m met with the 20 second delay.
    are there some other details I should be reporting here ‘guido’ which might point the finger at a cause?



  • Could you post a log of the process?


  • Alpha Testers

    you want a list of the current processes running on my system?


  • conexware

    there is no need to send anything yet


  • Alpha Testers

    @spwolf:

    there is no need to send anything yet

    something on the horizon maybe Boss ?…:D


  • Alpha Testers

    from starting program to it actually showing the “Select image filesname” dialog on screen takes 15-20 seconds as I reported without any media in the drive…if however I add either a blank dvd or cd it takes 46 seconds before that same dialog appears.


Log in to reply
 

Looks like your connection to PowerArchiver Forums was lost, please wait while we try to reconnect.