Closed GoogleCodeExporter closed 8 years ago
Could you be more specific about how to reproduce the issues? I've started
developing on Vista specifically to be able to see these sort of issues, but so
far
have not run into any on my own.
Original comment by brian.to...@gmail.com
on 24 Mar 2009 at 9:16
Surely
Wireless Monitor:
Apparently the inf protocol will not install in Vista, therefore monitoring of
wireless strength and/or transmission is impossible.
Vista 32 and 64 will not allow the installation of unsigned drivers, and there
is the
possibility that the wrong "something" may be accessed by the driver even if it
did
install. I have followed directions exactly to no avail. The inf simply will not
install as a protocol on my system.
================================================================================
===
Although I maybe far off base the following may help as I am doing what little
research I can (again this maybe way off base):
If you are running Vista or Windows 7.
What I am finding is that the INF will not install.
According to my research this is due to one of two problems if not both.
1.) the Driver is not digitally signed, therefore vista will not install the
driver
by default.
2.) the driver is utilizing older variable protocols and is no longer relevant
in the
new OS environment.
The current INF is attempting to access the following:
HKR,"Ndi\Interfaces","LowerRange",,"ndis5,ndis4,ndis5_uio" (INF Excerpt)
In Windows XP Pro and older this is correct, but in the new OS environment it
should
be accessing the "ndis6"
Unfortunately, I am no programmer, and do not understand how to modify the old
drivers to access this new protocol.
================================================================================
=
The second issue is with system temperature readings.
I have the appropriate processor (T3200 Intel), and the temp can be read by
numerous
other softwares with similar protocols to refer to.
But under Vista 32 and 64, the temp configs will not work with the current dll.
I have gotten the temp to work through linking to other software (Speedfan,
MBM5,
etc) but these require a third party software intervention. ie. another program
must
be running.
================================================================================
====
Third currently known issue.
Now this may be a vista thing, and I am just barely beginning to explore the
possibilities as to why, but if you utilize a measure disk config, you can only
get
readings for installed harddrives.
In windows XP I can get measurements on my DVD Players, external harddrives,
even
have a remote to measure my NAS, and Thumbdrives & flashcards.
In vista 32 and 64, I can only get measurements on internal harddrives,
apparently
all external storage measurements have been cut off.
================================================================================
===
This is what I am currently having issues with, I hope the further explanations
assist.
If you require more, do not hesitate to ask.
I am also attempting to see if I can get some volunteers from Donationcoder.com
to
step up.
Also i have been posting this new Rainmeter development site, anywhere there is
a
question.
Apologies in advance for any problems this may cause in the future.
Original comment by evmckay
on 25 Mar 2009 at 7:06
Also I can recreate the situations, and attach step-byp-step visuals if you
require.
Let me know
Thanks again
Original comment by evmckay
on 25 Mar 2009 at 7:08
The wifi issue should be solved now. The temperature measuring plugin is still
missing.
Original comment by kimmo.pekkola
on 19 Aug 2009 at 6:12
I have put out a call for a temperature dll build. We are facing a few issues in
regards to this, the main one being the utilization of drivers in 2nd and 3rd
generation system monitors, but our research is currently in an initial phase.
I will keep the issues updated as they are presented.
Original comment by evmckay
on 19 Aug 2009 at 6:29
Use CoreTemp.dll, SpeedFanPlugin.dll, or OpenHardwareMonitor.dll.
Original comment by birunthan.mohanathas
on 10 Jul 2011 at 9:12
Original issue reported on code.google.com by
evmckay
on 15 Mar 2009 at 8:42