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

[mloiselle]

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.

[LIGHTNING UK!]

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.

[mloiselle]

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