Jump to content

Recommended Posts

Posted

After using DVDFlick (v1.3.0.7) ImgBurn fails to ininiate the burn ptocess and I get an initial message that :"Get ASPI info failed" and a second popup saying 'F:\MyDVDS\Tom' File or folder does not exist.

interesting since my destination folder named in DVDFlick is "F:\MYDVDS\Tombstone". Unfornutaely the log file you wany got deleted when I elected to install a later verion than I had installed for burning the DVD planned.  Nonetheless the lasy two lines, which are the only errors mentioned read as follows:

Get ASPI32 Support Info Failed

Reason: Invalid ASPI Installation detected

 

These two lines appear one second apart

 

I will run DVD Flick again and save the Imgburn log and send it to you later this evening or early tomorrow morning as a supplement to this post.  In the interim, if you lnow what I'm doing wrong or if there is a setting I can change, please advise.  This is the first trouble I have had with using DVD Flick in conjunction with ImgBurn and the only setting I have changed is the Automatic Burn Speed.  I reduced it to 4x because I was experiencing audio being out of synch with video on a DVD I have been trying to burn.  Such was a suggestion I picked up when I google searched the synch issue.

 

Posted

I DID search the forum BEFORE posting this issue.  THERE IS NOTHING THERE.  As to my OS-XP Pro, SP3 which is lots more reliable than the pieces of garbage Miscrosoft has been putting out for the last five or six years.  If you don't care to address this issue, that's fine-perhaps someone a little less pigish will. 

Posted

I was able to burn a DVD using imgburn in build mode, but the DVD still has a synch issue so slowing down the write speed did not solve that problem.  I re-created the DVDFlick project and got the same results as previously described and am attaching a screen shot as well as various log files.  If anyone out there has constructive suggestions, please advise. 

imgburn_write.txt

dvdflick.log

ImgBurn.log

ImgBurn_Build_Tombstone.log

ImgBurn_error_screenshot.bmp

Posted

The only OS's that require ASPI are the really old ones like Windows 95 and 98.

 

XP shouldn't be using ASPI and so simply uninstalling and reinstalling the program (or resetting the settings back to default) would have fixed that and put the I/O interface back on SPTI.

 

Oh and it was a Sunday... a special Sunday known as 'Mother's Day' here in the UK. I try to check in regularly but there are days where I don't want to or can't do that.

×
×
  • Create New...

Important Information

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