Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About gregglee

  • Rank

Profile Information

  • Gender
  1. I have the same problem with many mb sensors disappeared. FWIW my installed 5.60.3700 has kerneld.v64 but not kerneld.x64 So I was going to try the beta. I downloaded 5.60.3776 but what I got was not an executable installer, but rather a zipped file that contains what resembles, but is not the same file by file, the files of installed 5.60.3700. What is the correct install procedure for the beta? Copy some of the files to the installed version?
  2. I realize the problem is likely the enclosure, but for the database: All above is using esata connection. I tried connecting by usb3 rather than esata. In this configuration windows did indicate a driver being installed, and the enclosure appears as a "USB mass storage device" separate from the two hdd devices. hdd reporting is similar to esata connected, but even less for the second drive. For example in Windows Device Manager and on some aida64 pages, it is identified only as "hard drive" rather than by name. In aida64 SMART page it does not appear on the drive list at all.
  3. I got an email back from Vantec confirming that the controller chipsets are JMicron JMS539A (USB3) + JMB391 (esata). Specs listed here http://www.jmicron.com/Product_list.htm My motherboard esata controller is JMB361 (with most recent driver) so I guess everything is about as compatable as it could be.
  4. SSD temp is now reported. One quirk: The first time I started AIDA64 after instaling the beta, it added the SSD temperature to OSD alreadfy selected and placed it just above the hdd temps. I had customized the OSD order and selections so no reason to expect that it would do this. I had also use "configure" to customize to shorter hdd labels in OSD. When the ssd was added, the ssd temp in OSD copied a label from one hdd and all the custom hdd labels were scrambled. Same labels that I used, but on the wrong drives. After re-edit they do stay put. There is now a pop u
  5. That message sounds like it came from a windows application, even if though it was displayed in the boottime script. So something from ASUS still seems to be running. Could be part of chiset driver installation and should be there, but I have found that ASUS optional s/w like AI suite, pc probe, etc. do not unistall completly with normal unnistall. Drivers, autoruns, etc along with many registry entries can remain. Look in program files9x86) to see what's in ASUS folder Or just search C: drive for ":ASUS." The ASUS\AASP\x.xx.xx folder that includes aacenter.exe and asloader.e
  6. In a newegg "feedback" for this drive I found a review that said: "It uses the JMicron JMS539 USB 3.0 chipset... The eSATA chipset is JMicron JMB391. He didn't say how he learned this. Another newegg reviewer using all four trays said that 3 of 4 drives were read.. On the other hand I got a reply from Vantec support after my first post here that says: "It will read the first drive and the rest is block by the chipset that control the SATA drive."
  7. No driver install. Instructions said that Windows 7 would take care of it. But I didn't see any evidence that a driver was actually installed No "device is ready for use" message for example. The enclosure doesn't seem to appear as a listed device. Chip. I could not find it listed on Vantec web site, and so far no where else.
  8. Please note that since my original post, I moved two hdds to new external enclsure and lost SMART and temp on one. Probably not the same issue as this but it is contained in this debug dump. I posted the new enclosure isuue separately a few minutes ago. ------[ AIDA64 v2.80.2300 ]------ ------[ Microsoft Windows 7 Home Premium 6.1.7601.18044 Service Pack 1 (64-bit) ]------ ------[ Motherboard Info ]------ Motherboard ID : 64-2001-000001-00101111-030811-ATHLON64$A1585000_BIOS DATE: 03/08/11 10:42:32 VER: 08.00.15 Motherboard Model : Asus M4A87TD Evo Motherboard Chipset : AMD
  9. I previously had two hdds in separate external enclosures (one esata and one usb3). All readings including SMART and temperature have been reported by AIDA64. I moved both drives to one four drive enclosure connected by esata. Other two trays are empty. The enclosure is a VANTEC NexStar HX4 NST-640SU3. Everything works, but AIDA64 reports SMART and temperature for only one of the two drives. Temperature is just not there at all. Under storage/smart the name of both drives appears, but SMART is blank and gray.for one. If I reverse the positions in the enclosure, no SMART or temp cha
  10. SSD SMART is visible. I enabled the RAID preferences anyway to check. No change. No RAID on system anyway . System is AMD not Intel. Has all lastest drivers, other than those that appear to be just to add Windows 8. I'm running windows 7-64. The beta download is an executable, not an installer so I ran it from download folder. No difference on SSD temp reading - none at all.
  11. I have a Corsair Neutron GTX 240 SSD. AIDA64 most recent version detects and reports data for SSD wherever AIDA64 detects hdds except that no temperature is reported by Computer / Sensor or by OSD or by Stability Test. Nothing else is missing as far as I can tell. To be precise: there is no sensor identified for ssd temperature, as opposed to havng an identified sensor but no reading. SSD is connected direct to mb sata plug and is the system drive, letter c:/. Speedfan and Cpuid HW Monitor do report temperature for the SSD.
  12. After I removed a logical drive (a hdd partiton) designated G, the OSD continued to display a reading for G utilization of 0%. I had forgotten to uncheck it in OSD configuration before I removed it. I don't think OSD is supposed to display a sensor that does not exist on the system. When I opened OSD configuration to remove it, it did not appear, so I could not uncheck it. If it does display a sensor, it should also be on config list. There is a workaround: I connected a flash drive, changed its letter to G in windows disk management, then started aida64. Now the G reading app
  • Create New...