Announcement

Collapse
No announcement yet.

Doo-Motion Installation in Pro-100

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Doo-Motion Installation in Pro-100

    I have tried to install doo-Motion on my lab Pro-100 several time now without success. The following list are some of the items I face. I have not been successful in finding any installation instructions and require a step by step to get this plug-in loaded.

    The know issues:
    1- Pro-100 C: drive is write protected, and all files that load to the C: drive dissapear when the pro-100 is rebooted.
    2- HS2Sentry restarts homeseer automatically which seems to not allow doo-motion to install properly.
    3- if doo-motion is installed on the C: drive then the database is cleared when pro-100 is rebooted.

    What I gave done to work around these issues...
    -reboot pro-100 to clear all memory
    -use updater to download download doo-motion
    -disable flash protection
    -reboot pro-100
    -see doo-motion install warning screen
    -stop process HS2Sentry
    -stop process homeseer.exe
    -stop all other homeseer related processes
    -perform doo-motion install process
    -install to D: application files only
    -reboot pro-100
    -enable flash protection
    -reboot pro-100
    -observer doo-motion enabled on interface screen
    -do not observe any way to config doo-motion
    -do not observe any way to launch doo-motion
    -observe log message (every minute)
    2/5/2006 9:41:49 AM DooMotion Error Unable to update DooMotion sensor device strings and timers (Error #424 on line 30 of EventTimer2_Timer - Object required)

    #2
    I am not entriely familiar with how software installation on the Pro-100 is handled. Is is possible to install a program outside of HS2? If so, install latest DooMotion from http://www.doosoft.com/downloads.php.

    If the separate install, then I will need to determine what needs to be done to get it to work with the Updater. If not, then there are more issues than the Updater functionality with the Pro-100 that I will need to deal with.
    Jim Doolittle

    My Twitter
    My Hardware & Software

    Comment


      #3
      Doo-motion Pro-100 Testing

      HS folks are making a change to accomodate the need to shutdown HS while a third party plug in updates. may want to coordinate with them.

      Pro-100 uses embedded XP and a write protected C: drive

      HS programs install on a flash D: drive (potential issue for large log files, may be good to be able to map where log files go)

      I installed a 1gb usb flash drive to move help and log files to.

      after ...
      shutting down the HS2Sentry program
      shutting down HS.exe and all child programs
      I clicked continue with doomotion installer
      doomotion appeared to install fine, but I see no way to launch or config the program

      I am familiar doomotion operating in HS1.7, but do not see any menu choices in HS2.0.

      Before I reload outside of Updater can you give me some pointers..
      Html to launch?
      Running processes...
      Config screens?

      I am very willing and happy to help with whatever you need, just let me know.

      Comment


        #4
        http://homeseerwebort/dmoptions for Options
        http://192.168.2.3:8080/dmsensors for adding and defining sensors

        As far as running processes, do you mean task manager processes? DooMotion is a .ocx plug-in so it will be hidden within the hs-compatibility.exe process.
        Jim Doolittle

        My Twitter
        My Hardware & Software

        Comment


          #5
          We have not tried DOOMotion on the PRO 100, it is possible that there may be some system files that are required and are missing. You should the DOOMotion plugin on the interfaces page. Did you enable it there? If so, any errors in the log? If it initialized ok, you should have a DOOMotion menu item on the log screen.
          website | buy now | support | youtube

          Comment


            #6
            NNilsen,

            I read your post and you mention that the C: drive is protected and you tried installing to C: but that didn't work because the files were removed upon reboot. You then tried installing to D:. Is this correct?

            DooMotion (as well as most other plug-ins) require that Config, DATA, and HTML files be in the same folder as HS:
            • hspi_doomotion.ini configuration file in HomeSeer 2\Config
            • Data files in HomeSeer 2\DATA\DooMotion\
            • Images in HomeSeer 2\html\Images\DooMotion
            • Couple of documents in HomeSeer 2\Docs
            • Uninstaller in HomeSeer 2\BIN\DooMotion
            As far as system files, MDAC 2.8+ and VBSCript 5.6+ are needed Microsoft installations that are on 99% of systems. The rest of the needed system files should be included within my installer.
            Jim Doolittle

            My Twitter
            My Hardware & Software

            Comment


              #7
              NNilsen,

              Make sure you disable the flash protection before running his installer, since it sounds like he installs some system files that may not be present in the system folder on the C drive. MDAC and VBScript are already installed on that unit.
              website | buy now | support | youtube

              Comment


                #8
                Yes, as Rich pointed out, there are system files put in the system folder and if these are not installed and registered properly, DooMotion will complain with errors similar to those reported. This would happen regardless of whether the supporting files are in the correct location.
                Jim Doolittle

                My Twitter
                My Hardware & Software

                Comment


                  #9
                  Test Results

                  >> /dmhost and /dmsensors display page not found.
                  >>Doomotion found but never started
                  2/11/2006 9:39:23 PM ~!~Info~!~HomeSeer version is: 2.0.2041.0
                  2/11/2006 9:39:28 PM ~!~Startup~!~Checking for available plug-ins
                  2/11/2006 9:39:30 PM ~!~Info~!~Found plug-in: DooMotion, version: 2.0.0.57
                  06 9:39:37 PM ~!~Startup~!~Start remoting
                  2/11/2006 9:39:37 PM ~!~Startup~!~Start event processing

                  2/11/2006 9:39:44 PM ~!~Info~!~Speaker client connected from: 127.0.0.1
                  2/11/2006 9:39:45 PM ~!~Info~!~Web Server authorized local login successful from: 127.0.0.1 User: default

                  2/11/2006 9:41:11 PM ~!~Error~!~Web Server Error 404, cannot serve file: d:\program files\homeseer 2\html/dmoptions
                  2/11/2006 9:41:28 PM ~!~Error~!~Web Server Error 404, cannot serve file: d:\program files\homeseer 2\html/dmsensors

                  found - hspi_doomotion.ini configuration file in HomeSeer 2\Config
                  found - Data files in HomeSeer 2\DATA\DooMotion\
                  found - Images in HomeSeer 2\html\Images\DooMotion
                  found - Couple of documents in HomeSeer 2\Docs
                  found - Uninstaller in HomeSeer 2\BIN\DooMotion

                  3 devices ]1,]2,]3
                  ---------------------------
                  My Next Steps
                  -reboot pro-100 to clear all memory
                  -disable flash protection
                  -reboot pro-100
                  -use the Doomotion uninstaller
                  -use updater to download doomotion
                  -see doomotion install warning screen
                  -stop process HS2Sentry
                  -stop process homeseer.exe
                  -stop all other homeseer related processes
                  -perform doomotion install process
                  -install to D: application files only
                  -observe files writing to C:
                  -reboot pro-100
                  -enable flash protection
                  -reboot pro-100

                  ... and report back the results

                  Comment


                    #10
                    I look forward to the results (hopefully positive). FYI, the DooMotion installer will overinstall just fine. The uninstaller need only be run if you no longer wish to use DooMotion.
                    Jim Doolittle

                    My Twitter
                    My Hardware & Software

                    Comment


                      #11
                      Test Results 2006-02-12

                      I performed the following Steps:
                      -reboot pro-100 to clear all memory
                      -disable flash protection
                      -reboot pro-100
                      -use updater to download doomotion
                      -restart HS2
                      -use the Doomotion uninstaller
                      -see doomotion install warning screen
                      -open taskmgr
                      -end process HS2Sentry
                      -end process homeseer.exe
                      -end process speaker, mapi, mp9
                      -perform doomotion install process
                      -install to D:\program files\homeseer 2 application files only (no help)
                      -observe files writing to C: and to D:
                      -reboot pro-100 using shutdown -r -t 10
                      -enable flash protection
                      -reboot pro-100 using shutdown -r -t 10

                      OBSERVATIONS----------------------------------------
                      see trial version in setup config and listed as ok
                      /dmhost and /dmsensors display page not found.
                      see log error message posting every minute.

                      LOG----------------------------------------------------
                      2/12/2006 11:38:16 AM ~!~Start~!~************************************************* *******************
                      2/12/2006 11:38:16 AM ~!~Start~!~ HomeSeer version 2.0.2041.0 Starting Now
                      2/12/2006 11:38:16 AM ~!~Start~!~************************************************* *******************
                      2/12/2006 11:38:16 AM ~!~Start~!~
                      2/12/2006 11:38:18 AM ~!~Startup~!~Loading Settings
                      2/12/2006 11:38:18 AM ~!~Warning~!~HomeSeer was not shut down successfully the previous time it was started.
                      2/12/2006 11:38:28 AM ~!~Info~!~HomeSeer is performing database maintenance on nacnet.mdb
                      2/12/2006 11:38:30 AM ~!~Info~!~Database maintenance Completed Successfully.
                      2/12/2006 11:38:30 AM ~!~Startup~!~Settings Loaded.
                      2/12/2006 11:38:30 AM ~!~Startup~!~Loading configuration file ...
                      2/12/2006 11:38:30 AM ~!~Info~!~Loading device types file...
                      2/12/2006 11:38:31 AM ~!~Database~!~Opening up HomeSeer database D:\Program Files\HomeSeer 2\Config\nacnet.mdb
                      2/12/2006 11:38:32 AM ~!~Info~!~Loading Devices...
                      2/12/2006 11:38:32 AM ~!~Load Config~!~17 total devices loaded.
                      2/12/2006 11:38:32 AM ~!~Load Config~!~Checking device type settings for all devices...
                      2/12/2006 11:38:32 AM ~!~Load Config~!~Finished checking device type settings.
                      2/12/2006 11:38:32 AM ~!~Load Config~!~Loading Events...
                      2/12/2006 11:38:33 AM ~!~Load Config~!~9 total events loaded.
                      2/12/2006 11:38:33 AM ~!~Info~!~Loading TV Timers...
                      2/12/2006 11:38:33 AM ~!~Database~!~HomeSeer configuration database D:\Program Files\HomeSeer 2\Config\nacnet.mdb has been closed.
                      2/12/2006 11:38:33 AM ~!~Info~!~HomeSeer version is: 2.0.2041.0
                      2/12/2006 11:38:33 AM ~!~Info~!~Initializing phone interface...
                      2/12/2006 11:38:34 AM ~!~Info~!~Adding phone line 1 Name: xxx-xxx-xxxx Modem: Way2Call Hi-Phone Desktop
                      2/12/2006 11:38:34 AM ~!~Info~!~Initializing Hi-Phone device...
                      2/12/2006 11:38:40 AM ~!~Startup~!~Checking for available plug-ins
                      2/12/2006 11:38:41 AM ~!~Info~!~Found plug-in: AC RF Processor, version: 1.1.0.11
                      2/12/2006 11:38:41 AM ~!~Info~!~Found plug-in: X10 CM11A/CM12U, version: 1.0.1.0
                      2/12/2006 11:38:42 AM ~!~Info~!~Found plug-in: DooMotion, version: 2.0.0.57
                      2/12/2006 11:38:43 AM ~!~Info~!~Found plug-in: Media Center, version: 2.0.0.2
                      2/12/2006 11:38:43 AM ~!~Info~!~Found plug-in: SmartHome PowerLinc USB, version: 1.0.0.7
                      2/12/2006 11:38:43 AM ~!~Info~!~Found plug-in: Power Monitor, version: 1.0.0.1
                      2/12/2006 11:38:44 AM ~!~Info~!~Found plug-in: Touchpad, version: 2.0.0.21
                      2/12/2006 11:38:44 AM ~!~Info~!~Found plug-in: Media Player, version: 2.0.0.7
                      2/12/2006 11:38:45 AM ~!~Startup~!~Restoring device status
                      2/12/2006 11:38:45 AM ~!~Startup~!~Initializing Plug-Ins
                      2/12/2006 11:38:45 AM ~!~Info~!~Initializing X10 Plug-in: SmartHome PowerLinc USB On USB
                      2/12/2006 11:38:45 AM ~!~Info~!~Initializing Plug-in: SmartHome PowerLinc USB
                      2/12/2006 11:38:45 AM ~!~Info~!~PowerLinc USB Plug-in, Version 1.0.7
                      2/12/2006 11:38:45 AM ~!~Startup~!~PowerLinc USB initialized successfully
                      2/12/2006 11:38:45 AM ~!~Info~!~Done initializing X10 interface SmartHome PowerLinc USB
                      2/12/2006 11:38:45 AM ~!~Startup~!~IR Label file (config\irlbl.cfg) missing or corrupt, creating new file
                      2/12/2006 11:38:45 AM ~!~Info~!~Done initializing infrared interface
                      2/12/2006 11:38:46 AM ~!~Info~!~Interface DooMotion is running as a trial, 17 days remaining.
                      2/12/2006 11:38:46 AM ~!~Info~!~Initializing Plug-in: DooMotion
                      2/12/2006 11:38:46 AM ~!~DooMotion startup~!~Register callback completed
                      2/12/2006 11:38:46 AM ~!~COM Plugin~!~Calling InitIO
                      2/12/2006 11:38:46 AM ~!~COM Plugin Info~!~DooMotion version is: 2.0.57
                      2/12/2006 11:38:46 AM ~!~DooMotion Info~!~Initializing DooMotion sensors...
                      2/12/2006 11:38:46 AM ~!~DooMotion Info~!~hspi_doomotion.chm file was not found. Help system will not be available.
                      2/12/2006 11:38:47 AM ~!~DooMotion Warning~!~If upgrading from a HomeSeer Version 1.X, shut down HomeSeer and make sure that the DATA/DooMotion folder and its contents have been copied to the program folder of the new HomeSeer version
                      2/12/2006 11:38:47 AM ~!~DooMotion Warning~!~Also copy hspi_doomotion.ini from HomeSeer Version 1.X config folder to HomeSeer 2 config folder
                      2/12/2006 11:38:47 AM ~!~DooMotion Info~!~Creating new sensor data file
                      2/12/2006 11:38:47 AM ~!~COM Plugin~!~InitIO error:
                      2/12/2006 11:38:47 AM ~!~COM Plugin Error~!~Error initializing Custom Interface: Unable to initialize sensors (Error #424 on line 40 of InitSensors - Object required)
                      2/12/2006 11:38:47 AM ~!~Error~!~Initializing interface: DooMotion->Unable to initialize sensors (Error #424 on line 40 of InitSensors - Object required)
                      2/12/2006 11:38:47 AM ~!~Info~!~Done initializing plug-in DooMotion
                      2/12/2006 11:38:47 AM ~!~Error~!~Unable to initialize interface AC RF Processor :Either no license or trial has expired
                      2/12/2006 11:38:47 AM ~!~Error~!~Initializing interface: AC RF Processor->Unable to initialize sensors (Error #424 on line 40 of InitSensors - Object required)
                      2/12/2006 11:38:47 AM ~!~Info~!~Done initializing plug-in AC RF Processor
                      2/12/2006 11:38:47 AM ~!~Info~!~Initializing Plug-in: Power Monitor
                      2/12/2006 11:38:47 AM ~!~Power Monitor Info~!~Power Monitor Plug-in Register callback complete
                      2/12/2006 11:38:47 AM ~!~COM Plugin~!~Calling InitIO
                      2/12/2006 11:38:47 AM ~!~COM Plugin Info~!~Power Monitor Initializing...
                      2/12/2006 11:38:49 AM ~!~Info~!~Done initializing plug-in Power Monitor
                      2/12/2006 11:38:50 AM ~!~Info~!~Initializing Plug-in: Media Player
                      2/12/2006 11:38:50 AM ~!~Info~!~Media Player plug-in version: 2.0.7
                      2/12/2006 11:38:50 AM ~!~COM Plugin~!~Calling InitIO
                      2/12/2006 11:38:50 AM ~!~COM Plugin Info~!~Media Player version: 2.0.7(c) 2002-2005 HomeSeer Technologies, LLC
                      2/12/2006 11:38:51 AM ~!~Info~!~Windows Media Player version: 9.0.0.3250
                      2/12/2006 11:38:52 AM ~!~Startup~!~Media Player foreground initialization completed
                      2/12/2006 11:38:52 AM ~!~Startup~!~Media Player background initialization started...
                      2/12/2006 11:38:52 AM ~!~Info~!~Done initializing plug-in Media Player
                      2/12/2006 11:38:52 AM ~!~Info~!~Initializing Plug-in: Media Center
                      2/12/2006 11:38:52 AM ~!~COM Plugin~!~Calling InitIO
                      2/12/2006 11:38:52 AM ~!~COM Plugin Info~!~Media Center Initializing...
                      2/12/2006 11:38:52 AM ~!~Media Center~!~Media Center 2.0.2 Configuration initializing.
                      2/12/2006 11:38:52 AM ~!~Media Center~!~Media Center Configuration completed.
                      2/12/2006 11:38:52 AM ~!~Info~!~Done initializing plug-in Media Center
                      2/12/2006 11:38:52 AM ~!~Info~!~Initializing Plug-in: Touchpad
                      2/12/2006 11:38:52 AM ~!~COM Plugin~!~Calling InitIO
                      2/12/2006 11:38:52 AM ~!~COM Plugin Info~!~Touchpad Initializing...
                      2/12/2006 11:38:52 AM ~!~Touchpad~!~Touchpad 2.0.21 starting.
                      2/12/2006 11:38:52 AM ~!~Startup~!~Touchpad is configured for HomeSeer 2.0
                      2/12/2006 11:38:52 AM ~!~Touchpad~!~Touchpad Configuration completed.
                      2/12/2006 11:38:52 AM ~!~Info~!~Done initializing plug-in Touchpad
                      2/12/2006 11:38:53 AM ~!~HSPhone~!~HomeSeer Phone Web Interface initializing.
                      2/12/2006 11:38:53 AM ~!~Info~!~Local IP address is: 192.168.1.9 (255.255.255.0)
                      2/12/2006 11:38:53 AM ~!~Info~!~Web Server thread started on port 80
                      2/12/2006 11:38:53 AM ~!~Startup~!~Initializing email 1 1
                      2/12/2006 11:38:54 AM ~!~Startup~!~Initializing text to speech
                      2/12/2006 11:38:54 AM ~!~Info~!~Email receive thread started
                      2/12/2006 11:38:55 AM ~!~Info~!~Listening for remote speaker connections on port 8742
                      2/12/2006 11:38:55 AM ~!~Startup~!~Start remoting
                      2/12/2006 11:38:55 AM ~!~Startup~!~Start event processing
                      2/12/2006 11:38:55 AM ~!~Info~!~This version of HomeSeer is registered.
                      2/12/2006 11:38:55 AM ~!~Startup~!~Running startup script
                      2/12/2006 11:38:55 AM ~!~Info~!~Initializing email for MAPI
                      2/12/2006 11:38:55 AM ~!~Startup~!~Scripting is OK
                      2/12/2006 11:38:56 AM ~!~Info~!~Done with scripting
                      2/12/2006 11:38:56 AM ~!~Startup~!~Starting scheduler
                      2/12/2006 11:38:56 AM ~!~Info~!~Starting the HS2 Sentry EXE
                      2/12/2006 11:38:56 AM ~!~Startup~!~Start up complete.
                      2/12/2006 11:38:58 AM ~!~Database Item~!~Saving Event Controls VR
                      2/12/2006 11:38:59 AM ~!~Database Item~!~Saving Event Controls VR
                      2/12/2006 11:39:00 AM ~!~Database Item~!~Saving Event Genre VR
                      2/12/2006 11:39:00 AM ~!~Database Item~!~Saving Event Genre VR
                      2/12/2006 11:39:01 AM ~!~Database Item~!~Saving Device Quick Genre
                      2/12/2006 11:39:01 AM ~!~Database Item~!~Saving Event Artist VR
                      2/12/2006 11:39:01 AM ~!~Database Item~!~Saving Event Artist VR
                      2/12/2006 11:39:02 AM ~!~Info~!~MAPI Init, found 0 messages
                      2/12/2006 11:39:02 AM ~!~Info~!~Mail login successful
                      2/12/2006 11:39:03 AM ~!~Database Item~!~Saving Device Quick Artist
                      2/12/2006 11:39:03 AM ~!~DEBUG~!~Media Player: Starting load of collection GetPlayLists:1
                      2/12/2006 11:39:04 AM ~!~Database Item~!~Saving Event PlayList VR
                      2/12/2006 11:39:04 AM ~!~Database Item~!~Saving Event PlayList VR
                      2/12/2006 11:39:05 AM ~!~Database Item~!~Saving Device Quick PlayList
                      2/12/2006 11:39:05 AM ~!~Database Item~!~Saving Event Album VR
                      2/12/2006 11:39:05 AM ~!~Database Item~!~Saving Event Album VR
                      2/12/2006 11:39:06 AM ~!~Info~!~Web Server authorized local login successful from: 127.0.0.1 User: default
                      2/12/2006 11:39:07 AM ~!~Database Item~!~Saving Device Quick Album
                      2/12/2006 11:39:07 AM ~!~Startup~!~Media Player background initialization completed
                      2/12/2006 11:39:18 AM ~!~Info~!~Speaker client connected from: 127.0.0.1
                      2/12/2006 11:39:46 AM ~!~X10 Received~!~D16 (?) D On
                      2/12/2006 11:39:55 AM ~!~DooMotion Error~!~Unable to update DooMotion sensor device strings and timers (Error #424 on line 30 of EventTimer2_Timer - Object required)
                      2/12/2006 11:40:13 AM ~!~X10 Received~!~D16 (?) D Off
                      2/12/2006 11:40:15 AM ~!~X10 Received~!~D16 (?) D On
                      2/12/2006 11:40:55 AM ~!~DooMotion Error~!~Unable to update DooMotion sensor device strings and timers (Error #424 on line 30 of EventTimer2_Timer - Object required)
                      2/12/2006 11:41:55 AM ~!~DooMotion Error~!~Unable to update DooMotion sensor device strings and timers (Error #424 on line 30 of EventTimer2_Timer - Object required)
                      2/12/2006 11:42:55 AM ~!~DooMotion Error~!~Unable to update DooMotion sensor device strings and timers (Error #424 on line 30 of EventTimer2_Timer - Object required)
                      2/12/2006 11:43:22 AM ~!~Error~!~Web Server Error 404, cannot serve file: d:\program files\homeseer 2\html/dmoptions
                      2/12/2006 11:43:55 AM ~!~DooMotion Error~!~Unable to update DooMotion sensor device strings and timers (Error #424 on line 30 of EventTimer2_Timer - Object required)
                      2/12/2006 11:44:55 AM ~!~DooMotion Error~!~Unable to update DooMotion sensor device strings and timers (Error #424 on line 30 of EventTimer2_Timer - Object required)
                      2/12/2006 11:45:42 AM ~!~Info~!~Web Server authorized local login successful from: 192.168.1.87 User: default
                      2/12/2006 11:45:42 AM ~!~Error~!~Web Server Error 404, cannot serve file: d:\program files\homeseer 2\html/dmchart
                      2/12/2006 11:45:56 AM ~!~DooMotion Error~!~Unable to update DooMotion sensor device strings and timers (Error #424 on line 30 of EventTimer2_Timer - Object required)
                      2/12/2006 11:46:56 AM ~!~DooMotion Error~!~Unable to update DooMotion sensor device strings and timers (Error #424 on line 30 of EventTimer2_Timer - Object required)

                      Comment


                        #12
                        How about trying the latest build at http://www.doosoft.com.downloads.php. If I have to make changes to get DM to install on Pro-100, then it would be the build that I would be starting with
                        • Download DooMotion
                        • Disable flash
                        • Install DooMotion to D:\program files\homeseer 2
                        • Enable flash
                        If you have to do reboots, then go ahead. I am not familiar (obviously) with adding programs to the Pro-100.

                        I noticed that your log snippet also contains a problem with the ACRF plug-in. That plug-in is by a different author but looks to be suffering from a similar problem.
                        Jim Doolittle

                        My Twitter
                        My Hardware & Software

                        Comment


                          #13
                          NNilsen,

                          Were you successful in figuring out how to load the DooMotion and ACRF plugins on the PRO-100?

                          If you did, please share how you finally got it working.

                          Thanks.

                          Doug

                          Comment


                            #14
                            No success yet

                            I love the pro-100
                            it looks good
                            it's fast
                            it's efficient
                            compact, no heat
                            protect c: drive is a good thing for daily operation

                            In my opinion the pressing item that needs to be addressed is data storage space 'memory'

                            HS log files logging to the d: drive use up space
                            updater files kill the d:drive

                            I have not been able to load two third party add-ons using updater because
                            zip files eat up d:
                            help files eat up d:

                            Suggested fix's

                            in HS setup
                            -allow specification of log file location (I install and external USB CF disk and manually move log files to it)

                            - allow specification of updater files (I move help, zip and docs to my E: drive)

                            in Pro-100
                            - configure a larger d: drive (standard or optional cost)

                            Workarounds....
                            Is there a way to launch the final updater step from data on another drive
                            Is there an easy way to manually install the files to the correct locations

                            Comment


                              #15
                              Zip files are deleted after they are downloaded and unzipped. Check if the help files are installed in the HS html folder. Those can be deleted and they free up a lot of space. Check your HS options and make sure you only keep a couple days worth of log files. The default is 5 days. After 5 days it starts deleting log files.

                              We will be updating the flash to give more space to the HS partition.
                              website | buy now | support | youtube

                              Comment

                              Working...
                              X