Jump to content

raw1000

Members
  • Posts

    3
  • Joined

  • Last visited

raw1000's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. In response to your questions I have an ASUS Rampage IV Extreme m.b. with the latest UEFI BIOS (ver 3504), a Koutech IO-RCM620 USB 2.0 3.5" Card Reader, and running Win 7 Pro. 64-bit - all updates. No other software (including the OS) has ever had problems seeing the card reader slots. It is too awkward to populate all readre slots just to appease your program because I'm not about to purchase a Sony mem stick or a microdrive. I do have an SD and xD which cuts the number of error messages down to six. But that's six times every ime I edit or add an item to any panel type. THX
  2. Also in addition to my comment above ... the error occurrs also when you try to modify ANY item in one of the OSD, Gadget, LCD or Sensor panels. This happens on each item you add or modify - regardless of whether it is a "drive" item or not. Waiting for an answer or hopefully a fix ???
  3. Regarding the same error message mentioned above ... I'm a 2nd level computer support person/programmer and would like to buy the engineer license to use for my client's systems. However, I don't have much faith in the product if you can't fix a simple bug like bypassing volume checks on empty card reader slots. I was using the trial version and had to click on "cancel" twelve times for each item I wanted to add to the OSD, Gadget, LCD or Sensor panels. It is clearly caused by my four empty card-reader slots. This is happening because your programmers have put the volume (or drive) check at the entry to the panel setup screens instead of at the addition of a specific drive item where it belongs. That way it would only popup an error if you were trying to add a drive that was actually empty. I'm waiting to see if this can be fixed before I spend $149. I'm sure a lot of other users have card readers and the same issue but are too complacent to bother trying to get a fix. It should be fairly simple to bypass USB drive types which is how card-readers are attached. Or just move the calls in the code to check the volume/drive when a user is adding a drive to a panel. So where do you stand on this issue???
×
×
  • Create New...