Jump to content
View in the app

A better way to browse. Learn more.

Pulseway

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

mzenhorst

Members
  • Joined

  • Last visited

  1. I have no issues with normal virtualbox disks, just with rawdisks. It looks then if the device is not allowing write access for some reason. Unfortunately I cannot reproduce on a different computer, hence I think this will not get resolved. I'll work around it by starting the vm from a service and depend PC Monitor on it. If PC Monitor is started while vbox is running no error is thrown during restarts of the vm.
  2. Hello, I tried the unlocker and I did the following case: Start PC monitor service Then start VM, failed with: Failed to open a session for the virtual machine OXX. Failed to open image 'D:\OXX\OXXShared.vmdk' for writing due to wrong permissions (VERR_VD_IMAGE_READ_ONLY). Failed to attach driver below us! Image is read-only. (VERR_VD_IMAGE_READ_ONLY). AHCI: Failed to attach drive to Port1 (VERR_VD_IMAGE_READ_ONLY). Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392} The unlocker does not show any locking handles. However this only happens when I start the PC Monitor service before I start the VM. Otherwise it will start normally. System: Windows XP Professional version 2002 SP3 (build 5.1.2600) vmdk file is a raw device file, it points to PhysicalDisk0. How could I further debug this?
  3. I'm running PC Monitor and all is well. Except for the fact that it seems to be locking files at OS level. Mainly when I'm running my VirtualBox image with a raw disk I get the following error: Failed to open image: '<filename>' for writing due to wrong permissions (ERR_VD_IMAGE_READ_ONLY). I have found that disabling the PC Monitor service will let me start the VirtualBox image correctly. I have tried this several times. Therefore I can only conclude that PC Monitor is blocking the write mode. However I'm not sure whether it is the vmdk file or the physical disk itself that is locked by PC Monitor. I'm suspecting the physical drive since creating the vmdk file failed with a sharing exception (VERR_SHARING_VIOLATION) until I disabled the PC Monitor service I hope you can help me by explaining why PC Monitor is locking files? Kind regards, Mark Zenhorst

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.