flat assembler
Message board for the users of flat assembler.
Index
> DOS > dissassembly a dos4gw code |
Author |
|
pabloreda 18 Jun 2013, 19:44
HI,
I found this post https://groups.google.com/forum/?fromgroups=#!searchin/comp.graphics.algorithms/new$203d$20voxel/comp.graphics.algorithms/UqHsc-DVwO8/y17WuZE3xfAJ and I like to see what does this guy, the webpage not have the exe anymore. I write to her but not response. but with wayback site a get the demo http://web.archive.org/web/19980712165309/http://faza.com/spec.htm But I don't know how dissassebly a dos4gw .exe. any hint to get the assembly source of the exe? thank's |
|||
18 Jun 2013, 19:44 |
|
pabloreda 18 Jun 2013, 22:10
thank's baldr
I have the exe and run ok in dosbox, it's a watcom compiled program. I try the wdis(watcom disassembly), but not admit .exe, tell about coff or something |
|||
18 Jun 2013, 22:10 |
|
baldr 20 Jun 2013, 16:08
pabloreda,
I can't say much about wdis behavior. Maybe you can make that .Exe accessible somewhere? Then I'll try to prepare it for IDA disassembling. |
|||
20 Jun 2013, 16:08 |
|
pabloreda 20 Jun 2013, 22:27
thank's a lot baldr!
I do the dissasembly at last, IDA work like a charm, I have a ASM and a C!! The reason for analyse this program is for try to guessing the Unlimited Detail Format, (the guys of euclideon), some points in common with this code. thank's again |
|||
20 Jun 2013, 22:27 |
|
bitRAKE 21 Jun 2013, 02:50
The video demos running directly off USB are quite impressive. Seems clear that some kind of spacial compression is designed into the algorithm. Also, Euclideon has said the data sources need to be preprocessed by them.
Here is how I imagine it: The binary of the coordinates define the partition address. This address could be masked and found in several hash tables (depending on LOD). For example, there would be only one point cloud representation of a grain of sand, but several hash entries which point to that description. That would reduce it to a couple 100 instructions per pixel, regardless of point count. Here is their latest video: http://www.youtube.com/watch?v=Irf-HJ4fBls |
|||
21 Jun 2013, 02:50 |
|
f0dder 25 Jun 2013, 21:06
bitRAKE wrote: Here is their latest video: I had to stop after 6 minutes - the narrator's voice is awfully annoying, and (up to that point, anyway) it contained nothing but their usual marketing bullshit superlatives and all-fluff-no-content hype. Their previous "infinite detail" stuff was also in no way impressive, as it consisted of extremely repetitive data. So, is there anything interesting and/or substantial after the 6-minute mark? To me, the company has all the marks of a "We'reReallyJustInItToGetBoughtOutAndLaughAtTheSuckers" scam. _________________ - carpe noctem |
|||
25 Jun 2013, 21:06 |
|
pabloreda 25 Jun 2013, 22:19
there are a very curios thing about this subject, the amount on point are implosible on current technology. I found a similiar?? proyect from 1997
you can look in http://chorasimilarity.wordpress.com/tag/unlimited-detail/ |
|||
25 Jun 2013, 22:19 |
|
bitRAKE 25 Jun 2013, 22:23
Yeah, I mute the videos - he has always been annoying as fuch. From what I've gathered, he already got funding for this Geoverse app and are working on some government projects? I don't know if there is any novelty to his specific algorithm, but it doesn't seem to merit reverse engineering this DOS exe when similar public methods can achieve the same?
_________________ ¯\(°_o)/¯ “languages are not safe - uses can be” Bjarne Stroustrup |
|||
25 Jun 2013, 22:23 |
|
bitRAKE 26 Jun 2013, 01:05
“Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth.” Arthur Conan Doyle
Lets start with some facts extracted from S. A. Janczewski (1999):
Then we have some facts from Euclideon (2013):
Many techniques can be avoided as they would never be fast enough. Assuming, 2^25 pixels per second means 128 cycles per pixel on single 4Ghz processor - very conservative resolution at 20 fps. http://www.ausgamers.com/forums/general/thread.php/3260288 Nnaimcek wrote: The index is an octree, hence the ".OCT3" extension. Compression for Mr. Dell means the "recycling of common structures" i.e., storing the locational codes' common prefixes and common suffixes just once. Recycling common prefixes gives octrees (because locational codes in 3-D are ogdoadic sequences). Recycling common suffixes gives DAGs (because hardly do non-leaf nodes store anything except the indices of their children. A leaf's color is likely stored in lieu of its index. Already this, with 32-bit indices, results in about 2:7 compression). An impressive voxel engine: http://youtu.be/VYfBrNOi9VM ...and some research papers: http://maverick.inria.fr/Members/Cyril.Crassin/ _________________ ¯\(°_o)/¯ “languages are not safe - uses can be” Bjarne Stroustrup |
|||
26 Jun 2013, 01:05 |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.