A little more specific. I learned a bit more about the BIOS, CMOS, and POST. I also learned that there were warring factions on NICs when they first came out. I even shared with my husband about the limit on rewrites on a Jump Drive - which he then looks at me and says, "well that's logical". (Thank you, Mr. Spock. By the way, that means it was something he didn't know!)
Bluetooth technology, harddrives, digital cameras, Firewires, USB, and RAM were things that I already knew something about - sometimes through prior problems with, sometimes through personal research. But it was nice to hear that there are adaptors for firewires so I don't need to buy a 6 pin to go with my 4 pin firewire.
The graphic cards and CPU presentations were slightly more enlightening for me, as in I feel I can look for what I need now instead of going with that one because the salesperson said it is what I need.
Overall, it was an interesting class - although it did take longer that I expected.
When we presented on our malware and security, I found that I learned just as much about Trojan Horses as I did about worms during the research. They seem slightly intertwined - maybe because as Ron said, a Trojan Horse can carry worms. It is scary to see how malevolent people can be - sometimes just to see what they can do.
Thursday, November 27, 2008
Tuesday, November 25, 2008
What did I learn?
Thanks to Ron, I learned that "Bios is dry". (His words not mine.)
I learned the simple logic that a computer follows, via our first simple computer exercise. I re-examined my use of operating systems and found that both OS X and Windows versions 2000 and XP work for me. I found out that the different OS interfaces are all very similar, and most of the time they can be used with a little intuition and a little bit of looking around.
I also found out that I like what I do to prevent disaster on my computers. I feel that I have a solid plan. That insight might change by next class, but for now I feel good about it.
I don't know all of the individual components of what is inside of the computer case, but I know enough to get me into trouble. My husband tried to add a new DVD burner to his computer only to find that he didn't have room for the ribbon cable - there was too much already there. We talked to another techie and Arthur got himself a new connector to clip onto an existing ribbon cable. He warned me that it may take several tries and that he may need to get more ribbon cables and more clips, but it was worth a try. He clipped the ribbon cable, and it worked.
My point is, with him around and continually going into the computers to fix, repair, replace, or just play around, I already knew a lot about what was inside - I just need the actual thing in front of me to follow connections and see how everything connects and works. I do know that after this course, I feel more confident about opening a computer on my own. I'm not sure how much I would DO on my own, but I wouldn't be afraid to open it any more.
I learned the simple logic that a computer follows, via our first simple computer exercise. I re-examined my use of operating systems and found that both OS X and Windows versions 2000 and XP work for me. I found out that the different OS interfaces are all very similar, and most of the time they can be used with a little intuition and a little bit of looking around.
I also found out that I like what I do to prevent disaster on my computers. I feel that I have a solid plan. That insight might change by next class, but for now I feel good about it.
I don't know all of the individual components of what is inside of the computer case, but I know enough to get me into trouble. My husband tried to add a new DVD burner to his computer only to find that he didn't have room for the ribbon cable - there was too much already there. We talked to another techie and Arthur got himself a new connector to clip onto an existing ribbon cable. He warned me that it may take several tries and that he may need to get more ribbon cables and more clips, but it was worth a try. He clipped the ribbon cable, and it worked.
My point is, with him around and continually going into the computers to fix, repair, replace, or just play around, I already knew a lot about what was inside - I just need the actual thing in front of me to follow connections and see how everything connects and works. I do know that after this course, I feel more confident about opening a computer on my own. I'm not sure how much I would DO on my own, but I wouldn't be afraid to open it any more.
My OS Experience
I was told I never answered the Journal part of my OS experience, which is now on my page on the Wiki, but let me make reference to it here, as well. I spoke to the person who introduced my husband to Puppy Linux, to find out what he thinks about it and why he likes it so much. He likes the speed at which it works. He also likes the drivers available for graphics. I never did ask why graphics are so important to him.
I watched Pirates . . , and found Jobs character to be a bit over the edge. Gates seemed to be a scheming puppy dog, but the computer information was interesting. Now the question is: How much of is true and how much was created for the dramatic effect?
I have installed and operated a few different OS types, not the least of which was Windows XP as a parallel OS on my personal Mac Top.
I have also used Puppy Linux on my husband's laptop and Ubuntu on his at home computer. The first time I used Ubuntu was quite by accident. He has the OS choice at the very beginning of the boot up - but if you don't make a choice, Ubuntu is the default (probably because it is password protected). I didn't know this, got confused at the sign in screen but entered a known password that worked, and started using it. Some things are different, but nothing that can't be figured out. The only thing I couldn't figure out is how to quit the program (Little red ball at upper RIGHT of screen). That was how my husband found out I had used his computer. (LOL)
I watched Pirates . . , and found Jobs character to be a bit over the edge. Gates seemed to be a scheming puppy dog, but the computer information was interesting. Now the question is: How much of is true and how much was created for the dramatic effect?
I have installed and operated a few different OS types, not the least of which was Windows XP as a parallel OS on my personal Mac Top.
I have also used Puppy Linux on my husband's laptop and Ubuntu on his at home computer. The first time I used Ubuntu was quite by accident. He has the OS choice at the very beginning of the boot up - but if you don't make a choice, Ubuntu is the default (probably because it is password protected). I didn't know this, got confused at the sign in screen but entered a known password that worked, and started using it. Some things are different, but nothing that can't be figured out. The only thing I couldn't figure out is how to quit the program (Little red ball at upper RIGHT of screen). That was how my husband found out I had used his computer. (LOL)
Monday, November 24, 2008
Question #3
3. What are the essential "big picture" hardware pieces a computer must have to be a computer. Explain why each piece is essential.
According to tomshardware.com, every computer needs:
PC case (built in Power supply) = this is to hold all of the component parts and power them
Motherboard = Used to hold and provide links for all of the component parts
Processor = Allows communication between component parts
CPU cooler = prevents overheating of parts and therefore prolongs the life of the CPU
RAM = Random Access Memory - volatile storage of what is being done
Harddrive = permanent storage of what must be done to access component parts
Graphics card = allows visual interface
(CD ROM or DVD Drive and Floppy disk drive) I feel these are optional but most programs come on CD or DVD today
Operating System = Tells what works how
Monitor = allow output
Keyboard = allows input
Mouse = allows input
I also think a Network Interface Card is needed to stay connected, but I don't remember that being mentioned.
Does this answer the question? I sure hope so.
I have to say that understanding how to put parts together on a computer and what each does makes as much sense to me as understanding the putting together of ingredients to a cake. The flour provides the base, the shortening allows it to stay moist, the eggs help coagulate, the baking powder keeps it soft, the baking soda allows it to rise. It still doesn't explain to me why it is a cake. A computer has all of these above named parts - some are needed, some are extra, - but it still doesn't make sense to me that it works together as a unit and what it actually does. Is it because I am a resistant learner? (AM I a resistant learner? - I know I used to be about computers, but am I still?) Or is it still just too imaginary for me? Maybe if I actually had to DO it, physically do it, it might make a difference. I know there have been times when Arthur (my husband) opened the computer case to replace, remove, upgrade, or install and I had no problem understanding what he was doing and why. So why do I feel so confused and overwhelmed now? Maybe it is not yet personally relevant. The good news is that after the series of classes, I know where to find the answers if it ever does become personally relevant.
According to tomshardware.com, every computer needs:
PC case (built in Power supply) = this is to hold all of the component parts and power them
Motherboard = Used to hold and provide links for all of the component parts
Processor = Allows communication between component parts
CPU cooler = prevents overheating of parts and therefore prolongs the life of the CPU
RAM = Random Access Memory - volatile storage of what is being done
Harddrive = permanent storage of what must be done to access component parts
Graphics card = allows visual interface
(CD ROM or DVD Drive and Floppy disk drive) I feel these are optional but most programs come on CD or DVD today
Operating System = Tells what works how
Monitor = allow output
Keyboard = allows input
Mouse = allows input
I also think a Network Interface Card is needed to stay connected, but I don't remember that being mentioned.
Does this answer the question? I sure hope so.
I have to say that understanding how to put parts together on a computer and what each does makes as much sense to me as understanding the putting together of ingredients to a cake. The flour provides the base, the shortening allows it to stay moist, the eggs help coagulate, the baking powder keeps it soft, the baking soda allows it to rise. It still doesn't explain to me why it is a cake. A computer has all of these above named parts - some are needed, some are extra, - but it still doesn't make sense to me that it works together as a unit and what it actually does. Is it because I am a resistant learner? (AM I a resistant learner? - I know I used to be about computers, but am I still?) Or is it still just too imaginary for me? Maybe if I actually had to DO it, physically do it, it might make a difference. I know there have been times when Arthur (my husband) opened the computer case to replace, remove, upgrade, or install and I had no problem understanding what he was doing and why. So why do I feel so confused and overwhelmed now? Maybe it is not yet personally relevant. The good news is that after the series of classes, I know where to find the answers if it ever does become personally relevant.
Sunday, November 23, 2008
What??
I miss one class out of the entire 18 months and I suddenly feel like a fish out of water. Journal assignment number 4 is pick two of the following:
1. Describe what actions a computer takes from power-on to Log-in screen.
2. Describe what a computer does when you double-click MSWord's start
icon until you are brought to a blank document.
3. What are the essential "big picture" hardware pieces a computer
must have to be a computer. Explain why each piece is essential.
Did we talk about any of this in class? Does #3 mean that all computers need input, a processor, and output? Does #1 mean that computers basically "wake up" at power-on. This is where they check to see what's there, who's answering properly and that all of the ducks are in a row? And what happened to the last post that I composed but didn't post? Is it out there in the ethernet someplace? What??
Oh, by the way, I found and posted the lost post.
1. Describe what actions a computer takes from power-on to Log-in screen.
2. Describe what a computer does when you double-click MSWord's start
icon until you are brought to a blank document.
3. What are the essential "big picture" hardware pieces a computer
must have to be a computer. Explain why each piece is essential.
Did we talk about any of this in class? Does #3 mean that all computers need input, a processor, and output? Does #1 mean that computers basically "wake up" at power-on. This is where they check to see what's there, who's answering properly and that all of the ducks are in a row? And what happened to the last post that I composed but didn't post? Is it out there in the ethernet someplace? What??
Oh, by the way, I found and posted the lost post.
Tuesday, November 18, 2008
So what's going on . . .
Question #1: What goes on in a computer between turning on the power and seeing a useable screen? I know that all of the components get checked to make sure they are there and that they are operational. I know it runs different checks to ensure proper communication between parts, takes an inventory of what is and isn't there, and gets everything ready to roll. I guess I kind of envision it as a wake-up call. The power supply is the sound that wakes you up, then your senses take over and do an inventory of what is there and what isn't, and then what responds and what doesn't.
If, for instance, you wake up after sleeping on your arm, you may not realize that your hand is still there because you can't feel it, or maybe even move it. So the boot up process would detect this and try again (just like you), until communication is established, or until a fatal error is determined.
Of course, this analogy only works for those who have time to wake up gently. For the rest of us, the alarm jump starts our day.
This is a very non-technical ideal of what a computer does. Do I still need the technical description?
If, for instance, you wake up after sleeping on your arm, you may not realize that your hand is still there because you can't feel it, or maybe even move it. So the boot up process would detect this and try again (just like you), until communication is established, or until a fatal error is determined.
Of course, this analogy only works for those who have time to wake up gently. For the rest of us, the alarm jump starts our day.
This is a very non-technical ideal of what a computer does. Do I still need the technical description?
Monday, November 17, 2008
Keeping the distance
Although I try to keep my blogs and my assignments separate, they often seem to blend and merge. This may be in part due to the fact that I am supposed to "reflect" on what I learned or did in class. So I have decided to keep this distance with the blog.
I recently had my left knee arthroscopy, and although my doctor doesn't expect much improvement due to what he saw in the joint, I am happy to report that my pain (like that prior to surgery) is gone. My joint capsule is still a bit sore from being stretched, poked, prodded and cut into, but my level of pain is well within acceptable range for me. For that I am grateful.
I was also asked (for what seems like the 50th time, but is probably only the 5th) if I would consider presenting at a conference. My topic (chosen for me) would be classroom management. My first response to this is, "I have nothing special to offer." My colleague doesn't agree.
She was impressed when she walked into my class at the end of the school day on a Friday and discovered that all of my students were still there - silently waiting for me to dismiss them. (This was a consequence that they had earned.) When I did dismiss them 10 seconds later, many of them still wished me a good weekend.
I did agree to give the presentation on a few conditions, and now I am wondering - What could I possibly say? What would be interesting to other teachers? What would make a difference? What benefit would anyone attending MY presentation get? Could my methods (do I really have any?) help others or do they just work for me because of who I am and beleive myself to be? And still - What do I talk about?
I guess I could just explain how I do what I do, and then open the floor for questions, but is that cheating those who are attending and looking for answers? Do I have any answers to give? I really don't know.
I recently had my left knee arthroscopy, and although my doctor doesn't expect much improvement due to what he saw in the joint, I am happy to report that my pain (like that prior to surgery) is gone. My joint capsule is still a bit sore from being stretched, poked, prodded and cut into, but my level of pain is well within acceptable range for me. For that I am grateful.
I was also asked (for what seems like the 50th time, but is probably only the 5th) if I would consider presenting at a conference. My topic (chosen for me) would be classroom management. My first response to this is, "I have nothing special to offer." My colleague doesn't agree.
She was impressed when she walked into my class at the end of the school day on a Friday and discovered that all of my students were still there - silently waiting for me to dismiss them. (This was a consequence that they had earned.) When I did dismiss them 10 seconds later, many of them still wished me a good weekend.
I did agree to give the presentation on a few conditions, and now I am wondering - What could I possibly say? What would be interesting to other teachers? What would make a difference? What benefit would anyone attending MY presentation get? Could my methods (do I really have any?) help others or do they just work for me because of who I am and beleive myself to be? And still - What do I talk about?
I guess I could just explain how I do what I do, and then open the floor for questions, but is that cheating those who are attending and looking for answers? Do I have any answers to give? I really don't know.
Wednesday, November 5, 2008
My favorite OS
When I mentioned that I use both Mac OS X and WIndows XP on a daily basis, my husband asked about my favorite OS. My answer was that I didn't have one. It seems whichever OS is up and running is the one I run with. I actually had to stop and actively think about the differences. Then I realized that I like the Mac OS X interface for internet much better. I have found that if my Internet activity is slowing down on the Mac, I can easily clear my history and that tends to speed things up. The Windows machine is much more involved and much less accurate. My husband pointed out that it doesn't clear the history on the WIndows machine, it 'hides' it. You need a special program to actually "wipe" out the information, and what this does is overwrites the information that is still there after 'removing' it. He called it invasive; I called it scary.
Subscribe to:
Posts (Atom)