disassembly?
in [General Programming]
|
Prev: Boost and UMFPACK: anyone tried it?
Next: Statistics for Business and Economics 9 ED by Anderson, Sweeney solutions manual
From: Richard Heathfield on 3 Mar 2010 17:39 Bill Cunningham wrote: <snip> > I tried to disassemble a AVI file the other day That figures. What did you hope to achieve by it? -- Richard Heathfield <http://www.cpax.org.uk> Email: -http://www. +rjh@ "Usenet is a strange place" - dmr 29 July 1999 Sig line vacant - apply within
From: Moi on 3 Mar 2010 18:01 On Wed, 03 Mar 2010 22:39:23 +0000, Richard Heathfield wrote: > Bill Cunningham wrote: > > <snip> > >> I tried to disassemble a AVI file the other day > > That figures. What did you hope to achieve by it? He tried to find his cat. AvK
From: Jongware on 4 Mar 2010 05:57 On 3/3/2010 23:14 PM, Bill Cunningham wrote: [..] > I tried to disassemble a AVI file the other day and my linux told me the > file was too large. The disassembly that was being created that is. Would > using the split program to split up something between 700M and 1.2G allow me > to successfully disassemble an avi. That is a distinction between data and code. This message you are reading now is *data*. "Disassembling" it will not yield anything useful -- for that, you would need to disassemble the program that created it. AVI is a data format, not an executable program. An AVI *player*, on the other hand, is a program and can be disassembled. > This is what I'd like to find out from the AVIs chunk size and so on and > maybe change that in the binary. That would take reverse engineering. [related to > The about numbers 0A 200D 67 and so one, are they the binary? ] Use a Hex Viewer to view data. Use a Hex Editor to change data. No reverse engineering needed. You would use reverse engineering on the program that created the data file in the first place, to find out what the meaning is from that data. Fortunately, the AVI file format is well-documented. It's rather *unfortunate*, on the other hand, you are expecting to be able to simply change stuff in the binary and still have a working AVI file. Reading the file specifications, you'll see stuff like avimainheader.dwWidth Specifies the width of the AVI file in pixels. avimainheader.dwHeight Specifies the height of the AVI file in pixels. and if you are thinking you can double the movie size by changing dwWidth from 320 to 640 and dwHeight from 240 to 480, well, you are way beyond your capabilities. [Jw]
From: Bill Cunningham on 4 Mar 2010 13:21 "Jongware" <jongware(a)no-spam.plz> wrote in message news:4b8f9217$0$22943$e4fe514c(a)news.xs4all.nl... > That is a distinction between data and code. This message you are reading > now is *data*. "Disassembling" it will not yield anything useful -- for > that, you would need to disassemble the program that created it. I see. > AVI is a data format, not an executable program. An AVI *player*, on the > other hand, is a program and can be disassembled. ok >> This is what I'd like to find out from the AVIs chunk size and so on >> and >> maybe change that in the binary. That would take reverse engineering. > > [related to > > The about numbers 0A 200D 67 and so one, are they the binary? ] > > Use a Hex Viewer to view data. Use a Hex Editor to change data. No reverse > engineering needed. > > You would use reverse engineering on the program that created the data > file in the first place, to find out what the meaning is from that data. > Fortunately, the AVI file format is well-documented. I have noticed that. What I have read is that AVI is really basically a RIFF. I have docs on that to. That's another thing I would like to do is remove the AVI packaging. > It's rather *unfortunate*, on the other hand, you are expecting to be able > to simply change stuff in the binary and still have a working AVI file. > Reading the file specifications, you'll see stuff like > > avimainheader.dwWidth Specifies the width of the AVI file in pixels. > avimainheader.dwHeight Specifies the height of the AVI file in pixels. > > and if you are thinking you can double the movie size by changing dwWidth > from 320 to 640 and dwHeight from 240 to 480, well, you are way beyond > your capabilities. I see. But what would one do? Bill
From: Bill Cunningham on 4 Mar 2010 13:22
"Richard Heathfield" <rjh(a)see.sig.invalid> wrote in message news:oaOdnV2Yn4ebeBPWnZ2dnUVZ8rZi4p2d(a)bt.com... > Bill Cunningham wrote: > > <snip> > >> I tried to disassemble a AVI file the other day > > That figures. What did you hope to achieve by it? See where the AVI data is and I guess I'm off track there by what others further in the thread have said. Make a RIFF out of it. These 2 formats are well documented fortunately. Bill |