Jump to content
Sign in to follow this  
mloiselle

UNC path to invalid filename in command-line causes hang.

Recommended Posts

Prerequisite:

 

A local or network share containing a file larger than 2048kB not valid for burning (a text document for example).

 

Command:

 

The following command-line call of Imgburn causes it to stop responding:

 

ImgBurn.exe /MODE WRITE /SRC "\\SERVER_NAME\SHARE_NAME\FILENAME.TXT" /DEST D: /EJECT YES /VERIFY NO /OVERWRITE YES /START /WAITFORMEDIA /CLOSESUCCESS

 

 

Note:

This has been reproduced on XP 32bit and Vista 64bit.

Share this post


Link to post
Share on other sites

It's kinda by design.

 

The program is still doing stuff and will eventually return the normal error about the file being invalid or unsupported.

 

All that's happening is that the quick image format checks have failed and so a really thorough one (testing for a sequence of known bytes within the first 80 sectors worth of data or so) will be taking place. It's slow going and I expect network file I/O latency etc makes things run even slower.

Share this post


Link to post
Share on other sites

Hey you're right, giving it enough time returns the correct error message. So accessing a local share using UNC must also use the network I/O as you said.

 

Thanks,

Mat

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

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