Solved: Unable to print after Windows update on Epson LX LQ Dot Matrix

Solved: Epson Dot Matrix Killer Patch - El parche que acabó con las Epson matriciales

No se puede imprimir en Epson LX y LQ matriciales después de actualizaciones de Windows Update


A partir de mediados del mes de noviembre del 2017, si se aplicaron los siguientes parches de Windows Update

• 2017-11 Monthly Rollup - KB4048958
• 2017-11 Security-only update - KB4048961
• 2017-11 Monthly Rollup - KB4048957
• 2017-11 Security-only update - KB4048960
• 2017-11 Monthly Rollup - KB4048959
• 2017-11 Security-only update - KB4048962

Dejaron fuera de servicio a todas las impresoras matriciales LX, LQ de marca Epson

Los mecanismos de reparación anteriores requerían pasar varias horas realizando restauración del sistema y desactivar el Windows Update

El día de ayer 21-11-2017 finalmente liberaron la corrección para todas las plataformas afectadas.

Aplicar inmediatamente la versión qué corresponda.
http://www.catalog.update.microsoft.com/Search.aspx?q=KB4055038

En todos los KB después de las quejas de los usuarios agregaron la leyenda

"After installing this update, some Epson SIDM (Dot Matrix) and TM (POS) printers cannot print on x86 and x64-based systems."

Hoy día dice qué se resolvió
"This issue has been resolved in KB4055038."

B.

Fuentes para workarounds:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/eb8e8076-2c22-4109-b15b-5d710110af92/printing-problem-epson-lx-300-?forum=winserverprint

 

https://www.tachytelic.net/2017/11/unable-print-dot-matrix-printers-windows-updates/

 

https://support.microsoft.com/es-ec/help/4048957/windows-7-update-kb4048957

VMware Problems using some USB devices in a virtual machine (774) / Problemas usando dispositivos USB en una máquina virtual

Source: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=774


Details

 

You cannot use a specific USB device in my virtual machine.

The guest operating system locks up.

Failure when you plug in a USB device

You see an error message similar to:.

 

Inappropriate ioctl for device

 

  

Solution

 

1. Determine whether the USB device needs extra configuration. Issues can occur because the USB devices do not implement the USB protocol as expected. To resolve this issue, you can use certain "quirks" in the guest's interactions with the USB device. To add quirks: 
1. Open the vmware.log file.
2. Search for the device manufacturer's name. Find a line that looks similar to:
1. vmx | USB: Found device [name:Apple\ IR\ Receiver vid:05ac pid:8240 path:13/7/2 speed:full family:hid]
2. The line has the name of the USB device and its vid and pid information. Make a note of the vid and pid values.
3. Edit the .vmx file. Add this line to the .vmx file, replacing vid and pid with the values noted in Step 2, each prefixed by the number 0 and the letter x.
1. For example, for the Apple device found in step 2, this line is:
2. usb.quirks.device0 = "0x05ac:0x8240 skip-reset"
3. Save and close the .vmx file.
4. Restart the virtual machine and try connecting the device again.

 

If the issue is not resolved, replace the quirks line added in Step 4 with one of these lines, in the order provided, and repeat Steps 5 to 8:

 

usb.quirks.device0 = "vid:pid skip-refresh"

usb.quirks.device0 = "vid:pid skip-setconfig"

usb.quirks.device0 = "vid:pid skip-reset, skip-refresh, skip-setconfig"

 

Notes:

 

◾Use one of these lines at a time. If one does not work, replace it with another one in the list. Do not add more than one of these in the .vmx file at a time.

◾The last line uses all three quirks in combination. Use this only if the other three lines do not work.

 

 

ClearOS add new network card after initial setup

Spanish Keywords: Agregar una tarjeta de red adicional a un servidor de ClearOS 5.x después de la configuración inicial

source: http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,24/func,view/id,4315/





I'm new to ClearOS and am loving it. Am no pro, but I needed to add a third NIC to create a DMZ. Sadly, Multiple reboots didn't do the trick for me.... So I had to do it manually.... and with help from posts in this forum and the web, it worked 

I'm sure there are easier ways to do this, but this is how i went about it.

Logged onto a console, Alt+F2, and did the following;

To see if the third NIC had been detected, i did;



Code:


--------------------------------------------------------------------------------

# kudzu -p | grep network
--------------------------------------------------------------------------------


network.hwaddr: xx:xx:xx:xx:xx:xx
network.hwaddr:yy:yy:yy:yy:yy:yy
network.hwaddr:zz:zz:zz:zz:zz:zz

so the third network.hwaddr above is for the new card.

To find the mac address of eth0 and eth1, i did,



Code:


--------------------------------------------------------------------------------

#cd /etc/sysconfig/network-scripts/
# less ifcfg-eth0
# less ifcfg-eth1
--------------------------------------------------------------------------------


Better still you could do; (be sure to use caps on HWaddr)



Code:


--------------------------------------------------------------------------------

# ifconfig | grep HWaddr
--------------------------------------------------------------------------------


then; copy ifcfg-eth1 to ifcfg-eth2



Code:


--------------------------------------------------------------------------------

# cp ifcfg-eth1 ifcfg-eth2
--------------------------------------------------------------------------------


then using your favourite text editor, vi, nano.....



Code:


--------------------------------------------------------------------------------

#nano ifcfg-eth2
--------------------------------------------------------------------------------


change the lines,

DEVICE='eth1' to 'eth2'
IPADDR="192.168.X.X" to the desired ip of DMZ "10.0.x.x"
NETMASK="255.255.255.0" to desired mask
HWADDR="xx.xx.xx.xx.xx.xx" to the mac address of the new card.

save and exit.

then;



Code:


--------------------------------------------------------------------------------

# ifup eth2
--------------------------------------------------------------------------------


then Alt+F7 (to go back to the GUI) and voila there it was eth2 under network->Settings->Ipsettings.....