Re: Activ Inspire Software Download 27
Higinia Livoti
The Promethean ActivPanel provides seamless, integrated, and interactive learning. The panel is packed with interactive tools that help teachers and students make the most of instructional moments. This quick reference guide provides instructions for using the center console, connecting to a laptop, and using the Unified Menu.
This Getting Started Guide for the ActivPanel Titanium was published by Promethean and contains information related to operating your ActivPanel Titanium and using the various apps available through the Locker including Whiteboard, Capture, Annotate and others.
Challenge Details: Inspire Sussex is on a mission to inspire and empower individuals with learning disabilities. Currently, we're raising funds for our upcoming Social Hub on Greenfield Road, Eastbourne. To amplify our efforts, we've joined forces with Buzz Active and The Eastbourne Chamber of Commerce to introduce a unique fundraising challenge. Your participation will contribute significantly to creating a space that will be a beacon of inspiration, connection, and positive change within our community.
Whether you're a seasoned paddler or a beginner seeking a new adventure, this challenge is tailored to all skill levels. Beyond just reaching the 100-kilometer mark, our goal is to foster camaraderie and ignite a shared passion for an active lifestyle.
since the version 2.24, Activinspire is disown by his maintainer that fail to resolve some dependencies. Activinspire is a very good software for interactive whiteboard, but its linux version (for ubuntu focal) is package by crazy people with terrible script, gnome extension, old dependencies... For exemple, a few version ago, the deb contain 3 times the software inside for no reason. So i understand the maintainer..
- MD5, version...etc
- Remove /etc/xdg but keep /etc/udev (needed???)
- Remove /usr/share/gnome-shell (i am on kde so i don't see the need of this extension and i don't think it's the way to go)
- Remove com.ubuntu.user-interface.gschema.xml that seems no longer needed
- Remove killing inspire at launch as it seems not needed any more (had to test more)
- Update dependencies : icu60 seems no longer needed and openssl1.1 instead of 1.0
- Resolve dependency by brutally adding in /opt/activsoftware libre2.so.5 and libwebp.so.6 in /opt/activsoftware from ubuntu focal deb ( -5 and )
It seems to work well on my setup (except small font in the menu that don't bother me to much and the impossibility to print but it was like this before). Before taking my time to understand how to become the new maintainer, i need to know if people are interested and i need some test. I put all the file need to compile and test the 2.24 version here :
It's a version to be compile locally with activinspire deb directly in the folder, the link for the activinspire deb will be update for AUR version to be download it from promothean server. The rest is rework script and lib from ubuntu package, so i don't think it will pose some license problem.
As far as I know, you can only authenticate from an Ubuntu distribution (20.04) according to their instruction on their website ( ). Follow the steps on another (virtual) machine, but then use a command to download and save the .deb-package, for example sudo apt download activinspire.
edit: The binaries only seem to work in an x11 session. Trying to execute them on a wayland compositor leads to weird segmentation faults. If someone can fix the problem or just find an easy workaround, please do tell. Thank you.
It is looking for symbol _ZN3re23RE23Arg12parse_stringEPKcmPv in its own packaged libQt6WebEngineCore.so.6, which does not exist. If you make it use the libQt6WebEngineCore.so.6 form the Arch package qt6-webengine, it is looking for Symbol _ZN9QtPrivate25QMetaTypeInterfaceWrapperI4QUrlE8metaTypeE, which does not exist in the Arch version of the library.
Printing doesn't work for me either. I just hadn't noticed it yet because I never print.So far I don't have an idea on how to debug this either, but I'll try. As a workaround you can export to PDF and then print the PDF.
First, I'm unable to print from activinspire. Using File -> Print... only opens a window stating "No printers installed on this computer" even though printing worked with 2.18. Any idea what's wrong here or how to debug the problem?
I tried to add them as additional Deployment Types, but I don't think this is right, and only the Priority 1 MSI appears to be installed and the wording on the Deployment Types pane suggests to me this is only to give the administrator an option to deploy a single application but offer multiple deployment types dependent on platform or perhaps other requirements.
Secondly, when updating applications, is it necessary to use the supersedence option - and if so, is it necessary to keep each revision of a piece of software? There is a suggestion here of using batch scripts to call installers/uninstallers but this doesn't seem especially elegant, especially with the application above with multiple parts.
The best and most future ready solution would be to created separate applications for all of them. Indeed one application with multiple deployment types won't works as it goes through all the deployment types (by priority) and installs the first applicable one.
I am curious about this also. I have never had great luck installing/updating applications. My most recent deployment of Acrobat X was lackluster at best. It was very hit or miss as far as whether or not the installation was successful. Of course, every time I test these things in a test environment, they go smoothly. Drop the same procedure into a production environment and wacky things start to happen.
It is not necessary to use the supersedence option, but it may be necessary depending on the Application. If you update the package content, and detection method for an application (specifically in your case, updated the Application with a different MSI) then the App will probably not be discovered any longer, and devices that App is deployed to will then run the Deployment Type (or Program in old school lingo). This may be an effective method to upgrade devices, so long as the MSI will happily install on top of existing devices without the need for a prior uninstall. This is not always the case though, so careful testing is required. But for many of our Apps (Foxit Reader Enterprise for example), we simply updated the MSI and then SCCM will evaluate the software as no longer being installed and run the new MSI, and update all devices that the Application is deployed to.
Did you come up with a solution to this? If not - after taking a crash course this weekend I have one that works. You *do* need to add each MSI to it's own application, so create one for each. But.. from there go back into each and use "dependencies" So, ActivInspire.msi is dependent on ActivInspireCoreRes.msi. ActiveInspireCoreRes.msi is dependent on ActivInspireHelp.msi. ActivinspireHelp.msi is dependent on ActivInspireHWRRes.msi. I keep the ActivDriver on it's own. When you do that, and deploy, it ties them all together and installs in order. Did the same for ITunes and QuickTime.
my way to do this (notably for activInspire) is to wrap those installer with the PowerShell App Deployment Toolkit as I really don't want to create 5 or 6 applications at each new version and manage the supersedence and dependencies
My example is not quite so complicated, but I built an 'Application' with two deployment types to install Microsoft Visual C++ Redistributable, one each for 32-bit and 64-bit. When it's a 32-bit OS I only need the x86 version to install, however on a 64-bit OS I need both the x86 and x64 versions to install.
Result:
When a Windows 64-bit client goes to install Microsoft Visual C++ Redistributable, it checks the first deployment type and meets it's requirement,and so commences install.
It is dependent on the x86 install, so it will go ahead and install that first.
Now satisfied it has met it's dependencies, it will install x64.
When a Windows 32-bit client goes to install Microsoft Visual C++ Redistributable, it checks the first deployment type, however does not meed it's requirement, so passes to the next on the list, which has no requirements, and so commences install.
It installs the x86 deployment type and reports success.