Thank you for your help!!, I'll try your code to begin with no doubt.
And yes, FF 33 is the end of the file, after the 33 follow some bytes that represent the date and hour, not of interest. 0x33 is iso coded, so in ascii is the number 3.
For more details below is the main structure I mentioned in my 1rst post:
Thank you for your help ahamed.
---------- Post updated at 03:05 PM ---------- Previous update was at 01:07 PM ----------
Hello again ahamed,
It works nice!
Now for each block I try to extract (if present) the bytes after the FF 34 and begins with 0x03 followed by 0x80 or 0x81or 0x83 or 0x86 or 0x87 more 16 bytes more how it is shown in image attched in previous post.
I've added a new line as below:
But how to include it in the "if" statement and extract those bytes only when the 0x03 0x8Z (where Z could be 0,1,3,6,7) appears after the occurrence of 0xFF 0x34?
For each block I'd like to have one line in put file.
Hi all,
Does anybody know or guide me on how to remove the first N bytes and the last N bytes from a binary file? Is there any AWK or SED or any command that I can use to achieve this?
Your help is greatly appreciated!!
Best Regards,
Naveen. (1 Reply)
Hello,
I have come across the necessity for me to deal with binary sequences and I had a few questions.
1- Does any UNIX scripting language provide any tool or command for converting text data to binary sequences? Example of binary sequence: "0x97 0x93 0x85 0x40 0xd5 0xd6 0xd7"
2- If I want... (2 Replies)
Hi,
I have an one-line file consisting of a sequence of 660 letters. I would like to extract 9-letter blocks iteratively:
ASDFGHJKLQWERTYUIOPZXCVBNM
first block: ASDFGHJKL
1nd block: SDFGHJKLQ
What I have so far only gives me the first block, can anyone please explain why?
cat... (7 Replies)
Hi,
This is part of a large text file I need to separate out.
I'd like some help to build a shell script that will extract the text between sets of dashed lines, write that to a new file using the whole or part of the first text string as the new file name, then move on to the next one and... (7 Replies)
The title is clear: why does ext3 allocate 8 blocks for files that are few bytes long?
If I create a file named "test", put a few chars in it, and then I run:
stat test
I get that "Blocks: 8"
I searched in the web and found that ext does that, it allocates 8 blocks even if It doesn't need... (4 Replies)
Hello guys. I really hope someone will help me with this one..
So, I have to write this script who:
- creates a file home/student/vmdisk of 10 mb
- formats that file to ext3
- mounts that partition to /mnt/partition
- creates a file /mnt/partition/data. In this file, there will... (1 Reply)
Hi,
I have a file with more than 28000 records and it looks like below..
>mm10_refflat_ABCD range=chr1:1234567-2345678
tgtgcacactacacatgactagtacatgactagac....so on
>mm10_refflat_BCD range=chr1:3234567-4545678...
tgtgcacactacacatgactagtatgtgcacactacacatgactagta
.
.
.
.
.
so on
... (2 Replies)
I have a fastq file from small RNA sequencing with sequence lengths between 15 - 30. I wanted to filter sequence lengths between 21-25 and write to another fastq file. how can i do that? (4 Replies)
I have a text file, input.fasta contains some protein sequences. input.fasta is shown below.
>P02649
MKVLWAALLVTFLAGCQAKVEQAVETEPEPELRQQTEWQSGQRWELALGRFWDYLRWVQT
LSEQVQEELLSSQVTQELRALMDETMKELKAYKSELEEQLTPVAEETRARLSKELQAAQA
RLGADMEDVCGRLVQYRGEVQAMLGQSTEELRVRLASHLRKLRKRLLRDADDLQKRLAVY... (8 Replies)
I sat down yesterday to write this script and have just realised that my methodology is broken........
In essense I have.....
----------------------------------------------------------------- (This line really is in the file)
Service ID: 12345 ... (7 Replies)
Discussion started by: Bashingaway
7 Replies
LEARN ABOUT ULTRIX
od
od(1) General Commands Manual od(1)Name
od - create file octal dump
Syntax
od [options] [file] [offset] [label]
Description
The command displays file, or its standard input, in one or more dump formats as selected by the first argument. If the first argument is
missing, -o is the default. Dumping continues until end-of-file.
Options
-a[p|P] Interprets bytes as characters and display them with their ACSII names. If the p character is given also, then bytes with even
parity are underlined. The P character causes bytes with odd parity to be underlined. Otherwise the parity bit is ignored.
-b Displays bytes as unsigned octal.
-c Displays bytes as ASCII characters. Certain non-graphic characters appear as C escapes: null= , backspace=, formfeed=f, new-
line=
, return=
, tab= ; others appear as 3-digit octal numbers. Bytes with the parity bit set are displayed in octal.
-d Displays short words as unsigned decimal.
-f Displays long words as floating point.
-h Displays short words as unsigned hexadecimal.
-i Displays short words as signed decimal.
-l Displays long words as signed decimal.
-o Displays short words as unsigned octal.
-s[n] Looks for strings of ASCII characters of n minimum length. By default, the minimum length is 3 characters.
-v Displays all data and indicates lines identical to the last line shown with an * in column 1.
-w[n] Specifies the number of input bytes to be interpreted and displayed on each output line. If w is not specified, 16 bytes are read
for each display line. If n is not specified, it defaults to 32.
-x Displays short words as hexadecimal.
An upper case format character implies the long or double precision form of the object.
The offset argument specifies the byte offset into the file where dumping is to commence. By default this argument is interpreted in
octal. A different radix can be specified; If ``.'' is appended to the argument, then offset is interpreted in decimal. If offset begins
with ``x'' or ``0x'', it is interpreted in hexadecimal. If ``b'' (``B'') is appended, the offset is interpreted as a block count, where a
block is 512 (1024) bytes. If the file argument is omitted, an offset argument must be preceded by ``+''.
The radix of the displayed address is the same as the radix of the offset, if specified; otherwise it is octal.
The label is interpreted as a pseudo-address for the first byte displayed. It is shown in ``()'' following the file offset. It is
intended to be used with core images to indicate the real memory address. The syntax for label is identical to that for offset.
Restrictions
A file name argument can't start with ``+''. A hexadecimal offset can't be a block count. Only one file name argument can be given.
It is an historical botch to require specification of object, radix, and sign representation in a single character argument.
See Alsoadb(1) - VAX only, dbx(1)od(1)