LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Unzip.vi only works with 1-internal file, error2 with multiple even in raw form.

I am wondering if there is any status update on this bug yet. To recap, the LabView 8.5 unzip function is broken under Windows, returning error 2 ("System Exec.vi: Command was "touch 01162006102008 "myuncompressedfile.txt"") after the first file extracted.

LabView's unzip function is basically worthless until this is addressed, so this seems like a fairly serious issue.

I know the software release process is a long one, but would it be possible to either provide a corrected version of the VI here or release the diagram password so that the code could be corrected in the meantime? The error is likely a very simple one. (The unzip process itself is probably fine, but after unzipping the file it tries to update the file's timestamp using a command (touch) that isn't legal under cmd.exe.)

-Rob
0 Kudos
Message 11 of 15
(1,282 Views)

Hello Rob,

R&D has acknowledged that this is a serious issue, and the developers are looking for the best way to help people using this VI.  We will update the Known Issues document  if another workaround or better solution becomes available.  Please search for bug ID number 4E1B60P2  -- the bug ID I filed earlier was a duplicate -- and check up on this in a month or two.  Please contact support if this bug is a showstopper for you and is halting your project and you need assistance in finding a new workaround.

Best Regards,
T. McCarty
Applications Engineering



Message Edited by Support on 01-17-2008 11:34 AM
0 Kudos
Message 12 of 15
(1,265 Views)
are there any news on this topic now - I really would appreciate if the unzip function would work.
0 Kudos
Message 13 of 15
(1,168 Views)
Good news: issue 4E1B60P2 is marked as fixed in LV 8.2.1: see http://zone.ni.com/devzone/cda/tut/p/id/6927
0 Kudos
Message 14 of 15
(1,159 Views)
Whoops, I meant fixed in LV 8.5.1.
0 Kudos
Message 15 of 15
(1,158 Views)