When I try to install macOS in VMware Workstation I get a popup error when I try to login with my Apple ID:
ICLOUD_UNSUPPORTED_DEVICE
That's all it says.
How do I make my VM appear as an iCloud supported device?
Shut down the VM gracefully, then add the following to the end of your virtual machine's .vmx file to make VMware believe it is running on Mac hardware:
board-id = "Mac-551B86E5744E2388"
hw.model.reflectHost = "FALSE"
hw.model = "MacBookPro14,3"
serialNumber.reflectHost = "FALSE"
serialNumber = "C02XXXXXX153"
smbios.reflectHost = "FALSE"
efi.nvram.var.ROM.reflectHost = "FALSE"
efi.nvram.var.MLB.reflectHost = "FALSE"
efi.nvram.var.ROM = "3c0754a2f9be"
Boot the VM.
Open iTunes, click Account menu, then Sign In.
Source for the above lines
I have a local network with a printer, laptop, desktop and a Raspberry Pi that acts as SMB NAS + Kodi + Pi-Hole + a whole lot more.
For a very long time my PC (Win10-latest) would not automatically find some other local network attached devices. The only ones that it would find would be Printer, Router and Kodi (streaming + library).
If I tried mapping a network drive manually or tried to access the local IP of device manually, it would work and then the device would appear under network. (workaround but still annoying)
I have tried all the solutions I could find online to enable automatic discovery with no luck:
Set WiFi to be private
Enable sharing + discovery
Make sure workgroup is WORKGROUP
Manually enable UpNP, SSDP + 2x Function Discovery services
Check firewall settings and allow File and Printer Sharing (LLMNR-UDP-In) for Domain
Weird thing is, my Android phone with SolidExplored had no problem finding other local devices including the SMB.
Eventually I tried the net view command and it came up with:
net view
System error 384 has occurred.
You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack.
So I checked smbstatus on my Raspberry and it said it is connected with SMB3_11. I then manually modified my smb.conf file on the Raspberry to be server min protocol = SMB2 but the System error 384 continued.
I then enabled SMB 1.0/CIFS File Sharing Support from Turn Windows Features on or off restarted my PC and all my local network devices appear!
I would like to know if anyone else experienced the same issues? I don't even understand what I have misconfigured.
# Global parameters
[global]
log file = /var/log/samba/log.%m
logging = file
map to guest = Bad User
max log size = 1000
obey pam restrictions = Yes
pam password change = Yes
panic action = /usr/share/samba/panic-action %d
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
passwd program = /usr/bin/passwd %u
server min protocol = SMB2
server role = standalone server
unix password sync = Yes
usershare allow guests = Yes
idmap config * : backend = tdb
guest ok = Yes
[homes]
comment = Home Directories
create mask = 0775
directory mask = 0775
read only = No
valid users = %S
[printers]
browseable = No
comment = All Printers
create mask = 0700
guest ok = No
path = /var/spool/samba
printable = Yes
[print$]
comment = Printer Drivers
guest ok = No
path = /var/lib/samba/printers
[R]
comment = 8Tb HD Raspberry Downloads
create mask = 0775
directory mask = 0775
force group = pi
force user = pi
path = /media/pi/Raspberry/Downloads/
read only = No
wide links = Yes
[Private]
comment = 8Tb HD Raspberry Private
create mask = 0775
directory mask = 0775
force group = pi
force user = pi
guest ok = No
path = /media/pi/Raspberry/Private/
read only = No
wide links = Yes
The issue was missing wsdd. Installed it, setup a systemd service with a few changes and all works perfect now.
I built my own version of Chromium using official instruction with very slight changes in the code that do not touch the core things. When I try to launch it on Windows 10 (tried Home and LTSC), is shows "RESULT_CODE_MISSING_DATA" error on each page, including internal ones, like "settings".
The build works on Windows 10 correctly if I launch it with "compatibility to Windows 8" option, but that's a bad option as it launches with additional borders, maybe it's because of Metro UI:
enter image description here
The build launches on Windows 7 well without any additional changes.
I tried to build 82.x.x.x and 81.x.x.x builds, they all emerge this error on Windows 10.
I tried to do builds on multiple OS (Win7, Win10), the error still presents.
my args.gn:
is_debug = false
is_component_build = false
enable_nacl = false
symbol_level = 1
target_cpu = "x86" # I tried x64, same problem
blink_symbol_level = 1
proprietary_codecs = true
ffmpeg_branding = "Chrome"
is_component_ffmpeg=true
is_official_build=true
Ok, after several build tries I built chromium well-working after removing the is_component_ffmpeg=true flag from args.gn.
Thanks Asesh for helping.
I have followed instructions here:
https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md
to compile chormium on Windows 7 x64.
It takes some long time to compile, but the problem is not the slow compiling, the problem is in fact that when the browser i built, it runs very, very slow. Is uses much more RAM then usual Chome and it even cannot run on Virtual Machine with 3GB of RAM (shows error).
How can I compile Chromium that can run normally without performanse problems?
If you built it according to instructions then I suppose the problem was in "is_debug = true".
In case you want build browser for normal usage try to change this string from dev manual from:
gn gen out/Default --args="is_component_build = true is_debug = true"
to
gn gen out/Default --args="is_official = true"
"is_officail" flag makes a lot of optimizasions.
see https://www.chromium.org/developers/gn-build-configuration
for full gn-docs
you most likely need
is_official_build = true
is_debug = false
dcheck_always_on = false
blink_symbol_level = 0
symbol_level = 0
in your gn args.
I have an old USB device that is not recognized by windows 7, so I grabbed the device driver for the chip that handles the USB communications. After I modified it I used it to install for the device. Stupid I know, but now I need to get rid of it.
Below is the code from the inf setup file. This does not have the VID and PID that I changed. I need to reverse all the changes it made.
; Installation INF for the Cypress Generic USB Driver for Windows Vista
; Processor support for OS unknown platforms.
;
; (c) Copyright 2010 Cypress Semiconductor Corporation
;
[Version]
Signature="$WINDOWS NT$"
Class=USB
ClassGUID={36FC9E60-C465-11CF-8056-444553540000}
provider=%CYUSB_Provider%
CatalogFile=CYUSB.cat
DriverVer=10/12/2010,3.4.4.000
[SourceDisksNames]
1=%CYUSB_Install%,,,
[SourceDisksFiles]
CYUSB.sys = 1
[DestinationDirs]
CYUSB.Files.Ext = 10,System32\Drivers
[ControlFlags]
ExcludeFromSelect = *
[Manufacturer]
%CYUSB_Provider%=Device,NT,NTx86,NTamd64
;for all platforms
[Device]
;%VID_XXXX&PID_XXXX.DeviceDesc%=CyUsb, USB\VID_XXXX&PID_XXXX
;for windows 2000 non intel platforms
[Device.NT]
; Cypress FX2LP default ID
%VID_04B4&PID_8613.DeviceDesc%=CyUsb, USB\VID_04B4&PID_8613
; Cypress FX1 default ID
%VID_04B4&PID_6473.DeviceDesc%=CyUsb, USB\VID_04B4&PID_6473
; Cypress Streamer Device. CyStream firmware examples use this VID/PID
%VID_04B4&PID_1003.DeviceDesc%=CyUsb, USB\VID_04B4&PID_1003
; Cypress FX2LP Example Device. DVK firmware examples use this VID/PID
%VID_04B4&PID_1004.DeviceDesc%=CyUsb, USB\VID_04B4&PID_1004
;for x86 platforms
[Device.NTx86]
; Cypress FX2LP default ID
%VID_04B4&PID_8613.DeviceDesc%=CyUsb, USB\VID_04B4&PID_8613
; Cypress FX1 default ID
%VID_04B4&PID_6473.DeviceDesc%=CyUsb, USB\VID_04B4&PID_6473
; Cypress Streamer Device. CyStream firmware examples use this VID/PID
%VID_04B4&PID_1003.DeviceDesc%=CyUsb, USB\VID_04B4&PID_1003
; Cypress FX2LP Example Device. DVK firmware examples use this VID/PID
%VID_04B4&PID_1004.DeviceDesc%=CyUsb, USB\VID_04B4&PID_1004
;for x64 platforms
[Device.NTamd64]
; Cypress FX2LP default ID
%VID_04B4&PID_8613.DeviceDesc%=CyUsb, USB\VID_04B4&PID_8613
; Cypress FX1 default ID
%VID_04B4&PID_6473.DeviceDesc%=CyUsb, USB\VID_04B4&PID_6473
; Cypress Streamer Device. CyStream firmware examples use this VID/PID
%VID_04B4&PID_1003.DeviceDesc%=CyUsb, USB\VID_04B4&PID_1003
; Cypress FX2LP Example Device. DVK firmware examples use this VID/PID
%VID_04B4&PID_1004.DeviceDesc%=CyUsb, USB\VID_04B4&PID_1004
[CYUSB]
CopyFiles=CYUSB.Files.Ext
AddReg=CyUsb.AddReg
[CYUSB.HW]
AddReg=CYUSB.AddReg.Guid
[CYUSB.Services]
Addservice = CYUSB,2,CYUSB.AddService
[CYUSB.NT]
CopyFiles=CYUSB.Files.Ext
AddReg=CyUsb.AddReg
[CYUSB.NT.HW]
AddReg=CYUSB.AddReg.Guid
[CYUSB.NT.Services]
Addservice = CYUSB,2,CYUSB.AddService
[CYUSB.NTx86]
CopyFiles=CYUSB.Files.Ext
AddReg=CyUsb.AddReg
[CYUSB.NTx86.HW]
AddReg=CYUSB.AddReg.Guid
[CYUSB.NTx86.Services]
Addservice = CYUSB,2,CYUSB.AddService
[CYUSB.NTamd64]
CopyFiles=CYUSB.Files.Ext
AddReg=CyUsb.AddReg
[CYUSB.NTamd64.HW]
AddReg=CYUSB.AddReg.Guid
[CYUSB.NTamd64.Services]
Addservice = CYUSB,2,CYUSB.AddService
[CYUSB.AddReg]
; Deprecating - do not use in new apps to identify a CYUSB driver
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,CYUSB.sys
; You may optionally include a check for DriverBase in your application to check for a CYUSB driver
HKR,,DriverBase,,CYUSB.sys
HKR,"Parameters","MaximumTransferSize",0x10001,4096
HKR,"Parameters","DebugLevel",0x10001,2
HKR,,FriendlyName,,%CYUSB_Description%
[CYUSB.AddService]
DisplayName = %CYUSB_Description%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\System32\Drivers\CYUSB.sys
AddReg = CYUSB.AddReg
LoadOrderGroup = Base
[CYUSB.Files.Ext]
CYUSB.sys
[CYUSB.AddReg.Guid]
HKR,,DriverGUID,,%CYUSB.GUID%
[Strings]
CYUSB_Provider = "Cypress"
CYUSB_Company = "Cypress Semiconductor Corporation"
CYUSB_Description = "Cypress Generic USB Driver"
CYUSB_DisplayName = "Cypress USB Generic"
CYUSB_Install = "Cypress CYUSB Driver Installation Disk"
VID_04B4&PID_8613.DeviceDesc="Cypress EZ-USB FX2LP No EEPROM"
VID_04B4&PID_6473.DeviceDesc="Cypress EZ-USB FX1 - No EEPROM"
VID_04B4&PID_1004.DeviceDesc="Cypress EZ-USB Example Device"
VID_04B4&PID_1003.DeviceDesc="Cypress EZ-USB Streamer Device"
VID_XXXX&PID_XXXX.DeviceDesc="Cypress USB Generic Driver (3.4.4.000)"
CYUSB.GUID="{AE18AA60-7F6A-11d4-97DD-00010229B959}"
CYUSB_Unused = "."
Another option (the Microsoft way, without doing random unknown deletings in the registry) is to start CMD as "run as admin" and then list all installed drivers in the Windows 7 driver store via:
pnputil -e
if this caused a longer list you can pipe that into a file via:
pnputil -e > C:\driverexport.txt
If you have found now the driver you need to remove use the following comand:
pnputil.exe -d OemNUMBER.inf
replace NUMBER with your number from your example. You might try to use -F to force the uninstallation. Once a reboot is done the driver should be gone.
This might be also usefull to delete old drivers and get some HD space back.
Source
If you have installed a driver for a device and you want to remove it (and the driver store) just plug in your device. Open Device Manager, right click the device and select Uninstall. There will be a box that says "Remove driver software" - check this box and Uninstall the driver. This should remove it from the driver store and uninstall the device from the registry.
If all drivers for the device has been removed you should be able to plug it in and see that no driver loads for the device. If it does there could be multiple versions in your driver store and you go through the same steps until Windows doesn't recognize the device.
Note that the SYS file will remain in the C:\Windows\System32\drivers directory per policy, but if all devices and installations are removed that use it you can safely delete this driver as well.
While the steps mentioned in answers above may be correct, this is a significantly easier method to do it:
Go to Device Manager or alternatively run the command
devmgmt.msc
Right-click the device you need to uninstall and go to Properties. Select the Details tab and then select INF Name from the drop-down list
Once you have the INF Name type in this command in a command window opened with Admin privileges
pnputil.exe -d INFName.inf
if you face issues try forced deletion
pnputil.exe -f -d INFName.inf