Tag Info

New answers tagged

2

Short Answer: This printer does not work "out-of-the-box" with Ubuntu 14.04. Additional Details: EDIT: HopelessN00B pointed-out there's OSX drivers available. Though OSX is closer to BSD than Linux (as others have mentioned), there may be a chance; The OSX driver download contains two *.dmg files. If there's a PPD file or two in there, there's a chance ...


1

They don't seem to offer Linux drivers on their website, but they do offer OSX drivers. Since OSX is really just a customized version of Linux BSD, you might be able to make the OSX drivers work on Linux, with a little effort. The linked page also has a contact option - I'd ask Fuji about their Linux support before doing anything else, as that seems like ...


2

As a lesson to people who try to install old versions of Linux on new hardware, this won't work... RHEL 6.2 was released in December 2011 The HP ProLiant DL380 Gen9 server was released a few weeks ago in late 2014... HP's compatibility matrix states the certified operating systems and minimum versions needed to operate on a given hardware platform. ...


3

I'm pretty sure that the printer should look like this: There's a group policy setting: Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Printer Redirection Also, Easy Print requires: Remote Desktop Connection (RDC) 6.1 At least Microsoft .NET Framework 3.0 Service Pack 1 ...


0

Did you try making a Selection Profile and selecting the driver(s) with it? You can select the selection profile in the deployment share properties under the Windows PE -> Drivers and Patches. This will integrate the drivers into your PE image so that i can load them without needing to connect to the network. Now this does directly integrate the driver ...


0

The required NIC driver "MUST" be either off-line injected and loaded by loaddrv at boot or on-line injected (Dism) in your Boot.wim file. Off course if the NIC driver is not properly loaded you will never see the MDT repository that means no access to anything MDT has to offer using its shares. I think PE is detecting the NIC but your driver is not ...


1

I'm going to assume you're deploying Windows 7. I ran into a similar issue on newest Intel wired NIC chipsets. Check the Kernel Mode Driver Framework for an update. Windows 7 launched with version 1.9 per TechNet, and this needs to be injected into the image as a task in MDT. Windows 8 certified hardware will likely target KMDF 1.11 This Post explains ...


0

A while ago I wanted to play a little bit with data packets like layer 2, layer 3 or higher layers. I found a nice tool, based on python to do that. This tool calls Scapy. You can capture and manipulate packets. Or you can build a packet based filter for your need.


2

If you want to analyze the packet as the Linux kernel receives it you will have to write a kernel driver, possibly going as far as modifying the kernel itself. When the interface receives data the processing begins immediately. Anything that is registered to receive the next layer will have its handler called. Since the MAC header doesn't require very ...



Top 50 recent answers are included