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?
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!)
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?
Sorry for the confusions I caused. Let me try again.
========================= Author: Cpt. Vince
Drew,
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.
(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.
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.