Original War Support Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report #454  -  PakView does not extract Data2.owp
Posted Dec 06, 2017 - updated Dec 06, 2017
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Not a bug" and resolution "NOT AN ISSUE".
Issue details
  • Type of issue
    Bug report
  • Status
     
    Not a bug
  • Assigned to
    Not assigned to anyone
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     P40fA
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Time spent
    No time spent
  • Category
    Not determined
  • Resolution
    NOT AN ISSUE
  • Priority
    Not determined
  • Reproducability
    Not determined
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png Not determined
Issue description
In 2.0.5.12, PakView does not extract most of the files contained in the Data2.owp archive. All steps within the program work normally but no or only some files (with no apparent distinction) appear in the extracted folders. Specifically, the Data4.wav and such are not extracted in any run. Multiple folders tried, write rights checked.

Using Windows 10.
Steps to reproduce this issue
In 2.0.5.12:

- Launch PakView. - Open Data2.owp. - Use Extract To and select a target folder.

The directory structure from the archive is replicated in the target folder but no files inside them are created. Only about two or three wav files sometimes appear in the Exclamations folders, with a duration of cca 2 secs each and no recognizable content.

#1
Comment posted by
 Stucuk
Dec 06, 15:53
With 2.0.5.92 and higher PakView can extract the compressed wav files in OWP's. http://www.owsupport.com/files/Release_OW_2.0.6.128_RC3.rar

The issue was updated with the following change(s):
  • The status has been updated, from New to Not a bug.
  • This issue has been closed
  • The resolution has been updated, from Not determined to NOT AN ISSUE.
  • This issue's progression has been updated to 100 percent completed.