The scanner driver installation found at
http://www.fujitsu.com/global/support/products/computing/peripheral/scanners/fi/software/ps-ip-twain32.html
can encounter significant problems in certain situations.
Install Issues
Ensure the programs that are set in the HKLM run keys can run correctly. If they are not properly initialised for any reason then the Adobe Acrobat Scanning functionality can be impacted.
USB Port Connection Issues
The scanners do not behave as expected if they are not presented to exactly the same USB port as the scanner was originally connected to. If the scanner is unplugged and plugged into a different USB port it will not function as expected. The correct port can be found by trying each port in sequence. Do not rely on the appearance of the device in the Devices and Printers windows. It may appear as a device, but not function on all ports except the original port.
Below is the relevant passage from a forum post here which explains why this occurs.
“This is a known "feature" of Windows. Unless the device contains an unique ID string
(aka "USB serial number") Windows can't tell that it is same device in a different usb port.
Fujitsu just slashed few cents on manufacturing by not providing this ID.”
The documentation directs users to install the software, reboot and then connect the scanner. However, testing has shown that the scanner comes online correctly, without a reboot, even if it is ON and connected during the installation.
Thursday, December 31, 2015
Thursday, December 17, 2015
App-V 5 and network executables
Firstly just don't. But if you have to...
This post relates to issues encountered when attempting to publish and launch App-V 5 applications which are on network locations.
This article
https://packnowledge.wordpress.com/2013/03/20/launching-a-network-executable-inside-an-app-v-5-virtual-environment-2/ discusses a situation where providing the machine account with access to the network resources can resolve an error which appears when attempting to launch the application:
TargetFileName.exe - Application Error
The application was unable to start correctly (0xc0000142). Click OK to
close the application.
However in a recent scenario a resolution was not found. Here the application exe target had been moved from an actual Windows 2000 server share where launching worked fine, to a share on an enterprise storage system which used isilon OneFS. Unsuccessful attempts to resolve it included creating a test share on the isilon OneFS system with completely open permissions and also restricting the network protocol to SMB (not SMB2 or 3). More info here
https://support.microsoft.com/en-us/kb/2696547
Before it was even possible to carry out a launch, the application would only publish IF the drive mapping to the share was disconnected or deleted. If the drive mapping was connected to the share then publishing would fail with the following responses (errors).
publish-appvclientpackage : Application Virtualisation Service failed to complete requested operation.
Operation attempted: Publish AppV Package.
Windows Error: 0x3A - The specified server cannot perform the requested operation
Error Module: Share Component. Internal error detail: 8DC022250000003A.
This was observed in 5.0 SP2 HF4, 5.0 SP3 and 5.1
The App-V package was simple in that it consisted of only a shortcut to the exe file on a drive mapping and an ini file in the windows folder. Appsense Environment Manager was used instead to deliver a shortcut and copy the ini file to the users Windows 7 virtual store.
This post relates to issues encountered when attempting to publish and launch App-V 5 applications which are on network locations.
This article
https://packnowledge.wordpress.com/2013/03/20/launching-a-network-executable-inside-an-app-v-5-virtual-environment-2/ discusses a situation where providing the machine account with access to the network resources can resolve an error which appears when attempting to launch the application:
TargetFileName.exe - Application Error
The application was unable to start correctly (0xc0000142). Click OK to
close the application.
However in a recent scenario a resolution was not found. Here the application exe target had been moved from an actual Windows 2000 server share where launching worked fine, to a share on an enterprise storage system which used isilon OneFS. Unsuccessful attempts to resolve it included creating a test share on the isilon OneFS system with completely open permissions and also restricting the network protocol to SMB (not SMB2 or 3). More info here
https://support.microsoft.com/en-us/kb/2696547
Before it was even possible to carry out a launch, the application would only publish IF the drive mapping to the share was disconnected or deleted. If the drive mapping was connected to the share then publishing would fail with the following responses (errors).
publish-appvclientpackage : Application Virtualisation Service failed to complete requested operation.
Operation attempted: Publish AppV Package.
Windows Error: 0x3A - The specified server cannot perform the requested operation
Error Module: Share Component. Internal error detail: 8DC022250000003A.
This was observed in 5.0 SP2 HF4, 5.0 SP3 and 5.1
The App-V package was simple in that it consisted of only a shortcut to the exe file on a drive mapping and an ini file in the windows folder. Appsense Environment Manager was used instead to deliver a shortcut and copy the ini file to the users Windows 7 virtual store.
Sunday, December 13, 2015
Handbrake output is poor quality, distorted or scrambled.
This fix resolves and issue where output from Handbrake is very poor quality. It could also be described as badly distorted or scrambled. It looks like a kind of codec issue. This article explains how to fix it.
Essentially obtain this 64-bit version http://download.videolan.org/pub/libdvdcss/1.2.11/win64/libdvdcss-2.dll
and copy it to
C:\Program Files\Handbrake on a 64 bit system.
http://www.jargonfreehelp.com/fixing-handbrake/
Thursday, December 3, 2015
Subscribe to:
Posts (Atom)