similar to: Wits end! ndis got me - give me sanity with my wireless!!!

I am trying to build FreeBSD update, STABLE branch, and buildkernel apparently snagged on ndis, which I don't want to do without. According to "man ndis", I need in kernel config options NDISAPI device ndis device wlan which I have: device wlan # 802.11 support options NDISAPI # This is in the hope of enabling Hiro USB wireless adapter device

Did find a solution to this? I am getting the same relocation errors. It seems rather odd that the relocation errors should refer to the directory that ndis is built in, rather than the one it is installed in. That doesn''t make sense, does it? Brian Utterback This message posted from opensolaris.org

I would like to implement a replacement MSCDEX driver (based on the replacement in FreeDOS SHSUCDX http://johnson.tmfc.net/freedos/shsucdx.html and SYSLINUX) however instead of talking to disk BIOS calls or PATA chipset I would like it to talk to the NDIS driver and act as a TFTP client simply forfulling application get block requests through TFTP. Its not clear where the ISO9660 CD

I found the 3Com one, but I'm looking for the intel one. The PXE PDK doesn't have it anymore, and the intel site points me to the proboot.exe archive, which has no *.dos files in it. Does anyone know of other generic drivers for dos that work with memdisk's keeppxe option?

Hi Todd, I did some tests with NDIS 6 TAP-Windows about three years ago. The outcome of that was https://github.com/gsliepen/tinc/pull/73/commits/ 0c010ff9fe50b4046b5c7977bafac3e74037f075 It was a long time ago and I don't remember the details, but I remember I was quite confused because I couldn't explain why OpenVPN did not seem to exhibit any performance issues on the same driver,

While I'm aware that tinc is known to have problems with the latest Windows TAP driver (NDIS 6), we want to run tinc on Windows server 2016 which doesn't support NDIS 5 drivers. Since using the old version of the TAP driver is not an option, I'd like to better understand the issues with tinc and the NDIS 6 TAP driver. Can anyone point me to a discussion of the known issues? From

http://bugzilla.mindrot.org/show_bug.cgi?id=510 Summary: corrupted mac address disconnecting Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P1 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

I've an asterisk 1.2 connecting to a quescom gateway via SIP, the caller (asterisk) can hear the called, but the called hears nothing. Since both machines are on public ip, what other problem can it be ? There's one configuration working : lynksys pap -sip-> asterisk server -sip-> quescom this way both sides can hear voice but with : lynksys pap connected to a switch -sip->

Am having a unique problem, calls received on my SPA942 seem to end after 15 seconds, but calls made from this device do not have this problem. For this device (when receiving calls) I get periodic "chan_sip.c set_destination: can't find address for host" I have set the "canreinvite=no" in the sip.conf. Does anyone have a sample entry from sip.conf for the Lynksys SPA 942

Wine FAQ says Wine is not an emulator, but in fact, it works like an emulator - it does not enhance Linux API, but simply creates a virtual Windows environment completely isolated from other parts of the system. * If one runs a .NET based program, Wine requires Win32 Mono to be installed under Wine, instead of Mono already installed in the system. * If a program tries to do html rendering, Wine

The Wine maintenance release 1.8.4 is now available. What's new in this release (see below for details): - Various bug fixes. - A few more cards added to the GPU description table. The source is available from the following locations: http://dl.winehq.org/wine/source/1.8/wine-1.8.4.tar.bz2 http://mirrors.ibiblio.org/wine/source/1.8/wine-1.8.4.tar.bz2 Binary packages for various

I just got the D-Link DWL-G520M PCI wireless card. I'm not interested in super-G or any other post-802.11b feature in particular; the reason I got it was because the marketing materials hinted that (at least some revision of it) had the Atheros chipset. It isn't recognized at all by ath(4) on 5.5. Here is the pciconf -lv section: none0@pci0:14:0: class=0x020000 card=0x3a681186

> On 15 Nov 2018, at 05:56, jiangyiwen <jiangyiwen at huawei.com> wrote: > > Hi Stefan, Michael, Jason and everyone, > > Several days ago, I discussed with jason about "Vsock over Virtio-net". > This idea has two advantages: > First, it can use many great features of virtio-net, like batching, > mergeable rx buffer and multiqueue, etc. > Second, it can

The Wine development release 5.17 is now available. What's new in this release (see below for details): - ADVAPI32 library converted to PE. - Beginnings of an NDIS network driver. - Still more restructuration of the console support. - Various bug fixes. The source is available from the following locations: https://dl.winehq.org/wine/source/5.x/wine-5.17.tar.xz

Hi Im a little perplexed by this situation I have centos 4.5 installed on 2 pcs - each with 2 network cards machine 1 eth0 Link encap:Ethernet HWaddr 00:14:2A:6B:C8:CC inet addr:10.54.7.2 Bcast:10.54.7.255 Mask:255.255.255.0 eth1 Link encap:Ethernet HWaddr 00:11:50:9B:A2:90 inet addr:10.54.0.2 Bcast:10.54.0.255 Mask:255.255.255.0 machine 2 eth0

FWIW: I order a lot of Dells. My boss is cheap. That being said, I *like* Dell, it's a very well designed box. It's been said many times that Dell does not innovate, instead they copy and improve and I firmly agree with the "improve" part - they are a dream to work on. Some things to watch out for with Dell: 1. They typically tack on a shipping charge of $139 Cdn (yes they

On Sun, Nov 08, 2015 at 10:15:31AM +0200, Yan Vugenfirer wrote: > > > On 06 Nov 2015, at 08:51, Vadim Rozenfeld <vrozenfe@redhat.com> wrote: > > > > On Thu, 2015-11-05 at 21:46 +0000, Richard W.M. Jones wrote: > >> On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: > >>> On Wed, 2015-10-28 at 14:53 +0300, Roman Kagan wrote: >

I know, I know... don't use the non-standard kernels unless you have to... BUT: I have a D-Link N150 USB card. Bus 001 Device 004: ID 0846:9030 NetGear, Inc. WNA1100 Wireless-N 150 [Atheros AR9271] This isn't supported in C5, but it is supported in newer kernels (ath9k_htc). So let's try NDISwrapper: # rpm -i kmod\-ndiswrapper\-1.56\-1.el5.elrepo.i686.rpm

I've been asked to assess the cost of implementing Asterisk with a single T1 line in one of our offices. I've had plenty of experience w/ TDM400 cards, but T1 is new for me so a couple of questions: 1) Will I need a digital or analogue interface card? I expect digital is the answer, but the Digium web site said something about analogue cards being able to support "provider T1

I went to the wiki and searched for both wireless and wifi and did not find anything related to wireless cards in CentOS. I think it would be stellar to have something similar to the laptops page but for wifi chipsets. I would propose it have three categories: FOSS chipsets Native driver but not FOSS chipsets (ie atheros via madwifi) NDIS Wrapper FSF has compiled somewhat of a list at