Jump to content

Praz

Members
  • Posts

    40
  • Joined

  • Last visited

Posts posted by Praz

  1. Hi Fiery

     

    Mass storage mode shows 00 00. Mini monitor mode also shows 00 00. However as the DPF is only seen for a few seconds when in mini monitor mode I'm not real sure this Registry value is correct.

     

    The Device ID is 04E8-2033 when in mass storage mode. I haven't been able to get the info from AIDA64 quick enough once switched to mini monitor mode. I am able to acces the DPF properties in Device Manager and it shows 04E8-2034 for mini monitor mode as shown below.

     

    I am not able to kill sam_controller.exe as it is not shown in Task Manager. Perhaps this is because the install does not finish? I have performed an uninstall of Samsung Frame Manager but the results are the same.

     

    I have also tried what you stated in PM with the results being the same. AIDA64 initializes the DPF, a blue screen showing AIDA64 is displayed for approximately 5 seconds, the Windows USB disconnect sound is played and the DPF disappears from the system. After successfully installing the driver when AIDA first initializes the DPF I can close AIDA64, manually switch the DPF to mini monitor mode and the same disappearance after 5 seconds occurs. This seems to point to an issue with the Samsung driver itself and not something amiss with AIDA64.

    post-47-0-82791400-1408280486_thumb.jpg

  2. Hi Fiery

     

    I have been messing with the SPF-87H DPF for the last couple of day but unfortunately have nothing positive to report. I have tested on multiple system with both Win7 and Win8. Following the steps you wrote above AIDA64 will initialize the PDF only if it is in mass storage mode first. If already in mini monitor mode AIDA64 reports "SPF error: USB device not found". After launching AIDA64 the PDF switches to mini monitor mode and displays data from AIDA64 for approximately 5 seconds. Then the PDF disappears from the system and is not shown anywhere including Device Manager. Closing AIDA64, changing the PDF back to mass storage mode, and restarting AIDA64 shows "SPF Init OK" but the PDF screen does not switch from the default info view and no data is displayed from AIDA64. The system must be rebooted for the 5 seconds of displayed info to be shown again.

  3. This is weird. Even searching for that display from the page you linked to shows no results. Doesn't make sense when I'm at the page where the display is listed.

     

    Both displays are the Crystalfontz 634 serial version. They are probably 8 - 10 years old. I forget I had them till going through a bunch of stuff not long ago. I have one display per computer (Win8.1) connected with a FTDI based USB to serial cable. I'm using CrystalControl2 and accessing the AIDA64 data using WMI.

  4. Hi Fiery

     

    Thank for all the detailed info. AX206 displays seem hard to locate here in the States. As the GOverlay display cost very little money I'll probably pick one up to use for now. I'll keep looking for a AX206 display or possibly when you have the Matrix Orbital GTT coding done pick up one of them. Do you anticipate AIDA64 working with all the differnt size GTT displays?

  5. Hello Fiery

     

    Is direct support of the display linked below possible? If a USB dump or other info is needed I will purchase this disaply in order to provide the necessary info if support may be possible.

     

    http://coldtearselectronics.wikispaces.com/LCDsysinfo+For+GOverlay+-+Powerful+Info+Gadget+for+gamers

     

    Thanks

     

    Edit: Below is sample code for controlling the LCD.

     

     

    Custom Usage:
    The LCD can be customly controlled by using
    USB control packets using default control
    endpoint (no bulk or interrupt endpoint). Therefore, using the below library, user can create
    their own applications to control the LCD in Linux and Windows environment.
    Controlling the LCD using Python in Linux
    Please visit Github for library
    using Python by Dan Gardner
    https://github.com/dang
    ardner/pylcdsysinfo
    Controlling the LCD using C# library.

    * LCDDrive.Startup();
    * Load LIBUSB Driver. If device is detected, nothing will return. If no device, will display error message.
    * Need to be called in when the application start.
    *
    * LCDDrive.turn_off_dimLCD_during_idle();
    * By default, LCD will turn to idle mode(dim
    the LCD) if no command is send to LCD within 10secs.
    * Running this function will disable this feature
    *
    * LCDDrive.turn_on_dimLCD_during_idle();
    * Enable back the above feature
    *
    * LCDDrive.ChangeLCDBrightness(int value)
    * Change the brightness of LCD immediately (v
    alue must be >0 and <255) 0=shutoff 255=brightness (Does
    not save to device) for example: LCDDrive.Change
    LCDBrightness(255): Set to brightness immediately.
    *
    * LCDDrive.SaveBrightnessvaluetodevice(int off_value, int on_value)
    * Save the brightness value of LCD to device. off_value and on_value must be >0 and <255
    * for example: LCDDrive.SaveBrightnessvaluetodevice(0, 255): Set the device to turn off the LCD during idle
    and turn to max brightness when working.
    *
    * LCDDrive.Clear_lines(bool line1, bool line2, bool line3, bool line4, bool line5, bool line6, int colour)
    * Clear the lines of the LCD. Because Clear line ta
    kes time, sleep the thread for sometime before issuing next
    command
    * set line1-line6 to true to clear the lines, otherwise set to false to retain the line
    * Color Value (integer value) This can
    be a 16bit colour value in RRRRRGGGGGGGBBBBB Format
    * or use the present value in ColourValue_16bit enum
    * for example: LCDDrive.Clear_lines(true, true
    , true, true, true, false, (int)ColorValue_16bit.Purple);
    * This will clear the top5 line and retain the last line, the line will be cleared to Purple colour.
    *
    * LCDDrive.Display_icon_on_grid(int position, int icon_number)

     

  6. Thanks for the quick reply. Two more questions if I may. No data is written to the drive for the read tests? And the data that is written to the drive is it random in nature or compressible such as all zeros?

    On an SSD the Buffered Write test, although writing to the first sectors at the operating system level, would be spread out across the NAND by the drive's controller. so overall the effect of excessive writes to the SSD would be no greater then the other write tests.

    Thanks again

×
×
  • Create New...