We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hi,
I have this design for a controller but i dont know the program for it?
Where can I find the code for it? I tried google coding but cannot find it. I normally write Pascal(Delphi) but this needs to be in Keil C for a 8051.
I need to get it working quickly. Who will help?
Since this thread is still being very active, I wish to take this opportunity to hear some comments about UNIX from experts:
It will not support, nor port to, any Linux based OS. Or an Apple/Mac/iPhone platform either: those are for "gadget geeks."
The allowable operating systems are: DEC's CP/M 2.2, CP/M 3, MP/M, MP/M-II, CPM-86, IMSAI's IMDOS, MSDOS, Microsoft Windows 3.1 and above.
If you are unfamiliar with most of those OS's, then you'll need to use "Linux" to 'feel' like you've done 'real computer' work so you can classify yourself as a 'wiz kid' to your peers. Eventually, you'll tire of that and realize that you've spent all of your time 'fixing' it, and not actually getting any true "work" done.
You didn't mention UNIX; I think that, Linux is not UNIX, Linux is UNIX-like.
UNIX is not an RTOS, neither is Linux. whether it is geek friendly, is up to the geek :-)
We all know why you don't like our man Vince
I don't dislike him in the least. He's just a little, er, wordy at times.
- you think he is demonstration of an American war monger who dedicates his life to developing weapons
You missed a bit:
- you think he is demonstration of an American war monger who dedicates his life to fantasising about developing weapons
Does that make you a crazed, leftist propagandist?).
No, that makes me amused.
Unix or not Unix is a licensing issue. No need to fight about.
For Linux, there is the RT-Linux route. You can run real-time solutions "below" the Linux kernel.
Surely, if the motion is Perpetual, then time is not an issue...?
(Lunchtime doubly so!)
A full life cycle test must of course be done.
But ... but ... that'll require a supercomputer! Only supercomputers can finish endless loops in ten minutes.
I am curious about:
1. Does that mean, Cpt. Vince does not like/trust UNIX? 2. Does that mean, Cpt. Vince have never used UNIX? 3. If Cpt. Vince does not like/trust UNIX, then why?
C language was developed to develop UNIX.
For someone like me, MSDOS/Windows/UNIX/Linux are all very good.
Are you sure?
I know that it was, indeed, used to develop UNIX - but was that the specific reason for creating it?
"For someone like me..."
What are the criteria for being "like" you...?
I heard something about the preempt-rt patch that adds some real-time features to the Linux kernel. But I don't really know what it is.
(It is interesting/good to hide in the middle of this thread.)
Does what mean?
Yes, it takes great power to fold the space-time continuum.
Sorry for the confusions I caused. Let me try again.
========================= Author: Cpt. Vince
Drew,
(Remember, a computer is a tool. Don't spend all of your time fixing your tools---sharpening is fine, fixing isn't... get a new tool). ==================================================
Cpt. Vince didn't mention UNIX; so I am curious about: 1. Does that mean, Cpt. Vince does not like/trust UNIX? 2. Does that mean, Cpt. Vince have never used UNIX? 3. If Cpt. Vince does not like/trust UNIX, then why?
For someone like me, I am not smart, not able to distinguish the advantage/disadvantage of different OS, and not able to sharpen the OS on my desktop, in my limited experiences, MSDOS/Windows/UNIX/Linux are all good enough to me.
Some people in my region say that: In Europe and America, people do not use Windows on critical areas; they only trust UNIX and Linux/BSD. I don't believe such a rumor, but it is surprising that Cpt. Vince loves Windows so much.
en.wikipedia.org/.../C_(programming_language)
C is a general-purpose computer programming language developed in 1972 by Dennis Ritchie at the Bell Telephone Laboratories to implement the Unix operating system.[2]
2. ^ Stewart, Bill (January 7, 2000). "History of the C Programming Language". Living Internet. www.livinginternet.com/.../iw_unix_c.htm. Retrieved on 2006-10-31.
it is surprising that Cpt. Vince loves Windows so much.
John Linq,
UNIX/Linux
Using Linux is fine, but I have seen too many code-monkeys boasting their Linux systems as ever-so superior than Windows, etc. If they're using the OS as a development platform for a cross compiler then it is JUST A TOOL. Otherwise they better be writing something that runs on the Linux system itself.
Be it Linux/Unix/PC or otherwise, some code-monkeys are using it as a mechanism to become more geekafied. Embedded Linux is fine. But with any major OS vendor, if you are doing High Reliability applications there is a the reliance on so many non-certified drivers and services. All sources of failure.
Many of these code-monkeys are using the Linux alternative because it makes them feel like they are 'true computer geeks' while I view it as the only contemporary way to experience the OS's of old. Where we were 'the geeks' and that was definitely not a 'cool' thing: those heady days of social ostracization. In those days, the UNIX system usually wasn't found in your basement lab, or your bedroom. Businesses had them with expensive computers.
I was only poking fun at those type of 'wannabe' geeks. Linux is fine, and getting better. I was one of the last guys on the block to use a 'mouse' instead of the command line because I was ever-so proficient at the keyboard and the OS.
It is amazing how much partisanship there is on the 3 or 4 dominant operating systems. (Windows, "MAC", Linux, and true UNIX). Again, unless you are writing code that runs on the same OS, then picking the right tool for the job shouldn't be because of its "coolness factor." The PC has the most engineering tools that run on it. How many FPGA development systems, or EDAs, IDEs, or CAD packages run on [PC-based] Linux? (I know its not zero, but there are only a few worth using).
Unless you run with the big-boys like Solaris [running a qualified OS (UNIX)], Windows is the OS that offers the best choice of tools. Using Linux where Windows would best apply is going down that whole retro-OS dinking-around and a myriad of frustrations that look like you're a savvy computer guy. Fine, it might work with the stupified, but don't think that dropping the L-word is going to impress me.
I'm not going to tell my mother-in-law to buy that---super superior 'better than windows' and cooler than a MAC---Linux Box so she can browse the web, get email, and write letters. The best tool for that job is most likely in the MAC world. The best tool for doing an 8051, or C166, or ARM, or whatever is Keil's IDE running on a PC. (It is a Keil forum after all).
It is not out of 'love of Windows', but the 'love' of the right tool for the job... even if it isn't a perfect tool.
--Cpt. Vince Foster 2nd Cannon Place Fort Marcy Park, VA (NOTE: New posts should be at the bottom, in chronological order... we all know how to scroll up)
I have implemented systems for Windows NT requiring 24x7x365 usage. It does work quite well, as long as people can avoid adding these strange little hardware extras to the computer, and in the progress install a large number of more or less buggy drivers. After all, a very large number of blue-screens (yes, the color blue should sue M$ for the bad reputation) are from the drivers.
The Windows driver model is - in my view - quite lousy. Few people manages to produce reasonably bug-free Windows drivers, which directly results in a lot of complaints about unstable Windows machines. It really doesn't help how stable the kernel is if the drivers have critical bugs because they are too complicated to write.
But if I have the choice, I would prefer BSD or Linux before Windows. The source code availability increases the options available. The licensing fees allows inexpensive work with clusters or other redundant solutions. And there are a lot of server applications that have matured for 20 years or more in the unix world.
One thing to note is that the unix world decided to go for source-code compatiblity, whilw M$ strived for binary compatibility in Windows. Because of this, unix programs are normally written to auto-detect machine capabilities at compile time so you get very optimized binaries.
Another thing is that M$ is walking towards managed code. This may affect the market a lot when some of the following steps are taken and .NET becomes the native API - will WIN32 be emulated or an alternative API?
You'll have to wait for our captain to get feedback on his view of Unix or any of the derivatives.
"For someone like me, I am not smart," Define smart. A professor who gets home and afer a couple of hours are asked by his wife where the dog is? Skills tends to develop in different directions, often following our interests. In some parts of the world, it is considered smart to not walk into the wrong parts of the city.
<snip>
To summarise:
You need Windows to use Keil tools.
(NOTE: New posts should be at the bottom, in chronological order... we all know how to scroll up)
Yes sir right away sir!