My Vintage Dream PC

[StickThatInYourPipeAndSmokeIt]

Unfortunately, it's not quite that simple. The votes can only
be as good as the data used to make the decisions. Now think
of two CPUs who are voting based on bad data and the third who
is voting based on the correct data.

/BAH

Then give yourself about two milliseconds to calculate the odds of that
ever happening, dismiss the dumb twit's premise, and move on. Have a
nice day, dumb twit.

 

[StickThatInYourPipeAndSmokeIt]

There you go, wrong yet again.

You're an idiot, and an asshole, asshole.

Tried the shorted voltmeter thing yet?
Huh?

Looked up any CML data sheets?

Why would I need to? Oh.. you seem to think that I am going to respond
to your retarded question. Looks like you are wrong... again... as
usual.

Did you read the post where I told you that I looked at CML *years*
ago, or are you just continuing with your typical mental masturbation
retarded twit mindset?

 

[Archimedes' Lever]

Cheap computers just
aren't worth the grief they cause.

I never said that the computer was cheap, you illiterate retard. I said
that the cost was cheap, dumbass. There is a HUGE difference. Learn to
get your facts straight. Hell, learn to read.

Sorry, but top of the line motherboards run faster than ANY OEM server
or desktop mainboard that is two years old right out of the chute, before
it even makes it to a store shelf or web page ad. I have researched the
big computer makers and NONE of them are cutting edge, so you could never
keep up with a system I put together.

My assembled systems cost less, and are more reliable, and perform any
task faster than your labeled crap ever has or ever could. It is a well
known fact among VAR suppliers that folks that want their custom 1U
servers assembled for them do not want a mainboard from one to three
years prior with a price tag on it that is 3 times what it is worth.

Your brainlessness is what causes your grief, Johnny. You
subconsciously beat yourself up for being so dumb, because even your sub
conscious is smarter than you are and doesn't like what it sees.

 

[Archimedes' Lever]

Cripes, I wouldn't touch anything that you "put together." My business
is too important to be near a guy who doesn't understand digital
voltmeters.

John

You're an idiot. I digitized IR sensor levels into a precision digital
display with full range emissivity adjustment over 20 years ago into a
device that started at $2500 each. That was in '87, when $2500 was a lot
of money. We also did 4 to 20mA linear and non-linear.

I have been putting computing machines together since the HeathKit
pre-286 days.

I could build a box better than yours with one of my oldest cases I
have. It is a flip top that was a lab tool standard years back. You are
likely familiar with it, although given your wimptard attitude, you
likely never put lab gear together before either.
I know more about putting together hot (as in speed, idiot), and
reliable PCs and other computing machines than you ever will.

You missed the "Truth" target again, as usual.

 

[Archimedes' Lever]

And I don't want Microsoft, or anyone else, changing anything on my
computer without my permission.

John

They don't do it without your permission, idiot.

You are about as thick as a would be intelligent person can get.

 

[FatBytestard]

On Mon, 01 Jun 2009 19:45:50 -0700, Archimedes' Lever

<snip>

One instruction? - Pull Power Cord.

ALL ZEROS.

I win.
Nope.
True CORE memory holds its state across power failures.
And RAM memory may well come up in a random state.
--
ArarghMail905 at [drop the 'http://www.' from ->] http://www.arargh.com
BCET Basic Compiler Page: http://www.arargh.com/basic/index.html

To reply by email, remove the extra stuff from the reply address.

And most hardware initializes the ram to a known state (and on some it
does it to start out with good ECC).

Some to all one's... some to all zeros, some to the address of the ram written
to the ram as data.

bill

I have ECC RAM. It is not for correcting power outages, it is for
correcting occasional bit errors, and only then below a certain number of
them in any given instance, and with a threshold on how many in sequence
can be off as well.

When the power is off, ECC RAM shuts off too. Even "good ECC RAM".

Yup. I've fixed it too.

How can you tell the memory state is all zeros with the plug pulled.
could have bits that are stuck open. Course you can't read that with power
removed.

And on power application it's all reinitialized (if functioning properly)
so the state of the bits is dependant on the firmware/hardware on the box.
Which was my point.

Also... what if in that memory design a low voltage level was a logical one.



Bill
--

Should it or better... does it even matter which position one refers
to as being which state?

Is that not the job of one final set of inverters on the read bus?

Does that read vector not "appear" to the reading device as being a
logic 1 for a high voltage, and a zero for a low or zero voltage logic 0?

So, does it matter how the memory element actually stores it if it gets
properly read out to the rest of the world?

 

[FatBytestard]

Any application or any person can screw up or delete a file. RAID
doesn't help that... it just makes a bad file less likely to get lost.

You really do not understand the difference between a corrupt file on a
file system, and a file that you or another one of your retard crew
filled with bad info, and then wrote (saved). That FILE will NOT be
corrupt, dumbass. The contents of the file are the USER's
responsibility. Any errant data in that file is YOUR BABY. The file
itself will read, open, and save just fine from the file system's POV. I
cannot believe that you are so thick that you do not understand what you
are backing up for, or what it is capable of.

The backup is a tool against hard drive failure, not retard crew
failure, dumbshit.

 

[FatBytestard]

And what if a current file has become damaged, or changed such as to
become wrong? In a rolling backup scheme, the old, correct files are
lost forever.

Losing company history is insane.

John

Sorry, dumbass. I know how hard it is for you to follow and keep up
with modern times. Are you still running Windows 95? I would not be
surprised.

A single, 1.5TB drive can hold 50 of your 30GB daily backups. 50 times
your $2 DVD is 100 dollars, which is not far off the reliable hard drive
price, idiot. That is uncompressed. It would hold far more with
compression.

Hell I could beat the system you have with the DOS based Zip utility.

So seven drives would hold 350 days worth of backup before compression
alone. A five drive five day week schema would be even cheaper.

The reason you put them on days is so you can zoom in on any given day
if you are hunting a file. It makes it that much easier than a chrono
index on each drive.

You are at least ten years behind this mark, and miles below me,
Johnny.

You gotta get in to get out.

 

[FatBytestard]

We have a networked company file server (another identical HP box!)
that's full of RAID drives. But if I want everything backed up, it
still needs to be stored somewhere.

John

Idiot! The "NAS chassis" IS a "Network Attached Storage" solution,
dingledorf! The NAS device IS the backup device.

 

[Kim Enkovaara]

Those words, "hundreds of releases of the design", give me cold
shudders. We use a military drawing control system, and any product -
hardware, software, mixed - is formally released as a set of
standalone, numbered documents with rev letters, all under a master
bill of materials, itself numbered and rev lettered. Only
manufacturing makes and ships things, and only from the formally
released files.

You just number the things by hand. In real VCS systems the whole
release contents can be tied to one configuration specification.
When the product is 10+M lines of code, asics, assps, tens of
FPGAs etc. the releases consist of quite many variables. And then
expand that to a installed base of tens of years.

The idea of casually shipping rev 2.3.04b is a nightmare.

How about customer specific releases etc.

How do you know that you'll be able to run the VCS ten years from now,
and that all the files will be intact? How do you know which customers
are running which of the hundreds of possible versions of one product?

The VCS runs in current platforms, and needs to be maintained. So VCS
must be up to date, and migrated to new systems if needed etc. It is not
some static system that is once built.

The version of the system must be unique and tracaeable to full set of
source (and tools). Getting 10+ year old tools to run might be fun tough

Who manages the VCS?

VCS management people, whose job is to keep it healthy and running.

More important, of the copies of your things that have ever been
shipped to customers, what fraction had one or more bugs?

The is no bug free design, if it is not trivial very small design.
Even HW designs that have been manufactured for years in volume might
have bugs that are uncovered by some third party component process
change etc. For an asic 1 bug/10000 lines of code is quite normal
bug density during its lifetime, for software the density is higer.

Each of our formal letter release packages has a README file that
notes the reason for and nature of all changes. If a bug was fixed,
it's documented there. Releasing another package is a big public deal,
and if it was because of a bug, everybody knows it. It seldom is.

When there are thousands of changes the readme does not work. Release
notes are just highlight of changes. I think we are approaching this
from different directions, I'm thinking of designs that have hundreds
of designers (hw+sw+testing etc.) you are coming from the small end.

--Kim

 

[jmfbahciv]

Now that was an insightful commentary on OS design.

That is what a monitor is. Period.

/BAH

 

[jmfbahciv]

Then give yourself about two milliseconds to calculate the odds of that
ever happening, dismiss the dumb twit's premise, and move on. Have a
nice day, dumb twit.

Odds are high. Example: system is brought up with the incorrect
date/time.

/BAH

 

[jmfbahciv]

First off, Gates and Co. bought their DOS, and wrote a "tiny basic"
interpreter on top of it, poking into DOS and BIOS routines sans
regards to the consequences. It is rather well documented.

As for buffered mode I/O, perhaps you need to explain the differences
between it and DMA as implemented on the original PC.

Buffered mode I/O on the PDP-10 was an asynchronous operation. By that
I mean the user mode program could fill/empty one buffer while the
monitor was emptying/filling other buffers in the buffer ring. If
this approach is used, DOS would not have had to pull an entire
file into memory for an edit.

This missing functionality caused lots of "buffer overruns" which
overwrote monitor code when reading a very large file.

/BAH

 

[Archimedes' Lever]

And Windows sometimes trashes the innards of files without telling you
that it did it.

John

Bullshit, you lying, retarded bastard.

 

[Archimedes' Lever]

Who cares? I rarely stress a dual-core 1.9 GHz Xeon. I don't play
games on it.

Who said anything about games, you squirming little retard?

 

[Archimedes' Lever]

They vary from about 2 years old to just-purchased. The exact same
machines!

John

The proliant server model you have are likely from a six year old
design. Sorry, but I compute on machines that are newer than six years
old. and no, the brand name means nothing.

 

[StickThatInYourPipeAndSmokeIt]

Odds are high. Example: system is brought up with the incorrect
date/time.

/BAH

You are about as lost as it gets.

 

[David Powell]

Much like racing stripes on a 1980s Pontiac?

Actually, I don't think even C++'s proponents say it's faster to
compile or run. They hope it's faster or easier to write.

It got that name 1984ish. Perhaps a variation of "DoubleplusC"? If
you're familiar with Newspeak, particularly Doublethink, there's no
difficulty in reconciling the various claims for C++ with reality.

Regards,

David P.

 

[Richard Cranium]

I didn't buy brand names, I tested machines and picked the best. But
HP does provide serious, personal backup support, really good drivers,
stuff like that.

What's wrong with a six year old design, except that the bugs have all
been worked out? It's a dual-core 1.9 GHz Xeon, ecc ram, RAID drives,
redundant bios, fans, and power supplies. Zero problems so far. The
engineering gets done without interruptions from computer problems.

How can anybody but a gamer object to that? Should we add glass
porthole covers and neon lights?

What do you do that needs more compute power?

John

His list of NAMBLA friends is so voluminous that it requires Core i7
support at a minimum. He's already boasted of multiple 1.5TB HDDs.
They're probably filled with kiddiporn by now.

Archie is a premiere power user, with a secondary intellect and a
decidedly low-end personality.

 

[Rich the Cynic]

Whwy you loas an argument based on the facts - which of course you
always do - you cut over to insults.

Weasel.

Trollfeeder. ;-)

Cheers!
Rich