|
Obviously they are hoping for pearls of wisdom...you have quite a reputation! 
Funny, I've never noticed the Follow button(s) before...It is kinda creepy isn't it? 
"Go forth into the source" - Neal Morse
|
|
|
|
|
Aaah thats why Sean Ewington is following me No idea why but my guess is:
a.) I was suspect before/in between some years
b.) Sean Ewington has a very bad Reputation (-129,675 at the moment) and Needs some up votes from my side
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Sean is on my list so a good guess is we've said something naughty and thus warrant supervision wherever our trail leads on CP.
History is the joke the living play on the dead.
|
|
|
|
|
Quote: ...we've said something naughty...
Never! At least I don't like to remember. Most probably you are right
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Maybe he just enjoys the weekend music videos...and you haven't been sharing recently btw!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Quote: and you haven't been sharing recently btw
That is, because in the past few weeks I only listened to very old nostalgic things from Deep Purple and Led Zeppelin... and I think most here are not keen on this kind of Music
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
0x01AA wrote: Sean Ewington has a very bad Reputation (-129,675 at the moment)
Even in forums that allow for downvoting, you'd have to work pretty hard to get such a negative rep.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
They are hoping that you will give them the codez.
|
|
|
|
|
ProtoZwölf is the minimal configuration of the 8 bit computer I am building. I'm going to use it to develop and debug all further hardware. This minimal computer needs a BIOS to communicate with a PC and test the new hardware expansions. Here is a screenshot of the first running version, in emulation:
ProtoZwölf starting up[^]
Ok, the list of checks and initialization is still a little short, but it will grow longer. For now we only can check the ROM, the RAM and serial I/O. It's ok that the checksum is wrong. I don't update it every five minutes while I still change the code.
BIOS setup does not do very much yet. I don't have any convenient place to store the configuration. If I use EEPROMs or Flash ROMs, I could save them in the ROM, but that would kill the IC if used too much.
BIOS CMD is the part I'm working on right now. I am going to need a protocol to upload test programs and (if I use EEPROMs) BIOS updates. A complete memory check may also be nice.
Really booting will have to wait. I'm going to need a boot device first and then an OS to boot.
The first real obstacle was the stack protocol for calling subroutines. To avoid 'knots' on the stack, the traditional protocol inlined the subroutine's address and the parameters in the code.
Yuk! That's very close to self modifying code which has gone out of fashion for many good reasons. The solution: I need separate call and parameter stacks. Ugly on most processors, but not here. I have 16 general purpose registers at my disposal and can make any one of them the stack pointer at any time. All I have to do is to initialize two registers to suitable addresses and then switch between them using the SET X (SEX) instruction as needed. Program counters work similar, only that it's the P register and the SEP instruction that designates the program counter:
Here is a 'sexy' subroutine. It can call more subroutines until I have a stack overflow and saves and restores all registers that are changed (obviously a big thing on a processor with so many free registers).
; =========================================================================================
; RS232 Out (software protocol)
;
; Parameters:
; 01 Character to be sent (byte)
;
; Return:
; ---
; =========================================================================================
RS232OutSoftware: SEX R2 ; save registers RE and RF on the call stack
GHI RF
STXD
GLO RF
STXD
GHI RE
STXD
GLO RE
STXD
SEX R6 ; load parameter 01 into RE.1
IRX
LDX
PHI RE
REQ ; Q = 0
LDI BIT_COUNT ; load bit counter into RE.0
PLO RE
SEQ ; Q = 1 (start bit)
LDI BIT_DELAY ; delay for one bit phase
PLO RF
SER_Delay1: DEC RF
GLO RF
BNZ SER_Delay1
SER_TransLoop: GHI RE ; shift out highest bit from the character
SHRC
PHI RE
LSDF
SEQ ; Q = 1 if bit = 0
SKP
REQ ; Q = 0 if bit = 1
LDI BIT_DELAY ; delay for one bit phase
PLO RF
SER_Delay2: DEC RF
GLO RF
BNZ SER_Delay2
DEC RE ; decrement bitcount
GLO RE
LBNZ SER_TransLoop ; shift out another bit if not done yet
REQ ; Q = 0 (parity bit, always 0?)
LDI BIT_DELAY ; delay for one bit phase
PLO RF
SER_Delay3: DEC RF
GLO RF
BNZ SER_Delay3
LDI BIT_DELAY ; delay for one bit phase (stop bit)
PLO RF
SER_Delay4: DEC RF
GLO RF
BNZ SER_Delay4
SEX R2 ; restore registers RE and RF from call stack
IRX
LDXA
PLO RE
LDXA
PHI RE
LDXA
PLO RF
LDX
PHI RF
SEP R5
;------------------------------------------------------------------------------------------
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
modified 2-Jun-18 6:51am.
|
|
|
|
|
|
OriginalGriff wrote:
So how does a single hardware failure disrupt a mission-critical and very, very public system like that? Somebody didn't do their job properly, did they?
Probably one of their legacy back-end services (trying to give them a break here).
|
|
|
|
|
Someone decided they could cut their operating costs by at least half by eliminating all but the active node in their backend clusters. Those other boxes were just sitting there, doing nothing but increasing the electric bill, after all.
|
|
|
|
|
Obligatory CommitStrip: The price of backups[^]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Engineering World - YouTube[^]
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Very cool! Thanks for posting!
|
|
|
|
|
WebMSX[^]
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
I crashed it. 
10 print "Hello"
20 goto 10
run
Had to power off to restart it!
|
|
|
|
|
Marc Clifton wrote: 10 print "Hello"
20 goto 10
run
This reminds me of the abuse that my classmates & I heaped upon a sperge in our high school comp sci class (BASIC) back in the TRS-80 days. He would ask why he was having problems, and we'd tell him to add this line:
5 NEW
|
|
|
|
|
I was looking for a way to mimic network latency on android and came across this response on stack overflow. This made me laugh.
http://i65.tinypic.com/2i7o0mg.jpg[^]
Poor soul lost his iPhone to the experiment ! 
Zen and the art of software maintenance : rm -rf *
Maths is like love : a simple idea but it can get complicated.
|
|
|
|
|
Typical iPhone user At least they have an excuse to get the latest version now
|
|
|
|
|
virang_21 wrote: Poor soul
No. No sympathy. None.
|
|
|
|
|
I've seen that before...but still very funny!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Languages like C# have enough built in exception types to handle most situations. But you can also create your own. Do you use custom exceptions? If so, what strategies do you use to determine when to use them and how they look?
Edit - By how they look, I mean do you keep them basic and mostly use message, or do you do things like populate data?
modified 1-Jun-18 15:51pm.
|
|
|
|
|
Yes. But not frequently.
I don't know what you mean by "how they look".
|
|
|
|
|
Mostly, I limit myself to creating custom exceptions for class libraries. Some of the circumstances in which I find them useful...
1) Allow the consumer to easily differentiate and catch my exception.
2) Share additional information with the consumer, usually via properties, without forcing them to de-serialize the message text.
3) The occasional instance when the built-in exceptions don't fit.
Not sure what you mean by "how they look".
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
