C:\Windows\System32\Spool\Printers
Stop spool service
delete all files
start spool service
How To Repair Broken EFI Partition
Assign both your Windows partition and your EFI partition a drive letter. The EFI partition by default is not assigned a drive letter, but you can use diskpart to assign a letter temporarily. Then make sure you know which drive letter each partition is assigned in the environment you’re using. When you’ve got both partitions assigned a drive letter and you know which partition has which drive letter, modify the example command below as needed. In the command below, the EFI partition is X: and the Windows partition is C. Change those as needed for your setup:
C:\Windows\System32\bcdboot C:\Windows /s X:
That will cause the EFI bootloader files from your Windows partition to be copied onto your EFI partition, which should get it working.
If it doesn’t work, try formatting your EFI partition as FAT32 just to erase it and start from scratch, then try running that command again. Again, that command is what Windows Setup runs when it first installs Windows in order to set up the EFI partition, so it should be able to get you a working EFI partition again.
PHP FPDF library to generate pdf with code39 barcode
require(“/path/to/fpdf.php”);
$pdf = new FPDF(‘L’,’mm’,array($X,$Y));
$pdf->AddFont(‘code39′,”,’code39.php’);
$pdf->AddPage();
$pdf->SetFont(‘code39’,”,12);
$pdf->Text(5,3,’*
$pdf->SetFont(‘Arial’,”,18);
$pdf->Text($x,$y,’
$pdf->Output(‘F’,’/path/to/file/myfile.pdf’);
to generate a code39 file from ttf:
https://www.fruit-lab.de/index.php?id=3
http://www.fpdf.org/
How to connect to Sql Server 2017 from php on debian 10
apt-get update
apt-get install unixodbc unixodbc-dev php-odbc php-cli
wget https://packages.microsoft.com/debian/10/prod/pool/main/m/msodbcsql17/msodbcsql17_17.4.1.1-1_amd64.deb
odbcinst -i -d -f /opt/microsoft/msodbcsql17/etc/odbcinst.ini
nano /etc/odbc.ini
[MySQLServerDB]
Description = Database SqlServerDB
Driver = ODBC Driver 17 for SQL Server
Server = server[,port]
Hyper-V Virtual Switches
Types of Virtual Switches
External – This type of switch is bound to the physical network cards located in the host. As you would imagine, they provide VMs located on these switches with access to the physical network the Hyper-V host is connected to. The External switch can also share management traffic as well as VM traffic on the same switch and this is one of the options that can be set when creating the external switch.
Internal – This switch is not bound to a physical network card so only allows traffic between VMs and the host itself. However, a new addition to the Internal switch functionality in 2016 is the addition of the NAT forwarding internal switch which does allow external connectivity via NAT from the Hyper-V host.
Private – This type of switch is only used for virtual machines to communicate with each other. This type of switch might be useful for certain specific types of traffic such as cluster network if only using one host as it can’t be utilized between hosts.
Basic VLAN concepts
Based on HP
You can configure the link type of a port as access, trunk, or hybrid. The link types use the following VLAN tag handling methods:
- Access: an access port can forward packets from only one VLAN and send these packets untagged. An access port can connect a terminal device that does not support VLAN packets or is used in scenarios that do not distinguish VLANs.
- Trunk: a trunk port can forward packets from multiple VLANs. Except packets from the port VLAN ID (PVID), packets sent out of a trunk port are VLAN-tagged. Ports connecting network devices are typically configured as trunk ports.
- Hybrid: a hybrid port can forward packets from multiple VLANs. The tagging status of the packets forwarded by a hybrid port depends on the port configuration. A hybrid port can connect a network device or terminal device that can identify packets tagged with some VLANs.
The PVID identifies the default VLAN of a port. Untagged packets are transmitted through the default VLAN.
When you configure the PVID on a port, follow these guidelines:
- An access or trunk port sends packets from the default VLAN untagged.
- A hybrid port can send packets from the default VLAN tagged or untagged.
- An access port can join only one VLAN. The VLAN to which the access port belongs is the PVID of the port.
- A trunk or hybrid port supports multiple VLANs and the PVID configuration.
Based on Cisco:
Each port or LAG is marked with one of the following modes:
- Access: port belongs to a single untagged VLAN. When a port is in Access mode, the packet types that are accepted on the port (packet type) cannot be designated. It is not possible to enable/disable ingress filtering on an access port.
- Trunk: port can be member of one or more VLANs. It is an untagged member of at most one VLAN, and is a tagged member of all other VLANs of which it is a member.
- General: port can be tagged or untagged and be members of one or more VLAN. (full 802.1Q mode).
For each port or LAG (Link Aggregation Group), select one of the following values:
- Forbidden: port is not able to join the VLAN even if it is was dynamically added using a protocol such as GVRP.
- Excluded: port is not a member of the VLAN. However, the interface can be added to the VLAN through GVRP. This option is not available for the default VLAN.
- Untagged: interface is an untagged VLAN member. Packets forwarded by the interface are untagged.
- Tagged: interface is a tagged member of a VLAN. All packets forwarded by the interface are tagged and contain VLAN information.
For each port or LAG, one or both of the following values may be selected:
- PVID: port PVID is set to this VLAN.
- Multicast TV VLAN: select to make the port a member of the selected VLAN as a Multicast TV VLAN. This option is grayed out for Trunk and General port modes.
Recent Comments