 |

|
"as the chipmaker struggles to find a role in an industry increasingly focused on mobile and away from traditional PCs"
That's once again hype - yes mobile is blooming but most/real work done on traditional PC's.
dev
|
|
|
|

|
devvvy wrote: most/real work done on traditional intel PC's.
You missed a word out
|
|
|
|

|
Yeah, not surprised. I've built several desktop computers for myself and the AMD machines I've built died within two years. Of the four Intel machines I built, only one died and that was after four years; I put the others into retirement after five.
m.bergman
For Bruce Schneier, quanta only have one state : afraid.
To succeed in the world it is not enough to be stupid, you must also be well-mannered. -- Voltaire
In most cases the only difference between disappointment and depression is your level of commitment. -- Marc Maron
I am not a chatbot
|
|
|
|

|
Weird, I have not lost any of my AMD PCs, I still have working K6-II, Duron 600MHz, Athlon XP 1700+ (with a small part of the silicon chip missing, but still working), Phenom 9850 BE, Phenom II 975 BE. Over the time power supplies and motherboards died but none of the processors. Starting with the Athlon they were all pretty heavily overclocked - max with basic air cooling.
Except for 1 NVidia card (8800GT, that is one good card), all my graphics cards were ATI. I have lost only one of them, due to fan melting (literally) twice and then, on the second go, trying to remove the radiator myself, by hand. The first fix was done locally and they kind of glued the radiator with epoxy and used too much. Let's just say that when the radiator came off it took some SMDs from the PCB surrounding the chip with it.
I now use ATI graphics but Ivy Bridge i7 - WoW runs about 50% more FPS on Intel compared to AMD processors and that's the only gaming habit I still afford.
|
|
|
|

|
The project I am working on now is pretty tough. Was wondering about some other projects that others here have worked on that were ultimately successful?
This project I am working on involves taking a C# library running on one server type machine, and interfacing it with the Micros ISLs for the Micros POS. It communicates with the C# server library using WCF (which I had not used before). Of course, Micros uses native DLLs so I had to write C++/CLI wrappers for everything else too. In addition, this C# library I wrote has to load an embedded system and put the Micros sales into our web server.
It is going to work, as I prototyped it a while ago, but now I am deep in the muck of implementation.....
I will get quite a bit of personal satisfaction when this project is working, especially since my company has paid for 2 different implementations of POS software that ultimately did not work and cost a small fortune.
|
|
|
|

|
I find any code I work on is getting harder - it sucks to get old.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|

|
John Simmons / outlaw programmer wrote: I find any code I work on is getting harder - it sucks to get old.
That can't be good!
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|

|
I worked real hard to eliminate any innuendo from my post.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|

|
My grandmother used to have a word of advice on getting old. She said, "Don't."
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|

|
BrainiacV wrote: She said, "Don't." She say how? (I don't want to use the one sure-fire method to do so. My sister was 20 years older than me, now I'm 9 years older than her.)
|
|
|
|

|
Unfortunately she died before passing on the secret.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|

|
BrainiacV wrote: Unfortunately she died And that's the surefire method that my sister used so I became older than her. I do have an infantile sense of humor that I stubbornly retain despite my wife's objections. Probably a misused method of keeping the mind young.
|
|
|
|

|
Yeah, today happens to be my birthday and I've been saying fantasy or not, I plan on seeing 125.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|

|
BrainiacV wrote: I plan on seeing 125. I'm pleased to say I am under half that age, but not by that much and unfortunately that time is approaching twice as fast. (IE, by next year, I'll have added 2 years to double my age. Of course that's true for everyone.)
When I was born the life expectancy was 72 and today it only has increased to 75. The good news is that when you live longer, your personal life expectancy increases as well. So if you make it to 124, you might reach your goal. Of course we both could snuff the candle tomorrow improving everyone else's odds of exceeding 75.
You related to that singer that bemoans the fact that we only live a 100 years? Ignoring the fact that only a few of us really reach that age and then go on and prove the singer wrong cause they just keep going, going...
|
|
|
|

|
Either that or I expect to be crossloaded into silicon by then.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|

|
Thank you. Now I don't want you running out and getting me any inexpensive gift
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|

|
gift? I wouldn't dream of doing that to you.
|
|
|
|

|
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|

|
David Knechtges wrote: interfacing it with the Micros ISLs for the Micros POS. It communicates with the C# server library using WCF (which I had not used before).
I beg your pardon for my ignorance, how's anything "Micro" or "Embedded" to understand WCF? I'd explore just plan socket on both end (hope string/int representation be same on both ends)
dev
|
|
|
|

|
Well, Micros is the POS application - one that is used in many retail stores and restaurants. It is PC based with a way to run custom DLLs - which are native code interface DLLs.
The embedded system I am using is communicated with over a 900MHz radio. The PC communicates with it using an antenna attached to it that runs on an RS232 port on the PC.
So essentially, what I have is:
1 or more Micros POS terminals talking to my custom C# server over WCF (using C++/CLI to wrap the classes/communications)
C# server communicating with the embedded system using the antenna on the RS232 port
C# server communicating with a IIS web server on the same intranet
C# server communicating with another windows application over WCF on the same intranet
Sheesh, even me writing it out is confusing!
|
|
|
|

|
okay, clear. Thought you are saying embedded system is communicating with a windows box via WCF!!!
dev
|
|
|
|

|
Clearly what is meant is that the application that communicates uses WCF (but an existing driver probably exists to do all the low-level bits) So the application can use the higher-level functionality provided by the drivers and windows to open sockets or rawIO connections. On the Project itself, it seems to me (Sorry if this offends) that the design of the system (not application) is flawed. It's like using a sledgehammer to whack in nails, and while it will work it may be a little over-engineered. Truely the POS equipment / software for scanners should interface to the DB already (how it gets it's prices anyway) and you could then just add-in some SQL triggers to decrement "instock" (or similar) of item. Raising a purchase ledger (should be done automatically through stock system), can then be stored online, but it should only ever be stock, prices and promo's that are read by online anyway... Just my two-cents, but might have saved you a lot of headache. Difficult projects for me are all about difficult clients, they either have other contractors in poking about what you've done breaking things, or they change their mind about what they want (both result in a fresh bill)
|
|
|
|

|
why are you replying to me Lewis, it's not my project
dev
|
|
|
|
 |