Direct Turbo Studio v21.11.1606

[Don007]

Powerful, easy-to-use authoring tool for creating virtual environments.

FEATURES​

Filesystem and Registry Virtualization Turbo Studio lets you easily design and configure virtual filesystem within application containers. Virtual files are accessible by the containerized application but isolated from native applications installed on the host device based on configurable isolation semantics. With Turbo, virtual files can reside in privileged directories without permissions, and shared DLLs in the virtual filesystem do not interfere with those installed by native applications on the host. Turbo Studio allows quick viewing, editing, and import or export of virtual registry contents. Like the virtual filesystem, Studio offers a range of configurable isolation semantics. Isolation Modes Turbo Studio supports configuration of all isolation modes supported by Turbo VM, that define interaction between the containerized and host environment. Spoiler: Info Full: Only values from the virtual file-system or registry are accessible to the containerized application, even if a corresponding value exists on the host device. Writes to the registry are redirected to the sandbox. This mode completely isolates the container application from the host device. Write Copy: Values from both the host device are accessible to the container application. If a value exists on both the host device and virtual registry, the virtual value takes precedence, but writes to the virtual environment are redirected to the sandbox. This mode allows containerized applications to see host data but protects the host from changes. Merge: Data from both the host device and the virtual registry are accessible to the container application, with virtual values taking precedence if a conflict exists. Any changes are written out to the host device. This mode allows the containerized application to interact with the host device. Hide: Attempts to read or write values in the sub-folder will fail and the values will not be visible to the containerized application. This mode prevents the application from accessing data on the host device that might cause issues with its execution.
	Network Virtualization Turbo Studio provides full configurability of the Turbo network virtualization layer. Containerized applications can have application-specific network configurations as well as defined inter-container communication routing rules. Proxy: Route network traffic from the container through a specified proxy.This allows system administrators to monitor application activity and prevent data leaks. DNS: Configure Domain Name System (DNS) records within the container. Redirect traffic for specified host-names to administrator-defined IP addresses. This is valuable in development and legacy application scenarios where a required host-name cannot be changed and updating network records is undesirable. IP Restrictions: Create network rules for specific addresses, ports, adn protocols to be accessible or blocked from the container. Lock down vulnerable legacy applications to specific application servers safe from malware attacks on external networks.
Services and DCOM Configure services within a virtualized Service Control Manager. Turbo Studio supports virtualization of servers such as SQL Server, MySQL, IIS, and nginx. Studio also allows configuration of remote DCOM servers, which arise in many advanced Windows applications. Studio automatically captures services during the application snapshot or container commit stages of an application build.

You must be registered for see links

File Size : 44 MB

 

[WideGlide]

Nice share, thanks for the work.

 

[Zeljko Bondzic]

Thanks for the "App Virtualization" software

 

[hkoolh]

Thanks much . . . .