Dustin <
abugh...@gmail.com> wrote in
news:XnsA220DEB284D85C9...@94.75.214.90:
> "p-0.0-h the cat" <supe...@poohland.invalid> wrote in
>
news:t16219lr6givhje9k...@4ax.com:
> Selective quoting? I left what I choose to respond too. Is that what you
> have an issue with, Pooh?
>
> In all actuality, poohskie, I haven't lost any arguments with you so
> far. You told me SMART was better if corp did it, as they have quality
> control standards I couldn't even hope to touch. It isn't. You've since
> posted a url which supports MY position, not yours. "hotshot" indeed.
>
> You claimed dell/hp make better computers than what I could build. They
> don't. Btw, I serviced a Dell yesterday and even took pics in case I had
> to "prove" it. I found NO FCC/UL sticker anywhere on that machine. It's
> an inspiron tower with a bestec power supply; rated for 300watts.
> *laugh*. the 12volt rail is bad; it's pushing just a hair under 7volts.
>
> it's got a western digital BLUE drive; I was impressed with that, even
> if it's one of the lesser rated ones. The power supply is your typical
> low end powered junk, tho. Just enough to run her, and barely that.
>
> The tower was made in china and isn't too flimsy, but isn't all that
> great either. Like I said, I took pics of her this time to show you. [g]
>
> It has a microATX mainboard inside; an off brand one at that. It's NOT a
> Dell mainboard. Intel CPU, and sata II ports. But again, it's a rather
> generic board. hehehe.. QC eh?
>
> Then you have that HP I worked on with bad restore disc creation
> software right out of the gate. I will get you the url to that. I'm
> going to be seeing it's owner in a few days to pickup some audio discs.
>
> Let's see.. Then we went to the licensing discussion. I've yet to find
> anything on google that has an example of someone being punished for not
> turning in his machine to be fcc/ul licensed. Here's my guess on that:
>
> Once you build the machine and turn it in, you have to keep the same
> components and everything else the same to keep that certification.
> Right? We can agree that you can't go making changes and still claim
> certification can't we?
>
> Well, If your a small oem system builder, like myself, Just how often do
> you suppose we keep the same identical configuration before changes are
> made? We have to continue keeping up with changes in the industry, We
> have to offer systems which are current.
>
> That means, the system configurations are subject to change. They might
> come one way for this price, but for an additional charge, we'll include
> more ram, bigger HD, change out optical drives for one with more
> features. Perhaps add a secondary optical drive, maybe upgrade the video
> card.
>
> It's upto the customer how badass they want it to be. We have base
> models, then "deluxe" models. once we're changing out hardware that was
> previously "fcc/ul" certified, wouldn't that violate our certification
> for that "model"? I'm thinking this would.
>
> 3 or even 6 months from now, the base model might have nearly the same
> stock features as the deluxe one did, due to price changes. It might
> have a video card from Nvidia as opposed to ATI this time around. A
> better mainboard with a nicer chipset might be available and would be in
> use. This would technically make it a far different machine than the one
> I assembled some months back. I couldn't very well stick the same "fcc"
> sticker on the back of it, now could I?
>
> In 3-6 months, I'd repeat this process. That's alot of licensing
> machines that are only built new in that configuration for a few months
> before they have more uptodate components. The only thing that might
> remain the same for a little while is the cpu's themselves. With the
> option of swapping it out for the latest and greatest, pending the
> mainboard can support it.
>
> So, wouldn't it be far less of a headache for you to just use fcc/ul
> licensed products and build the machine from those components in the
> first place? Seems like it would.
>
> Probably why Dell didn't fcc/ul this machine I worked on. They're always
> discontinuing them, and incrementally releasing new "versions" of the
> same base model. That would be costly to re-certify them all.
>
> Then we had the virus discussion. That was fun. You never demonstrated
> any understanding of how a prepender functions. You cited a url that has
> several problems, some dealing specifically with it's explanation of a
> prepender and how it functions.
>
> You tried to bait me with some silly nonsense about assembler not being
> pure as I posted it because I relied on microcode/firmware (whatever you
> wish to refer to it as) and didn't create that code myself. That's
> really reaching there pooh.
>
> Then you tried to bait me with "guessing" that xor is used in the cipher
> algorithm. That's ALL you guessed correctly about the crypto being used,
> btw. And that's ONLY specifically the crypto irok itself performs. The
> crypto irok has on itself is NOT a simple xor cipher. And you damn sure
> didn't guess anything about that. I had to tell you it's armored.
> Despite the urls describing it also telling you it is. I wouldn't even
> say it's a guess since I told you encryption is used and xor is a common
> function.
>
> In this case, Irok is indeed using it as a math function and not a
> logical operation. NO different than if I'd used add/sub/divide/multi
> instead of xor. Except that I'd have to write additional code to
> reverse the process; which isn't something I wanted to do for this.
> Virus writing is different than application writing. You don't want to
> use more bytes than you need.
>
> You couldn't tell me how many bytes consisted of a header or what the
> header itself even was. You cited a url with bad references to this
> header and a clear lack of understanding by it's author concerning
> viruses and associated terminology. It looks like some computer science
> dropout wrote it, Pooh.
>
> The only thing you've demonstrated skill in so far is the ability to
> troll me. By baiting me into technical discussions that you can't hold
> your own in.
Dustin that must be the Word Wall Of The Month. You wrote 1,031 words or
4,712 characters! Are you posting while taking stimulants? :)
--
Jax