summaryrefslogtreecommitdiff
path: root/phnxdeco-0.33.orig/src/phnxdeco_en.txt
diff options
context:
space:
mode:
Diffstat (limited to 'phnxdeco-0.33.orig/src/phnxdeco_en.txt')
-rw-r--r--phnxdeco-0.33.orig/src/phnxdeco_en.txt26
1 files changed, 0 insertions, 26 deletions
diff --git a/phnxdeco-0.33.orig/src/phnxdeco_en.txt b/phnxdeco-0.33.orig/src/phnxdeco_en.txt
deleted file mode 100644
index 1715b09..0000000
--- a/phnxdeco-0.33.orig/src/phnxdeco_en.txt
+++ /dev/null
@@ -1,26 +0,0 @@
-/*
- * PhoenixBIOS Decompress
- *
- * Copyright (C) 2000, 2002, 2003 Anthony Borisow
- *
- */
-
- There are some keys during startup:
- 1) "-ls" list contents starting from the tail of file
- 2) "-xs" extract contents starting from the file's tail
- 3) "-l" list contents starting from the beginning
- 4) "-x" extract contents from the beginning of file
- 5) "-c" disable printing of copyright strings
-
- Ok, some info. Couple weeks ago (2003) I've downloaded an IBM-Netvista BIOS
-which had a firmware update with garbage both in the beginning and in the
-tail of BIOS. Of course, it's impossible to determine where the "real"
-update was. And thus all offsets in that file were misplaced. I couldn't
-extract it. The solution is disable printing this kind of copyright strings,
-the key "-c".
- If the BIOS file is broken, and we want to unpack it any way then
-the keys "-x" and "-xs" should be used. What they mean - when first key used
-file is decompressed from the start, in the latter case - from the tail.
-Just the same with the listing - keys "-l", "-ls".
- Help just prints what the program is for.
-