The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Shut down, move it to a different USB port, and reboot.
If that doesn't work, go do Device Manager and uninstall the driver, then refresh the Device Manager to reinstall it (on Weven, "Scan for Changes").
If that doesn't work, run a disc scan, to look for/repair bad sectors.
If it's still no good, then look for any software that you installed when you first got the device (if anything), and: - Check each executable and DLL in its installation directory for dependencies (Dependency Walker is good for this), making a note of any that are outside of the device's proprietary directory (e.g. in the Windows dir/system dir/shared dirs).
- Uninstall the software, making sure that the proprietary directory it was installed to is really gone (i.e. delete it manually, if it's still there).
- Check any of the dependencies to files in other directories. If the files were made by the company that made the device. rename them (as long as the device wasn't made by Microsoft).
- You can get rid of any registry entries, too, if you do that kind of thing (if you've never edited a Win registry, leave it).
If that doesn't fix it, you'll probably have to settle for getting some new hardware.
I wanna be a eunuchs developer! Pass me a bread knife!
I have been turning away from .Net lately and looking for alternatives. I don't want to have to rewrite everything when a certain company heads into a different direction once more.
My answer is C++. I always liked its flexibility to allow you to do very low level programming just as well as very high level programming. And today I stumbled over this video[^], in which Bjarne Stroustrup answers two simple questions.
Now I know why I like C++ so much. Thanks, Bjarne.
I like C++, but I don't like what it's turning into (and how many code designs insist on the most complicated implementations.) Moreover, just because something could be represented as an object and in a hierarchy doesn't mean that it should be.
That's not limited to C++. I have encountered four different types, what architecture and class design are concerned:
1) Archi... what? (perfect chaos)
2) Get the job done and worry about future problems when they arise.
3) Must use every pattern in the book at least once in every project. And at least one or two of my own.
4) Software as a religion, with the one and only way to do things. All others lead straight to hell. (Strict order, but absolutely helpless when something happens that is not dealt with in their particular bible)
I attempt to live C++ actually. I use to be in C programming. There was nothing about objection, overload etc. Now I do work in C++, during for 4 months I can used to program with it. Can somebody give some advises how to learn C++ or how can I get much progress ASAP ? Thanks
1) Learn C, especially how to write functions. A C++ object's methods work very much like C functions. You will be able to use your experience with C here.
2) Learn about object orientation by understanding the concept. The way the concepts are implemented in C++ (or any other language) are secondary at the moment. Begin with understanding what an object actually is: A data structure with attached functions to allow safe manipulation of the data inside that structure.
3) Learn the difference between a class (the definition) and objects (individual instances of a class). That will lead you to learning about the basic lifecycle of an object. Allocation of memory and automatic execution of the constructor when you create a new object with 'new', and automatic execution of the destructor and freeing memory when you destroy an object with 'delete'. Despite their somewhat scary names, constructors and destructors are just functions which are called automatically when you create or destroy objects. It's very important that you learn to use them to initialize or clean up an object.
4) Learn to use encapsulation to divide up the internal state of an object and its external interface. Other objects can only access methods or member variables of an object which you have declared as 'public'. They get no access to the members you declare to be 'private'. This way you can limit how the object's state is altered from the outside and keep it valid at all times. Limitations and restrictions may sound like a bad thing, but in reality they are your best friend.
5) Learn how to use inheritance and how to design class hierarchies. It's a powerful instrument for writing type safe code and avoiding redundancy. It is also an instrument you have to learn to play well, because it can also quickly lead to bad design.
Speaking of bad design: C++ allows classes and functions to be 'friends' of other classes. That actually means breaking the encapsulation. Like feeling the need to use 'goto', it's a sign that you should rethink your design.
Oh, It's unbelievable that there are responses for my questions! Thanks for the suggestions, really! Actually, I have got the concepts things about C++, like objects, hierarchies things. I guess I am lack of some projects experiences. Even I got the concepts about it, I have no idea how to use them in programming. It might be the more practices make it perfect. I have to spend much time on it and use C++ times and times. Anyway, thanks a lot! Buy the way, I red effective C++ recently. It talks about STL and boost things. I almost program with BOOST and STL library every day. They are important for the C++, aren't they ?
Actually, I have got the concepts things about C++, like objects, hierarchies things. I guess I am lack of some projects experiences. Even I got the concepts about it, I have no idea how to use them in programming. It might be the more practices make it perfect.
You have sensed the trouble; lack of experience.
If you cannot apply concepts like object orientation, you don't really understand them yet. You should therefore stop saying, "I get the concepts." You should ask questions like, "How do I learn to view a project as a collection of objects?" or "How do I decide which operations are closely enough related to put into a single object?"
For the first question, I personally very much like the work of Rebecca Wirfs-Brock (search "Wirfs-Brock" on amazon) on class roles and collaborations. I used Designing Object Oriented Software to teach a team of C developers OOP, but I suspect the more recent titles are also good.
For the second question, much as been written on the web on "separation of concerns" and "dependency injection". But as a practical matter of learning, you should start writing module tests for each class you write. Nothing slims down your classes like having to test all the interfaces and import all the dependencies into each test case.
Thanks again. It 's quite boring reading book without implement project, isn't ? It was supposed to be a tool or a manual when I got some problem. I will follow your suggestion anyway, spending much time to read the book and practicing more~
It 's quite boring reading book without implement project
This is always the problem for learning. If you are lucky, some employer will let you learn on their time. Otherwise, there's nothing to do but try to think of some sufficiently interesting thing to code on your own time. Best of luck.
Actually, I have got the concepts things about C++, like objects, hierarchies things...Even I got the concepts about it, I have no idea how to use them in programming.
Well then you don't actually understand the concepts.
As I recall it took me about 2 years to figure out how to apply objects to designs in C++ after I figured out the syntax of classes in C++. Before that I was still doing structured programming rather than object oriented programming even though I was using C++ (and classes.)
I have a couple of suggestions based on my experiences. Although you may think you got everything, it's more likely that you don't. Practice says more than theory.
I remember myself that one day it hit me: "AHA!!!". It was like that, from one day to the other everything made sense.
The problem is that it's very difficult to get to the "AHA!!!" moment, but I do know that the fastest way to get there is by having real world experiences.
I don't think you should learn object oriented design through C++ as many of its little nuances can get in the way of learning the real deal which is object oriented design. I'd say to go with C# first if you want to learn OO design.
Now, there are a few steps I'd suggest you to take:
1 - Read open source code of well designed OO applications. If you look around it shouldn't be hard to find.
2 - Design a real OO application, with its own domain model layer, with all objects that contain both data and behavior, completely separated from user interface or data access layer. You can get a lot of ideas from open source projects and design pattern books. Try creating an application for someone you know that run a small business, for free, as an experimental project.
3 - Publish the code so people can give you their opinion and point out where you went wrong and where you did right. Here is where the real learning will occur.
4 - Port your application to C++
Just an idea of what I believe is a good way to learn OO C++
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
Oh~It's amazing that so much experiences and thanks for sharing. As you said, it 's the directly way reading some open source code instead of book, I will have a try to find some in communities. It's sure thing that I will avoid the open source code without documents, it 's really nightmare, isn't it ? For the 2nd tip, it 's out of my range, It might I am from a China... I have never thought about run a business, even it 's for free. But you are right. I must have a try. I will publish the code if everything is fine which I make a real project. Anyway, thanks! sincerely !