|
I saw though that someone else had solved your problem and felt like having a bit of a dig! 
Morality is indistinguishable from social proscription
|
|
|
|
|
Yea, lol this stuff is pretty out there if you have only been exposed to userspace programming. Now onto assembly language!
|
|
|
|
|
|
Please post your question in one forum only.
|
|
|
|
|
Hi all, I would like to check the throughput of the RAID controller and I need to avoid the bottle neck of HDD. So I would like to make sure all the test data is written to HDD's write cache. Could anyone know how to control the data to be written in the cache(not memory cache) only?
|
|
|
|
|
You should be able to disable the OS cache; but the behavior inside the HD itself is a black box to anyone outside. The best you can do is to leave the array idle for a while between test runs so that the controller should flush the on board cache and to limit your writes to slightly less than the maximum the cache can hold.
3x12=36
2x12=24
1x12=12
0x12=18
|
|
|
|
|
Thanks, Dan. But is there any way to determine which size to write is suitable, i.e. if the HDD's cache is 16MB? I would like to flush the cache first then write some data but if the data is too small the throughput may still too slow. And if writing large data it may be written to disk instead if OS cache is disabled. How can I balance it to keep using the HDD's cache?
|
|
|
|
|
OS cache and the cache on the HD are completely independent. Disabling the former will have no effect on the latter. You'll have to experiment with various sizes to see what happens. I'd hope that the controllers in the drives would use the full xxMB of cache for writes if saving and not hold any in reserve for read use; but I don't know if that's actually the case.
3x12=36
2x12=24
1x12=12
0x12=18
|
|
|
|
|
If I understand what you're trying to do, you have one very serious problem. Doing this while running under Windows, any process can use the drive at any time, including during your testing, screwing up the results.
I do believe that you cannot do what you want while running Windows. You'd have to do it under DOS or some other single tasking O/S.
|
|
|
|
|
Dave Kreskowiak wrote: I do believe that you cannot do what you want while running Windows. You'd have to do it under DOS or some other single tasking O/S.
I think you're overstating the difficulty of avoiding problem. I was benching several methods of reading large data files a few weeks ago, and while there were a number of high outliers roughly half to two thirds of the results came within about 30ms on 2.5ish second test runs. It was easy to see which runs got hammered by a different processes IO. (Probably WMP in my case since i was doing it on my dev system while listening to music).
3x12=36
2x12=24
1x12=12
0x12=18
|
|
|
|
|
How to interact with the game controller is connected to the usb port in C#?
modified on Tuesday, December 29, 2009 3:02 AM
|
|
|
|
|
Google for "XNA Framework".
|
|
|
|
|
To expand on Dave's response, some USB devices can emulate a COM port, so you can just use the System.IO.Ports.SerialPort class. Otherwise, you may have to import some Win32 API methods (using the DllImport attribute), depending on the device class (HID, CDC, etc). Plus, you'll need to know the format the controller uses to send its data to the PC.
Dybs
The shout of progress is not "Eureka!" it's "Strange... that's not what i expected". - peterchen
|
|
|
|
|
I know it's a programming website and my question has nothing to do with programming, but I exist in CP for some time and I love the community. 
Problem Statement
OK. The problem is: it takes extremely much time to recognize a CD or DVD for my DVD-ROM drive. By extremely long I mean 5-15 minutes. What is interesting, it happens only for the first CD/DVD used from system start. The further insterted CDs are recognized and read much slower than before the problem appeared, but they are recognized at almost normal time.
I suppose is enough information for somebody who knows what's going on. However, here is the background.
Background
1. I messed up IDE cable. I thought that there is a problem with HDD and a "HDD cable" mislead me. In effect, I was plugging/unplugging CD cable and maybe I damaged it.
2. I do not know a model of my CD-ROM. I mean, it is a classical no-name from a computer bought as a whole. I regret buying it that way.
Any ideas? Thanks in advance.
Greetings - Jacek
|
|
|
|
|
There are a couple of things you might try. First off, clean the drive. Get a commercial CD cleaning kit that includes a dummy disk for the drive and give it a good dusting. When the drive tries to read a disk, if it runs into errors it will retry for a while, and it can sometimes take a few minutes. Secondly, check the jumpers on the drives - all of them. A single IDE port/cable is allowed to have 1 or 2 devices attached. Most machines using IDE technology have two ports, each supporting two devices. If you have only one HDD and one CD, the best configuration is to let each be Master (or no selection on the jumpers at all, depending on the manufacturer) of its own cable. If you must use two devices on a port, one must be Master, and the other Slave. Since a CD drive is slower than a HDD, the HDD should always be the Master. In the event that you have two HDDs, put them both on the same cable, and connect the CD to its own separate cable.
One other thing to consider is replacing the cable. If you've damaged it, or you have an old ATA33 cable on a modern IDE port, you're asking for trouble. They're cheap to replace so, given your mention that it might be damaged, you might as well start with this step and see what happens.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
Thank you.
Yeah, I had been "googling" and read about switching jumpers in several forums. I technically know what are jumpers, but I don't have a faintest idea where are they in this specific case. On a motherboard? On a cable? On a CD/HD drive?
I have a single HDD with SATA cable and a single DVD-ROM drive with ATA cable. I consider my PC as modern one (2007).
Greetings - Jacek
|
|
|
|
|
Jacek Gajek wrote:
I have a single HDD with SATA cable and a single DVD-ROM drive with ATA cable
Never mind then, you don't have a jumper issue. The jumpers are important only when you have two ATA drives on a single cable, as one drive must be master, the other the slave. Even this depends on where you live, as many European models use a third position - CS (chip select) - which is rarely used in the US.
I haven't built any machines using SATA drives yet, but I don't believe they require jumpers to work. But since you suspect there might be damage to a cable I'd replace them both, just to be sure. As I mentioned, they're cheap. The DVD-ROM should be given a good cleaning, too, as dirt on the optics commonly causes read errors, which lead to many retries and long delays.
You might also reinstall the DVD-ROM driver software, if it shipped with drivers. Sometimes drivers get corrupted, though I have no idea how that can happen. I've had several HP products fail to respond after months of service, and reinstalling them often restored full function. Use the System applet in Control Panel to access Device Manager, then delete the drive from the list. Then reinstall the software per the manufacturer's directions.
It's also a possibility that the drive itself is failing. I know that sounds unreasonable, but I've had two fail on me in less time. Happily, they no longer cost more than the computer.
The last possible problem I can think of is an ugly one - the drive controller on the motherboard may be failing. I haven't had this happen in a long time, but it does occasionally occur. It used to be possible to buy a drive controller card to bypass the onboard controller, but I haven't seen one of those in years.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
Roger Wright wrote: Then reinstall the software per the manufacturer's directions
I doubt that a company which sold me this computer knows who is a manufacturer of their DVD drives... It's name is "DVD Multi recorder". Therefore, excluding the step quoted above, I tried all of that.
What's fun, for some time DVD was recognized as FDD. After messing (plugging/unplugging) with ATA cable it wasn't recognized at all. After next messing, the current state has been achieved.
Roger Wright wrote: It's also a possibility that the drive itself is failing.
It is higly improbable, because it happend just after some risky operations where performed, which wasn't directly related to the drive itself. A fatal coincidence might happen, though (hope not).
Roger Wright wrote: the drive controller on the motherboard may be failing
Yep that would be ugly. The motherboard is ASUS, though. On the other side, why the hell could it fail in this specific moment?
Thank you for your interest and helpful answers. I will try to find someone who has such cleaning CD and stealencourage him to giveborrow it to me for a yearday or two.
Greetings - Jacek
|
|
|
|
|
Roger Wright wrote: Never mind then, you don't have a jumper issue. The jumpers are important only when you have two ATA drives on a single cable, as one drive must be master, the other the slave. Even this depends on where you live, as many European models use a third position - CS (chip select) - which is rarely used in the US.
I noticed some other symptoms (I left DVD broken since I didn't need it at the time and now I need it so the problem comes back).
1. When that long recognition occurs, a HDD led is on (constant, no blinking).
2. After about 15 min DVD is recognized (I see it's label in explorer and can view DVD properties in a device manager).
3. I tried to copy a file from DVD. The OS (Win 7 Pro) almost hung - every operation was taking much time, even though I have Quad processor. In a task manager, I noticed that one of cores is 100% utilized by kernel (a red indicator). Transfer was ~1,5 MB/s, which is unaccteprable for 5 GB file
4. Both explorer and device manager show a not existing CD drive (not DVD).
Is it possible that computer thinks that there is CD drive and it is a "master" and it slowes down everything (it read about it here[^], the last issue, on the bottom of the table?
Greetings - Jacek
|
|
|
|
|
Hi to All,
I wanted some information or idea on protocol analyzer (Bus analyzer)....
Can anyone please give me a brief idea on Bus Analyser...
I want to know what is it and how it works..like (I have read that bus analyzer comes with a hw and sw....now how anyone connects it..to USB?..and how we can analyze)
One small example would be very very great...
Thanks in advance.
-----------------------------
I am a beginner
|
|
|
|
|
Did you even bother to type "USB bus analyzer[^]" into Google or Yahoo before posting such a basic question?
|
|
|
|
|
No actually I tried...But it shows different vendors or software available for that.....I have not got any generic explanation for it...like how it works and what it does...
-----------------------------
I am a beginner
|
|
|
|
|
That's where you go to the vendor web sites and read documentation on these things so you get a better idea of what you're looking at.
|
|
|
|
|
A protocol analyzer sits either in the middle of a connection, passing data through, or TEE-d into the connection.
In general terms there is either a hardware/software component (newer), or a hardware stand alone system (older). Some systems can be said to be software only (e.g. TCP/IP, USB), but since that puts the computer in the middle, there is still a hardware component requirement (i.e multiple ports, etc).
You can get them for RS-232, RS-485, USB, I2C, etc, pretty much any type of data stream.
They sit on the desired communication bus, and provide knowledge of data, and depending on the type of communications, the control signals/data as well.
They are used to monitor, or debug communications between systems.
The other analyzer that might be what your thinking of for bus monitoring is a Logic State Analyzer or LSA. That involves individual or bus connections to monitor logic levels (i.e. tapping into the DMA bus of a computer, and monitoring the data flow. Two different things for different needs, the LSA is far more into the hardware of the beast, while the Protocol analyzer sits between the beasts.
Neither are complicated to use, just complicated to really understand and analyze what you are getting back from them.
For a better explanation, try http://en.wikipedia.org/wiki/Bus_analyzer[^].
Hope that helps a bit, although the other reply thread does have a point, but hey, it's Christmas.
|
|
|
|
|
hrishiS wrote: I am a beginner
Yep, I guess you are.
If you really want to play, then you hook the HW part of the analyser up to the bus, then you connect the analyser to another PC (normally) which has their SW on it, to capture the bus data for analysis.
And a USB analyser is really, really painfull to analyse,. At a bus level the USB protocol is painfull.
Morality is indistinguishable from social proscription
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
