Yes so Dusty admits that EXEVALID is *SLOPPY* and *INACCURATE*

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

Threaded View

<CUT OUT>

|           *** DO NOT USE THIS UTILITY! ***


             p-0.0-h the cat  

                         Dusty

It was made for Windows 98  

and MD-DOS 7 only

And you are test on tham right?

Re: Yes so Dusty admits that EXEVALID is *SLOPPY* and *INACCURATE*

Hot-Text used his keyboard to write :
Quoted text here. Click to load it

Shhhh.



Re: Yes so Dusty admits that EXEVALID is *SLOPPY* and *INACCURATE*


Quoted text here. Click to load it

LOL.. lemme show you something neat.

First, your work:

(which compiles to 2800 bytes)

print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;
open"i",1,filename$
input #1,a$ BYTE
input #1,b$ BYTE
input #1,partialblockLOW$ BYTE
input #1,partialblockHIGH$ BYTE
input #1,blocksLOW$ BYTE
input #1,blocksHIGH$ BYTE
close 1

partialblockLOW&=ASC(partialblockLOW$)
partialblockHIGH&=ASC(partialblockHIGH$)

blocksLOW&=ASC(blocksLOW$)
blocksHIGH&=ASC(blocksHIGH$)

partialblock&=256*partialblockHIGH&
partialblock&=partialblock&+partialblockLOW&

blocks&=256*blocksHIGH&
blocks&=blocks&+blocksLOW&

totalsize&=blocks&*512
partialblock&=512-partialblock&
if partialblock&>0 then
totalsize&=totalsize&-partialblock&
endif

print" "
print"Totalsize ";
print totalsize&;
print" bytes"

end

Now my work (which compiles to 2624 bytes and could be made even smaller)

dim(poohwaste(2))
print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;
AX=&HEX3D00
DX = VARPTR(Filename$)
INT86(&HEX21,AX,NA,na,DX,NA,NA,NA,NA,NA)
file_handle=ax
ax=&hex3f00
bx=file_handle
cx=6
dx=varptr(Poohwaste(0))
if bx>=5 then
int86(&hex21,ax,bx,cx,dx,na,na,na,na,na)
endif

ax=&hex3e00
bx=file_handle
if bx>=5 then
int86(&hex21,ax,bx,na,na,na,na,na,na,na)
endif
c$=""
ax=varptr(Poohwaste(0))
bx=ax+1
for cx= ax to bx
ax=peek(cx)
a$=chr$(ax)
c$=c$+a$
next cx
ax=varptr(Poohwaste(0))
ax=ax+2
partialblocklow&=peek(ax)
ax=ax+1
partialblockhigh&=peek(ax)
ax=ax+1
blockslow&=peek(ax)
ax=ax+1
blockshigh&=peek(ax)

partialblock&=256*partialblockHIGH&
partialblock&=partialblock&+partialblockLOW&

blocks&=256*blocksHIGH&
blocks&=blocks&+blocksLOW&

totalsize&=blocks&*512
partialblock&=512-partialblock&
if partialblock&>0 then
totalsize&=totalsize&-partialblock&
endif
print" "
print"Totalsize ";
print totalsize&;
print" bytes"

end  

Quoted text here. Click to load it

I'm not fighting for anything. Script kiddie. [g]



--  
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: Yes so Dusty admits that EXEVALID is *SLOPPY* and *INACCURATE*


Quoted text here. Click to load it

save my reputation? LOL. Bro, your program is sloppy and uses more ram than  
my original version did, by 2 kilobytes. How the fuck did you waste 2k more  
to run and not even poll a folder? :)


  



--  
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: Yes so Dusty admits that EXEVALID is *SLOPPY* and *INACCURATE*


Quoted text here. Click to load it

ASIC can't be held responsible for script kiddie/sloppy programming  
practices. That's entirely on you. And no, I haven't been up all night  
working on this little diddy for you. I've been waiting days (patiently) to  
post it. BD posted something in which this program and examples/comparisons  
(that I've already taken the time to do, but you uhh, wouldn't take the  
cookie) seemed like a perfect reply, on their own.

I've no investment in this, script kiddie. I made my point with the first  
question; what's the program doing. This just drills the point thru you;  
leaving a rather large exit hole. I mean, c'mon... your demo uses more  
memory to run than either of the full blown programs.

Your no coder. :) Of any sort. You're a bser.

  



--  
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: Yes so Dusty admits that EXEVALID is *SLOPPY* and *INACCURATE*


Quoted text here. Click to load it

Dustin when you posted the Exevalid source code 2 weeks ago, Pooh Cat told  
you where it was going wrong but you repeatedly refused to believe him so  
he wrote a better version to demonstrate a way to overcome your errors.  

It's no use rewriting Exevalid now.... you had your chance when discussing
it with Pooh!


--  
Jax    :)

Re: Yes so Dusty admits that EXEVALID is *SLOPPY* and *INACCURATE*

Quoted text here. Click to load it

LOL!

--  
Jax    :)

Site Timeline