-
Notifications
You must be signed in to change notification settings - Fork 3
FAQ
List of Crossmeta for Windows frequently asked questions.
- Download the appropriate release verison and extract all files from the zip file.
- Run setup.exe from the extracted file.
- Follow the Installation wizard and finisth the installation.
If the Uninstall option is not available from Windows Programs or Features control panel settings, you can remove it from the command prompt as follows.
- Launch Administrator Command Prompt in elevated mode
"\program files\crossmeta\setup.exe /u- Use service_crossmeta.cmd applet
cd c\program files\crossmeta
service_crossmeta.cmd check
C:\Program Files\crossmeta> service_crossmeta.cmd check
Starting Remount Root file system ...
Root file system check done and remounted.Crossmeta drivers can be unloaded cleanly, when there are no open files by applications. To initiate unload
cd c\program files\crossmeta
C:\Program Files\crossmeta>service_crossmeta.cmd status
cxvfs is RUNNING
cxfuse is STOPPED
cxnfs is STOPPED
cxhfs is STOPPED
cxvfsmgr is RUNNING
C:\Program Files\crossmeta>service_crossmeta.cmd stop- umountall returns WIN32 error code 170 to indicate busy file systems but sometimes it can return -1 when there are no mounted file systems. In that case you can unload directly
net stop cxvfsThe Crossmeta Kernel has full PnP interface to Windows NT kernel and cloud disk attachment and removal is supported as any other PnP disk. You can verify its operation with dmesg
# dmesg
Crossmeta Solutions Crossmeta 2.0-RELEASE #230 : Mon Apr 17 19:09:56 PDT 2017
bldmaster@buildhost.crossmeta.org:/build/release_2_0/crossmeta/sys/kern
VFS: PnP DEVICE ARRIVAL \??\SCSI#Disk&Ven_Google&Prod_PersistentDisk#4&21cb0360&0&000200#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} -> Disk Unit 1
da1: major 3 minor 0x1000a
## cmd /c tasklist | grep busybox
busybox.exe 4960 RDP-Tcp#10 2 3,496 K
busybox.exe 3112 RDP-Tcp#10 2 1,420 K
busybox.exe 1612 RDP-Tcp#10 2 1,144 K
#The command (cmd) program automaically executes program with extension specified in PATHEXT variable. It is typically defined as follows
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
Since the crossmeta commands in v:\bin directory have case-sensitive extension .exe to them, it is required to specify the full filename with extension to run them. If preferred you can add .exe to PATHEXT so that it can be run without specifying any extension name.
set pathext=PATHEXT=.COM;.EXE;.exe;BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
- The Crossmeta kernel messages from msgbuf can be viewed with dmesg
v:\bin\dmesg.exe- For any DLL related errors make sure v:\bin;v:\lib are in the PATH environment variable