|
Are devices (storage devices) that have multiple path I/O avialable for Home use What I mean is in price etc.....
|
|
|
|
|
I try to get them use WMI, but in WMI the Win32_TemperatureProbe's CurrentreadingThe property's presence is reserved for future use.
I find somebody get the cpu and mainboard’temperature us acpi.
how to get the temperature?
|
|
|
|
|
Never use WMI!!! For work with hardware or other devices that are always different on different computers, you need knowledge in Assembler and C++. To get information from sensors you should at first: determine physical address of sensors, then use I\O to read information, this is formula of universal programm that read CPU and mainboard temperature on any computer where sensors installed of course!!!. For me it is impossible to reach how to do it. I know how to do this by theory, I have much search in google and MSDN but my results aren't good.
If somebody knows how to do it, please write some examples.
|
|
|
|
|
I've been working on a microcontroller project that routinely dumps status and debug information out its serial port. It always does this, regardless of whether or not anything is listening or even connected to the port.
If I boot my PC while it's connected to this thing, Windows XP often interprets the status and debug messages as mousespeak, installs a serial mouse driver, and then tries to interpret subsequent messages as if they were coming from a mouse. This results in occasional wild cursor movements and random mouse click events, as though some spastic ghost was trying to operate the mouse.
I can effectively kill the spastic ghost by uninstalling the serial mouse driver after XP has booted, but the problem comes back the next time I boot the machine.
If I disable the serial mouse driver instead of uninstalling it, the problem goes away and stays away, even after I boot again. This would be a fine solution if it was for just me, but I want to deploy this system to customers, and it would not look good at all to try to explain all this to them and to have them dinking around with mouse drivers.
I discovered (by Googling) that Windows supports a /NOSERIALMICE option within the BOOT.INI file that's supposed to prevent it from automatically detecting serial mice. I tried this option and it didn't work.
A second round of Googling revealed that /NOSERIALMICE was for Windows NT and that it's been replaced in Windows XP with the /FASTDETECT option. Unfortunately, /FASTDETECT didn't work for me, either. (In fact, it was already present in the BOOT.INI file when I started all this.)
Apparently this is not an uncommon problem. For example, quite a few links from Google described similar behavior when booting a Windows computer while it's connected to a talkative GPS device. These same links recommended /NOSERIALMICE or /FASTDETECT as the solution, but they don't seem to have any effect for me.
Can anyone suggest a different way to solve this problem? Or perhaps a hint about what I might be doing wrong with /NOSERIALMICE or /FASTDETECT?
Thanks,
rmac
|
|
|
|
|
|
Randor wrote: You did not mention if you added the COM port to the boot switch. /FASTDETECT:[PORT #]
No. I didn't try specifying the COM port. All the documentation that I found (including the link you gave) said that if you don't specify a COM port, it turns off the serial mouse detection on all COM ports. It's easy enough to try, though. I'll do so and report back.
Thanks,
-- rmac
|
|
|
|
|
I have tried it now both ways -- with and without specifying the COM port explicitly. Either way, Windows XP installs the serial mouse driver and then acts goofy as a result because there really isn't a serial mouse out there. It's as if the /FASTDETECT switch doesn't work, or isn't recognized, or perhaps that Windows isn't even looking at my BOOT.INI file???
Thanks for any more hints you might have.
-- rmac
|
|
|
|
|
The /FASTDETECT switch is there only for backwards compatibility with WinNT. Your problem starts when the shell hardware detection service finds the new "Mouse".
Disabling the shell hardware detection service is a bit rough as a solution though, as it will stop all hardware detection.
In the workaround section of this[^] article there is some info on how to stop the enumeration of comports. I haven't tried it myself though.
|
|
|
|
|
Good news. After a bit more Googling, I did find a way from Microsoft that works for me to turn off automatic detection by Windows of devices connected to the COM ports. As with many similar articles, this one cites a talkative GPS device as a typical example of why this sort of thing is needed sometimes.
The referenced page notes that the situation can get even more complicated if a USB-to-serial adapter is involved, because it might incorrectly detect and try to emulate a serial mouse instead of a serial port. Since that's beyond the control of Windows, the Microsoft fix won't work and you would then be trying to sort out problems with the adapter along with everything else.
-- rmac
|
|
|
|
|
Hello guys .
Provided I know Pid and Vid of a device (say a scanner or printer).
How I am going to get the plug'n play instance (ie, the find new hardware popup when the device is actually conneted) . Is there any way to initiate it through a VB.Net appliation.
I mean Ineed to get the plug'n play instance without actually connecting the hardware device.
please give some ideas or suggesstions.
|
|
|
|
|
Unless there is a hidden API to the PnP no, you cannot add data to the enum sectin of the registry (where all the HW IDs are stored).
Not only that, this section is owned by the system, so even admins cant delete it directly.
Morality is indistinguishable from social proscription
|
|
|
|
|
Ok thanks a lot ........... so theres no way to initiate an artificial pnp instance. I need to think a bit differently.
BTW could you please explain what do u mean by 'hidden API to the PnP'.
|
|
|
|
|
He meant unless there's a way to get at the pnp that's not documented or intended for public consumption. The real risk with trying to program to a nonppublic API even if you can find one by reverse engineering the code is that there's no promise it won't be changed by the next OS/Service pack/Windows update patch. Public APIs are guaranteed to remain constant. Non public ones can be changed at any point.
You know, every time I tried to win a bar-bet about being able to count to 1000 using my fingers I always got punched out when I reached 4....
-- El Corazon
|
|
|
|
|
how i can get system hardware information ( such as installed memory, cpu model, optical drives,...) with assembly(masm), without dos interupts(just bios ints)?
and
how i can use amd show ps/2 mouse in bios mode by in,out (without int 33)
|
|
|
|
|
|
Hi all,
My PC has Intel DG33FB MotherBoard and core 2 duo Processor 2.53GHz with 2GB transcend RAM.
I have installed XP in my system. Later i installed windows 2003 server as 2nd OS. My problem is for Windows 2003 server the graphics and audio driver are not getting installed. Can anyone help me in this regard
Regards
sunil
|
|
|
|
|
|
Hi everyone,
I got these errors at Event Viewver and I must be wait about 3 or 4 minutes for loading Windows
"The driver detected a controller error on \Device\Harddisk0\D."
"A parity error was detected on \Device\Ide\IdePort0."
"An error was detected on device \Device\Harddisk0\D during a paging operation."
I searched on the internet and saw people had this problem but I couldnt find any helpful answer for myself I scaned my harddisk with some tools and they didnt find any problem on the harddisk this problem is very wonderful for me for example when I turn on my computer and after boot up and loading windows I see that windows cant detect my graphic card and when I want to install graphic driver it hangs.
Harddisk is Western digital(500GB) and Motherboard P35-DS3R and graphic Leadteck 8600GTS and OS xp2(I saw these errors on other windows)
|
|
|
|
|
The most common cause of this problem is using a 40-way cable on an ATA-66 (or faster) parallel ATA drive. These drives require an 80-way cable (every other wire being a ground wire) to run at the highest speeds.
To prevent the problem Windows drops the bus speed further and further down and eventually reverts to Programmed I/O, which is incredibly slow. This generally causes timeouts when doing I/O.
New Serial ATA wiring does not have this problem, but Windows treats any disk error on an ATA-compatible drive in the same way if using the standard ATA driver (atapi.sys/pciide.sys).
Check that the cable is the correct type, is not damaged and is correctly installed. Also check that it's relatively short, just long enough to reach between the controller and disk. If you can, swap the cable with a known good one.
If you still have problems the disk or motherboard may be faulty.
Another source of problems that can manifest in many different ways is component overheating, due to inadequate ventilation or blocked ventilation holes. It's common to get a build-up of dust in fans and other confined spaces.
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
|
Thanks Mike for your transparent answer does graphic card culprit for this problem or vista 64Bit (I bought this computer 3 or 4 months ago but I have this error of 1 months ago) So you think this problem is of hardware and not sotftware,right?
|
|
|
|
|
I dont get this error repeated I get this error when I want to run a program or when I want to sacan my harddisk with Anivirus I get this error on the XP pack2 on the XP pack1 when I want to uninstall a program or delete some files my computer is freezed but on the Vista I can delete files.
And another question do you have any idea about graphic driver that windows shows me this device has problem but when I restart it,it doesnt show any problem
|
|
|
|
|
I'm currently struggling with writing a simple UMDF driver for USB Device Firmware Upgrade (DFU) to be used on WinXP.
I've used the final stage of the OSR USB Fx2 sample as starting point, but removed the read/write queue since the communication is done on ep0 solely.
It builds fine.
When I power up my device and try to install the driver it fails to start the driver and complains about a missing file (error code 10).
I fired up the Dependency Walker and it tells me that it cannot find DwmApi.dll.
I've tried to build with the build environment for both Vista and XP but the result stays the same.
What I've gathered from reading forums and such is that the DmwApi library is not used on XP platform and is designed for Vista. The problem "may be fixed from repairing the .NET installation" and I've tried this, but with the same result.
If I use the WdfVerifier and configure it to break when the WdfHost process starts, it fails and tells me that a file is missing. I suppose it's the same file, DwmApi.dll.
My question is simply "where did I screw up"...
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown
|
|
|
|
|
With Dependency Walker you have to differentiate between delay-loaded DLLs and static DLLs. Delay-loaded DLLs have an hourglass icon against them in the tree and module list; they're loaded when the first function in them is actually referenced. It's unlikely that DWMAPI.DLL is the problem, as it shouldn't be actually referenced by code running on XP.
In my case DWMAPI.DLL always shows up as missing when checking almost anything, because it's delay-loaded by IEFRAME.DLL if you've installed Internet Explorer 7 on Windows XP. In turn that's delay-loaded by MSHTML.DLL, which is delay-loaded by SHDOCVW.DLL, and that by SHELL32.DLL.
There will be some other DLL that isn't present.
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
|
Yep, I realized that the DwmApi lib is delay loaded.
On the other hand it was the only file I found to be missing. I guessed that it could not be this file, but thought "I don't know everything so it might be this file anyway".
Something has happened to my system, or I am making some kind of mistake, but neither my driver nor the UMDF example drivers will install correctly. Every single one fails to start with error code 10.
The most simple one is 'socketecho'. I have installed previously and even though it didn't work as I expected in overlapped mode, it installed and started as expected at that time. Now it doesn't start when I install it any longer.
I've tried to install the driver on other machines as well, but still with error code 10, so I guess it's related to the build tools and/or the .inf-file.
This is my first contact with WDF/UMDF and I haven't found very much help on the net. It seems like the framework isn't very well utilized. Even the forum on the MS Connect site contains about 10 posts from the last two years.
Any idea?
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
