Re: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and ... - Page 9

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

Threaded View

Re: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

Dustin that doesn't change the fact that copyright theft remains a federal  
offense.

--  
Jax    :)

Re: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.

On 5/8/2014 3:22 PM, Jax wrote:
Quoted text here. Click to load it
You should remind some of your friends of that.


Re: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

copyright theft? Copyright infringement became a federal issue a few years  
ago, but it used to be a civil matter.  





--  
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: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.

Dustin presented the following explanation :

Quoted text here. Click to load it

So Dustin, are you saying that this is wrong?

http://en.wikipedia.org/wiki/Solar_panel

"A solar panel is a set of solar photovoltaic modules electrically  
connected and mounted on a supporting structure. A photovoltaic module  
is a packaged, connected assembly of solar cells."

This is in agreement with what I have always thought, cells make up a  
module (just as connected electrochemical or storage cells make up a  
battery) and connected modules make up a panel (akin to a bank of  
batteries which in turn are made up of cells).

...and yes, it is another common misnomer is where flashlight "cells"  
are not *really* batteries despite what everybody calls them.

That's your cue Pooh, but be forewarned that I am not trying to control  
the lexicon - only trying to point out more sloppy terminology seeping  
into technical discussions.



Re: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

Rafters that's the way I use the term. I know what I saw in those photos  
Dustin posted showing him fixing solar panels. There's no point Dustin  
trying to call them by some grand name. They're solar panels.  

In fact Dustin also called them solar panels too until he started arguing
with me for no reason......  

--------

Subject: Solar panel 6.67kw install

<http://al.howardknight.net/msgid.cgi?STYPE=msgid&A=0&MSGI=%
3CXnsA0DEDA0BE9E3HHI2948AJD832@no%3E>

http://goo.gl/XVhxUh

--  
Jax    :)

Re: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Wikipedia? really?

Quoted text here. Click to load it

Well, if you go on a jobsite where solar module arrays are being installed,  
ask one of the electricians if you can take a look at a "panel". Don't  
worry about the laughter, yes, they are laughing at you, but hell, you  
invited them to do so.

One might even take you to a module, and show you a bunch of panels inside  
it, under fiberglass. They're wired together and you can visually see that  
each panel is a bunch of little cells wired together. The module has  
several of these self contained panels inside of it, and they're wired  
together. The "module" is the entire container, panels n all. the panels  
are inside of it, they are built from cells; you can see them. It's all  
under a big sheet of fiberglass. Working as one unit, a "module".

http://energyinformative.org/best-solar-panel-monocrystalline-
polycrystalline-thin-film/

Has a picture of a few up close. I can't help the fact that many people are  
calling multiple panels inside a module, a "solar panel". anymore so than I  
can help the fact some morons call md5 a checksum. It's still not accurate.

The panels are INSIDE the module. it's not the same damn thing. See the  
pic. I'm done with this. Ask your electrical inspector, general contractor,  
etc. [g]


Quoted text here. Click to load it

Have at it.


--  
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: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

I agree the terminology is muddled.



--  
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: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

Of course it is..... but in Dustin's inimitable style it's dressed up to  
give the superficial appearance that he is right. LOL!

--  
Jax    :)

Re: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

http://energyinformative.org/best-solar-panel-monocrystalline-
polycrystalline-thin-film/

Please do look at the pic. See the panels inside each "MODULE?" heh



--  
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: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

Well, in all fairness David, it's not hard to hunt down someone who isn't  
hiding.
  
Quoted text here. Click to load it

Yep, I do. I consider you to be an idiot for the most part.
  
Quoted text here. Click to load it

You don't know either of us, actually.
  

--  
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: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.

Dustin wrote:
Quoted text here. Click to load it

You seem to forget that I once was an ATCO, Dustin.

Were were often compared to mushrooms - kept in the dark and fed on  
horse-shit!



Re: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.

dnZ2d@bt.com:

Quoted text here. Click to load it

I don't give a fuck what you once were. It doesn't change the fact that you  
don't really know Pooh or myself.
  


--  
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: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

Okay. this one is 2128. [g]

DIM A(5)
print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;
open"i",1,filename$
FOR s = 0 to 5
INPUT#1,B$ BYTE
c=ASC(B$)
A(s)=c
NEXT s
close 1

partialblock=256*A(3)
partialblock=partialblock+A(2)

blocks&=256*A(5)
blocks&=blocks&+A(4)

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

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

end

compiles to 2128 bytes.

Notice the difference? :)
  
Quoted text here. Click to load it

Not really. Still more left to squeeze out of it. I'm just leaving your  
print statements in tact. I did clean up a little more of your code for you  
tho. You didn't need to clearout the b$ string variable like you did: I  
just saved you a few more bytes. [g]

Remove unneeded print statements and the file can be made even smaller.


DIM A(6)
print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;
open"i",1,filename$
FOR s = 1 to 6
B$=""
INPUT#1,B$ BYTE
c=ASC(B$)
A(s)=c
NEXT s
close 1

partialblock=256*A(4)
partialblock=partialblock+A(3)

blocks&=256*A(6)
blocks&=blocks&+A(5)

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

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

end


And because ASIC array elements actually start at 0, you didn't need to  
dimension 6 of them. 5 would do, in your case. 0 counts. [g]

Another demo doing the same thing is down to 2192 bytes, but uses dos  
interrupts and a more efficient array. [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: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

So is this one:

DIM A(5)
print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;
open"i",1,filename$
FOR s = 0 to 5
INPUT#1,B$ BYTE
a(s)=ASC(B$)
NEXT s
close 1

partialblock=256*A(3)
partialblock=partialblock+A(2)

blocks&=256*A(5)
blocks&=blocks&+A(4)

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

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

end


notice the little difference still? [g]

This one is only 2080 bytes, but doesn't close the file. Since you opened  
it for read only, it does no real harm in this case. closing the window  
returns the taken file handle. No functional loss, more bytes saved. [g]

DIM A(5)
print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;
open"i",1,filename$
FOR s = 0 to 5
INPUT#1,B$ BYTE
a(s)=ASC(B$)
NEXT s

partialblock=256*A(3)
partialblock=partialblock+A(2)

blocks&=256*A(5)
blocks&=blocks&+A(4)

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

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

end

This one is 2080 bytes in length, needs 6K of ram to run. By comparison,  
that's how much memory my first version of EXEVALID needs. a full two  
kilobytes less than your first demo version. and one full kilobyte less  
than your second demo version. [g]

I could remove the unnecessary print commands and reduce file size further.

And this one is 2064 bytes in length.

DIM A(5)
print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;
open"i",1,filename$
FOR s = 0 to 5
INPUT#1,B$ BYTE
a(s)=ASC(B$)
NEXT s

partialblock=256*A(3)
partialblock=partialblock+A(2)

blocks&=256*A(5)
blocks&=blocks&+A(4)

totalsize&=blocks&*512
partialblock=512-partialblock
totalsize&=totalsize&-partialblock

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

end

while this one is 2096 bytes in length:

DIM A(5)
print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;
open"i",1,filename$
FOR s = 0 to 5
INPUT#1,B$ BYTE
a(s)=ASC(B$)
NEXT s
close 1

partialblock=256*A(3)
partialblock=partialblock+A(2)

blocks&=256*A(5)
blocks&=blocks&+A(4)

totalsize&=blocks&*512
partialblock=512-partialblock
totalsize&=totalsize&-partialblock

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

end


--  
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: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

I beat you! :)

DIM A(5)
print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;
open"i",1,filename$
FOR partialblock = 0 to 5
INPUT#1,filename$ BYTE
a(partialblock)=ASC(filename$)
NEXT partialblock
close 1

partialblock=256*A(3)
partialblock=partialblock+A(2)

blocks&=256*A(5)
blocks&=blocks&+A(4)

totalsize&=blocks&*512
partialblock=512-partialblock
totalsize&=totalsize&-partialblock

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

end

2000 bytes on the nose, with file close command present. 1984 bytes without  
it.

Your method? Really? lol, I don't think so.

  



--  
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: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

I've actually got one down to 2096 bytes. How about you? :)

DIM A(5)
print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;
open"i",1,filename$
FOR s = 0 to 5
INPUT#1,B$ BYTE
c=ASC(B$)
A(s)=c
NEXT s

partialblock=256*A(3)
partialblock=partialblock+A(2)

blocks&=256*A(5)
blocks&=blocks&+A(4)

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

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

end

remove unnecessary print statements like I said before, it gets even  
smaller.

Btw, not only didn't you need b$ to be cleared everytime you used it, you  
didn't need to close the file; you were opening it for read access and  
since it's under NTVDM, no harm comes to it once you close the window. [g]

that's 2096 bytes and works just as well as your stuff, paco.




--  
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: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

How about 2080 bytes? [g] It becomes 2128 if I return the close 1 command,  
but you said get down and dirty. right? [g]

Thats three little tweaks that make it smaller and smaller and yet,  
smaller. taking nothing away from your useless demo.


DIM A(5)
print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;
open"i",1,filename$
FOR s = 0 to 5
INPUT#1,B$ BYTE
a(s)=ASC(B$)
NEXT s

partialblock=256*A(3)
partialblock=partialblock+A(2)

blocks&=256*A(5)
blocks&=blocks&+A(4)

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

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

end



--  
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: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

That's brilliant Pooh Cat!

--  
Jax    :)

Re: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.

127.0.0.1:

Quoted text here. Click to load it

You think so? How about 2000 bytes? I further optimized one of his "demos".  
His "best" is still 48 bytes bigger and uses more ram. [g] this one is  
exactly 2000 bytes in size and runs in 6k of ram. Poohs is bigger and runs  
in 7k of ram. HEHEHEHE

(still chews 4096k or more of storage space on you tho, but that's another  
subject entirely) See here:

DIM A(5)
print"Dusty Buster. Version 3"
print"Written by Pooh the cat April 25th, 2014"
print""
print"Enter filename: ";
input filename$;
open"i",1,filename$
FOR partialblock = 0 to 5
INPUT#1,filename$ BYTE
a(partialblock)=ASC(filename$)
NEXT partialblock
close 1

partialblock=256*A(3)
partialblock=partialblock+A(2)

blocks&=256*A(5)
blocks&=blocks&+A(4)

totalsize&=blocks&*512
partialblock=512-partialblock
totalsize&=totalsize&-partialblock

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

end

  



--  
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: Dustin fess up or you're fired. I asked for you to post tighter source than mine, and for it to be on my desk this morning. You have one hour.


Quoted text here. Click to load it

Optimizing a demo program..... is that what the Exevalid discussion has  
declined into?  

Dustin, a demo is not a production program.... it's never optimized. LOL.  
Everybody knows that! Even me.

--  
Jax    :)

Site Timeline