Commands that Function Differently in D3 Windows vs. UNIX

The commands below are supported for both D3 Windows and UNIX implementations. However, the functionality for the commands differ as described below.

Command

Description

basic-prot

For D3 Windows, this command is not required for FlashBASIC code. For non-Flashed code, functions the same as in D3 UNIX.

catalog

D3 Windows supports the (g option for adding modules to the global (domain) catalog for FlashBASIC programs. Not supported for D3 UNIX.

clear-locks

D3 Windows supports additional options for FSI item locks. FSI group locks are cleared and listed using the Monitor, not from TCL.

dev-make

Different device types are supported for each implementation. D3 Windows performs additional checks and displays.

dev-remov

D3 Windows performs additional checks and displays.

flush

For D3 Windows, not supported for the FSI.

free

For D3 Windows, not supported for the FSI. To verify free space in the FSI, use Windows Explorer.

istat

For D3 Windows, not supported for the FSI. To view the data distribution for the FSI, use the D3 File Manager’s File Properties dialog box instead.

list-locks

For D3 Windows, using the (g option lists only VME group locks. Otherwise, both VME and FSI locks are displayed.

restore

D3 UNIX displays a tape verification warning on full restores. D3 Windows does not.

set-active-update

For D3 Windows, supported in the VME only. For FSI data, use the ObjectReuseProt registry entry.

term

D3 UNIX optimizes only when using platform dependant FlashBASIC (C compiler).

verify-index

For D3 Windows, a log file is created by default in the current account.

what

D3 UNIX displays core memory while D3 Windows displays the total amount of RAM on the system.

where

For D3 Windows, the offset in the virtual modes does not display.