WinZip version 14.5 Command Line Interface terminates unexpectedly for no reason.

A windows batch file that I have been using for about 2 years to copy and compress files from a server onto a flash drive with file names made unique by system datetime has suddenly quit working for no reason. Does anybody know if WinZip version 14.5, a Corel company, has put any kind of date limitation for the use of the WinZip Command Line Interface program? This came as a real shock when I experienced it at a client's site yesterday. That was the first time I have used this windows batch file this year which makes me supicious why something that has work so well for so long suddenly quit working after the new year.

Perhaps a Microsoft update to Windows XP or Windows Server 2003 is the cause of this. The BAT file is a Windows batch file Shell script. I haven't bothered to learn VBScript yet.
Ted PalmerInformation Technology ConsultantAsked:
Who is Participating?
 
JohnConnect With a Mentor Business Consultant (Owner)Commented:
Put a "pause" after each line in the batch file. Pause will cause a stop, and "press any key to continue". That should tell you where it is failing and if it is WinZip or something else. WinZip is up to Version 16, so you might also consider updgrading. .... Thinkpads_User
0
 
Ted PalmerInformation Technology ConsultantAuthor Commented:
Is there a way I can single step through the BAT file script to see which line is failing?
0
 
Ted PalmerInformation Technology ConsultantAuthor Commented:
It also fails on a Windows XP machine the same way when I tested it just now.
0
KuppingerCole Reviews AlgoSec in Executive Report

Leading analyst firm, KuppingerCole reviews AlgoSec's Security Policy Management Solution, and the security challenges faced by companies today in their Executive View report.

 
Ted PalmerInformation Technology ConsultantAuthor Commented:
A closer inspection of the BAT file script revealed that while I changed the copy to destination drive letter, I forgot to also change the copy from drive letter. After I fixed this, the script ran as it did before without a problem. Since the symptoms were the same perhaps I should take a closer look at my clients network. The network administrator guy was there a couple days before me. He may have changed some drive letter mappings or something.

@think_pads user, your's is a good idea. I wished I thought of that. Since I don't want to take time to learn VBScript, that is what I'll do next time.
0
 
Ted PalmerInformation Technology ConsultantAuthor Commented:
THANK YOU..!!
0
 
JohnBusiness Consultant (Owner)Commented:
You are most welcome and I was pleased to help. ... Thinkpads_User
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.