pbcopter
-
Posts
77 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by pbcopter
-
-
It seems that the Battery Power and Battery input/output parameters are missing now from the latest beta build 1847
-
Hi Fiery,
It appears that the latest update 2.00.1740 beta has fixed this problem.
Thank you for your efforts.
Paul
-
Any updates on this issue?
-
I have found that this will occur when any internal drive is removed as well. For example, if the drive is disable in the Device manager.
If I uncheck Low-level SMART operations, the crash does not occur.
-
I eject it from the System Tray.
It happens with both USB and eSATA hard drives.
It does not happen with USB thumb drives.
-
I am using the latest beta version of AIDA64 Extreme build 1720 (although I have tested it with previous versions as well).
When I safely remove a portable drive, AIDA64 crashes with the following error.
Exception EStringListError in module aida64.exe at 000257C2.
List index out of bounds (8).
I am using the sensor panel.
I am running Windows 7 x64 Ultimate.
-
Would it be possible to add an Import/Export function to SideBar items
similar to what is now available for LCD Items?
Actually this would be desirable for all customizations in AIDA64.
Thank you.
Paul
Edit: I decided to try the new sensor bar instead of the Sidebar. It has import/export and looks nicer.
-
Thank you Fiery,
This version works fine.
I had to redo my LCD display since I could not find export/import on the older releases but not a big deal.
Thanks again.
Paul
-
Will do and thanks.
Paul
-
Please try to downgrade to AIDA64 Beta Build 1462, and let me know if it works flawlessly or has the same issue.
Thanks,
Fiery
Build 1462 works flawlessly.
-
AIDA64 Extreme 1.80 build 1469 beta shows error when Enable Logitech keyboard support is checked in perferences.
In fact, nothing happens for a few seconds when I try to check the box, then I get I/O error 53.
These two errors are logged in the event viewer.
Faulting application name: aida64.exe, version: 1.80.1469.0, time stamp: 0x2a425e19
Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58
Exception code: 0xc0000025
Fault offset: 0x00090788
Faulting process id: 0xef4
Faulting application start time: 0x01cc3b58a8d7170a
Faulting application path: G:\Programs\aida64extreme_build_1469_s2elk8yzgn\aida64.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: f0754f79-a74b-11e0-a5c5-001fd09a6b5e
Faulting application name: aida64.exe, version: 1.80.1469.0, time stamp: 0x2a425e19
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7bafa
Exception code: 0x0eedfade
Fault offset: 0x0000b727
Faulting process id: 0xef4
Faulting application start time: 0x01cc3b58a8d7170a
Faulting application path: G:\Programs\aida64extreme_build_1469_s2elk8yzgn\aida64.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: edd3e6cd-a74b-11e0-a5c5-001fd09a6b5e
After I press OK for the I/O error, the box for Enable Logitech keyboard support becomes checked.
I then select Apply and okay and no Logitech LCD support is available.
On the next AIDA64 startup, I cannot enter preferences. I get I/O error 53.
Any suggestions?
-
10.5.0.1026 is the latest, also self signed.
-
You're welcome, anytime.
Paul
-
Hi Fiery,
It appears that build 1257 fixes the problem with the eSATA drives.
Thank you for your efforts.
Paul
-
It works fine with a USB hard drive (WD Passport type)
Thank you.
Paul
-
Yes, I kept it running.
I'll check it with a USB drive.
Thank you,
Paul
BTW, my father was born in Budapest of course that was in 1923.
-
I tried to attach the three files but the system indicates they are too large
Used 493.17K of your 500K global upload quota (Max. single file size: 6.83K)
Edit: I deleted some previous attachements
Also, what do you mean by "running all the way"?
-
Hi Fiery,
I installed build 1255 and it works much better.
I reconfigured all my hard drive labels.
When I install a USB flash drive (no temp sensor), some of the labels disappear for a short time and then return to normal (all associations correct)
When I install an eSATA drive or USB hard drive that have temperature sensors, some of the labels disappear for the same short time and return with the label associations incorrect.
However, when I remove the eSATA drive or USB hard drive, all the label asociations return to normal.
I am nolonger required to restart AIDA64 to restore the associations as before.
It seems that when a new drive, with a temp sensor, is installed it is numbered during detection and that alters the numbers of the other drives.
Thank you,
Paul
-
Fiery,
Thank you for the response. I am sorry I have been unable to answer sooner.
It appears that update 1241 and beyond has fixed the HD temps disappearing from the sensor menu.
It is much more stable now.
However, the Vista sidebar still acts unpredicatably.
If I list all the drives in the side bar with the default labels and I add a drive, USB, etc. the drives associated with the labels will change, that
is, they are the wrong drive with each label.
When I remove the drive, they remain with the wrong drive/associated label.
I must restart AIDA64 to get the correct label/drive association back.
Any suggestions?
Thank you.
Paul
-
@Paul B,
Thanks for the for the response. Yes, I hope that a solution can be found because I like the feature also.
BTW, I'm Paul B also hence my username pbcopter.
-
I have discovered that if I connect an external USB drive to my system, the RAID drives will disappear immediately from AIDA64.
-
No, I don't use HWMonitor. Does that program cause this type of problem?
-
Attached is the information you requested after the disappearance of the RAID drives plus I added both the sensor page and sidebar under normal conditions.
I hope this helps.
Thank you again.
Paul
-
Will do.
Thanks
Paul
APC UPS battery voltage and power draw measurement
in Hardware monitoring
Posted
Thanks Fiery,
Paul