Re: Come on then Dusty. Tell Pooh how he did the *impossible* in less than 5 minutes. LOL....

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View

Quoted text here. Click to load it

You used the header trick I shared with you, as a .com, without closing the  
file anymore. [g] So again, you stopped doing proper file io to save one  
byte. [g]

And you still haven't fixed the print" " statement in yer source file.  
That's why it's eating "E".

Nice try to save your arse tho, really.  


--  
Take it easy... Don't let the sound of your own wheels drive you crazy.  
Lighten up while you still can. Don't even try to understand.  
Just find a place to make your stand and take it easy!


Re: Come on then Dusty. Tell Pooh how he did the *impossible* in less than 5 minutes. LOL.


Quoted text here. Click to load it

It's amazing your file magically shrank to 1.4k after I posted how to do  
it, isn't it? Also, is that file really try number 41? You've got to be  
kidding me, Pooh.

Wanna post source and compiling instructions? :) I bet it's the source you  
shared yesterday, that's not  closing a file anymore and is using my header  
trick to magically shrink; as it's 1852 bytes native ASIC exe. And I'm  
sorry, you've been accusing me of stealing your work; but it's clearly the  
reverse here. You like to spin things.

Also, I know for a fact, using my header trick and compiling as a .com  
instead of an exe, it can be made smaller; but you aren't thinking from the  
right way to go about it; or you would have dropped 400+ bytes on me, not  
the other way around. [g]

I used the exe header trick as one demonstration just to make a point. [g]
I didn't have to stop doing all of the tasks the other demos have done,  
aside from two of yours! Both of them no longer close files; because your  
using too many bytes getting creative with the math routines.

I've been teaching you Pooh, you haven't been teaching me.  

Also, you could use just recompile some of the older demo sources and upx  
them. ASIC wastes alot of bytes, UPX can take advantage. Don't use my com  
to exe trick tho, or UPX will have issues and the file won't be  
compressable. Since you've resorted to cutting corners to get one byte on  
me I wouldn't be surprised to see you using a 3rd party tool to compress  
the exe either.

For that matter, I suspect you've had to use a com2exe utility; I didn't.  
*hahaha*.

Spin all you like tho, I know it's what you'll do.


--  
Take it easy... Don't let the sound of your own wheels drive you crazy.  
Lighten up while you still can. Don't even try to understand.  
Just find a place to make your stand and take it easy!


Re: Come on then Dusty. Tell Pooh how he did the *impossible* in less than 5 minutes. LOL.


Quoted text here. Click to load it

Not closing file, like I said.
  
Quoted text here. Click to load it

I 'hacked' nothing. Your code is incomplete, the only way you could save  
bytes is by removing a necessary file function; close file. Now you're  
probably removing the print statements and stripping it to noting. :)

I didn't lose any coding exercise, I got tired of you simply revising my  
demos and taking credit you didn't deserve for them. So I reworked my  
header and spanked you good. No biggie. I hacked nothing.
  
Quoted text here. Click to load it

The fact you've accused me of hacking a header is funny as hell. What's  
funnier, my 1429 byte file still closes the exe, your one byte smaller one  
does not. That's not a good demonstration of superior coding, Pooh.
  
Quoted text here. Click to load it

*yawn*. the fact you think it's a hacked header tells me you really didn't  
have a clue bytes could be saved there. :) I hacked nothing, peon.
  


--  
Take it easy... Don't let the sound of your own wheels drive you crazy.  
Lighten up while you still can. Don't even try to understand.  
Just find a place to make your stand and take it easy!


Re: Come on then Dusty. Tell Pooh how he did the *impossible* in less than 5 minutes. LOL.


Quoted text here. Click to load it

Nice try at spinning, Dustin. If you have better code than Pooh Cat then
post it. If you haven't then accept Pooh Cat has won. It's simple!

--  
Jax    :)

Re: Come on then Dusty. Tell Pooh how he did the *impossible* in less than 5 minutes. LOL.

127.0.0.1:

Quoted text here. Click to load it

I already did, yesterday. it's still an .exe, only needs 2k to run,  
opens/reads/closes file properly. [g] Oh, and it's 427 bytes smaller than  
Poohs 1852 bytes best work; without my help. [g]

Sorry, lamer. You can't help him.
  



--  
Take it easy... Don't let the sound of your own wheels drive you crazy.  
Lighten up while you still can. Don't even try to understand.  
Just find a place to make your stand and take it easy!


Re: Come on then Dusty. Tell Pooh how he did the *impossible* in less than 5 minutes. LOL.


Quoted text here. Click to load it

Dustin your mistake was picking a technical fight with Pooh Cat. He's  
probably forgotten more about coding that you'll ever know.  

You shouldn't have made such a noisy challenge. Now you can't live it  
down. Next time make sure you know what you're talking about because
experts might be listening!

--  
Jax    :)

Re: Come on then Dusty. Tell Pooh how he did the *impossible* in less than 5 minutes. LOL.

127.0.0.1:

Quoted text here. Click to load it

he hasn't demonstrated that... shrug
  
Quoted text here. Click to load it

I do, thanks. and experts have already corrected you. Myself included. :)
  


--  
Take it easy... Don't let the sound of your own wheels drive you crazy.  
Lighten up while you still can. Don't even try to understand.  
Just find a place to make your stand and take it easy!


Re: Come on then Dusty. Tell Pooh how he did the *impossible* in less than 5 minutes. LOL.


Quoted text here. Click to load it
do
my
one  
Quoted text here. Click to load it
didn't  
Quoted text here. Click to load it

If you ignore everything I wrote that clearly shows the difference between  
your "demo" and mine, then sure, you 0wned me. :) If you don't ignore the  
differences, you got your ass handed to you on a platter. H0h0h0.
  



--  
Take it easy... Don't let the sound of your own wheels drive you crazy.  
Lighten up while you still can. Don't even try to understand.  
Just find a place to make your stand and take it easy!


Re: Come on then Dusty. Tell Pooh how he did the *impossible* in less than 5 minutes. LOL.


Quoted text here. Click to load it

And no matter how you spin it, the maths are not yours. You didn't invent  
them, You are NOT the first person to use ASIC in this fashion. You're over  
twenty years behind for credit. Sorry. LOL.

Btw, the "hacked header" you accused me of, is also known by advanced ASIC  
programmers; it's nothing "new" either. But, you didn't know about it. :)
  
Quoted text here. Click to load it

Hacking the header? BAHAHAHAHAHA.. That's funny as hell!
  
  



--  
Take it easy... Don't let the sound of your own wheels drive you crazy.  
Lighten up while you still can. Don't even try to understand.  
Just find a place to make your stand and take it easy!


Re: Come on then Dusty. Tell Pooh how he did the *impossible* in less than 5 minutes. LOL.


Quoted text here. Click to load it

My spin? You said I hacked a header. LOL! How exactly does one hack a  
header in this case? Seriously. It's new to me. lolz!

Do you really think in twenty years time, used by thousands of people, that  
you, and you alone are the first to deal with unsigned integers in the  
single byte fashion? That's brazen of you, very egotistical, and oh so  
untrue at the same time.




--  
Take it easy... Don't let the sound of your own wheels drive you crazy.  
Lighten up while you still can. Don't even try to understand.  
Just find a place to make your stand and take it easy!


Re: Come on then Dusty. Tell Pooh how he did the *impossible* in less than 5 minutes. LOL.


Quoted text here. Click to load it

Dustin..... so why did you post the code for Exevalid with an error in
it's handling of certain numbers if you had been aware of it for years?  

Just wondering!  

--  
Jax    :)

Re: Come on then Dusty. Tell Pooh how he did the *impossible* in less than 5 minutes. LOL.


Quoted text here. Click to load it

Hmm... How interesting...once again, when compiled using asicc test41 e  
b/exe, it's 1856 bytes. However, using the copy command correctly (binary  
file, Pooh [g]), it comes to 1426 bytes; using my header OR a decent  
com2exe utility. Using my header, if not properly put together with the  
copy command it's 1427 bytes. copy /b wasn't a typo, Pooh.

So I'm guessing you used a shitty com2exe conversion utility and/or made a  
funny typo concerning the file size here. Once again tho, you stripped out  
a file io call outright. Had you not done so, your demo source would be a  
bit larger than the one you're competing against. hehehehehehehehe.

I didn't embarras myself paco, I just proved you had no choice but to use  
the header trick *I* taught you. Or, you were fucked, plain and simple.

Quoted text here. Click to load it

The header trick isn't yours, and the maths isn't here. here's another way  
to do it, for shits and giggles:

print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;

bload filename$ 0 6
y=2
gosub grab_two_bytes:
r=512-f2&
y=4
gosub grab_two_bytes:
rem lets do some maths

f2&=f2&*512
f2&=f2&-r
print""
print"Totalsize ";
print f2&;
print" bytes"
end

grab_two_bytes:
gosub peekaboo:
f1=result
y=y+1
gosub peekaboo:
f2=result
f2& = f2 * 256
f2& = f2& + f1
return

peekaboo:
result = peek(y)
return

Quoted text here. Click to load it

You're using my header now. I appreciate the admiration. :) I didn't lose  
any exercise. Look what you've removed to try to beat me. lol. You removed  
close 1. Your program is no longer closing any files it previously opened.  
That's sloppy as is possible and isn't a win by any stretch. A  
disqualification if anything; you had to admit you couldn't beat me and  
still maintain the same functionality as my demo. My demo opens file, reads  
six bytes at once, closes file, does maths, and is only one byte larger  
than yours which no longer can close files it opens. That's a very bad  
example on your part, if you wanted to one up me bro.

This source above compiles to 1872 native asic 1441 using my header  
"hacking" as you like to call it. And it still closes the file too. [g]

The maths aren't yours, sorry.

  
Quoted text here. Click to load it

I didn't lose anything. You've resorted to outright copying my work. :)

I did everything needed in one byte of space more than you. LOL! My code is  
thus, more efficient.
  


--  
Take it easy... Don't let the sound of your own wheels drive you crazy.  
Lighten up while you still can. Don't even try to understand.  
Just find a place to make your stand and take it easy!


Site Timeline